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
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
A page action is the right way to do it. If you don't want it to be reinvoked
on subsequent partial submits, you have two options:
(1) map the page action to a fake view id - yes, a page action is allowed to
perform navigation and result in a different view id, just like struts! Perhaps
thats
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
Perfect! As always, thanks so much for answering so many questions!!!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057073#4057073
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057073
