When you embed an XML document in XPL, the namespace declarations visible at the level of the root element of that document are automatically added. This has benefits, for example you can define namespace prefix mappings once and for all at the level of the pipeline.
I can imagine how you may want an option to change this behavior, but currently your best bet is probably to store your document separately, e.g. status-event.xml:
<statusEvent> <status>submit</status> <dateTime/> </statusEvent>
And then:
<p:processor name="oxf:identity">
<p:input name="data" href="status-event.xml"/>
<p:output name="data" id="statusEvent"/>
</p:processor>But then, you may simply not want to use the identity processor and use a reference to status-event.xml everywhere.
-Erik
David Sinclair wrote: > Hi, > > When using the oxf:identity processor, is there a way to get rid of the > namespace declarations? > > I have this processor in my code: > > <p:processor name="oxf:identity"> > <p:input name="data"> > <statusEvent> > <status>submit</status> > <dateTime/> > </statusEvent> > </p:input> > <p:output name="data" id="statusEvent"/> > </p:processor> > > From which the output is (xmlns:oxf and xmlns:p come from the root > p:config element): > > <statusEvent xmlns:oxf="http://www.orbeon.com/oxf/processors"; > xmlns:p="http://www.orbeon.com/oxf/pipeline";> > <status>submit</status> > <dateTime/> > </statusEvent> > > I would rather not have the namespace decls. I can use xslt to get rid > of them, but it would be better of they werent inserted in the first > place... > > David Sinclair
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
orbeon-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/orbeon-user
