orbeon xerces

>
>
> Sorry. My pevious question was misleading. The xerces-impl-orbeon jar file was in the private folder.
>
>
> Is there a way to see the diff made on that xerces jar somewhere ?
> The forms I had were working before and they don't since I updated to the new code.
>
>
>
> Thank you in advance,
>
> Niko,
>
>
> >
>

>
> George,
>
> I think what you want is the file-serializer:
>
> http://www.orbeon.com/ops/doc/processors-serializers#file-serializer
>
> This pipeline will write the xml to a file, also keep it cached if
> you expect to re-read it.
>
> --Hank
>
>
> On Oct 15, 2007, at 4:05 PM, [hidden email]
> <mailto:[hidden email]> wrote:
>
>>
>> I am new to the list and was not successful in searching the archives
>> for this issue. I am writing a web app to edit a Java properties file
>> that is part of a Java application. The app reads the XML
>> configuration file when starting, edits and adding items works but I
>> can't write the xml file back to its original location on the server.
>> I can write to and read from the exists database. Is there any way to
>> write the XML on the server?
>>
>> --
>> You receive this message as a subscriber of the [hidden email]
>> <mailto:[hidden email]> mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> OW2 mailing lists service home page: http://www.ow2.org/wws
>
> Hank Ratzesberger
> NEES@UCSB
> Institute for Crustal Studies,
> University of California, Santa Barbara
> 805-893-8042
>
>
>
>
>

> Hello orbeons,
>
> I think I could fix my problem if I could integrate a new version of
> the saxon-orbeon jar file, responsible for handling the namespaces
> (root cause of my exception)
>
> I got the saxon project to compile and tried to integrate it with
> orbeon but the two seems to be quite out of sync ? I mean the saxon
> module and the orbeon module in the cvs repository:
> - different constructors
> - different package naming
> - ...
>
> Is the idea to go for the standard saxon jar file or to integrate the
> custom made one ?
> Can I help in any way ?
>
> Niko,
>

> So I've nailed this down to my problem being related to:
>
> http://www.orbeon.com/ops/doc/home-changes-36#d6e50
>
> where it says improved schema validation:
>
> That seems to have an impact on some of the xpl code I have:
>
>                 <xsl:template match="/">
>                     <xsl:copy>
>                          <delegation:execute service="TMS_WS"
> operation="setOutput" xsl:version="2.0">
>                             <tms:taskId>
>                                 <xsl:value-of select="/*: output/@taskId"/>
>                             </tms:taskId>
>                             <tms:data>
>                                 <xsl:apply-templates select="*"/>
>                             </tms:data>
>                             <tms:participantToken>
>                                 <xsl:value-of
> select="/*:output/@participantToken"/>
>                             </tms:participantToken>
>                         </delegation:execute>
>                     </xsl:copy>
>                 </xsl:template>
>
>
> Copy chokes on the xsl:copy with that Namespace exception coming from xerces.
>
> The root of the cause is that <tms:data> should contain an xml frament
> that defines a root space for itself. So the namespace for that
> frament starts with:
>
> <output xmlns="http://www.example.com/MyRequestRequest" ... >
>
> It looks like the updated version of Saxon is forcing more schema
> compliance, in regards to the XSTL2.0 specifications.
>
> Any ideas or comments you could have on this ?
> So many emails, but really hope to get this moving forward.
>
> Nicolas,
>
>
> On 10/15/07, Nicolas Modrzyk <[hidden email]> wrote:
>>
>> Sorry. My pevious question was misleading. The xerces-impl-orbeon jar file was in the private folder.
>>
>>
>> Is there a way to see the diff made on that xerces jar somewhere ?
>> The forms I had were working before and they don't since I updated to the new code.
>>
>>
>>
>> Thank you in advance,
>>
>> Niko,
>>
>>

> Nicolas,
>
> The Schema validation improvements we did for XForms do not use Xerces
> at all, so I doubt those can explain the issue you are seeing. For
> XForms, we use MSV.
>
> Also, the version of Saxon we are using does not have any XML Schema
> support besides simple types. Saxon comes in two versions: one basic and
> one schema-aware. The latter is commercial.
>
> -Erik
>
> Nicolas Modrzyk wrote:
> > So I've nailed this down to my problem being related to:
> >
> > http://www.orbeon.com/ops/doc/home-changes-36#d6e50
> >
> > where it says improved schema validation:
> >
> > That seems to have an impact on some of the xpl code I have:
> >
> >                 <xsl:template match="/">
> >                     <xsl:copy>
> >                          <delegation:execute service="TMS_WS"
> > operation="setOutput" xsl:version="2.0">
> >                             <tms:taskId>
> >                                 <xsl:value-of select="/*: output/@taskId"/>
> >                             </tms:taskId>
> >                             <tms:data>
> >                                 <xsl:apply-templates select="*"/>
> >                             </tms:data>
> >                             <tms:participantToken>
> >                                 <xsl:value-of
> > select="/*:output/@participantToken"/>
> >                             </tms:participantToken>
> >                         </delegation:execute>
> >                     </xsl:copy>
> >                 </xsl:template>
> >
> >
> > Copy chokes on the xsl:copy with that Namespace exception coming from xerces.
> >
> > The root of the cause is that <tms:data> should contain an xml frament
> > that defines a root space for itself. So the namespace for that
> > frament starts with:
> >
> > <output xmlns="http://www.example.com/MyRequestRequest" ... >
> >
> > It looks like the updated version of Saxon is forcing more schema
> > compliance, in regards to the XSTL2.0 specifications.
> >
> > Any ideas or comments you could have on this ?
> > So many emails, but really hope to get this moving forward.
> >
> > Nicolas,
> >
> >
> > On 10/15/07, Nicolas Modrzyk <[hidden email]> wrote:
> >>
> >> Sorry. My pevious question was misleading. The xerces-impl-orbeon jar file was in the private folder.
> >>
> >>
> >> Is there a way to see the diff made on that xerces jar somewhere ?
> >> The forms I had were working before and they don't since I updated to the new code.
> >>
> >>
> >>
> >> Thank you in advance,
> >>
> >> Niko,
> >>
> >>
>
>
> --
> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> http://www.orbeon.com/
>
>
> --
> 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
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

> Hi Erik,
>
> Thank you for your support!
>
> The exception message I am seeing is:
>
> org.orbeon.saxon.dom.DOMWriter#namespace ():118
> org.orbeon.saxon.event.NamespaceReducer#namespace():97
> org.orbeon.saxon.event.NamespaceReducer#startElement():85
> org.orbeon.saxon.event.ReceivingContentHandler#startElement():217
>
> So I am trying to go to that specific class in the code.
> I indeed checked out the code in the saxon module in cvs but it seems
> to be out of sync with the current ops trunk ?
>
> For example, I get the following error:
> The import org.orbeon.saxon.event.ContentHandlerProxyLocator cannot be
> resolved        in orbeon/src/java/org/orbeon/oxf/processor/transformer/xslt    XSLTTransformer.java
>
> And indeed it is not in the current cvs code.
> Is there a specific CVS tag I should use ?
>
> Niko,
>
>
>
>
> On 10/16/07, Erik Bruchez <[hidden email]> wrote:
> > Nicolas,
> >
> > The Schema validation improvements we did for XForms do not use Xerces
> > at all, so I doubt those can explain the issue you are seeing. For
> > XForms, we use MSV.
> >
> > Also, the version of Saxon we are using does not have any XML Schema
> > support besides simple types. Saxon comes in two versions: one basic and
> > one schema-aware. The latter is commercial.
> >
> > -Erik
> >
> > Nicolas Modrzyk wrote:
> > > So I've nailed this down to my problem being related to:
> > >
> > > http://www.orbeon.com/ops/doc/home-changes-36#d6e50
> > >
> > > where it says improved schema validation:
> > >
> > > That seems to have an impact on some of the xpl code I have:
> > >
> > >                 <xsl:template match="/">
> > >                     <xsl:copy>
> > >                          <delegation:execute service="TMS_WS"
> > > operation="setOutput" xsl:version="2.0">
> > >                             <tms:taskId>
> > >                                 <xsl:value-of select="/*: output/@taskId"/>
> > >                             </tms:taskId>
> > >                             <tms:data>
> > >                                 <xsl:apply-templates select="*"/>
> > >                             </tms:data>
> > >                             <tms:participantToken>
> > >                                 <xsl:value-of
> > > select="/*:output/@participantToken"/>
> > >                             </tms:participantToken>
> > >                         </delegation:execute>
> > >                     </xsl:copy>
> > >                 </xsl:template>
> > >
> > >
> > > Copy chokes on the xsl:copy with that Namespace exception coming from xerces.
> > >
> > > The root of the cause is that <tms:data> should contain an xml frament
> > > that defines a root space for itself. So the namespace for that
> > > frament starts with:
> > >
> > > <output xmlns="http://www.example.com/MyRequestRequest" ... >
> > >
> > > It looks like the updated version of Saxon is forcing more schema
> > > compliance, in regards to the XSTL2.0 specifications.
> > >
> > > Any ideas or comments you could have on this ?
> > > So many emails, but really hope to get this moving forward.
> > >
> > > Nicolas,
> > >
> > >
> > > On 10/15/07, Nicolas Modrzyk <[hidden email]> wrote:
> > >>
> > >> Sorry. My pevious question was misleading. The xerces-impl-orbeon jar file was in the private folder.
> > >>
> > >>
> > >> Is there a way to see the diff made on that xerces jar somewhere ?
> > >> The forms I had were working before and they don't since I updated to the new code.
> > >>
> > >>
> > >>
> > >> Thank you in advance,
> > >>
> > >> Niko,
> > >>
> > >>
> >
> >
> > --
> > Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> > http://www.orbeon.com/
> >
> >
> > --
> > 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
> > OW2 mailing lists service home page: http://www.ow2.org/wws
> >
> >
>

> hello hello,
>
> I will try to reformulate my question.
>
> If I use the orbeon-saxon jar file that is in the lib folder, I can
> compile the orbeon code properly, and create the orbeon war file.
>
> If I create a new orbeon-saxon.jar file from the code (CVS HEAD -
> saxon module), I get a new orbeon-saxon jar file.
> If I include that jar file into the orbeon lib folder, then  the
> orbeon code doesn't compile properly anymore.
>
> So it'd be nice if I could find the matching code so I can compile
> both the saxon-orbeon jar file, and the orbeon war file properly.
>
> I would love to be able to get the code before the objectweb forge
> goes down tomorrow.
>
> Thank you for any pointers,
>
> Niko,
>
> On 10/16/07, Nicolas Modrzyk <[hidden email]> wrote:
>> Hi Erik,
>>
>> Thank you for your support!
>>
>> The exception message I am seeing is:
>>
>> org.orbeon.saxon.dom.DOMWriter#namespace ():118
>> org.orbeon.saxon.event.NamespaceReducer#namespace():97
>> org.orbeon.saxon.event.NamespaceReducer#startElement():85
>> org.orbeon.saxon.event.ReceivingContentHandler#startElement():217
>>
>> So I am trying to go to that specific class in the code.
>> I indeed checked out the code in the saxon module in cvs but it seems
>> to be out of sync with the current ops trunk ?
>>
>> For example, I get the following error:
>> The import org.orbeon.saxon.event.ContentHandlerProxyLocator cannot be
>> resolved        in orbeon/src/java/org/orbeon/oxf/processor/transformer/xslt    XSLTTransformer.java
>>
>> And indeed it is not in the current cvs code.
>> Is there a specific CVS tag I should use ?
>>
>> Niko,
>>
>>
>>
>>
>> On 10/16/07, Erik Bruchez <[hidden email]> wrote:
>>> Nicolas,
>>>
>>> The Schema validation improvements we did for XForms do not use Xerces
>>> at all, so I doubt those can explain the issue you are seeing. For
>>> XForms, we use MSV.
>>>
>>> Also, the version of Saxon we are using does not have any XML Schema
>>> support besides simple types. Saxon comes in two versions: one basic and
>>> one schema-aware. The latter is commercial.
>>>
>>> -Erik
>>>
>>> Nicolas Modrzyk wrote:
>>>> So I've nailed this down to my problem being related to:
>>>>
>>>> http://www.orbeon.com/ops/doc/home-changes-36#d6e50
>>>>
>>>> where it says improved schema validation:
>>>>
>>>> That seems to have an impact on some of the xpl code I have:
>>>>
>>>>                 <xsl:template match="/">
>>>>                     <xsl:copy>
>>>>                          <delegation:execute service="TMS_WS"
>>>> operation="setOutput" xsl:version="2.0">
>>>>                             <tms:taskId>
>>>>                                 <xsl:value-of select="/*: output/@taskId"/>
>>>>                             </tms:taskId>
>>>>                             <tms:data>
>>>>                                 <xsl:apply-templates select="*"/>
>>>>                             </tms:data>
>>>>                             <tms:participantToken>
>>>>                                 <xsl:value-of
>>>> select="/*:output/@participantToken"/>
>>>>                             </tms:participantToken>
>>>>                         </delegation:execute>
>>>>                     </xsl:copy>
>>>>                 </xsl:template>
>>>>
>>>>
>>>> Copy chokes on the xsl:copy with that Namespace exception coming from xerces.
>>>>
>>>> The root of the cause is that <tms:data> should contain an xml frament
>>>> that defines a root space for itself. So the namespace for that
>>>> frament starts with:
>>>>
>>>> <output xmlns="http://www.example.com/MyRequestRequest" ... >
>>>>
>>>> It looks like the updated version of Saxon is forcing more schema
>>>> compliance, in regards to the XSTL2.0 specifications.
>>>>
>>>> Any ideas or comments you could have on this ?
>>>> So many emails, but really hope to get this moving forward.
>>>>
>>>> Nicolas,
>>>>
>>>>
>>>> On 10/15/07, Nicolas Modrzyk <[hidden email]> wrote:
>>>>> Sorry. My pevious question was misleading. The xerces-impl-orbeon jar file was in the private folder.
>>>>>
>>>>>
>>>>> Is there a way to see the diff made on that xerces jar somewhere ?
>>>>> The forms I had were working before and they don't since I updated to the new code.
>>>>>
>>>>>
>>>>>
>>>>> Thank you in advance,
>>>>>
>>>>> Niko,
>>>>>
>>>>>
>>>
>>> --
>>> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
>>> http://www.orbeon.com/
>>>
>>>
>>> --
>>> 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
>>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>>
>>>
>>
>> ------------------------------------------------------------------------
>>

> Nicolas,
>
> It seems that I had a few changes to Saxon that I hadn't committed.
> That's done now. Please update from CVS and let us know if that fixes
> the build!
>
> Thanks,
>
> -Erik
>
> Nicolas Modrzyk wrote:
> > hello hello,
> >
> > I will try to reformulate my question.
> >
> > If I use the orbeon-saxon jar file that is in the lib folder, I can
> > compile the orbeon code properly, and create the orbeon war file.
> >
> > If I create a new orbeon-saxon.jar file from the code (CVS HEAD -
> > saxon module), I get a new orbeon-saxon jar file.
> > If I include that jar file into the orbeon lib folder, then  the
> > orbeon code doesn't compile properly anymore.
> >
> > So it'd be nice if I could find the matching code so I can compile
> > both the saxon-orbeon jar file, and the orbeon war file properly.
> >
> > I would love to be able to get the code before the objectweb forge
> > goes down tomorrow.
> >
> > Thank you for any pointers,
> >
> > Niko,
> >
> > On 10/16/07, Nicolas Modrzyk <[hidden email]> wrote:
> >> Hi Erik,
> >>
> >> Thank you for your support!
> >>
> >> The exception message I am seeing is:
> >>
> >> org.orbeon.saxon.dom.DOMWriter#namespace ():118
> >> org.orbeon.saxon.event.NamespaceReducer#namespace():97
> >> org.orbeon.saxon.event.NamespaceReducer#startElement():85
> >> org.orbeon.saxon.event.ReceivingContentHandler#startElement():217
> >>
> >> So I am trying to go to that specific class in the code.
> >> I indeed checked out the code in the saxon module in cvs but it seems
> >> to be out of sync with the current ops trunk ?
> >>
> >> For example, I get the following error:
> >> The import org.orbeon.saxon.event.ContentHandlerProxyLocator cannot be
> >> resolved        in orbeon/src/java/org/orbeon/oxf/processor/transformer/xslt    XSLTTransformer.java
> >>
> >> And indeed it is not in the current cvs code.
> >> Is there a specific CVS tag I should use ?
> >>
> >> Niko,
> >>
> >>
> >>
> >>
> >> On 10/16/07, Erik Bruchez <[hidden email]> wrote:
> >>> Nicolas,
> >>>
> >>> The Schema validation improvements we did for XForms do not use Xerces
> >>> at all, so I doubt those can explain the issue you are seeing. For
> >>> XForms, we use MSV.
> >>>
> >>> Also, the version of Saxon we are using does not have any XML Schema
> >>> support besides simple types. Saxon comes in two versions: one basic and
> >>> one schema-aware. The latter is commercial.
> >>>
> >>> -Erik
> >>>
> >>> Nicolas Modrzyk wrote:
> >>>> So I've nailed this down to my problem being related to:
> >>>>
> >>>> http://www.orbeon.com/ops/doc/home-changes-36#d6e50
> >>>>
> >>>> where it says improved schema validation:
> >>>>
> >>>> That seems to have an impact on some of the xpl code I have:
> >>>>
> >>>>                 <xsl:template match="/">
> >>>>                     <xsl:copy>
> >>>>                          <delegation:execute service="TMS_WS"
> >>>> operation="setOutput" xsl:version="2.0">
> >>>>                             <tms:taskId>
> >>>>                                 <xsl:value-of select="/*: output/@taskId"/>
> >>>>                             </tms:taskId>
> >>>>                             <tms:data>
> >>>>                                 <xsl:apply-templates select="*"/>
> >>>>                             </tms:data>
> >>>>                             <tms:participantToken>
> >>>>                                 <xsl:value-of
> >>>> select="/*:output/@participantToken"/>
> >>>>                             </tms:participantToken>
> >>>>                         </delegation:execute>
> >>>>                     </xsl:copy>
> >>>>                 </xsl:template>
> >>>>
> >>>>
> >>>> Copy chokes on the xsl:copy with that Namespace exception coming from xerces.
> >>>>
> >>>> The root of the cause is that <tms:data> should contain an xml frament
> >>>> that defines a root space for itself. So the namespace for that
> >>>> frament starts with:
> >>>>
> >>>> <output xmlns="http://www.example.com/MyRequestRequest" ... >
> >>>>
> >>>> It looks like the updated version of Saxon is forcing more schema
> >>>> compliance, in regards to the XSTL2.0 specifications.
> >>>>
> >>>> Any ideas or comments you could have on this ?
> >>>> So many emails, but really hope to get this moving forward.
> >>>>
> >>>> Nicolas,
> >>>>
> >>>>
> >>>> On 10/15/07, Nicolas Modrzyk <[hidden email]> wrote:
> >>>>> Sorry. My pevious question was misleading. The xerces-impl-orbeon jar file was in the private folder.
> >>>>>
> >>>>>
> >>>>> Is there a way to see the diff made on that xerces jar somewhere ?
> >>>>> The forms I had were working before and they don't since I updated to the new code.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Thank you in advance,
> >>>>>
> >>>>> Niko,
> >>>>>
> >>>>>
> >>>
> >>> --
> >>> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> >>> http://www.orbeon.com/
> >>>
> >>>
> >>> --
> >>> 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
> >>> OW2 mailing lists service home page: http://www.ow2.org/wws
> >>>
> >>>
> >>
> >> ------------------------------------------------------------------------
> >>
>
>
> --
> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> http://www.orbeon.com/
>
>
> --
> 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
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

> Hi,
>
> I have a problem with the submission of a specific piece of instance,
> specified in submission's "ref" attribut, and a field with constraint.
>
> Namely, if "ref" attribut is specified for a submission and other field has
> a constraint and constraint is not satisfied, submission proceeds anyway,
> like constraint is not applied at all.
>
> However, if "ref" does not exist, constraint is applied correctly and
> submission does not proceed if constraint is false.
>
> Is this an unexpected behaviour or I'm doing something wrong?
>
> In case that is unexpected one, I could work around and submit the whole
> instance (although I'd like to submit only specific part of instance).
>
> Attached, you can find the example that works in XForms sandbox. Try with
> and without submission's "ref" attribute.
>
> Tnx,
>
> Nikola
>
>
> ------------------------------------------------------------------------
>
> Test submission with REF attribut and constraint
>
> Value not correct (100) Submit
>

> Hi Erik,
>
> Thanks for the followup!!
>
> I have less mismatches (^ ^)/
> I am attaching the remaining ones I have.
>
> Thank you again for your time and help,
>
> Niko,
>
>
>
> On 10/17/07, Erik Bruchez <[hidden email]> wrote:
>> Nicolas,
>>
>> It seems that I had a few changes to Saxon that I hadn't committed.
>> That's done now. Please update from CVS and let us know if that fixes
>> the build!
>>
>> Thanks,
>>
>> -Erik
>>
>> Nicolas Modrzyk wrote:
>>> hello hello,
>>>
>>> I will try to reformulate my question.
>>>
>>> If I use the orbeon-saxon jar file that is in the lib folder, I can
>>> compile the orbeon code properly, and create the orbeon war file.
>>>
>>> If I create a new orbeon-saxon.jar file from the code (CVS HEAD -
>>> saxon module), I get a new orbeon-saxon jar file.
>>> If I include that jar file into the orbeon lib folder, then  the
>>> orbeon code doesn't compile properly anymore.
>>>
>>> So it'd be nice if I could find the matching code so I can compile
>>> both the saxon-orbeon jar file, and the orbeon war file properly.
>>>
>>> I would love to be able to get the code before the objectweb forge
>>> goes down tomorrow.
>>>
>>> Thank you for any pointers,
>>>
>>> Niko,
>>>
>>> On 10/16/07, Nicolas Modrzyk <[hidden email]> wrote:
>>>> Hi Erik,
>>>>
>>>> Thank you for your support!
>>>>
>>>> The exception message I am seeing is:
>>>>
>>>> org.orbeon.saxon.dom.DOMWriter#namespace ():118
>>>> org.orbeon.saxon.event.NamespaceReducer#namespace():97
>>>> org.orbeon.saxon.event.NamespaceReducer#startElement():85
>>>> org.orbeon.saxon.event.ReceivingContentHandler#startElement():217
>>>>
>>>> So I am trying to go to that specific class in the code.
>>>> I indeed checked out the code in the saxon module in cvs but it seems
>>>> to be out of sync with the current ops trunk ?
>>>>
>>>> For example, I get the following error:
>>>> The import org.orbeon.saxon.event.ContentHandlerProxyLocator cannot be
>>>> resolved        in orbeon/src/java/org/orbeon/oxf/processor/transformer/xslt    XSLTTransformer.java
>>>>
>>>> And indeed it is not in the current cvs code.
>>>> Is there a specific CVS tag I should use ?
>>>>
>>>> Niko,
>>>>
>>>>
>>>>
>>>>
>>>> On 10/16/07, Erik Bruchez <[hidden email]> wrote:
>>>>> Nicolas,
>>>>>
>>>>> The Schema validation improvements we did for XForms do not use Xerces
>>>>> at all, so I doubt those can explain the issue you are seeing. For
>>>>> XForms, we use MSV.
>>>>>
>>>>> Also, the version of Saxon we are using does not have any XML Schema
>>>>> support besides simple types. Saxon comes in two versions: one basic and
>>>>> one schema-aware. The latter is commercial.
>>>>>
>>>>> -Erik
>>>>>
>>>>> Nicolas Modrzyk wrote:
>>>>>> So I've nailed this down to my problem being related to:
>>>>>>
>>>>>> http://www.orbeon.com/ops/doc/home-changes-36#d6e50
>>>>>>
>>>>>> where it says improved schema validation:
>>>>>>
>>>>>> That seems to have an impact on some of the xpl code I have:
>>>>>>
>>>>>>                 <xsl:template match="/">
>>>>>>                     <xsl:copy>
>>>>>>                          <delegation:execute service="TMS_WS"
>>>>>> operation="setOutput" xsl:version="2.0">
>>>>>>                             <tms:taskId>
>>>>>>                                 <xsl:value-of select="/*: output/@taskId"/>
>>>>>>                             </tms:taskId>
>>>>>>                             <tms:data>
>>>>>>                                 <xsl:apply-templates select="*"/>
>>>>>>                             </tms:data>
>>>>>>                             <tms:participantToken>
>>>>>>                                 <xsl:value-of
>>>>>> select="/*:output/@participantToken"/>
>>>>>>                             </tms:participantToken>
>>>>>>                         </delegation:execute>
>>>>>>                     </xsl:copy>
>>>>>>                 </xsl:template>
>>>>>>
>>>>>>
>>>>>> Copy chokes on the xsl:copy with that Namespace exception coming from xerces.
>>>>>>
>>>>>> The root of the cause is that <tms:data> should contain an xml frament
>>>>>> that defines a root space for itself. So the namespace for that
>>>>>> frament starts with:
>>>>>>
>>>>>> <output xmlns="http://www.example.com/MyRequestRequest" ... >
>>>>>>
>>>>>> It looks like the updated version of Saxon is forcing more schema
>>>>>> compliance, in regards to the XSTL2.0 specifications.
>>>>>>
>>>>>> Any ideas or comments you could have on this ?
>>>>>> So many emails, but really hope to get this moving forward.
>>>>>>
>>>>>> Nicolas,
>>>>>>
>>>>>>
>>>>>> On 10/15/07, Nicolas Modrzyk <[hidden email]> wrote:
>>>>>>> Sorry. My pevious question was misleading. The xerces-impl-orbeon jar file was in the private folder.
>>>>>>>
>>>>>>>
>>>>>>> Is there a way to see the diff made on that xerces jar somewhere ?
>>>>>>> The forms I had were working before and they don't since I updated to the new code.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thank you in advance,
>>>>>>>
>>>>>>> Niko,
>>>>>>>
>>>>>>>
>>>>> --
>>>>> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
>>>>> http://www.orbeon.com/
>>>>>
>>>>>
>>>>> --
>>>>> 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
>>>>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>>>>
>>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>
>> --
>> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
>> http://www.orbeon.com/
>>
>>
>> --
>> 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
>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>
>>

> Hi Erik,
>
> Thanks for the followup!!
>
> I have less mismatches (^ ^)/
> I am attaching the remaining ones I have.
>
> Thank you again for your time and help,
>
> Niko,
>
>
>
> On 10/17/07, Erik Bruchez <[hidden email]> wrote:
> > Nicolas,
> >
> > It seems that I had a few changes to Saxon that I hadn't committed.
> > That's done now. Please update from CVS and let us know if that fixes
> > the build!
> >
> > Thanks,
> >
> > -Erik
> >
> > Nicolas Modrzyk wrote:
> > > hello hello,
> > >
> > > I will try to reformulate my question.
> > >
> > > If I use the orbeon-saxon jar file that is in the lib folder, I can
> > > compile the orbeon code properly, and create the orbeon war file.
> > >
> > > If I create a new orbeon-saxon.jar file from the code (CVS HEAD -
> > > saxon module), I get a new orbeon-saxon jar file.
> > > If I include that jar file into the orbeon lib folder, then  the
> > > orbeon code doesn't compile properly anymore.
> > >
> > > So it'd be nice if I could find the matching code so I can compile
> > > both the saxon-orbeon jar file, and the orbeon war file properly.
> > >
> > > I would love to be able to get the code before the objectweb forge
> > > goes down tomorrow.
> > >
> > > Thank you for any pointers,
> > >
> > > Niko,
> > >
> > > On 10/16/07, Nicolas Modrzyk <[hidden email]> wrote:
> > >> Hi Erik,
> > >>
> > >> Thank you for your support!
> > >>
> > >> The exception message I am seeing is:
> > >>
> > >> org.orbeon.saxon.dom.DOMWriter#namespace ():118
> > >> org.orbeon.saxon.event.NamespaceReducer#namespace():97
> > >> org.orbeon.saxon.event.NamespaceReducer#startElement():85
> > >> org.orbeon.saxon.event.ReceivingContentHandler#startElement():217
> > >>
> > >> So I am trying to go to that specific class in the code.
> > >> I indeed checked out the code in the saxon module in cvs but it seems
> > >> to be out of sync with the current ops trunk ?
> > >>
> > >> For example, I get the following error:
> > >> The import org.orbeon.saxon.event.ContentHandlerProxyLocator cannot be
> > >> resolved        in orbeon/src/java/org/orbeon/oxf/processor/transformer/xslt    XSLTTransformer.java
> > >>
> > >> And indeed it is not in the current cvs code.
> > >> Is there a specific CVS tag I should use ?
> > >>
> > >> Niko,
> > >>
> > >>
> > >>
> > >>
> > >> On 10/16/07, Erik Bruchez <[hidden email]> wrote:
> > >>> Nicolas,
> > >>>
> > >>> The Schema validation improvements we did for XForms do not use Xerces
> > >>> at all, so I doubt those can explain the issue you are seeing. For
> > >>> XForms, we use MSV.
> > >>>
> > >>> Also, the version of Saxon we are using does not have any XML Schema
> > >>> support besides simple types. Saxon comes in two versions: one basic and
> > >>> one schema-aware. The latter is commercial.
> > >>>
> > >>> -Erik
> > >>>
> > >>> Nicolas Modrzyk wrote:
> > >>>> So I've nailed this down to my problem being related to:
> > >>>>
> > >>>> http://www.orbeon.com/ops/doc/home-changes-36#d6e50
> > >>>>
> > >>>> where it says improved schema validation:
> > >>>>
> > >>>> That seems to have an impact on some of the xpl code I have:
> > >>>>
> > >>>>                 <xsl:template match="/">
> > >>>>                     <xsl:copy>
> > >>>>                          <delegation:execute service="TMS_WS"
> > >>>> operation="setOutput" xsl:version="2.0">
> > >>>>                             <tms:taskId>
> > >>>>                                 <xsl:value-of select="/*: output/@taskId"/>
> > >>>>                             </tms:taskId>
> > >>>>                             <tms:data>
> > >>>>                                 <xsl:apply-templates select="*"/>
> > >>>>                             </tms:data>
> > >>>>                             <tms:participantToken>
> > >>>>                                 <xsl:value-of
> > >>>> select="/*:output/@participantToken"/>
> > >>>>                             </tms:participantToken>
> > >>>>                         </delegation:execute>
> > >>>>                     </xsl:copy>
> > >>>>                 </xsl:template>
> > >>>>
> > >>>>
> > >>>> Copy chokes on the xsl:copy with that Namespace exception coming from xerces.
> > >>>>
> > >>>> The root of the cause is that <tms:data> should contain an xml frament
> > >>>> that defines a root space for itself. So the namespace for that
> > >>>> frament starts with:
> > >>>>
> > >>>> <output xmlns="http://www.example.com/MyRequestRequest" ... >
> > >>>>
> > >>>> It looks like the updated version of Saxon is forcing more schema
> > >>>> compliance, in regards to the XSTL2.0 specifications.
> > >>>>
> > >>>> Any ideas or comments you could have on this ?
> > >>>> So many emails, but really hope to get this moving forward.
> > >>>>
> > >>>> Nicolas,
> > >>>>
> > >>>>
> > >>>> On 10/15/07, Nicolas Modrzyk <[hidden email]> wrote:
> > >>>>> Sorry. My pevious question was misleading. The xerces-impl-orbeon jar file was in the private folder.
> > >>>>>
> > >>>>>
> > >>>>> Is there a way to see the diff made on that xerces jar somewhere ?
> > >>>>> The forms I had were working before and they don't since I updated to the new code.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Thank you in advance,
> > >>>>>
> > >>>>> Niko,
> > >>>>>
> > >>>>>
> > >>>
> > >>> --
> > >>> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> > >>> http://www.orbeon.com/
> > >>>
> > >>>
> > >>> --
> > >>> 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
> > >>> OW2 mailing lists service home page: http://www.ow2.org/wws
> > >>>
> > >>>
> > >>
> > >> ------------------------------------------------------------------------
> > >>
> >
> >
> > --
> > Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> > http://www.orbeon.com/
> >
> >
> > --
> > 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
> > OW2 mailing lists service home page: http://www.ow2.org/wws
> >
> >
>
>

> Nikolas,
>
> I am not sure why you are getting these errors. It seems that everything
> is committed now. What JDK are you using to compile?
>
> -Erik
>
> Nicolas Modrzyk wrote:
> > Hi Erik,
> >
> > Thanks for the followup!!
> >
> > I have less mismatches (^ ^)/
> > I am attaching the remaining ones I have.
> >
> > Thank you again for your time and help,
> >
> > Niko,
> >
> >
> >
> > On 10/17/07, Erik Bruchez <[hidden email]> wrote:
> >> Nicolas,
> >>
> >> It seems that I had a few changes to Saxon that I hadn't committed.
> >> That's done now. Please update from CVS and let us know if that fixes
> >> the build!
> >>
> >> Thanks,
> >>
> >> -Erik
> >>
> >> Nicolas Modrzyk wrote:
> >>> hello hello,
> >>>
> >>> I will try to reformulate my question.
> >>>
> >>> If I use the orbeon-saxon jar file that is in the lib folder, I can
> >>> compile the orbeon code properly, and create the orbeon war file.
> >>>
> >>> If I create a new orbeon-saxon.jar file from the code (CVS HEAD -
> >>> saxon module), I get a new orbeon-saxon jar file.
> >>> If I include that jar file into the orbeon lib folder, then  the
> >>> orbeon code doesn't compile properly anymore.
> >>>
> >>> So it'd be nice if I could find the matching code so I can compile
> >>> both the saxon-orbeon jar file, and the orbeon war file properly.
> >>>
> >>> I would love to be able to get the code before the objectweb forge
> >>> goes down tomorrow.
> >>>
> >>> Thank you for any pointers,
> >>>
> >>> Niko,
> >>>
> >>> On 10/16/07, Nicolas Modrzyk <[hidden email]> wrote:
> >>>> Hi Erik,
> >>>>
> >>>> Thank you for your support!
> >>>>
> >>>> The exception message I am seeing is:
> >>>>
> >>>> org.orbeon.saxon.dom.DOMWriter#namespace ():118
> >>>> org.orbeon.saxon.event.NamespaceReducer#namespace():97
> >>>> org.orbeon.saxon.event.NamespaceReducer#startElement():85
> >>>> org.orbeon.saxon.event.ReceivingContentHandler#startElement():217
> >>>>
> >>>> So I am trying to go to that specific class in the code.
> >>>> I indeed checked out the code in the saxon module in cvs but it seems
> >>>> to be out of sync with the current ops trunk ?
> >>>>
> >>>> For example, I get the following error:
> >>>> The import org.orbeon.saxon.event.ContentHandlerProxyLocator cannot be
> >>>> resolved        in orbeon/src/java/org/orbeon/oxf/processor/transformer/xslt    XSLTTransformer.java
> >>>>
> >>>> And indeed it is not in the current cvs code.
> >>>> Is there a specific CVS tag I should use ?
> >>>>
> >>>> Niko,
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On 10/16/07, Erik Bruchez <[hidden email]> wrote:
> >>>>> Nicolas,
> >>>>>
> >>>>> The Schema validation improvements we did for XForms do not use Xerces
> >>>>> at all, so I doubt those can explain the issue you are seeing. For
> >>>>> XForms, we use MSV.
> >>>>>
> >>>>> Also, the version of Saxon we are using does not have any XML Schema
> >>>>> support besides simple types. Saxon comes in two versions: one basic and
> >>>>> one schema-aware. The latter is commercial.
> >>>>>
> >>>>> -Erik
> >>>>>
> >>>>> Nicolas Modrzyk wrote:
> >>>>>> So I've nailed this down to my problem being related to:
> >>>>>>
> >>>>>> http://www.orbeon.com/ops/doc/home-changes-36#d6e50
> >>>>>>
> >>>>>> where it says improved schema validation:
> >>>>>>
> >>>>>> That seems to have an impact on some of the xpl code I have:
> >>>>>>
> >>>>>>                 <xsl:template match="/">
> >>>>>>                     <xsl:copy>
> >>>>>>                          <delegation:execute service="TMS_WS"
> >>>>>> operation="setOutput" xsl:version="2.0">
> >>>>>>                             <tms:taskId>
> >>>>>>                                 <xsl:value-of select="/*: output/@taskId"/>
> >>>>>>                             </tms:taskId>
> >>>>>>                             <tms:data>
> >>>>>>                                 <xsl:apply-templates select="*"/>
> >>>>>>                             </tms:data>
> >>>>>>                             <tms:participantToken>
> >>>>>>                                 <xsl:value-of
> >>>>>> select="/*:output/@participantToken"/>
> >>>>>>                             </tms:participantToken>
> >>>>>>                         </delegation:execute>
> >>>>>>                     </xsl:copy>
> >>>>>>                 </xsl:template>
> >>>>>>
> >>>>>>
> >>>>>> Copy chokes on the xsl:copy with that Namespace exception coming from xerces.
> >>>>>>
> >>>>>> The root of the cause is that <tms:data> should contain an xml frament
> >>>>>> that defines a root space for itself. So the namespace for that
> >>>>>> frament starts with:
> >>>>>>
> >>>>>> <output xmlns="http://www.example.com/MyRequestRequest" ... >
> >>>>>>
> >>>>>> It looks like the updated version of Saxon is forcing more schema
> >>>>>> compliance, in regards to the XSTL2.0 specifications.
> >>>>>>
> >>>>>> Any ideas or comments you could have on this ?
> >>>>>> So many emails, but really hope to get this moving forward.
> >>>>>>
> >>>>>> Nicolas,
> >>>>>>
> >>>>>>
> >>>>>> On 10/15/07, Nicolas Modrzyk <[hidden email]> wrote:
> >>>>>>> Sorry. My pevious question was misleading. The xerces-impl-orbeon jar file was in the private folder.
> >>>>>>>
> >>>>>>>
> >>>>>>> Is there a way to see the diff made on that xerces jar somewhere ?
> >>>>>>> The forms I had were working before and they don't since I updated to the new code.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Thank you in advance,
> >>>>>>>
> >>>>>>> Niko,
> >>>>>>>
> >>>>>>>
> >>>>> --
> >>>>> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> >>>>> http://www.orbeon.com/
> >>>>>
> >>>>>
> >>>>> --
> >>>>> 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
> >>>>> OW2 mailing lists service home page: http://www.ow2.org/wws
> >>>>>
> >>>>>
> >>>> ------------------------------------------------------------------------
> >>>>
> >>
> >> --
> >> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> >> http://www.orbeon.com/
> >>
> >>
> >> --
> >> 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
> >> OW2 mailing lists service home page: http://www.ow2.org/wws
> >>
> >>
>
>
> --
> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> http://www.orbeon.com/
>
>
> --
> 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
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

> Nikola,
>
> Good catch! It seems that we are doing something in the wrong order then
> extracting and validating nodes during submission.
>
> I can't enter a bug right now because the OW2 servers are being migrated
> today, but I will as soon as the servers are back up.
>
> -Erik
>
> Nikola Radic wrote:
> > Hi,
> >
> > I have a problem with the submission of a specific piece of instance,
> > specified in submission's "ref" attribut, and a field with constraint.
> >
> > Namely, if "ref" attribut is specified for a submission and other field

> > like constraint is not applied at all.
> >
> > However, if "ref" does not exist, constraint is applied correctly and
> > submission does not proceed if constraint is false.
> >
> > Is this an unexpected behaviour or I'm doing something wrong?
> >
> > In case that is unexpected one, I could work around and submit the whole
> > instance (although I'd like to submit only specific part of instance).
> >
> > Attached, you can find the example that works in XForms sandbox. Try

> > and without submission's "ref" attribute.
> >
> > Tnx,
> >
> > Nikola
> >
> >
> > ------------------------------------------------------------------------
> >
> > Test submission with REF attribut and constraint
> >
> > Value not correct (100) Submit
> >
>
>
> --
> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> http://www.orbeon.com/
>