This content has been marked as final. Show 3 replies
Not at this stage, but if you are interested in contributing, let us know!
is there any schedule for tapestry integration?
I was about to ask the same question ;-)
I'm not sure to understand the concepts of Seam since I'm not very familiar with JSF/EJB but it seems to me that Seam=IoC+JSF workarounds. Tapestry has a very well designed model for component state so with Tapestry the seam state model would not be so useful. But I'd be like to understand what is the model for managing LazyExceptions and Hibernate. Does Seam provide methods to automatically reattach Hibernate entities to a new session? That's my major trouble with Spring+Hibernate+Tapestry.
Tapestry has a very well designed model for component state so with Tapestry the seam state model would not be so useful.
To the best of my knowledge, Tapestry does not have a notion of conversation, or of business process, nor does it have anything like Seam's bijection stuff for managing contextual state. Now, I don't know tapestry well, but I suspect Seam would make plenty of sense with tapestry.
Does Seam provide methods to automatically reattach Hibernate entities to a new session?
Actually, what it does is holds an extended persistence context (ie. single Hibernate session instance) open to service the entire conversation. So objects never need to be in the detached state. So you never experience lazyinitializationexceptions when you use those objects in the context of the conversation.