xslt-generated xforms model

> I have a XSLT processor to dynamically-generate XForms model by
> combining "template" xml file that contains complete structure of the
> xforms:model element with a second much smaller XML file. This second
> file contains 2 branches - one gets inserted into xforms:instance
> section of the "template", the other is transformed into xforms:bind
> elements that also get inserted into the "template" XML.
>
> This setup works nicely, except all xpath expressions containing
> single quotes are escaped on the output of the XSLT processor like
> this:
>
> <xforms:bind nodeset="unitofmeasurecode"
> constraint="matches(.,&apos;[A-Z]2&apos;)" required="true()"/>
>
> The OPS XForms engine is interpreting such XPaths in a strange way -
> no error is thrown, but the xxforms:valid element on "affected" nodes
> is set to "false" even though the value of the node is ok.
>
> Is this a bug of OPS XForms engine, or did I miss something in the way
> I produce the XML with the XSLT processor?
>
> I am using OPS 3b3 with classic XForms
>
> A.
>

> I have a XSLT processor to dynamically-generate XForms model by
> combining "template" xml file that contains complete structure of the
> xforms:model element with a second much smaller XML file. This second
> file contains 2 branches - one gets inserted into xforms:instance
> section of the "template", the other is transformed into xforms:bind
> elements that also get inserted into the "template" XML.
>
> This setup works nicely, except all xpath expressions containing single
> quotes are escaped on the output of the XSLT processor like this:
>
> <xforms:bind nodeset="unitofmeasurecode"
> constraint="matches(.,&apos;[A-Z]2&apos;)" required="true()"/>
>
> The OPS XForms engine is interpreting such XPaths in a strange way - no
> error is thrown, but the xxforms:valid element on "affected" nodes is
> set to "false" even though the value of the node is ok.
>
> Is this a bug of OPS XForms engine, or did I miss something in the way
> I produce the XML with the XSLT processor?
>
> I am using OPS 3b3 with classic XForms
>
> A.
>
>
>
>
>
> --
> 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
>
>
>

> Hi Alexander,
>
> You might have some "&apos;" instead "'" in the XSLT output, but that
> should work just the same. I have tried but didn't manage to reproduce
> this problem. Would you have, or be able to create, a standalone
> example that we might run locally to reproduce this?
>
> Alex
>
> On 12/9/05, Alexander Zatko <[hidden email]> wrote:
>> I have a XSLT processor to dynamically-generate XForms model by
>> combining "template" xml file that contains complete structure of the
>> xforms:model element with a second much smaller XML file. This second
>> file contains 2 branches - one gets inserted into xforms:instance
>> section of the "template", the other is transformed into xforms:bind
>> elements that also get inserted into the "template" XML.
>>
>> This setup works nicely, except all xpath expressions containing
>> single
>> quotes are escaped on the output of the XSLT processor like this:
>>
>> <xforms:bind nodeset="unitofmeasurecode"
>> constraint="matches(.,&apos;[A-Z]2&apos;)" required="true()"/>
>>
>> The OPS XForms engine is interpreting such XPaths in a strange way -
>> no
>> error is thrown, but the xxforms:valid element on "affected" nodes is
>> set to "false" even though the value of the node is ok.
>>
>> Is this a bug of OPS XForms engine, or did I miss something in the way
>> I produce the XML with the XSLT processor?
>>
>> I am using OPS 3b3 with classic XForms
>>
>> A.
>>
>>
>>
>>
>>
>> --
>> 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
>>
>>
>>
>
> --
> Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/
>
>
> --
> 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

> Alex,
>
> Yeah - I tried to modify the bizdoc example to generate the model
> dynamically, but that modification did not reproduce the problem. I
> will try to simplify my code to bare minimum and see if I will find
> where the culprit might be. I could also pack the whole app and post it
> on my ftp server if you wanted to check it out.
>
> A.
>
> On Dec 12, 2005, at 8:04 PM, Alessandro Vernet wrote:
>
> > Hi Alexander,
> >
> > You might have some "&apos;" instead "'" in the XSLT output, but that
> > should work just the same. I have tried but didn't manage to reproduce
> > this problem. Would you have, or be able to create, a standalone
> > example that we might run locally to reproduce this?
> >
> > Alex
> >
> > On 12/9/05, Alexander Zatko <[hidden email]> wrote:
> >> I have a XSLT processor to dynamically-generate XForms model by
> >> combining "template" xml file that contains complete structure of the
> >> xforms:model element with a second much smaller XML file. This second
> >> file contains 2 branches - one gets inserted into xforms:instance
> >> section of the "template", the other is transformed into xforms:bind
> >> elements that also get inserted into the "template" XML.
> >>
> >> This setup works nicely, except all xpath expressions containing
> >> single
> >> quotes are escaped on the output of the XSLT processor like this:
> >>
> >> <xforms:bind nodeset="unitofmeasurecode"
> >> constraint="matches(.,&apos;[A-Z]2&apos;)" required="true()"/>
> >>
> >> The OPS XForms engine is interpreting such XPaths in a strange way -
> >> no
> >> error is thrown, but the xxforms:valid element on "affected" nodes is
> >> set to "false" even though the value of the node is ok.
> >>
> >> Is this a bug of OPS XForms engine, or did I miss something in the way
> >> I produce the XML with the XSLT processor?
> >>
> >> I am using OPS 3b3 with classic XForms
> >>
> >> A.
> >>
> >>
> >>
> >>
> >>
> >> --
> >> 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
> >>
> >>
> >>
> >
> > --
> > Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/
> >
> >
> > --
> > 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
>
>
>
>
>
> --
> 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
>
>
>

> Hi Alexander,
>
> If it is simple to run your entire application and you can share that
> with the list, then you can put it up somewhere on an FTP server and
> send the link here. Otherwise, it will be better to create a smaller
> example. I'll let you decide what makes more sense.
>
> Alex
>
> On 12/13/05, Alexander Zatko <[hidden email]> wrote:
>> Alex,
>>
>> Yeah - I tried to modify the bizdoc example to generate the model
>> dynamically, but that modification did not reproduce the problem. I
>> will try to simplify my code to bare minimum and see if I will find
>> where the culprit might be. I could also pack the whole app and post
>> it
>> on my ftp server if you wanted to check it out.
>>
>> A.
>>
>> On Dec 12, 2005, at 8:04 PM, Alessandro Vernet wrote:
>>
>>> Hi Alexander,
>>>
>>> You might have some "&apos;" instead "'" in the XSLT output, but that
>>> should work just the same. I have tried but didn't manage to
>>> reproduce
>>> this problem. Would you have, or be able to create, a standalone
>>> example that we might run locally to reproduce this?
>>>
>>> Alex
>>>
>>> On 12/9/05, Alexander Zatko <[hidden email]> wrote:
>>>> I have a XSLT processor to dynamically-generate XForms model by
>>>> combining "template" xml file that contains complete structure of
>>>> the
>>>> xforms:model element with a second much smaller XML file. This
>>>> second
>>>> file contains 2 branches - one gets inserted into xforms:instance
>>>> section of the "template", the other is transformed into xforms:bind
>>>> elements that also get inserted into the "template" XML.
>>>>
>>>> This setup works nicely, except all xpath expressions containing
>>>> single
>>>> quotes are escaped on the output of the XSLT processor like this:
>>>>
>>>> <xforms:bind nodeset="unitofmeasurecode"
>>>> constraint="matches(.,&apos;[A-Z]2&apos;)" required="true()"/>
>>>>
>>>> The OPS XForms engine is interpreting such XPaths in a strange way -
>>>> no
>>>> error is thrown, but the xxforms:valid element on "affected" nodes
>>>> is
>>>> set to "false" even though the value of the node is ok.
>>>>
>>>> Is this a bug of OPS XForms engine, or did I miss something in the
>>>> way
>>>> I produce the XML with the XSLT processor?
>>>>
>>>> I am using OPS 3b3 with classic XForms
>>>>
>>>> A.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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
>>>>
>>>>
>>>>
>>>
>>> --
>>> Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/
>>>
>>>
>>> --
>>> 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
>>
>>
>>
>>
>>
>> --
>> 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
>>
>>
>>
>
> --
> Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/
>
>
> --
> 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

> I figured it out. In my model, I have bunch of bind elements containing
> constraint attribute with matches() function that uses the regex
> "multiplier" pattern:
>
> <xforms:bind nodeset="upcode" constraint=matches(.,'[0-9]{2}')"
> required="true()"/>
>
> The affected <page> element in the page-flow file looks like this:
>
> <page id="new-asn" path-info="/new-asn" xforms="xforms-model.xpl"
> model="notice.xpl" view="notice-view.xsl">
>
> When I look at the output XML of the xforms-model.xpl, the attribute
> values of all bind elements are ok - the curly brackets are there.
> However, on the notice.xpl input, the curly brackets are gone - the bind
> element looks like this:
>
> <xforms:bind nodeset="upcode" constraint=matches(.,'[0-9]2')"
> required="true()"/>
>
> And the XForms engine flags the node "upcode" as xxforms:valid="false".
> When I change the regex pattern to '[0-9]'[0-9]' all is well. It looks
> like some process that I do not have any visibility into (XForms engine,
> or something that precedes it during execution) strips off the curly
> brackets.

> Alexander Zatko wrote:
>> I figured it out. In my model, I have bunch of bind elements
>> containing constraint attribute with matches() function that uses the
>> regex "multiplier" pattern:
>> <xforms:bind nodeset="upcode" constraint=matches(.,'[0-9]{2}')"
>> required="true()"/>
>> The affected <page> element in the page-flow file looks like this:
>> <page id="new-asn" path-info="/new-asn" xforms="xforms-model.xpl"
>> model="notice.xpl" view="notice-view.xsl">
>> When I look at the output XML of the xforms-model.xpl, the attribute
>> values of all bind elements are ok - the curly brackets are there.
>> However, on the notice.xpl input, the curly brackets are gone - the
>> bind element looks like this:
>> <xforms:bind nodeset="upcode" constraint=matches(.,'[0-9]2')"
>> required="true()"/>
>> And the XForms engine flags the node "upcode" as
>> xxforms:valid="false". When I change the regex pattern to
>> '[0-9]'[0-9]' all is well. It looks like some process that I do not
>> have any visibility into (XForms engine, or something that precedes
>> it during execution) strips off the curly brackets.
>
> Brackets in attributes are interpreted by XSLT as "attribute value
> templates". This is probably what is happening in your case. Check
> this out for more information:
>
>   http://www.w3.org/TR/xslt#attribute-value-templates
>   http://www.w3.org/TR/xslt20/#attribute-value-templates
>
> -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

> Erik,
>
> I know about AWTs, but I am not sure how do this info apply to the
> problem at hand.
>
> A.
>
> On Dec 16, 2005, at 4:06 PM, Erik Bruchez wrote:
>
>> Alexander Zatko wrote:
>>
>>> I figured it out. In my model, I have bunch of bind elements
>>> containing constraint attribute with matches() function that uses the
>>> regex "multiplier" pattern:
>>> <xforms:bind nodeset="upcode" constraint=matches(.,'[0-9]{2}')"
>>> required="true()"/>
>>> The affected <page> element in the page-flow file looks like this:
>>> <page id="new-asn" path-info="/new-asn" xforms="xforms-model.xpl"
>>> model="notice.xpl" view="notice-view.xsl">
>>> When I look at the output XML of the xforms-model.xpl, the attribute
>>> values of all bind elements are ok - the curly brackets are there.
>>> However, on the notice.xpl input, the curly brackets are gone - the
>>> bind element looks like this:
>>> <xforms:bind nodeset="upcode" constraint=matches(.,'[0-9]2')"
>>> required="true()"/>
>>> And the XForms engine flags the node "upcode" as
>>> xxforms:valid="false". When I change the regex pattern to
>>> '[0-9]'[0-9]' all is well. It looks like some process that I do not
>>> have any visibility into (XForms engine, or something that precedes
>>> it during execution) strips off the curly brackets.
>>
>>
>> Brackets in attributes are interpreted by XSLT as "attribute value
>> templates". This is probably what is happening in your case. Check
>> this out for more information:
>>
>>   http://www.w3.org/TR/xslt#attribute-value-templates
>>   http://www.w3.org/TR/xslt20/#attribute-value-templates
>>
>> -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
>
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> 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

> Does your XForms model have an xsl:version attribute on its root  
> element, or does it at any point in time go through an XSLT  
> transformation?
>
> -Erik
>
> Alexander Zatko wrote:
>> Erik,
>> I know about AWTs, but I am not sure how do this info apply to the  
>> problem at hand.
>> A.
>> On Dec 16, 2005, at 4:06 PM, Erik Bruchez wrote:
>>> Alexander Zatko wrote:
>>>
>>>> I figured it out. In my model, I have bunch of bind elements  
>>>> containing constraint attribute with matches() function that uses  
>>>> the regex "multiplier" pattern:
>>>> <xforms:bind nodeset="upcode" constraint=matches(.,'[0-9]{2}')"  
>>>> required="true()"/>
>>>> The affected <page> element in the page-flow file looks like this:
>>>> <page id="new-asn" path-info="/new-asn" xforms="xforms-model.xpl"  
>>>> model="notice.xpl" view="notice-view.xsl">
>>>> When I look at the output XML of the xforms-model.xpl, the  
>>>> attribute values of all bind elements are ok - the curly brackets  
>>>> are there. However, on the notice.xpl input, the curly brackets are  
>>>> gone - the bind element looks like this:
>>>> <xforms:bind nodeset="upcode" constraint=matches(.,'[0-9]2')"  
>>>> required="true()"/>
>>>> And the XForms engine flags the node "upcode" as  
>>>> xxforms:valid="false". When I change the regex pattern to  
>>>> '[0-9]'[0-9]' all is well. It looks like some process that I do not  
>>>> have any visibility into (XForms engine, or something that precedes  
>>>> it during execution) strips off the curly brackets.
>>>
>>>
>>> Brackets in attributes are interpreted by XSLT as "attribute value  
>>> templates". This is probably what is happening in your case. Check  
>>> this out for more information:
>>>
>>>   http://www.w3.org/TR/xslt#attribute-value-templates
>>>   http://www.w3.org/TR/xslt20/#attribute-value-templates
>>>
>>> -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
>> ----------------------------------------------------------------------
>> --
>> --
>> 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
>
>
> --
> 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