Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [bpel-dev] Beautify XML for extension activities 
Hi Bob,
 
I added the InvokePipeletSerializer, the use case for InvokeServiceSerializer is the same. The new method DOMUtils#appendIndented just puts the nessecary whitespaces around the new element, depending on the indention of the previous / parent element.
 
The problem occurs when adding a pipelet to the pipeline. Up to now the result looked like:        
 
        <bpel:extensionActivity>
            <proc:invokePipelet name="InvokePipelet"><proc:pipelet class=""></proc:pipelet><proc:variables input="request" output="request"></proc:variables><proc:PipeletConfiguration></proc:PipeletConfiguration></proc:invokePipelet>
        </bpel:extensionActivity>
 
As I have no knowledge of the indention of "<bpel:extensionActivity>", the new result with indention applied is:
 
         <bpel:extensionActivity>
            <proc:invokePipelet name="InvokePipelet">
    <proc:pipelet class=""></proc:pipelet>
    <proc:variables input="request" output="request"></proc:variables>
    <proc:PipeletConfiguration></proc:PipeletConfiguration>
</proc:invokePipelet>
        </bpel:extensionActivity>
 
Further more: Even if I would know the indention, I couldn't add these whitespaces around "invokePipelet" as the BPELWriter expects no whitespaces before the <proc:invokePipelet> element. I could remove these whitespaces before returning, but that would be a workaround, especially as the need of just one element in the result is not documented in the BPELActivitySerializer.
 
So my request is to add the whitespaces of the current indention to the document fragment before calling BPELActivitySerializer#marshall (that way I get knowledge of the indention) and ignore these whitespaces afterwards.
 
Thanks,
Tobias Liefke

________________________________

Von: bpel-dev-bounces@xxxxxxxxxxx im Auftrag von Bob Brodt
Gesendet: Do 27.1.11 02:19
An: BPEL Designer project developer discussions.
Betreff: Re: [bpel-dev] Beautify XML for extension activities


Hi Tobias,

I'm trying to come up with a fix for this, but I'm not sure what exactly you're trying to do. Can you please send me your latest versions of the InvokePipeletSerializer and InvokeServiceSerializer classes that insert the text nodes?

Thanks!
_______________________________________
Robert ("Bob") Brodt
Senior Software Engineer, JBoss Riftsaw
JBoss by Red Hat


________________________________


	Hi Bob,
	 
	we are currently finishing our SMILA extensions for the BPEL designer. One of our goals is to beautify the generated XML. 
	 
	Now we have the following problem: When adding a new extension activity the serializer has no knowledge of the current indention - the "parentNode" parameter is just an empty document fragment. Additionally we can't indent our root element, as BPELWriter#extensionActivity2XML (line 1338) expects an element as first child of that fragment and throws a class cast for any (whitespace) text node.
	 
	Any suggestions?
	 
	Thanks,
	Tobias
	 

	_______________________________________________
	bpel-dev mailing list
	bpel-dev@xxxxxxxxxxx
	https://dev.eclipse.org/mailman/listinfo/bpel-dev

<<winmail.dat>>

Back to the top