"alesj" wrote :
| I think your solution to use SimpleThrowawayCL should work.
| But if we see any issues, I can add a copy method to the policy.
Yes, agreed.
The STCL is what should be used if the classloader itself doesn't provide a
"copy" method. As this is a generic feature, I'd be happ
"marius.bogoevici" wrote :
| Ales, also, can you provide an insight into the issue? I think that the
problem is caused by getThrowawayClassLoader() being called multiple times,
with the same policy (which causes the same classloader to be set repeatedly on
the policy), but I didn't see this
"alen_ribic" wrote :
| INFO [JBoss50ClassLoader] Policy doesn't have addTranslator, falling back
to ClassLoaderSystem.
|
| Being INFO and all I take it its normal operation?
|
Yes.
This only means you're using JBossCL pre 2.0.5.GA version,
as I only added translator per policy later on
I found the following log:
INFO [JBoss50ClassLoader] Policy doesn't have addTranslator, falling back to
ClassLoaderSystem.
Being INFO and all I take it its normal operation?
-Al
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231434#4231434
Reply to the pos
Thanks Marius. I did the latest build and it works now. I no longer get the
"Policy already has a classloader..." problem.
I will keep you posted if I get any related errors.
Thank you very much for your time to make the necessary chage.
-Alen
View the original post :
http://www.jboss.org/ind
Alen,
I made a small change to JBoss5LoadTimeWeaver, which should elliminate the
policy error.
Could you get the latest version and try again?
Thanks,
Marius
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231413#4231413
Reply to the post :
http://www.jbo
Alen,
I made a small change to JBoss5LoadTimeWeaver, which should elliminate the
policy error.
Could you get the latest version and try again?
Thanks,
Marius
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231408#4231408
Reply to the post :
http://www.jbo
Alen,
thanks for letting us know. I'll try to look into this.
Ales, also, can you provide an insight into the issue? I think that the
problem is caused by getThrowawayClassLoader() being called multiple times,
with the same policy (which causes the same classloader to be set repeatedly on
the
