I am using Seam 1.2.1GA and I have problem with s:convertEntity such as:
| h:selectOneMenu id=clientBranch
value=#{loggedInUser.clientBranch} styleClass=input-field required=true
style=width:50%
| s:selectItems
Your selection action passes the object x. You may be able to return a string
of the view such as /myobjectview.seam?id= + x.id. I haven't tried this.
Better still you could use the navigation rules in pages.xml as per the seam
documentation (section 5.1.1.2):
| page
I have a backing bean which is used in both the session and conversation
context as follows:
| @Name(searchCompany)
| @Scope(ScopeType.SESSION)
| @Roles( [EMAIL PROTECTED](name=findCompany,scope=ScopeType.CONVERSATION)}
)
|
In order for the outjected datamodel list to pick up the
You could use s:link with action parameter. The action event should return a
view-id (JSF or otherwise). Using the SeamFaceletViewHandler you should be able
to pass parameters to the action event e.g #{myBean.objectSelected(x)}
View the original post :
I am using seam 1.20. I have a problem starting a pageflow:
If I use the pageflow property of the @Begin annotation the pageflow will not
start and subsequently will not move from the first page. e.g:
| Pageflow
| pageflow-definition name=linkCorrespondence
|start-page name=upload
The seam documentation states in section 7.2.2:
anonymous wrote :
| If we are beginning the pageflow during the RENDER_RESPONSE phase?during a
@Factory or @Create method, for example?we consider ourselves to be already at
the page being rendered, and use a start-page node as the first node
Thank you for your help. I am now using Seam's EntityConvertor
http://wiki.jboss.org/wiki/Wiki.jsp?page=SeamEntityConverter
[/url]
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4023325#4023325
Reply to the post :
This is more a question of design or understanding:
In order to avoid the lazy initialization exception I have followed the seam
examples and used the TransactionalSeamPhaseListener and configured the
components.xml correctly. The entity manager is now injected using the @In
annotation. I can
