On Thu, Jun 6, 2013 at 12:23 AM, Chris Haddad <chad...@cobia.net> wrote:

> Do we have license access to standard JEE unit tests and samples?  Rather
> than re-create the wheel, demonstrate JEE interoperability with proven
> tests and samples.
>

+1 to use standard samples and tests.

>
> /Chris
>
>
> On Jun 3, 2013, at 11:03 PM, Supun Malinga wrote:
>
> Hi Piyum,
>
> In a bit of a rush. Replying briefly.
>
>
> On Mon, Jun 3, 2013 at 7:50 PM, Piyum Fernando <pi...@wso2.com> wrote:
>
>> As per the previous discussions, the plan is to add JSF,JPA and JTA
>> support with the upcoming release.
>>
>> Following will be used with AS as the default implementations of above
>> specs.
>>
>> JSF - Apache myfaces
>> JPA - OpenJPA
>> JTA - Atomikas
>>
>> I've created and tested few sample web apps to go with them.
>> Up to now all three impls work fine with AS.
>>
>
> Good work..
>
>
>>
>> Currently, I'm using two newly created class loading environments for JSF
>> and JPA.
>> Since Atomikas comes with carbon by default, web apps can use it by
>> adding the carbon environment.
>>
>
> Yeah this is kind of duplication. Same was done for spring jars in cxf
> runtime env. I think ideal solution is to create a mechanism to install
> runtime environments into carbon. Currently we only copy the jars in build
> time, but that is not good enough and will make the product size huge.
> Piyum please start another thread on that in Archi@ too.
>
>
>> We need to figure out how we add them to the AS pack.
>>     Single class loading env for all or separate ones for each spec?
>>     Are we going to add nested class loading envs ?
>>
>
> Piyum I think the best is to have a single runtime env for j2ee. But for
> the separation of  concern, as Sagara mentioned we should be able to have
> sub directories to keep libraries of individual piece (jpa, jta, myfaces,
> etc.). Common lib. jars we can keep in the top dir. Currently sub dirs. is
> not supported too.
>
>
>>
>> Are we going to ship samples/documentation with this release?
>> If so documentation can be done to go with the already created samples.
>>
>
> Yes we do need to ship sample docs. and get Mary's help to get this done.
> We would need to create a separate section in docs. for j2ee stuff.
>
>>
>>
>> TO DOs:
>>
>> -Test with a set of standard J2EE samples
>> -Add class file enhancement for bean classes(JPA)
>> -Create a proper document on how to create XADatasources with carbon
>> (master- datasources.xml) and how to use them inside the webb apps
>>
>>
>> Sagara, SupunM please add if I missed something.
>>
>> --
>> Piyum Fernando
>> Software Engineer
>>
>> Mobile: +94 77 22 93 880
>> Home:  +94 31 22 75 715
>>
>
>
>
> --
> Supun Malinga,
>
> Senior Software Engineer,
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
> email - sup...@wso2.com <sup...@wso2.com>
> mobile - 071 56 91 321
>  _______________________________________________
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
>


-- 
Piyum Fernando
Software Engineer

Mobile: +94 77 22 93 880
Home:  +94 31 22 75 715
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to