From: Houston, Mike <HoustonM@genrad.com> - 2001-09-04 14:04:27
Yes, there are two class paths. But once you put bsh in the server path, it
seems to use that version, even if it is in the application class path. The
older BSH has to be in the server class path, so anything I do with the
application class path is basically ignored.
There is a note in the weblogic documentation on their use of class loaders
Seems pretty clear that anything on the server CLASSPATH will be loaded with
a different loader than our EJB support classes. I think we are basically
stuck between a rock and hard place right now.
Thanks for your input.
From: Pat [mailto:pat@...]
Sent: Monday, September 03, 2001 7:30 PM
To: Houston, Mike; beanshell-users@...
Subject: Re: [Beanshell-users] Classloader Problems with BSH in Weblogic
On Fri, Aug 31, 2001 at 03:38:52PM -0400, Houston, Mike wrote:
> I tried putting 1.2b1 in the CLASSPATH first, and Weblogic fails to
> I get an exception that doesn't have BSH in the stack trace:
> Exception raised:
> Error setting attribute Name to value mydomain for
> mydomain:Name=mydomain,Type=Domain - with nested exception:
I thought there were two class paths in weblogic: the server path and a
separate application classpath...
I will investigate this tomorrow and let the list know if I find a solution.
Hopefully Weblogic will upgrade to 1.2 with the next service pack.
Beanshell-users mailing list