Niall Litchfield allegedly said,on my timestamp of 4/06/2004 9:45 PM:
No, an EJB CANNOT be shared between applications in J2EE. Applications in an EJB container run in DIFFERENT JREs and CANNOT share an EJB!
Useful info thanks.
However, knowing a little bit about how these things are implemented (containers), I wouldn't be surprised if it was the norm rather than the exception. The way out of this conundrum according to the J2EE experts is to create a messaging interface...
Oh Nuno, you should know better. What you need is an EJB to do the app specific processing and a web service invoked via soap to handle all the interapp communications and business rules (J2EE and .Net handled ther). Put your business rules in a (probably serialized) web service, your app specific in your EJB, your data in a black box RDBMS, your security via an authentication appliance. naturally you'll need to do all of this with a RAC back end an app server data farm or even grid. That client server stuff that just worked is so 1990s.
all in XML, of course. And don't forget the XSL to interface J2EE and .Net: it's that easy...
-- Cheers Nuno Souto in sunny Sydney, Australia dbvision@xxxxxxxxxxxxxxx ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------
