This content has been marked as final. Show 2 replies
Seam looks very promising and I am just trialing the platform for a web app product.
I have one question what would be the best way of loading an entity to view (outside of a business process), editing and then saving the updates to the entity.
The main use case is when I am viewing a reservation and then want to display the user component of the reservation in a seperate page. But would also like the genericness off using the same component to select the person from a list and then display the person entity in a seperate page.
Any thoughts would be more than welcome.
What do you mean by 'outside of a business process' ? Do you mean just always being able to use that entity without being tied to a specific name/scope?
A thought that I had that could solve it is to have a request parameter of the persons id, and load the person from this in a utility stateful ejb (I have not tried this method yet?)
I am not quite sure what you mean.
A stateless session bean could be used to retrieve your entity bean and display your user from the list.
Also I would like to extend this application into a Portal app in the near future, is there any indication when this functionality will become available (for Jboss Portal).
I will discuss portlet integration with Julien Viet (Project leader of JBoss Portal) this coming Thursday we will see from there how soon it can effectively be done. Please check on Jira for updates. http://jira.jboss.org