I guess you missed some replys then. The spec clearly states that the EJB should not try to load native libraries (chapter 18 if i�m correct).
The container may load native libraries if it chooses to do so, which means, you should try to make the library available to the EJB using the contaner. That�s what JCA is for. A mailing list for Enterprise JavaBeans development <[EMAIL PROTECTED]> wrote on 03/10/2002 21:41:49: > As far as I can tell up until this point all responses to my question > have fallen into one of the following categories, sometimes mixing them. > > 1. "Yep, you are right, JNI is allowed, but I wouldn't do it > because...". > > My Response: Ok but I not interested in whether it is good idea. I am > only interested in whether the spec allows it. > > 2. "Nope it is not allowed, because..." > > My Response: These responses always go over one of the arguments that I > already refuted. No one has directly given any conflicting opinion on > the arguments I posted. > > 3. "...spec doesn't matter, because the container implementation might > not let you do it anyways...". > > My Response: That point does not matter because I am not interested in > whether a random container might or might not allow it. I am interested > in what the spec says. > > =========================================================================== > 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". ==========================================================================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".
