Am I correct in saying that the annotation will control JTA and work in
either of the two profiles (web and full)?
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).
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.
-Dan
--
Sent from my CyanogenMod-powered
Android device, an open platform for
carriers, developers and consumers.
On Apr 27, 2012 4:54 AM, "Pete Muir" <pmuir(a)redhat.com> wrote:
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.
On 24 Apr 2012, at 09:10, Hantsy Bai wrote:
> Hi,
>
> I have read some content about the spec 1.1, but I want to know if there
> is a plan to provide a new transaction annotation...for EBJ or none EJB
> proramming.
>
> For example, provide a @Transactional annotation like Seam2 or Spring
> 3.1...and make it work in Servlet container(none JTA transation, jdbc
> only) or full profile container such as JBoss, Glassfish(JTA transaction
> by default) seamlessly.
>
> Automatically detect the Transaction will be used, or configure in
> beans.xml file.
>
>
> Regards
> Hantsy
> _______________________________________________
> cdi-dev mailing list
> cdi-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/cdi-dev
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev