Kind of like Rails has scaffolding based on actual DB metadata, it would
really great to specify a single component that would default a lot of
the form behavior based on EJB 3 metadata. I realize that you have to
do some jimmying at this point in the partial JEE 5 stack, but once
that's out-- all we need is the UI components that can survive long term
with the stack. You have quite a bit of opportunity to pioneer some
really cool 'drop in' RAD components.
-- Jacob
Mario Ivankovits wrote:
Hi Jacob!
If you can standardize on the EJB3 spec, then you can piggy back on
JBoss Seam for TX management and state management
I shy to use JBoss Seam in the "reference implementation". If you
would like to use JBoss Seam outside the JBoss Seam enabled JBoss
Application Server you have to add dozens of jars to your classpath,
you know?
And I dont know if I really need all this management now. I dont see
this "conversational scope" now in Faces Freeway as any transaction
will be finished in the same view. Save/Edit/Delete will all happen on
the same page - and then I always can use Session.persist().
I am not an JBoss Seam expert so I dont know if it is easily possible
to plugin support for it later, but this might change in the future as
I would like to use JBoss Seam in our application too :-)
---
Mario
