On Mon, Dec 20, 2010 at 08:50, Pradeep Fernando <[email protected]> wrote:
> hi, comments in line,
>
> On Mon, Dec 20, 2010 at 1:18 AM, Andreas Veithen
> <[email protected]> wrote:
>> The only documentation we currently have is this:
>>
>> http://axis.apache.org/axis2/java/core/docs/app_server.html
>>
>> It doesn't mention the step that you describe. It would actually be
>> interesting to understand why this is required. Maybe you can avoid
>> this if you include a modules.list file as described in the
>> documentation.
>
> These are not my steps. rather they are documented in elsewhere. But
> the information is scattered i guess.
>
> we have to rename and copy the .mar files as  the application server
> only look for files in WEB-INF/classes , and only jar files in
> WEB-INF/lib.
>
> This behaviour documented in [1]
>
> Without the child first class loading, axis2 lib will have conflicts
> with web sphere jars. This behaviour is described for web logic, but
> for web sphere it is documented here. [2]
>
> [1] 
> http://www-01.ibm.com/support/docview.wss?rs=0&q1=axis2&q2=technote&uid=swg21315686&loc=en_US&cs=utf-8&cc=us&lang=en
> [2] 
> http://www-01.ibm.com/support/docview.wss?rs=0&q1=axis2&q2=technote&uid=swg21264548&loc=en_US&cs=utf-8&cc=us&lang=en

The fact that parent-last class loading is required is not very
surprising. This will probably be the case for many application
servers. I'm more surprised about [1]. I'm wondering if that is
related to the following bug in WAS 7.0:

http://www-01.ibm.com/support/docview.wss?uid=swg1PK86109

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. What was the WebSphere version that
you used?

> --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]

Reply via email to