Whether it's an approved thing to do, you could certainly do it (via JNI),
but your portability across EJB servers would of course be limited.
-Chris.
> -----Original Message-----
> From: Tom Valesky [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 23, 1999 3:17 AM
> To: [EMAIL PROTECTED]
> Subject: EJB and native methods; also, restrictions in spec
>
> Can an EJBean have native methods?
>
> I can't find an explicit prohibition in the spec, but it seems like
> allowing
> a bean to call native methods would open a rather large can of worms.
> On the other hand, I can see a couple of situations where it'd be handy
> to have this option (mainly in the MIS development environment, where
> you sometimes have to build interfaces to _truly_ oddball legacy
> systems).
>
> PS re: restrictions -- Section 16.4 says "this is only a partial list of
> restrictions that the enterprise developer must observe." Are there
> plans to release a canonical, complete, and exhaustive list of
> restrictions
> that EJB developers must observe?
>
> ==========================================================================
> =
> Tom Valesky -- [EMAIL PROTECTED]
> http://www.patriot.net/users/tvalesky
>
> ==========================================================================
> =
> 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".
