We are looking very seriously at switching our app to an EJB architecture,
but the core functionality is provided by a C native library.
There have been suggestions to use "helper objects" which can use JNI, but
how does this work? how does the EJB talk to the helper object, where does
it live, etc?
I have read suggestions on this list to write a connector, see:
http://archives.java.sun.com/cgi-bin/wa?A2=ind9909&L=ejb-interest&F=&S=&P=24
948
but I'm thinking that this might be a problem since our C library needs to
keep some state.
I have also read a suggestion to change the permissions in the server.policy
file, see:
http://archives.java.sun.com/cgi-bin/wa?A2=ind9910&L=ejb-interest&P=R38058
We are looking at Allaire JRun 3.0 and BEA WebLogic, will either/both of
these allow us to change to policy to allow JNI calls?
Is this a problem? Should we not be using EJB at all then?? We can live
with doing something that is against the EJB spec as long as it will work
with our application server.
Thanks,
Paul
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
