Gents, the issue is due to the WLS 8.1 classloader not supporting nested archives. That is, a WAR file (archive) containing an AAR file (nested archive) fails to load because the classloader will not read into the AAR. The workaround, as you have both found, is to 'explode' the original war file to file file system. The result is that the AAR file is no longer nested, the classloader will read it.
Back to the original question, how to deploy an EAR? Upgrade the server to WLS 9.2, probably not the answer you want. Regards, Stephen "John Pfeifer" <[EMAIL PROTECTED]> 23/02/2007 12:10 PM Please respond to [email protected] To <[email protected]> cc Subject RE: [Axis2] Anything in the works to support Weblogic 8.1? I haven't tried that simply b/c I haven't had to at this point. I would guess that since the ear file can be staged as well that you should be able to do the same thing. I have seen the same problem that you had where the file name is part of the path. This results in an "Unknown" application type in weblogic and makes hot deployment difficult. Let me know if you get the ear working as I may be able to simplify my deployments by packaging several war files into a single ear. Jp4 -----Original Message----- From: Edison Aspert [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 4:38 PM To: [email protected] Subject: RE: [Axis2] Anything in the works to support Weblogic 8.1? Thanks John. It worked. My config.xml had something like this. <Application Name="axis2" Path="C:\Dev\Edx_PM Projects\workspace\axis2-1.1.1\dist\myapp.ear" StagedTargets="myserver" StagingMode="stage" TwoPhase="true"> <WebAppComponent Name="axis2" Targets="myserver" URI="axis2.war"/> </Application> Which didn't work. When I removed \myapp.ear from the path attribute, it worked. Is there a way to put axis2.war in a EAR and still deploy it? Thanks Aspert --- John Pfeifer <[EMAIL PROTECTED]> wrote: > I have been able to deploy axis2 in Weblogic 814 as > a war. That war is however exploded by weblogic > into the stage directory upon startup. I put the > war in the applications directory and weblogic takes > care of the rest. Sometimes you have to remove the > stage directory after a restart, but for the most > part hot deployments in dev have worked well. > > <Application Deployed="true" > > Name="pay-capture-gateway-web-service-container" > > Path="/home/jpfeifer/bea/weblogic814/testdomain/applications" > StagedTargets="testserver" > StagingMode="stage" TwoPhase="true"> > <WebAppComponent > > Name="pay-capture-gateway-web-service-container" > Targets="testserver" > URI="pay-capture-gateway-web-service-container.war"/> > </Application> > > I have found that the key is to set > StagingMode="stage". It will not work with > "nostage". > > Hope this helps. > > jp4 > -----Original Message----- > From: Edison Aspert [mailto:[EMAIL PROTECTED] > Sent: Thu 2/22/2007 2:06 PM > To: [email protected] > Subject: [Axis2] Anything in the works to support > Weblogic 8.1? > > Hello, > > Axis2 1.1 can be deployed in Weblogic 8.1 only as a > exploded deployment coz of the class loader issue in > WL81. > > Is there anything in the works so that the > deployment > process is the same across all app servers? > Something > like having the modules and services under > web-inf/lib > might fix this issue. Or even making it > configurable? > > Thanks > > Aspert > > > > ________________________________________________________________________ ____________ > Get your own web address. > Have a HUGE year through Yahoo! Small Business. > http://smallbusiness.yahoo.com/domains/?p=BESTDEAL > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > > ________________________________________________________________________ ____________ Don't get soaked. Take a quick peak at the forecast with the Yahoo! Search weather shortcut. http://tools.search.yahoo.com/shortcuts/#loc_weather --------------------------------------------------------------------- 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]
-- This message contains privileged and confidential information only for use by the intended recipient. If you are not the intended recipient of this message, you must not disseminate, copy or use it in any manner. If you have received this message in error, please advise the sender by reply e-mail. Please ensure all e-mail attachments are scanned for viruses prior to opening or using.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
