[JBoss Seam] - Re: EL Enhancements dont work in facelets tag file
by mbolcina
I am having similar problem. I am using facelets source tag:
taglib.xml
| <facelet-taglib>
| <namespace>http://Test</namespace>
| <tag>
| <tag-name>test</tag-name>
| <source>Test.xhtml</source>
| </tag>
| </facelet-taglib>
Test.xhtml (source of test tag)
| <ui:composition xmlns="http://www.w3.org/1999/xhtml" ...>
| <h:commandLink action="#{backingBean.test('123')}">
| testWithParam
| </h:commandLink>
| <h:commandLink action="#{backingBean.testNoParam}">
| testNoParam
| </h:commandLink>
| </ui:composition>
|
some xhtml file using test tag
| <ui:composition xmlns="http://www.w3.org/1999/xhtml" ...
| xmlns:t="http://Test">
| <t:test backingBean="#{testBean}"/>
| </ui:composition>
Link testNoParam is working.
Link testWithParam is NOT working. I get exception:
11:15:57,258 ERROR [ExceptionFilter] uncaught exception
javax.servlet.ServletException: Error calling action method of component with id test:_id54
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:152)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63)
at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60)
at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57)
at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79)
at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
I am using seam 1.2.1GA, project was created using seam-gen.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033634#4033634
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033634
17 years, 2 months
[JBoss Seam] - Re: clarification about propagation=
by codelion
I admit, you have to know what conversation to end. I looked closer at what I'm doing, and the problem/question seems to be:
Should propagation="end" end the conversation when entering the target page or when leaving (!) the target (!) page?
I argue it should when entering, but it apparently does when leaving.
In my test case I am coming via
<s:link view="/myOther.xhtml" value="Outta Here" propagation="end" />
into page myOther.xhtml that coincidentally also has in its myOther.page.xml
<page>
| <begin-conversation join="true" />
| </page>
My thought was like this: The propagation="end" means to end the conversation it was coming from (in my.xhtml).
End it. Now. First thing when dealing with conversations in the JSF Request-Response Life Cycle. Where in Seam Reference 6.1 it says "At the end of the restore view phase of the JSF request lifecycle, Seam attempts to restore any previous long-running conversation context. If none exists, Seam creates a new temporary conversation context."
I'd expect the propagation="end" at that point to make that conversation go away, and hence fulfill the "none exists" test.
If I have a propagation="none" it is gone indeed.
But if I have propagation="end" then the conversation still is there, and begin-conversation picks it up.
Me thinks this just happened as implementation detail, implementing propagation="end" like or similar to @End or like end-conversation, while it should be implemented to be effective at the same time as propagation="none" would be.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033628#4033628
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033628
17 years, 2 months