Hi,
Should the same technique be used to layer xhtml resources like
EJB's can be (using the @Install annotation)? If so, how would you have
multiple pages.xml files - and would it conflict?
Say I had a real view: "/product/function.xhtml" and I had customised
version of it deployed at a particular site called
"/site/product/function.xhtml". Could (or rather should) I use this
approach:
<page view-id="/product/function.xhtml">
<navigation>
<render view-id="/site/product/function.xhtml"/>
</navigation>
</page>
And refer to the view generally as only "/product/function.xhtml", but
actually load "/site/product/function.xhtml". Or should I use something
like EL at all times and resolve the actual resource via a method call
or resource bundle?
What methodology have you used to address this in the past?
Cheers,
David
[EMAIL PROTECTED] wrote:
pages.xml for a fake view id is like:
<page view-id="/entryPoint.xhtml">
| <action execute="#{something.doSomething}"/>
| <navigation>
| <render view-id="/displayWelcome.xhtml"/>
| </navigation>
| </page>
or something close to that.
There is no /entryPoint.xhtml file. thats just the URL you want to appear in
the browser.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057064#4057064
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057064
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
-----------------
Utiba Pty Ltd
This message has been scanned for viruses and
dangerous content by Utiba mail server and is
believed to be clean.
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
