Migrating from 2.8 to 3.0

--
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

--- Biju Narayanan <[hidden email]> wrote:
> Iam trying to migrate from Orbeon 2.8 to 3.0. The application uses
> dynamic Xform instances generated using Orbeon 2.8 PFC pipelines. What
> is the best approach to generate dynamic Xform instances in Orbeon 3.0?

Hi Biju,

Since the XForms model is in the view now, you can generate the initial
dynamic XForms instance in your model, pass it along to your view
implemented in XSLT, and include there the dynamic instance in the model.

Alex

--
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

Alessandro Vernet wrote: Yes, this is in fact much better than the 2.8 way. You may have for
example something like this in your page view (written with XSLT):

<xforms:model>
   <xforms:instance id="main">
     <xsl:copy-of select="/my-instance-generated-by-the-page-model"/>
   </xforms:instance>
</xforms:model>

With 3.0, the roles are this way better defined than with 2.8: the page
model produces everything that is dynamic for the view, including
dynamic XForms model / instance information.

-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