Re: Fortress: BCEL llibrary problem

[Neeme Praks <ne...@apache.org>]

There was also a related issue (related to hibernate and jboss) with the 
Respository.lookupClass approach and I replaced it with a more 
embeddable-friendly approach couple of days ago. No more static 
methods... ;-)

Rgds,
Neeme

Peter Severin wrote:

> Hi all,
>
> I am progressing with less and less patience through fortress setup. I 
> have an impression that there are not many users using this project as 
> I see many problems that should be visible in any non trivial project. 
> I was given an impression that fortress is very close to a release 
> date but now I am starting to wonder. Anyway here is the problem:
>
> I am using hibernate which uses BCEL library through some third party 
> library. Having the bcel library in classpath activates 
> WrapperObjectFactory which uses it to generate wrapper proxy classes 
> at runtime. The problem is that I don't want to use wrapper classes 
> generation in the first place. I solved this by recompiling 
> ProxyManager class. Not very nice. OTOH I would'n mind to use 
> WrapperObjectFactory but it seems to use some old version of BCEL or 
> maybe new ?! (I wasn't able to find out which). The idea is that at 
> one point Repository.lookupClass(Class) is used. The latest BCEL 
> version has only Repository.lookupClass(String) method.
>
> I still hope that I will be able to use fortress in my project. 
> Meantime could somebody recommend a similar, simplier library ? I am 
> interested in a "services framework" which can provide an 
> infrustructure similar to EJB session beans.
>
> Regards,
> Peter.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org