cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christofer Dutz" <>
Subject AW: Problems with JavaFlow
Date Sat, 10 Jan 2009 15:54:57 GMT

At first I decided to completely abandon BCEL Instrumentation, since if it's
deprecated now, I can't see the sense of artificially keeping it alive :-)

I finally managed to solve some of the major problems I was having:
1. as soon as I have my "cocoon-javaflow-maven-plugin" and the
"cocoon-maven-plugin" in my pom, the default cocoon-plugin freezes up.
2. I had to dynamically add the current "target/classes" to the plug-ins
classpath, in order to make the ASM stuff work.
3. Implement the pattern-matching to control which classes to instrument
(currently all are instrumented)

I am not really satisfied with my solution of (1) ... since it involved
simply inserting my new plugin in the "generate-test-sources" phase, which
is not very pretty. I'm not quite sure, why the cocoon plug-in freezes ...
maybe someone on this list has an idea.
I solved number 2 by creating a URLClassLoader and inserting it.
As soon as I have issue 3 finished, I'll zip the project up and send it to


-----Urspr√ľngliche Nachricht-----
Von: Christofer Dutz [] 
Gesendet: Montag, 5. Januar 2009 10:48
Betreff: AW: Problems with JavaFlow

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.


-----Urspr√ľngliche Nachricht-----
Von: [] Im Auftrag von Torsten Curdt
Gesendet: Montag, 5. Januar 2009 09:47
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
> 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
> 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.


View raw message