Re: Deploying components common to EJB-tier and WEB-tier

2002-03-09 Thread Bill Winspur
I have been putting the shared classes in an extension that I build into both the ear and the war. - Original Message - From: "Sanjay Kumar Pandey" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Tuesday, March 05, 2002 10:27 PM Subject: Deploying components common to EJ

Re: Deploying components common to EJB-tier and WEB-tier

2002-03-06 Thread Stephen Davidson
Hi Sanjay. I am using Ear files, so I put common components in a jar file (which I call common.jar), which is in the ear file. Than in the war(s) and jar(s) of the ear file, I specify the common.jar file in the manifest file as Ram suggested. -Steve Ramamurthy K wrote: > Hi Sanjay >There

Re: Deploying components common to EJB-tier and WEB-tier

2002-03-06 Thread Eric Hodges
Sun provides a manifest classpath mechanism for sharing components within an EAR. I don't know if Orion supports it yet, though. If not, you can include the components in both the EJB JAR and the WAR. - Original Message - From: "Sanjay Kumar Pandey" <[EMAIL PROTECTED]> To: "Orion-Inter

Re: Deploying components common to EJB-tier and WEB-tier

2002-03-06 Thread Mike Cannon-Brookes
The easiest way to do this is just to put them inside one of your EJB JAR files - by the specification any classes in an EJB Jar file have to be visible to all other modules in the application. If you're looking for an Orion specific solution, you can just use the element in orion-application.xm

RE: Deploying components common to EJB-tier and WEB-tier

2002-03-06 Thread Ramamurthy K
Hi Sanjay There are few approaches. The best is use the apporach of Java Extension Mechanism if your application server support java 1.3. Place the common componets in your application directory and specify realtive path in your both manifest files of war and jar. with regards