Select1 and repeat

> Hi all,
>
> I have a problem with the select1 control in a repeat loop.
>
> When a itemset is connected to the control I cannot use the repeat
> feature.
> Without there's no problem.
>
> See the attached file to see what I mean.
>
> Any hint ?
>
> Marc

> Hi all,
>
> I have a problem with the select1 control in a repeat loop.
>
> When a itemset is connected to the control I cannot use the repeat
> feature.
> Without there's no problem.
>
> See the attached file to see what I mean.
>
> Any hint ?
>
> Marc

> Erik,
>
> If you press the + button the XForms engine hangs.
>
> Marc
>
> -----Message d'origine-----
> De : Erik Bruchez [mailto:[hidden email]] De la part de Erik Bruchez
> Envoy? : mercredi 9 novembre 2005 16:55
> ? : [hidden email]
> Objet : Re: [ops-users] Select1 and repeat
>
> Marc,
>
> This seems to work for me with the latest code. See attached screenshot and updated version of your file (with just a couple of example values added and your itemset uncommented).
>
> Note that it works in the current online XForms sandbox as well:
>
>    http://www.orbeon.com/ops/goto-example/xforms-sandbox
>
> -Erik
>
> [hidden email] wrote:
>
>>Hi all,
>>
>>I have a problem with the select1 control in a repeat loop.
>>
>>When a itemset is connected to the control I cannot use the repeat
>>feature.
>>Without there's no problem.
>>
>>See the attached file to see what I mean.
>>
>>Any hint ?
>>
>>Marc
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> 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,
>
> If you press the + button the XForms engine hangs.
>
> Marc
>
> -----Message d'origine-----
> De : Erik Bruchez [mailto:[hidden email]] De la part de Erik Bruchez
> Envoyé : mercredi 9 novembre 2005 16:55
> À : [hidden email]
> Objet : Re: [ops-users] Select1 and repeat
>
> Marc,
>
> This seems to work for me with the latest code. See attached screenshot and updated version of your file (with just a couple of example values added and your itemset uncommented).
>
> Note that it works in the current online XForms sandbox as well:
>
>    http://www.orbeon.com/ops/goto-example/xforms-sandbox
>
> -Erik
>
> [hidden email] wrote:
> > Hi all,
> >
> > I have a problem with the select1 control in a repeat loop.
> >
> > When a itemset is connected to the control I cannot use the repeat
> > feature.
> > Without there's no problem.
> >
> > See the attached file to see what I mean.
> >
> > Any hint ?
> >
> > Marc
>
>
>
>
> --
> 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,
>
> If you press the + button the XForms engine hangs.
>
> Marc
>
> -----Message d'origine-----
> De : Erik Bruchez [mailto:[hidden email]] De la part de Erik
> Bruchez Envoyé : mercredi 9 novembre 2005 16:55 À :
> [hidden email] Objet : Re: [ops-users] Select1 and repeat
>
> Marc,
>
> This seems to work for me with the latest code. See attached screenshot and updated version of your file (with just a couple of example values added and your itemset uncommented).
>
> Note that it works in the current online XForms sandbox as well:
>
>    http://www.orbeon.com/ops/goto-example/xforms-sandbox
>
> -Erik
>
> [hidden email] wrote:
> > Hi all,
> >
> > I have a problem with the select1 control in a repeat loop.
> >
> > When a itemset is connected to the control I cannot use the repeat
> > feature.
> > Without there's no problem.
> >
> > See the attached file to see what I mean.
> >
> > Any hint ?
> >
> > Marc
>
>
>
>
> --
> 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
>
>
>

> Hello!
>
> I'm trying to use the Xinclude processor, to include dynamic content in
> my page.
>
> When the page loads, I get an error :
> Warning: Include operation failed, reverting to fallback. Resource error
> reading file as XML (href='input:dynamic-content'). Reason: unknown
> protocol: input
>
> I think it probably is "a small stupid thing" that I didn't do
> correctly, but I can't figure what.
>
> Any help, or exemple using Xinclude processor with dynamic content
> (other that the one on the orbeon site) would really be appreciated.
>
> The code for a simple exemple is found below. I also tried with a
> seperate "tampelate" file in which to include the dynamic content with
> no more success.
>
> I also tried to upgrade to the latest unstable version, with no more
> success (eclipse reports studio version 1.2.3.200509020246)
>
> Thanks for your help.
>
> Sébastien Noir
>
> File : modifyBug_view_pipe.xpl
>
> <p:config
>     xmlns:p="http://www.orbeon.com/oxf/pipeline"
>     xmlns:oxf="http://www.orbeon.com/oxf/processors"
>     xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>     xmlns:xdb="http://www.orbeon.org/oxf/xml/xmldb"
>     xmlns:my="http://www.epfl.ch/lamp/processors"
>     xmlns:xi="http://www.w3.org/2003/XInclude"
>     >
>
>     <p:param name="data" type="output"/>
>
>     <!-- Generate the users pop-up -->
>     <p:processor name="my:UsersPopUpValueGenerator">
>         <p:output name="mainoutput" id ="users"  />
>     </p:processor>
>
>     <p:processor name="oxf:xinclude">
>         <p:input name="dynamic-content" href="#users"/>
>         <p:input name="config">
>             <html><head><title>Test</title></head>
>                 <body>
>                     <h1>This is a inclusion test</h1>
>                     <!-- This is where the inclusion is performed -->
>                     <p>
>                        <xi:include href="input:dynamic-content"/>
>                     </p>
>                 </body>
>             </html>
>         </p:input>
>
>         <p:output name="data" id ="result" ref="data"/>
>
>     </p:processor>
> </p:config>
>
>
>
>
> --
> 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 Sebastien,
>
> My guess is that your <xi:include> is processed when the XPL file
> read, and in that context the "input:dynamic-content" cannot be
> resolved. Can you try to put the content of your HTML in a separate
> file and reference that file on the with the href attribute when
> calling the XInclude processor, e.g. <p:input name="config"
> href="your-file.xhtml"/>?
>
> Alex
>
> On 11/15/05, Sebastien Noir <[hidden email]> wrote:
>
>>Hello!
>>
>>I'm trying to use the Xinclude processor, to include dynamic content in
>>my page.
>>
>>When the page loads, I get an error :
>>Warning: Include operation failed, reverting to fallback. Resource error
>>reading file as XML (href='input:dynamic-content'). Reason: unknown
>>protocol: input
>>
>>I think it probably is "a small stupid thing" that I didn't do
>>correctly, but I can't figure what.
>>
>>Any help, or exemple using Xinclude processor with dynamic content
>>(other that the one on the orbeon site) would really be appreciated.
>>
>>The code for a simple exemple is found below. I also tried with a
>>seperate "tampelate" file in which to include the dynamic content with
>>no more success.
>>
>>I also tried to upgrade to the latest unstable version, with no more
>>success (eclipse reports studio version 1.2.3.200509020246)
>>
>>Thanks for your help.
>>
>>S?bastien Noir
>>
>>File : modifyBug_view_pipe.xpl
>>
>><p:config
>>    xmlns:p="http://www.orbeon.com/oxf/pipeline"
>>    xmlns:oxf="http://www.orbeon.com/oxf/processors"
>>    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>    xmlns:xdb="http://www.orbeon.org/oxf/xml/xmldb"
>>    xmlns:my="http://www.epfl.ch/lamp/processors"
>>    xmlns:xi="http://www.w3.org/2003/XInclude"
>>    >
>>
>>    <p:param name="data" type="output"/>
>>
>>    <!-- Generate the users pop-up -->
>>    <p:processor name="my:UsersPopUpValueGenerator">
>>        <p:output name="mainoutput" id ="users"  />
>>    </p:processor>
>>
>>    <p:processor name="oxf:xinclude">
>>        <p:input name="dynamic-content" href="#users"/>
>>        <p:input name="config">
>>            <html><head><title>Test</title></head>
>>                <body>
>>                    <h1>This is a inclusion test</h1>
>>                    <!-- This is where the inclusion is performed -->
>>                    <p>
>>                       <xi:include href="input:dynamic-content"/>
>>                    </p>
>>                </body>
>>            </html>
>>        </p:input>
>>
>>        <p:output name="data" id ="result" ref="data"/>
>>
>>    </p:processor>
>></p:config>
>>
>>
>>
>>
>>--
>>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 and Sebastien,
>
> Yes, the problem is exactly that: all XML files parsed from XPL
> currently by default do XInclude processing by using the XML parser's
> support, and we don't have an easy way to disable it. The current way to
> have control over this at the moment is to use the URL generator
> manually. There, you can specify that you don't want XInclude processing
> to take place at parsing time, see:
>
> http://www.orbeon.com/ops/doc/processors-generators-url#xml-mode
>
> So your solution, for now, consists in reading the file with the URL
> generator without XInclude, then passing the read file to the XInclude
> processor.
>
> And in the meanwhile, suggestions as to how XInclude processing should
> be configured are welcome!
>
> -Erik
>
> Alessandro Vernet wrote:
> > Hi Sebastien,
> >
> > My guess is that your <xi:include> is processed when the XPL file
> > read, and in that context the "input:dynamic-content" cannot be
> > resolved. Can you try to put the content of your HTML in a separate
> > file and reference that file on the with the href attribute when
> > calling the XInclude processor, e.g. <p:input name="config"
> > href="your-file.xhtml"/>?
> >
> > Alex
> >
> > On 11/15/05, Sebastien Noir <[hidden email]> wrote:
> >
> >>Hello!
> >>
> >>I'm trying to use the Xinclude processor, to include dynamic content in
> >>my page.
> >>
> >>When the page loads, I get an error :
> >>Warning: Include operation failed, reverting to fallback. Resource error
> >>reading file as XML (href='input:dynamic-content'). Reason: unknown
> >>protocol: input
> >>
> >>I think it probably is "a small stupid thing" that I didn't do
> >>correctly, but I can't figure what.
> >>
> >>Any help, or exemple using Xinclude processor with dynamic content
> >>(other that the one on the orbeon site) would really be appreciated.
> >>
> >>The code for a simple exemple is found below. I also tried with a
> >>seperate "tampelate" file in which to include the dynamic content with
> >>no more success.
> >>
> >>I also tried to upgrade to the latest unstable version, with no more
> >>success (eclipse reports studio version 1.2.3.200509020246)
> >>
> >>Thanks for your help.
> >>
> >>Sébastien Noir
> >>
> >>File : modifyBug_view_pipe.xpl
> >>
> >><p:config
> >>    xmlns:p="http://www.orbeon.com/oxf/pipeline"
> >>    xmlns:oxf="http://www.orbeon.com/oxf/processors"
> >>    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> >>    xmlns:xdb="http://www.orbeon.org/oxf/xml/xmldb"
> >>    xmlns:my="http://www.epfl.ch/lamp/processors"
> >>    xmlns:xi="http://www.w3.org/2003/XInclude"
> >>    >
> >>
> >>    <p:param name="data" type="output"/>
> >>
> >>    <!-- Generate the users pop-up -->
> >>    <p:processor name="my:UsersPopUpValueGenerator">
> >>        <p:output name="mainoutput" id ="users"  />
> >>    </p:processor>
> >>
> >>    <p:processor name="oxf:xinclude">
> >>        <p:input name="dynamic-content" href="#users"/>
> >>        <p:input name="config">
> >>            <html><head><title>Test</title></head>
> >>                <body>
> >>                    <h1>This is a inclusion test</h1>
> >>                    <!-- This is where the inclusion is performed -->
> >>                    <p>
> >>                       <xi:include href="input:dynamic-content"/>
> >>                    </p>
> >>                </body>
> >>            </html>
> >>        </p:input>
> >>
> >>        <p:output name="data" id ="result" ref="data"/>
> >>
> >>    </p:processor>
> >></p:config>
> >>
> >>
> >>
> >>
> >>--
> >>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
>
>
>

> Erik,
>
> Would it work to reference the file from the <p:input name="config"
> href="..."/> of the XInclude processor? Or would the XInclude be
> processed in this case by the parser even before the data gets to the
> XInclude processor. E.g.:
>
> <p:processor name="oxf:xinclude">
>     <p:input name="dynamic-content" href="#users"/>
>     <p:input name="config" href="my-file.xml"/>
>     <p:output name="data" id="result" ref="data"/>
> </p:processor>

> Alex and Sebastien,
>
> Yes, the problem is exactly that: all XML files parsed from XPL
> currently by default do XInclude processing by using the XML parser's
> support, and we don't have an easy way to disable it. The current way
> to have control over this at the moment is to use the URL generator
> manually. There, you can specify that you don't want XInclude
> processing to take place at parsing time, see:
>
> http://www.orbeon.com/ops/doc/processors-generators-url#xml-mode
>
> So your solution, for now, consists in reading the file with the URL
> generator without XInclude, then passing the read file to the XInclude
> processor.
>
> And in the meanwhile, suggestions as to how XInclude processing should
> be configured are welcome!
>
> -Erik
>
> Alessandro Vernet wrote:
>
>> Hi Sebastien,
>>
>> My guess is that your <xi:include> is processed when the XPL file
>> read, and in that context the "input:dynamic-content" cannot be
>> resolved. Can you try to put the content of your HTML in a separate
>> file and reference that file on the with the href attribute when
>> calling the XInclude processor, e.g. <p:input name="config"
>> href="your-file.xhtml"/>?
>>
>> Alex
>>
>> On 11/15/05, Sebastien Noir <[hidden email]> wrote:
>>
>>> Hello!
>>>
>>> I'm trying to use the Xinclude processor, to include dynamic content in
>>> my page.
>>>
>>> When the page loads, I get an error :
>>> Warning: Include operation failed, reverting to fallback. Resource
>>> error
>>> reading file as XML (href='input:dynamic-content'). Reason: unknown
>>> protocol: input
>>>
>>> I think it probably is "a small stupid thing" that I didn't do
>>> correctly, but I can't figure what.
>>>
>>> Any help, or exemple using Xinclude processor with dynamic content
>>> (other that the one on the orbeon site) would really be appreciated.
>>>
>>> The code for a simple exemple is found below. I also tried with a
>>> seperate "tampelate" file in which to include the dynamic content with
>>> no more success.
>>>
>>> I also tried to upgrade to the latest unstable version, with no more
>>> success (eclipse reports studio version 1.2.3.200509020246)
>>>
>>> Thanks for your help.
>>>
>>> S?bastien Noir
>>>
>>> File : modifyBug_view_pipe.xpl
>>>
>>> <p:config
>>>    xmlns:p="http://www.orbeon.com/oxf/pipeline"
>>>    xmlns:oxf="http://www.orbeon.com/oxf/processors"
>>>    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>>    xmlns:xdb="http://www.orbeon.org/oxf/xml/xmldb"
>>>    xmlns:my="http://www.epfl.ch/lamp/processors"
>>>    xmlns:xi="http://www.w3.org/2003/XInclude"
>>>    >
>>>
>>>    <p:param name="data" type="output"/>
>>>
>>>    <!-- Generate the users pop-up -->
>>>    <p:processor name="my:UsersPopUpValueGenerator">
>>>        <p:output name="mainoutput" id ="users"  />
>>>    </p:processor>
>>>
>>>    <p:processor name="oxf:xinclude">
>>>        <p:input name="dynamic-content" href="#users"/>
>>>        <p:input name="config">
>>>            <html><head><title>Test</title></head>
>>>                <body>
>>>                    <h1>This is a inclusion test</h1>
>>>                    <!-- This is where the inclusion is performed -->
>>>                    <p>
>>>                       <xi:include href="input:dynamic-content"/>
>>>                    </p>
>>>                </body>
>>>            </html>
>>>        </p:input>
>>>
>>>        <p:output name="data" id ="result" ref="data"/>
>>>
>>>    </p:processor>
>>> </p:config>
>>>

> On 11/25/05, Erik Bruchez <[hidden email]> wrote:
>
>>I don't think I replied to this, but I suggest we just change the
>>current behavior of processing XInclude by default from XPL (or add an
>>option to allow that). The PFC applies XInclude and that covers many
>>use cases. For other use cases, you can use the XInclude processor or
>>URL generator explicitly. Otherwise, it looks like XInclude processing
>>by default causes more problems than it solves.
>
>
> That change sounds good to me.