Hi Chamil,

Can you please  explain the complete architecture for this integration ?
also includes other possible approaches we evaluated  with pros and cons.
Basically you need to summarise results of your POC carried out during Q1.


Thanks !


On Tue, Apr 22, 2014 at 12:23 PM, Chamil Jeewantha <[email protected]> wrote:

>
> We are planning to integrate Apache TomEE [1] to AS to add out of the box
> AS Java EE Web Profile[2] support.
>
> *What is Java EE Web Profile?*
>
>  It is subset of complete Java EE APIs that is needed for majority of
> modern web applications. It contains only the following APIs out of Full
> JavaEE spec.
>
> CDI, EJB, JPA, JSF, JSP, JSTL, JTA, Servlet, Javamail & Bean Validation.
>
>
> *What is TomEE?*
>
> TomEE is pronounced "Tommy". It is a *Java EE 6 Web Profile certified
> stack* based on Apache Tomcat.
>
> They are focused on:
>
>    - Don't mess with Tomcat
>       - Vanilla Tomcat + TomEE jars
>    - Keep it simple
>       - deliver JavaEE Web Profile in the simplest way possible.
>
> The TomEE provides each of the above specs using popular Apache
> implementations of the above Web Profile specs.
>
> CDI                        - Apache OpenWebBeans
> EJB                        - Apache OpenEJB
> JPA                        - Apache OpenJPA
> JSF                        - Apache MyFaces
> JSP                        - Apache Tomcat
> JSTL                      - Apache Tomcat
> Servlet                  - Apache Tomcat
> JTA                       - Apache Gerenimo Transaction
> Javamail              - Apache Gerenimo JavaMail
> Bean Validation - Apache BVal
>
> *What are the benefits of TomEE on AS?*
>
>    - All-Apache solution
>    - TomEE is a certified stack of Java EE 6 Web Profile
>    - interrelationship among the above mentioned Spec implementations are
>    handled by TomEE
>    - Annotation Scanning for each spec separately is time consuming.
>    Tomee has optimized scanning
>    - Low memory footprint.
>    - No tight coupling on Tomcat
>
> Even though the WSO2 AS supports both JPA & JAX-WS, JPA is not available
> for JAX-WS and JAX-RS applications. Because the JPA & JAX-WS intergration
> is not completed.
> This problem can be solved using TomEE+ which has integrated JAX-WS,
> JAX-RS, JMS & Connector in addition to Web Profile. TomEE+ in future.
>
> Your comments, concerns & suggestions are highly appreciated.
>
> [1] http://tomee.apache.org/
> [2] http://jaxenter.com/introducing-the-java-ee-web-profile-36201.html
>
> --
> K.D. Chamil Jeewantha
> Associate Technical Lead
> WSO2, Inc.;  http://wso2.com
> Mobile: +94716813892
>



-- 
Sagara Gunathunga

Senior Technical Lead; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;    http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to