Hi Rajendra, I'm using ant.
I'm specifying .war properly in application.xml. I didn't understand which lib you are referring to for specifying the struts.jar. Might be that is the problem. Could you please explain it again ? Regards, Sourav -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 9:10 PM To: Struts Users Mailing List Subject: RE: Help needed in Struts deployment on Weblogic 8.1 the ear should know where the war is. Are you using ant ? Where you make your web app... make sure you include struts.jat in <lib dir tag . thanks -raj souravm <[EMAIL PROTECTED] To: "Struts Users Mailing List" <[EMAIL PROTECTED]> com> cc: Subject: RE: Help needed in Struts deployment on Weblogic 8.1 30/07/2003 08:46 PM Please respond to "Struts Users Mailing List" Hi Rajendra, The problem is - f I only deploy the .war of my application. It works fine. However, if I deploy the same .war within a .ear file, the error appears. Regards, Sourav -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 6:52 PM To: Struts Users Mailing List Subject: Re: Help needed in Struts deployment on Weblogic 8.1 This note might help: Appservers are not meant to make everything deployed on them accessible to the classpath of everything else. You still need to tell it where things lie. I'll assume that the servlet is in a WAR file, and the WAR file, in turn, is packaged in an EAR file, like this: theEar.ear |-- theEjb.jar |-- theWar.war |-- lib/libJar.jar theWar.war then, in order to find the EJB, needs to have a MANIFEST.MF file in it, with a Class-Path entry of theEjb.jar (the packaging as according to the relative locations in the EAR file). If you have a class that doesn't live in either the EJB jar or the WAR archive, then you should package that up into a jar file, and put it in the EAR (like lib/libJar.jar). Then, extend the Class-Path entry for theWar.war to include lib/libJar.jar. Likewise, if the EJB jar needs it, extend the Class-Path entry in it's MANIFEST.MF file. These issues are covered in the J2EE 1.3 spec, and the Java Extension Mechanism Spec. (J2EE 1.2 was meant to use this as well, but it was only implicit, not explicit.) thanks -raj "Navneet Saraogi" <[EMAIL PROTECTED] To: [EMAIL PROTECTED] nfosys.com> cc: Subject: Help needed in Struts deployment on Weblogic 8.1 30/07/2003 06:40 PM Please respond to "Struts Users Mailing List" Hi, We've a application that uses Struts 1.0 & Ejb's... This application is deployed on Weblogic 8.1 on a Windows XP machine... We've created an ear for the application and deployed it using the admin console... The familiar classNotFound issue has been hauting us for some time... Initially I placed the struts.jar in the WEB-INF\lib of the web module(web.war) and deployed only the web module... It was working fine till then... Then I added a ejb module(ejb.jar) and created a app.ear using these files... This is when the problem started... Initially the ActionForm class of the struts package was not getiing loaded... We moved the struts.jar from the web-inf\lib to applib folder of the ear... This issue was resolved but then the classes present in the .war files were not getting loaded... We've other jar files that were initially present in the WEB-INF\lib folder which were also not getting loaded... We then moved all the jar files to the outer most ear... Even then the issue was not resolved... We added the MANIFEST.MF file to the web.war & ejb.jar specifying the classpath for the jar files... No solution still... Next we added the classpath to the MANIFEST.MF file of the ear... Still no solution... We tried probably every possible permutation & combination of placing the jar files in the various modules but some classes never get loaded... What is the solution to this problem?? We are using a evaluation copy of Weblogic... Is it because of that??? If not, is it an inherent problem with struts 1.0 (in this case should we use struts 1.1??).... Any help in this matter would be welcomed... Navneet Saraogi --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
