Agreed. We should view transactions+persistence as an atomic concern.
-Dan
On Tue, Nov 24, 2009 at 7:05 AM, Pete Muir <pmuir(a)redhat.com> wrote:
I think we can delete the transaction module, and just put all of
this in
persistence. I can't see why you would want one module and not the other....
On 24 Nov 2009, at 04:08, Steven Boscarine wrote:
> I committed the code from
http://www.seamframework.org/Community/HowDoIGetAJPAEntityManagerReferenc...
https://svn.jboss.org/repos/seam/modules/trunk/persistence
> and
https://svn.jboss.org/repos/seam/modules/trunk/transaction
>
> I imported persistence into a trivial web app and it appears to work. I
haven't had time to write any useful tests yet.
>
> The transaction project is not compiling. Perhaps it's older code? I
commented out the dependencies that are not on the repo and changed
jsr299-api to cdi-api. It was originally failing to validate because it was
missing ${webbeans.groupId}.
>
>
>
>
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen