Login  Register

XUpdate behavior

classic Classic list List threaded Threaded
4 messages Options Options
Embed post
Permalink
Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

XUpdate behavior

Duane Gran
20 posts
I'm using the XUpdate processor to reorder elements in an instance  
document.  The XUpdate command works to remove an element, but not to  
insert it.  I've confirmed that I have valid XPath statements, but  
I'm at a loss how to further test XUpdate outside of OPS.  Below is  
my processor code:

  <p:param name="instance" type="input" debug="debug-update-input"/>
   <p:param name="data" type="output" debug="debug-update-output"/>

   <p:processor name="oxf:xupdate">
     <p:input name="data" href="#instance"/>
     <p:input name="config">
       <!-- the following should update the instance document to move  
the subtitle
         above the second title.  -->
       <xu:modifications version="1.0">
         <xu:variable name="sub" select="/form/document/mods:mods/
mods:titleInfo/mods:subTitle"/>
         <xu:remove select="/form/document/mods:mods/mods:titleInfo/
mods:subTitle"/>
         <xu:insert-before select="/form/document/mods:mods/
mods:titleInfo/mods:title[2]">
           <xu:value-of select="$sub"/>
         </xu:insert-before>
       </xu:modifications>
     </p:input>

     <p:output name="document-info" ref="data"/>
   </p:processor>

This is based on the following XUpdate use case:

   http://www.xmldatabases.org/projects/XUpdate-UseCases/#22

Are there some limitations in the OPS implementation or am I doing  
something wrong here?  Many thanks in advance.

Duane



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

RE: XUpdate behavior

Ryan Puddephatt
769 posts
Duane,
        I have had problems with XUpdate as its not fully supported, Orbeon
are concentrating on W3C specs rather than new technologies! Try using XSLT
to do it!

Ryan Puddephatt
Web Developer
TFX Group
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP
 
* [hidden email]
( 01506 407 110
7  01506 407 108
 

>-----Original Message-----
>From: Duane Gran [mailto:[hidden email]]
>Sent: 31 December 2005 04:18
>To: [hidden email]
>Subject: [ops-users] XUpdate behavior
>
>I'm using the XUpdate processor to reorder elements in an instance
>document.  The XUpdate command works to remove an element, but not to
>insert it.  I've confirmed that I have valid XPath statements, but
>I'm at a loss how to further test XUpdate outside of OPS.  Below is
>my processor code:
>
>  <p:param name="instance" type="input" debug="debug-update-input"/>
>   <p:param name="data" type="output" debug="debug-update-output"/>
>
>   <p:processor name="oxf:xupdate">
>     <p:input name="data" href="#instance"/>
>     <p:input name="config">
>       <!-- the following should update the instance document to move
>the subtitle
>         above the second title.  -->
>       <xu:modifications version="1.0">
>         <xu:variable name="sub" select="/form/document/mods:mods/
>mods:titleInfo/mods:subTitle"/>
>         <xu:remove select="/form/document/mods:mods/mods:titleInfo/
>mods:subTitle"/>
>         <xu:insert-before select="/form/document/mods:mods/
>mods:titleInfo/mods:title[2]">
>           <xu:value-of select="$sub"/>
>         </xu:insert-before>
>       </xu:modifications>
>     </p:input>
>
>     <p:output name="document-info" ref="data"/>
>   </p:processor>
>
>This is based on the following XUpdate use case:
>
>   http://www.xmldatabases.org/projects/XUpdate-UseCases/#22
>
>Are there some limitations in the OPS implementation or am I doing
>something wrong here?  Many thanks in advance.
>
>Duane




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

Re: XUpdate behavior

Duane Gran-2
43 posts
Ryan,

I'm happy to report that by switching from xu:value-of to xu:copy-of  
it works just fine now.

Duane

On Jan 2, 2006, at 4:46 AM, Ryan Puddephatt wrote:

> Duane,
> I have had problems with XUpdate as its not fully supported, Orbeon
> are concentrating on W3C specs rather than new technologies! Try  
> using XSLT
> to do it!
>
> Ryan Puddephatt
> Web Developer
> TFX Group
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotand
> EH54 7DP
>
> * [hidden email]
> ( 01506 407 110
> 7  01506 407 108
>
>
>> -----Original Message-----
>> From: Duane Gran [mailto:[hidden email]]
>> Sent: 31 December 2005 04:18
>> To: [hidden email]
>> Subject: [ops-users] XUpdate behavior
>>
>> I'm using the XUpdate processor to reorder elements in an instance
>> document.  The XUpdate command works to remove an element, but not to
>> insert it.  I've confirmed that I have valid XPath statements, but
>> I'm at a loss how to further test XUpdate outside of OPS.  Below is
>> my processor code:
>>
>>  <p:param name="instance" type="input" debug="debug-update-input"/>
>>   <p:param name="data" type="output" debug="debug-update-output"/>
>>
>>   <p:processor name="oxf:xupdate">
>>     <p:input name="data" href="#instance"/>
>>     <p:input name="config">
>>       <!-- the following should update the instance document to move
>> the subtitle
>>         above the second title.  -->
>>       <xu:modifications version="1.0">
>>         <xu:variable name="sub" select="/form/document/mods:mods/
>> mods:titleInfo/mods:subTitle"/>
>>         <xu:remove select="/form/document/mods:mods/mods:titleInfo/
>> mods:subTitle"/>
>>         <xu:insert-before select="/form/document/mods:mods/
>> mods:titleInfo/mods:title[2]">
>>           <xu:value-of select="$sub"/>
>>         </xu:insert-before>
>>       </xu:modifications>
>>     </p:input>
>>
>>     <p:output name="document-info" ref="data"/>
>>   </p:processor>
>>
>> This is based on the following XUpdate use case:
>>
>>   http://www.xmldatabases.org/projects/XUpdate-UseCases/#22
>>
>> Are there some limitations in the OPS implementation or am I doing
>> something wrong here?  Many thanks in advance.
>>
>> Duane
>
>
>
>
> --
> You receive this message as a subscriber of the ops-
> [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
> wws



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

Re: XUpdate behavior

Erik Bruchez
Administrator
6632 posts
In reply to this post by Ryan Puddephatt
Ryan Puddephatt wrote:

 > I have had problems with XUpdate as its not fully supported, Orbeon
 > are concentrating on W3C specs rather than new technologies!

I just thought I would mention that XUpdate is not a new technology,
it's a dead one ;-)

-Erik




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws