-
1. Re: seam-issues sample
gavin.king Feb 8, 2007 5:36 AM (in response to samau)Its a bug in the example. Fixed in CVS.
-
2. Re: seam-issues sample
samau Feb 8, 2007 9:51 PM (in response to samau)The CVS version fixes the first problem. However the 2nd problem still exist.
Register a user, click on create issue, then select project will give the following
javax.servlet.ServletException: Could not get property value of component _idJsp1:_idJsp29:0:_idJsp41 org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:61)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) -
-
4. Re: seam-issues sample
tvrtko Feb 14, 2007 8:48 AM (in response to samau)If you login and select a project, then go back to home screen and select the same project again, you will as a result get two conversations: go back to home to see them.
How can I change this behavior so that instead of creating a new conversation I end up joining the existing conversation when I select the project from project list?
I tried all kinds of permutations of join=true and id="#{...}" on several @Begin annotations with no luck.
Also, help me understand, why is the "Project" code split into ProjectSelectorBean, ProjectEditorBean and ProjectFinderBean (same for issue)? Could it all be inside one bean or is code split into several beans because of different life cycles or some other reasons?
Regards,
Tvrtko -
5. Re: seam-issues sample
gavin.king Feb 14, 2007 8:50 AM (in response to samau)This example is old, and no longer the recommended approach.
The CVS version of seam-gen gives you a more uptodate approach to ths kind of app.