I guess a configuration option would be helpful. I would do it myself but at this moment a have no time for such things so I prefer hacks which of course cannot be contributed to the project :). But at least I can provide you with some feedback which I think this project always needs.
Cand you tell me what is the intended release date ? Also what happend with nightly builds ? I think that for almost I week Fortress have no builds available on gump sites.
Regards, Peter.
Berin Loritsch wrote:
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.
The BCEL used is the one that is most recent (BCEL 5.1). We can fix the problem in a few different ways. One that I think would be most beneficial for you is to be able to declare which type of Proxy service you want.
We can change the lookupClass() method to use the String variant, which should fix classloader issues.
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.
Ok. I still have a limited amount of information to work with here. However would this help you?:
1) Add an attribute to the root config element in the .xconf which identifies the type of config we want such as "proxy-type".
2) proxy-type="none" uses a NoopWrapperObjectFactory (one that does nothing)
3) proxy-type="discover" (default) tries to use BCEL, and falls back to JDK 1.3
4) proxy-type="bcel" tries to use BCEL and fails if it is not present
5) proxy-type="java" uses JDK 1.3 proxies.
I can get that done within a day or two (unless someone beats me to it).
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
