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


 
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
DACS.JAVA(7)						  DACS Miscellaneous Information					      DACS.JAVA(7)

NAME
dacs.java - DACS Java support DESCRIPTION
This document describes support for Java provided by DACS. To enable Java support, DACS must be configured using the --enable-java flag. It may also be necessary to specify the location of the Java commands and include files. See dacs.install(7)[1]. Note Java support is currently very limited and should be considered experimental. It is currently only possible to call dacsauth(1)[2] and dacscheck(1)[3] using the Java Native Interface (JNI) provided. The command line arguments to both of these commands are exactly as documented in their manual pages. Each argument is passed as a String. The code is not thread-safe and is probably not suitable for being called many times within a particular process due to assumptions it makes about dynamic memory allocation. There are no immediate plans to improve or extend Java support. Using the existing capability to build the JNI layer, however, it should not be difficult for an experienced Java programmer to build upon the example Java code provided. With Java support enabled, building DACS will copy the JNI shared library and a .jar file to the library directory (default: /usr/local/dacs/lib), and the JNI include files to the include directory (default: /usr/local/dacs/include). The tools/java/jni distribution directory contains a simple script called javarun that demonstrates how to run dacsauth or dacscheck as a Java application. For example, to validate the Unix password for user somebody, run (as root): ./javarun dacsauth -m unix suff -user somebody -prompt DIAGNOSTICS
The return codes are as documented in the command's manual page. AUTHOR
Distributed Systems Software (www.dss.ca[4]) COPYING
Copyright2003-2012 Distributed Systems Software. See the LICENSE[5] file that accompanies the distribution for licensing information. NOTES
1. dacs.install(7) http://dacs.dss.ca/man/dacs.install.7.html 2. dacsauth(1) http://dacs.dss.ca/man/dacsauth.1.html 3. dacscheck(1) http://dacs.dss.ca/man/dacscheck.1.html 4. www.dss.ca http://www.dss.ca 5. LICENSE http://dacs.dss.ca/man/../misc/LICENSE DACS 1.4.27b 10/22/2012 DACS.JAVA(7)