> What was the WebSphere version that >> you used? > I used the WebSphere v 7. Which fix pack level?
We currently have Axis2 1.5.1 working with WAS V7 FP 11, I think was working OK with FP 9; don't know about earlier FPs, but always go with latest possible. We're currently still renaming the .mar files to .jar in the lib directly. I haven't tested this in a while, so if someone knows if that step is not still required please reply. Thanks, www -----Original Message----- From: Andreas Veithen [mailto:[email protected]] Sent: Tuesday, December 21, 2010 2:27 PM To: [email protected] Subject: Re: Is there a proper documentation on deploying AXIS2 in IBM Web Sphere On Tue, Dec 21, 2010 at 07:54, Pradeep Fernando <[email protected]> wrote: > Hi, > >> I've encountered this issue when trying to deploy an application that >> uses Plexus. The bug basically implies that all applications that >> create custom class loaders (and do some reasonably sophisticated >> stuff with them) will be broken. > The IBM documentation has defended it, by claiming that it is in the > recent servlet spec. (class loading lookup places). > If that so, I guess we have to fix it rather than documenting it. wdyt ? They actually say two things. One is that Axis2 versions prior to 1.4.1 had an issue because they were bundled with the servlet API JARs and this is in conflict with the servlet specs. This may be true (it is probably a matter of interpretation, but I'm not sure). But they also say that in order to deploy Axis2 1.4.1 (which has no problem with the servlet spec), you need to copy/rename the MAR files. I think that this issue could be caused by PK86109. If this can be confirmed, then we only need to document that Axis2 needs to be deployed with parent-last class loading and specify the minimum fix pack level (FP7 for WAS 7.0). > What was the WebSphere version that >> you used? > I used the WebSphere v 7. Which fix pack level? > --Pradeep > > -- > Pradeep Fernando. > http://pradeepfernando.blogspot.com/ > > --------------------------------------------------------------------- > 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] The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
