Hi Supun,

As the initial plan is to provide JSF, JPA and JTA support with the
upcoming release,
IMO let's go with Apache myfaces, OpenJPA and Atomikas (because it already
comes with carbon).

I will check, are there any problems with OpenEJB and atomikas.
Anyway if so, we can go for another option like Geronimo transactions when
we adding the EJB support.

Yes, +1 to start next step with open-ejb.

Thanks.




On Tue, May 28, 2013 at 12:32 PM, Supun Malinga <[email protected]> wrote:

> Hi Piyum,
>
> On Tue, May 28, 2013 at 12:12 PM, Piyum Fernando <[email protected]> wrote:
>
>> Hi Sagara,
>>
>> Up to now we are almost done with JPA as I created and tested some
>> samples (Webapp/JaxRs/JasWs + JNDI+ Accessing carbon/external data sources
>> +JPA).
>> Everything went well when we enable the relevant class loading
>> environments.
>>
>> Need further work to find the better way to provide class file
>> enhancement.
>>
>> JTA work is already started and I'm working on it.
>> Currently carbon go with  Atomikas as the default JTA implementation.
>>
>> IMO Atomikas seems better than Geronimo transactions considering the
>> available resources and documentation.
>>
>
> Need to see if it integrates fine with open-ejb.
> I think we can start with open-ejb (since this is what we decided to
> provide ejb support) and then have the other connecting pieces. That would
> be a easier approach. WDYT?
>
> thanks,
>
>>
>> I will start a new thread to discuss JTA.
>>
>> Thanks!
>>
>>
>>
>>
>>
>> On Mon, May 27, 2013 at 8:49 PM, Sagara Gunathunga <[email protected]>wrote:
>>
>>> What is the current progress of this ? Ideally we should have start JTA
>>> also by now.
>>>
>>> Thanks !
>>>
>>>
>>> On Thu, May 9, 2013 at 10:24 PM, Supun Malinga <[email protected]> wrote:
>>>
>>>> Hi Piyum,
>>>>
>>>> On Thu, May 9, 2013 at 6:29 PM, Piyum Fernando <[email protected]> wrote:
>>>>
>>>>> There are three major JPA implementations;
>>>>>     OpenJPA
>>>>>     Eclipcelink
>>>>>     Hibernate
>>>>>
>>>>> I tried all three with AS using a simple webapp and worked fine.
>>>>> I will test them with sample JAXRS and JASWS applications too and will
>>>>> look in to the edge cases.
>>>>>
>>>>
>>>> +1
>>>>
>>>>>
>>>>> As per the small discussion we had (Sagara, SupunM and me) we were
>>>>> thinking of using OpenJPA as the default JPA provider because, most
>>>>> probably we will be using OpenEJB to provide EJB support in near future.
>>>>>
>>>>
>>>>>
>>>>>
>>>>> Most importantly JPA spec comes with a concept called "Enhancements"
>>>>> which optimize the Entity classes of the application.
>>>>> What  an enhancer does is  post-process the class files of the entity
>>>>> classes and optimize them[1].
>>>>>
>>>>> JPA providers provide facilities to do it in application build time or
>>>>> at runtime.
>>>>>
>>>>> In the context of J2EE containers, enhancement is supported at the
>>>>> application deployment or at the runtime[2].
>>>>>
>>>>> Are we going to support enhancements in AS? IMO we should.
>>>>>
>>>>> I will look in to this further and update.
>>>>>
>>>>
>>>> +1, As we discussed offline please look at a reference implementation
>>>> and see whats the possible ways to do this. There is some kind of a hood
>>>> concept, and we need to identify how that can be achieved within carbon.
>>>>
>>>> thanks,
>>>>
>>>>>
>>>>>
>>>>>
>>>>> [1]
>>>>> http://openjpa.apache.org/builds/2.1.1/apache-openjpa/docs/ref_guide_pc_enhance.html
>>>>> [2]
>>>>> http://openjpa.apache.org/builds/2.1.1/apache-openjpa/docs/ref_guide_pc_enhance.html#ref_guide_pc_enhance_runtime_container
>>>>>
>>>>> --
>>>>> Piyum Fernando
>>>>> Software Engineer
>>>>>
>>>>> Mobile: +94 77 22 93 880
>>>>> Home:  +94 31 22 75 715
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Supun Malinga,
>>>>
>>>> Software Engineer,
>>>> WSO2 Inc.
>>>> http://wso2.com
>>>> http://wso2.org
>>>> email - [email protected] <[email protected]>
>>>> mobile - 071 56 91 321
>>>>
>>>
>>>
>>>
>>> --
>>> 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
>>>
>>>
>>
>>
>> --
>> 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 - [email protected] <[email protected]>
> mobile - 071 56 91 321
>



-- 
Piyum Fernando
Software Engineer

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

Reply via email to