geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Blevins <david.blev...@visi.com>
Subject Re: Where should g. jee5 stuff go?
Date Mon, 21 Aug 2006 21:29:49 GMT
On Aug 21, 2006, at 1:05 PM, David Jencks wrote:

> It's pretty obvious where to put jee5 specs, and now I've committed  
> this one.  I was trying to ask where we want to put work on jee5  
> implementations so they won't interfere with the j2ee 1.4  
> implementation.  I can see two choices:
>
> - if we can run the j2ee 1.4 tck with jee5 spec jars, we could do  
> the jee5 work in trunk
> - if we can't run the j2ee 1.4 tck with jee5 spec jars, we have to  
> do the work somewhere else, and I'm suggesting the sandbox for  
> now.  This might be a good idea anyway until something actually works.

Ah, ok.  Well you might be able to get away with running the TCK  
against the JTA 1.1 library as it doesn't appear to have any Java 5  
dependency.  But all the rest of them do.

Maybe do the TX side of things in trunk and the rest in sandbox.  Or  
all of it out on sandbox.

-David


> thanks
> david jencks
>
> On Aug 21, 2006, at 12:52 PM, David Blevins wrote:
>
>> You can put it here for now http://svn.apache.org/repos/asf/ 
>> geronimo/specs/branches/jee5_exp/
>>
>> When Jason's done with the new spec layout, I'll be working on  
>> moving those in to trunk.
>>
>> -David
>>
>> On Aug 20, 2006, at 5:41 PM, David Jencks wrote:
>>
>>> I've implemented the jta 1.1 feature locally and want to do the  
>>> ejb 3/jpa container managed persistence stuff.  Where should I  
>>> put it?
>>>
>>> jta 1.1 adds one interface to jta 1.0.1B with AFAICT no other  
>>> changes (I haven't actually been able to locate the spec, just  
>>> the javadoc).  Anyone know if we can run the j2ee 1.4 tck using  
>>> jee5 spec jars?
>>>
>>> If not, I think we'll have to do something like copy the tm  
>>> module to somewhere else for jee5 work.  Maybe a copy of tm in  
>>> sandbox?  I worry about getting out of sync with m2 related  
>>> reorganizations.
>>>
>>> My first guess at the CMP is to do most of the work in the tm  
>>> module. but I might change my mind at any time.
>>>
>>> thanks
>>> david jencks
>>>
>>
>


Mime
View raw message