I still need more info as I don't know of any class loading issues in 3.2
and
using a TCL associated with the UnfiedLoaderRepository has visibility to all
classes except those loaded from wars. Show the stack trace of the context
where the CNFE occurs and if you have an example deployment create a
bug at sourceforge with the deployment attached.

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "Michael Bartmann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 20, 2002 12:57 PM
Subject: [JBoss-dev] serious classloading problem in Branch_3_2


> Hi Guys,
>
> sorry to disturb you with this question, you might qualify it as "non
> development"
> but as Marc suggested to me at the palma training I use Branch_3_2 to go
> live
> in a customer project....    ...and here I am, to put it simple:
>
> If there is a xxx.jar in server/project/lib which gets deployed (there is
a
> 61.xxx.jar in temp),
> is there any reason you cant get classes out of this xxx.jar loaded via
> a TCL
> (which uses UCL, verified by exception-trace)
>
> Is there
> 1) a bug I dont know about
> 2) a concept I dont know about, something I have to specify.
>
> If you need some more information: this is a recompiled borland jar-file
> with every
> Class.forName() replaced by Thread.currentThread()..blabla..loadClass().
> I even dont find any class using the management-console
> (jboss.system:service=serverinfo,
> displayInfoForClass()), and these ARE in lib and contain the classes I
> am looking
> for (double.checked, copy-pasted classnames).
>
> Help,
> Michael




-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to