Deploying EAR

[Aaron Abraham]

Hi,
We have a situation where we need to deploy multiple modules to the 9iAS application server. These modules will have different development cycles, and will need independent deployments (without having to do regression testing for all when deploying one).
A user can browse from one module to another, keeping session information, so I cannot advocate different EAR files for each. Additionally, we use local EJB's between the modules, so different EARs is definitely out.
On the other hand, if I put different JARs in the same EAR, and different WAR files, will this have any other drawbacks?
Can anyone please help me out on what I can do on this?
Regards
Aaron

[syed mraza]

Hi
i dont see any reason y u cant use the different ear files ( assuming they r on the same JVM ) i have been using the different applications in differnt ear files (sitting in same JVM) who use each other's local interfaces. and for the same session we are using SSO.
We faced problems during testing when different JAR ( having entity beans ) were accessing same database.
Raza

[Aaron Abraham]

Hi,
Thanks for the reply, but as per the concept, the web context will be different across EAR files. So, session information will not be carried across EAR's. Isn't this causing you a problem in your application?
Also, the local interfaces should be inaccessible outside an EAR, since you can only call one from an EJB in an EAR,... or does Oracle give a way around this?
I'm not clear why having multiple EJB's in different JAR's would have an issue with accessing the database. So long as the datasource is specified in the application server, this should run. Am I missing getting your situation correctly?
Regards
Aaron