Shash, I removed BCEL from my classpath and setI think I've got this licked in CVS, using issue #841137, update keel-server. We were copying the configuration tree, and needed to set the attributes of the top-level configuration item "keel". As a result, proxy-type was null, and was being set to the default value of "discover". I have tried "java" and "none" and both work OK.
proxy-type to "none". My startup failed with a
ClassNotFoundException referencing the BCEL library. I
traced through the Keel and Fortress Container setup
and the handling of "proxy-type" seemed appropriate. I
haven't found a reason for why it won't respond to
"none". I'll be happy to chase down any ideas or
leads...
I still can't explain the ClassNotFoundException you mention above. If proxy-type is indeed "bcel", then the container should throw a ConfigurationException if BCEL cannot be loaded by the classloader. If it is set to "discover", and BCEL is not present, it should use java.lang.Proxy. The only way I can see this happening is somehow it finds the "signature" class it is looking for, "org.apache.bcel.classfile.JavaClass", and thinks that BCEL is present, but then gets an exception later in some other BCEL class it is looking for. The other possibility is that BCEL is being asked to enhance a class that it itself cannot find. But you say BCEL is removed from classpath....I'm baffled. If you still see this, try setting some breakpoints in org.apache.avalon.factory.impl.factory.ProxyManager and the BCEL generators in same package.
Shash
http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
