java - Replacing Seam with jee6 in conversation -
a project i'm working on going upgrade jee5/seam jee6, "those descide" think idea drop seam since of features have been incorporated jee6. have case doesn't seem able solve in jee6.
we have several wizards using conversationscope. use seams flushmodetype.manual in order avoid getting "dirty" data commited until want wants commit (each page-load gets own transaction since nothing written database until flush, commits doesn't change state of database).
i have made few attempts using persistencecontexttype.extended in jee6 seems can't find way defer flush database seam , workarounds seems to use detached objects or separate view-model.
we how working attached objects make (for our cases) things simple understand , fast develop.
is there solution can keep working attached objects in conversations?
as big fan of seam2 wrote great apps using conversations, conversation scoped entity manager flush mode set manual , detached objects.
however, must admit pattern, despite being pushed in seam manual , working great far hibernate jpa implementation, fundamentally broken. reason explained in post mark struberg: is there way fix jpa entitymanager?
so, answer no, there no practical solution keep working attached objects in conversations. should work detached objects.
there another great cdi blogger experimented conversation scoped entity manager: conversational crud. might worth reading if keep on trying work attached objects.
Comments
Post a Comment