Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

j-Interop 2.04 (RC 8) (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News j-Interop 2.04 (RC 8) (Default branch)
# 1  
Old 01-27-2009
j-Interop 2.04 (RC 8) (Default branch)
j-Interop is a Java Open Source library (under LGPL) that implements the DCOM wire protocol (MSRPC) to enable development of Pure, Bi- Directional, Non-Native Java applications which can interoperate with any COM component. The implementation is itself purely in Java and does not use Java Native Interface (JNI) to provide COM access. This allows the library to be used from any Non-Windows platform. It comes with pre- implemented packages for automation. This includes support for IDispatch, ITypeInfo, and ITypeLib. For more flexibility (in the cases where automation is not supported), it provides an API set to directly invoke operations on a COM server. License: GNU Lesser General Public License (LGPL) Changes:
This drop fixes issues related to reference counting done by the library for each COM object. It is highly recommended to move to this release as soon as time permits. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Activex / Unix Interop

Hi, I need an ActiveX com component to raise events in a Unix program. Is it possible for Unix programs to interop with Win32 ActiveX exe? Thanks, Lee. (1 Reply)
Discussion started by: lee_b
1 Replies
Login or Register to Ask a Question

LEARN ABOUT MOJAVE

jstack

jstack(1)						      General Commands Manual							 jstack(1)

NAME

       jstack - stack trace

SYNOPSIS

       jstack [ option ] pid
       jstack [ option ] executable core
       jstack [ option ] [server-id@]remote-hostname-or-IP

DESCRIPTION

       jstack  prints  Java  stack traces of Java threads for a given Java process or core file or a remote debug server. For each Java frame, the
       full class name, method name, 'bci' (byte code index) and line number, if available, are printed. With the -m option,  jstack  prints  both
       Java  and  native frames of all threads along with the 'pc' (program counter). For each native frame, the closest native symbol to 'pc', if
       available, is printed. C++ mangled names are not demangled. To demangle C++ names, the output of this command may be piped to c++filt.

       NOTE - This utility is unsupported and may or may not be available in future versions of the J2SE SDK.  jstack is not  currently  available
       on Windows platforms or on the Linux Itanium platform.

PARAMETERS

       Options are mutually exclusive. Option, if used, should follow immediately after the command name.

       pid	      process  id  for which the stacktrace is to be printed.  The process must be a Java process. To get a list of Java processes
		      running on a machine, jps may be used.

       executable     Java executable from which the core dump was produced.

       core	      core file for which the stack trace is to be printed.

       remote-hostname-or-IP
		      remote debug server's (see jsadebugd) hostname or IP address.

       server-id      optional unique id, if multiple debug servers are running on the same remote host.

OPTIONS

       -m	      prints mixed mode (both Java and native C/C++ frames) stack trace.

       -h	      Prints a help message.

       -help	      Prints a help message.

SEE ALSO

       pstack(1) c++filt(1) jps(1) jsadebugd(1)

KNOWN BUGS

       Mixed mode stack trace, the -m option, does not work with the remote debug server.

								   13 June 2004 							 jstack(1)