cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Oliver <res1c...@verizon.net>
Subject Re: extending FOM? (was on cocoon-users: Re: Parsing Source into DOM in Flow)
Date Sun, 07 Dec 2003 18:07:31 GMT
Why not have processPipelineTo take a javax.xml.transform.Result instead 
of an OutputStream?

Guido Casper wrote:

>Did anyone else also feel the need to have something like
>processPipelineTo but getting a DOM or just an InputStream instead of
>just streaming it directly to another OutputStream?
>
>Guido
>
>
>Geoff Howard wrote:
>  
>
>>Upayavira wrote:
>>    
>>
>>>Maybe my last question was too specific.
>>>
>>>I'm trying to parse the contents of a source into a DOM in
>>>Flowscript, but am getting all sorts of errors. Can anyone provide a
>>>better way than this (which doesn't work)?
>>>
>>>var resolver =
>>>
>>>      
>>>
>cocoon.getComponent(Packages.org.apache.excalibur.source.SourceResolver.
>ROLE);
>  
>
>>>var source = resolver.resolveURI("blah.xml");
>>>var builder =
>>>
>>>      
>>>
>Packages.javax.xml.parsers.DocumentBuilderFactory.newInstance().newDocum
>entBuilder();
>  
>
>>I think I have observed that you cannot use the returned result of a
>>java method call ( newInstance() ) as a java object in flow (
>>.newDocumentBuilder() ).
>>
>>The workaround I have found is to separate the calls:
>>
>>var builderFactory =
>>Packages.javax.xml.parsers.DocumentBuilderFactory.newInstance();
>>
>>var builder = builderFactory.newDocumentBuilder();
>>
>>I don't know if this is a bug or not, don't know if it's only when
>>calling with Packages or not.  I also have not carefully confirmed
>>this.
>>
>>Finally, don't we have a convenience component to do this?
>>
>>Geoff
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>>For additional commands, e-mail: users-help@cocoon.apache.org
>>    
>>
>
>
>  
>



Mime
View raw message