On Fri, 04 Jun 2004 19:49:15 +1000, Nuno Souto <dbvision@xxxxxxxxxxxxxxx> wrote: > You're not the only one... > > Couple of minor questions for your duh-veloper: when another application > sharing the same database has to use these rules in the app server, > where does it get them from? > > 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. > No, Java communications are slow as a dog. > No, .NOT is not any better in the same respect. 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. bitterly yours Niall Litchfield Oracle DBA http://www.niall.litchfield.dial.pipex.com ---------------------------------------------------------------- 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 -----------------------------------------------------------------