Jules - good tracking, but can we see some stack traces?
Does the Class.forName() call end up being passed to
the ContextLoader?
It should so long as it was called by a class also loaded
by the ContextLoader.
It may be that some classes are being loaded from the system
classpath, when they really should be on the context classpath.
If a bit of SOAP is on the system classpath, then it will be
loaded from there in preference to the contextloader (parents
always get a go first). But then those classes would not be
able to use Class.forName() to get classes that are only in the
context classloader.
cheers
PS.Does anybody want to be off the CC list on this?
Julian Gosnell wrote:
> I just tried it...
>
> Things are getting more interesting.
>
> The problem arises when SOAP tries to load
> javax.activation.DataSource from
> WEB-INF/lib/activation.jar
>
> It looks like this and 5 other classes from the same
> jar are all loaded successfully.
>
> Then a little bit later SOAP tries to load
> javax.activation.DataSource again using
> Class.forName() and the call throws a
> ClassDefNotFoundError...
>
>
> It looks like it should have found the class already
> loaded - but failed to.....
>
>
> Jules
>
>
> --- Julian Gosnell <[EMAIL PROTECTED]> wrote: >
> I'll try this this evening,
>
>>
>>Jules
>>
>> --- Greg Wilkins <[EMAIL PROTECTED]> wrote: >
>>
>>>The Jetty loader has not changed for a while.
>>>
>>>It either just uses the parent classloader (ie
>>>jboss's classloader) or
>>>if there is a WEB-INF/classes directory or jars in
>>>WEB-INF/lib, then
>>>it creates a derivation of URLClassLoader with the
>>>jboss loader as the
>>>parent.
>>>
>>>Has anybody tried running jetty with debug on
>>>
>>(maybe
>>
>>>verbose)
>>>so you can see the loader setup and each class as
>>>
>>it
>>
>>>is loaded.
>>>
>>>Debug can be controlled via JMX.
>>>
>>>cheers
>>>
>>>
>>>
>>>
>>>Julian Gosnell wrote:
>>>
>>>
>>>>Nothing has changed in Jetty between the last
>>>>
>>2.4
>>
>>>>release which worked and RH, which doesn't.
>>>>
>>>>The only changes made to the integration were
>>>>
>>made
>>
>>>>last nigh, after I had discovered the problem.
>>>>
>>>>The integration code retrieves a ClassLoader
>>>>
>>>passed by
>>>
>>>>the J2EEDeployer on the deployment thread and
>>>>
>>>passes
>>>
>>>>this into Jetty to use for the deployment.
>>>>
>>>>I've no idea what sort of changes have been made
>>>>
>>>to
>>>
>>>>this ClassLoader - perhaps Jetty is making some
>>>>assumptions about it that have changed
>>>>
>>underneath
>>
>>>>us....
>>>>
>>>>Jules
>>>>
>>>
>>>
>>>--
>>>Greg Wilkins<[EMAIL PROTECTED]> GB
>>>
>>Phone:
>>
>>>+44-(0)7092063462
>>>Mort Bay Consulting Australia and UK. Mbl
>>>
>>Phone:
>>
>>>+61-(0)4 17786631
>>>http://www.mortbay.com AU
>>>
>>Phone:
>>
>>>+61-(0)2 98107029
>>>
>>>
>>
> ____________________________________________________________
>
>>Do You Yahoo!?
>>Get your free @yahoo.co.uk address at
>>http://mail.yahoo.co.uk
>>or your free @yahoo.ie address at
>>http://mail.yahoo.ie
>>
>>_______________________________________________
>>Jboss-development mailing list
>>[EMAIL PROTECTED]
>>
>>
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
> ____________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
> or your free @yahoo.ie address at http://mail.yahoo.ie
>
--
Greg Wilkins<[EMAIL PROTECTED]> GB Phone: +44-(0)7092063462
Mort Bay Consulting Australia and UK. Mbl Phone: +61-(0)4 17786631
http://www.mortbay.com AU Phone: +61-(0)2 98107029
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
