I resolved my BCEL related class format errors. MyThat's great, I'll take one problem over two anyday :-)
model (SpiderModel) extends AbstractBaseModel within
my project. Both AbstractBaseModel and SpiderModel
were implementing the Model interface. Actually, my
hierarchy isn't that simple, but my error was caused
by multiple declarations of the same interface in the
hierarchy.
I'll do the same tracing through the proxy generation and try to see why it ignores proxy-type setting. I think you and I both need to look at that code again, so we can definitely say there is not something awry in your config.,/env., it is something universal. But, I haven't looked at that code since Fortress was integrated into Keel, so I don't have any immediate suggestions. More tomorrow.Of course, now that that's solved (thanks for all the help/suggestions by the way!), I need to determine why my container is using BCEL at all. Clearly, in my last snapshot of Keel head, BCEL wasn't active or else I would have faced this ClassFormatError previously.
Shash, I removed BCEL from my classpath and set
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...
Shash
http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
