Why the login page can not load Xincludes element?

hello, I upgraded a web app from the version 3.9 to 4.10. The login page can not load the following code(maybe it loaded but I can not see the navigation bar showing on the web page),
<xi:include href="/apps/includes/navigation.xhtml" xxi:omit-xml-base="true"/>, however, it works well in the orbeon 3.9 version. So how to fix this bug, Thanks.
here are the two attachments:
navigation.xhtmlcontroller.xhtml

Henry,

And where is your controller.xhtml referenced from? Is it referenced from a <page view="…"> in a page-flow.xml?

Alex

Hi, Alex
Yes, the controller.xhtml is referenced from page-flow.xml in the same
folder.

Henry

--
View this message in context: http://discuss.orbeon.com/Why-the-login-page-can-not-load-Xincludes-element-tp4660654p4660665.html
Sent from the Orbeon Forms community mailing list mailing list archive at Nabble.com.

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi, Alex
Yes, the controller.xhtml is referenced from page-flow.xml in the same
folder.

Here is the page-flow.xml:

<config xmlns="http://www.orbeon.com/oxf/controller">
                <page path-info="*" view="controller.xhtml"/>
    <epilogue url="oxf:/config/epilogue.xpl"/>
</config>

Henry

--
View this message in context: http://discuss.orbeon.com/Why-the-login-page-can-not-load-Xincludes-element-tp4660654p4660667.html
Sent from the Orbeon Forms community mailing list mailing list archive at Nabble.com.

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi, Alex
Yes, the controller.xhtml is referenced from page-flow.xml in the same
folder.

Here is the page-flow.xml:

<config xmlns="http://www.orbeon.com/oxf/controller">
                <page path-info="*" view="controller.xhtml"/>
    <epilogue url="oxf:/config/epilogue.xpl"/>
</config>

Henry


--
View this message in context: http://discuss.orbeon.com/Why-the-login-page-can-not-load-Xincludes-element-tp4660654p4660668.html
Sent from the Orbeon Forms community mailing list mailing list archive at Nabble.com.

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi, Alex Yes, the controller.xhtml is referenced from page-flow.xml in the same folder. Here is the page-flow.xml: Henry

---

View this message in context: Re: Why the login page can not load Xincludes element?
Sent from the Orbeon Forms community mailing list mailing list archive at Nabble.com.

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi, Alex
Yes, the controller.xhtml is referenced from page-flow.xml in the same folder.

Here is the page-flow.xml:

<config xmlns="http://www.orbeon.com/oxf/controller">
                <page path-info="*" view="controller.xhtml"/>
    <epilogue url="oxf:/config/epilogue.xpl"/>
</config>

Henry

Alessandro Vernet wrote

Henry,

And where is your controller.xhtml referenced from? Is it referenced from a <page view="…"> in a page-flow.xml?

Alex

Hi, Alex
Yes, the controller.xhtml is referenced from page-flow.xml in the same folder.

Here is the page-flow.xml:

<config xmlns="http://www.orbeon.com/oxf/controller">
                <page path-info="*" view="controller.xhtml"/>
    <epilogue url="oxf:/config/epilogue.xpl"/>
</config>

Henry

Hi Henry,

OK, I tried this here, and I think it's just a matter of your navigation.xhtml having the <xf:instance> as a root element, instead of <include>. And of course, make sure to copy all the namespaces declarations you had on the <include> to the <xf:instance>.

I tried this by creating an include.xml in apps/xforms-hello, and including it in view.xhtml.

Alex

Hello, Alex,
I have solved the problem of showing navigation bar, however, if the include file have the multiple instances(eg: attachment model.xhtml), can I simply replace the<include> to <xf: group> as the root element? Thank you.

Henry

Hello, Alex,
I have solved the problem of showing navigation bar, however, if the include file have the multiple instances(eg: attachment model.xhtml), can I simply replace the<include> to <xf: group> as the root element? Thank you.

Henry model.xhtml

Hi Henry,

If you have multiple <xf:group> under your <include>, I imagine that this content goes in the view, which means you could put a new <xf:group appearance="xxf:internal"> as root element, instead of <include>.

The appearance="xxf:internal" attribute is optional, but this tells Orbeon Forms not generate any markup in the HTML for that element, so you won't make the generated HTML any different by adding that <xf:group appearance="xxf:internal">.

Alex