Hi,
I think prior to an initial release, I should do a little more debuging
... At the moment the tool is allmost unusable, if the person doesn't
know what he's dooing ;)
But I'll keep you posted ;)
Chris
Philippe Gauthier - INSERM SIRH schrieb:
Hi Christofer,
This really looks cool and convenient, feel free to share.
Regards,
Joerg Heinicke a écrit :
Hi Chris,
this sounds really interesting. Maybe you can send this mail to the
developer's mailing list as well.
And the end you probably have to issue an entry in Jira.
Thanks,
Joerg
On 24.04.2007 14:06, Christofer Dutz wrote:
I just finished my first version of a very very simple Eclipse
pulgin, which I can use for debuging my pipelines.
Usually I inserted a map:serialize type="xml" in the place I wanted
to have a closer look at. Unfortunately - especially when
dealing with ajax request - this breaks the application. The
LogTransformer produces so extremely ugly output, that I
didn't really want to use it.
My Eclipse Plugin is assigned to files with an ending of ".plog" and
opens a specialy adapted Xml Editor with a text
field for choosing a socket port and a button to start listening. As
soon as the Editor is listening, my CocoonPipelineDebuggerTranformer
can connect to it and send it it's content. I now can really have a
look at what is passing through the pipeline and the
really good thing is, that I can insert multiple debugs in one
pipeline and by this recieve multiple stages of one pipeline
execution. Multiple editor Insatnces can listen to individual ports
and every instance of the debug transformer can hereby
log to a different editor.
I found this really helpfull and would like to donate it, if anyone
is interested in this.
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
