True, it could be a matter of packaging. We could include the necessary JAR files as part of the Servlet support in the respective distributions. In a sense, they would be "blessed" extensions, which is all any user really cares about (how else do they know what's in weld-servlet.jar, for example).<div>
<br></div><div>-Dan<br><br><div class="gmail_quote">On Mon, Apr 30, 2012 at 15:59, Mark Struberg <span dir="ltr"><<a href="mailto:struberg@yahoo.de" target="_blank">struberg@yahoo.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Over in DeltaSpike we are currently discussing the jpa module. Plans are to implement it there as portable extension. I see no need why we need to duplicate the effort by implementing it in both Weld and OWB ;)<br>
<br>
The big benefit of this approach is that this will also run on any CDI-1.0 container!<br>
<div class="im"><br>
<br>
LieGrue,<br>
strub<br>
<br>
>________________________________<br>
> From: Dan Allen <<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>><br>
</div>>To: Pete Muir <<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>><br>
>Cc: <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
>Sent: Monday, April 30, 2012 9:42 PM<br>
<div class="im">>Subject: Re: [cdi-dev] CDI have any plan to process Transaction?<br>
><br>
><br>
</div><div><div class="h5">>I molded this into a mini blog. Pete, if you are interested, feel free to post this as it will likely solve a wider misunderstanding from going around:<br>
><br>
><br>
>"A standard, universal @Transactional annotation is coming in Java EE 7. However, there are some important things to keep in mind:<br>
><br>
><br>
>- @Transactional *is* being developed as a revision to the JTA spec (as an MR)<br>
>- @Transactional *is not* being developed by the CDI EG, nor will it be in the CDI spec<br>
>- Feedback on @Transactional should be sent to the Java EE platform EG *not* to the CDI EG. The platform EG is conducting the revision to the JTA spec.<br>
><br>
><br>
>Java EE does not recognize a Servlet container as a compliant environment and therefore this feature will not be available there by default (mainly due to the absence of JTA in this environemnt).<br>
><br>
><br>
>However, to bridge the divide, Weld and OpenWebBeans will both likely offer support for @Transactional in a Servlet environment since we acknowledge that it *is* important, and is an environment preferred by many developers (but we still strongly urge you to migrate to the web profile!!)."<br>
><br>
><br>
>-Dan<br>
><br>
>On Mon, Apr 30, 2012 at 04:55, Pete Muir <<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>> wrote:<br>
><br>
>Just to be 100% clear, as there is a lot of confusion around this topic.<br>
>><br>
>>* @Transactional *IS NOT* being developed by the CDI EG nor will it be in the CDI spec<br>
>>* @Transactional *IS* being developed as a revision to the JTA spec (as a MR IIRC, but that was not my/our decision to make)<br>
>>* Feedback on @Trasnactional should be sent to the Java EE platform EG NOT to the CDI EG. The platform EG is conducting the revision to the JTA spec.<br>
>><br>
>>HTH!<br>
>><br>
>><br>
>>On 30 Apr 2012, at 09:19, Pete Muir wrote:<br>
>><br>
>>><br>
>>> On 29 Apr 2012, at 23:12, Dan Allen wrote:<br>
>>><br>
>>>> Am I correct in saying that the annotation will control JTA<br>
>>><br>
>>> Yes, this will be an amendment to the JTA spec AIUI. So back where it belongs!<br>
>>><br>
>>>> and work in either of the two profiles (web and full)?<br>
>>><br>
>>> We haven't discussed this, but I'm assuming both. I will raise this.<br>
>>><br>
>>>><br>
>>>> Btw, Java EE does not recognize a Servlet container as a compliant environment and therefore this feature will not be available there (without special support for it).<br>
>>><br>
>>> Correct. Main obstacle is actually a lack of JTA there, rather than the declarative control… But I think OWB and Weld will both offer something here as we all regard it as important!<br>
>>><br>
>>>><br>
>>>> I agree with this stance since the web profile should be recognized as the low end environment. Otherwise there is not enough core services to provide a dependable and portable programming model. If you (general audience) want to use a Servlet container, you aren't using Java EE and will have to supplement with addons like CDI extensions or Spring.<br>
>>>><br>
>>>> -Dan<br>
>>>><br>
>>>> --<br>
>>>> Sent from my CyanogenMod-powered<br>
>>>> Android device, an open platform for<br>
>>>> carriers, developers and consumers.<br>
>>>><br>
>>>> On Apr 27, 2012 4:54 AM, "Pete Muir" <<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>> wrote:<br>
>>>> Java EE 7 will include @Transactional. This will be provided by the Java EE platform, rather than CDI specifically. It will be a CDI interceptor, and so enabled as other CDI interceptors are.<br>
>>>><br>
>>>> On 24 Apr 2012, at 09:10, Hantsy Bai wrote:<br>
>>>><br>
>>>>> Hi,<br>
>>>>><br>
>>>>> I have read some content about the spec 1.1, but I want to know if there<br>
>>>>> is a plan to provide a new transaction annotation...for EBJ or none EJB<br>
>>>>> proramming.<br>
>>>>><br>
>>>>> For example, provide a @Transactional annotation like Seam2 or Spring<br>
>>>>> 3.1...and make it work in Servlet container(none JTA transation, jdbc<br>
>>>>> only) or full profile container such as JBoss, Glassfish(JTA transaction<br>
>>>>> by default) seamlessly.<br>
>>>>><br>
>>>>> Automatically detect the Transaction will be used, or configure in<br>
>>>>> beans.xml file.<br>
>>>>><br>
>>>>><br>
>>>>> Regards<br>
>>>>> Hantsy<br>
>>>>> _______________________________________________<br>
>>>>> cdi-dev mailing list<br>
>>>>> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
>>>>> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> cdi-dev mailing list<br>
>>>> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
>>>> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> cdi-dev mailing list<br>
>>> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
>><br>
>><br>
><br>
><br>
><br>
>--<br>
><br>
</div></div>>Dan AllenPrincipal Software Engineer, Red Hat | Author of Seam in Action<br>
<div class="im HOEnZb">>Registered Linux User #231597<br>
><br>
><br>
><a href="http://google.com/profiles/dan.j.allen" target="_blank">http://google.com/profiles/dan.j.allen</a><br>
><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
><br>
><br>
</div><div class="HOEnZb"><div class="h5">>_______________________________________________<br>
>cdi-dev mailing list<br>
><a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
><a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
><br>
><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://google.com/profiles/dan.j.allen" target="_blank">http://google.com/profiles/dan.j.allen</a><br>
<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>
</div>