Hi Torsten, I am currently not @home, so I don't want wo piss off my customer by working on private stuff ;-) I'll try to sort out some small Issues with having both the javaflow and the cocoon plugin active at the same time and will send you a zip with the complete package. Switching to ASM sounds great. As I mentioned the javaflow guys switched to ASM as default a few months ago (unfortunately this is the time where JavaFlow stopped working for me.
Chris -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Torsten Curdt Gesendet: Montag, 5. Januar 2009 09:47 An: [email protected] Betreff: Re: Problems with JavaFlow Hey Chris > I have finished a working prototype of the Javaflow Maven plug-in. Where is it? 8-) > Still there has to be some beautifying to be done. One thing I noticed while > working on it was that BCEL seems to have been completely deprecated. Yeah, I would like to get rid of it - frankly speaking :) > Therefore I tried switching to ASM, but the switch to ASM doesn't seem to be > a easy as implied by the Ant-Task code. I'll have to manually add the Flow > classes to the classpath available to the plug-in. I guess it's just a > little more Maven-Learning for me to do first ... :-) Let me have a look. > Unfortunately even with an instrumented Invoker and all JavaFlow classes > instrumented, I still get the same error message. Thanks for your work. This is motivating. I'll clean up javaflow trunk and build a testcase of what is needed in Cocoon. And then we can take it from there. cheers -- Torsten
