You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Henri Gomez <he...@gmail.com> on 2010/05/04 18:44:11 UTC
Re: OpenEJB 3.1.3
Oups, just see you reply Matthias (gmail label/filter problem).
I got it but wonder why there is Spring Core 2.5.6 included ?
Regards
2010/4/30 Matthias Wessendorf <ma...@apache.org>:
> Hi,
>
> I am using that too (3.1.3 SNAPSHOT) + OpenJPA2.
>
> JEan-Louis made "binary preview" available.
>
> Based on the patch:
> https://issues.apache.org/jira/browse/OPENEJB-1257
>
> thread:
> http://markmail.org/message/6bd5p5qz7z2i3jdj
>
> On Fri, Apr 30, 2010 at 6:51 AM, Henri Gomez <he...@gmail.com> wrote:
>> Hi to all,
>>
>> We're currently use OpenEJB 3.1.2 with Tomcat 6 and are very happy with it.
>>
>> We'll have to use JPA 2.0 and someone on the Facebook Fan Page told me
>> it allready works and should be available in OpenEJB 3.1.3.
>>
>> When should be released OpenEJB 3.1.3 ?
>>
>> BTW, did there is a 3.1.3-SNAPSHOT build available somewhere ?
>>
>> Regards
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
Re: OpenEJB 3.1.3
Posted by Jean-Louis MONTEIRO <je...@atosorigin.com>.
Don't know if it's relevant or not but i guess it won't be possible because
of licensing issues.
May be David (or Jon or Kevan) can give a more accurate answer.
Jean-Louis
--
View this message in context: http://openejb.979440.n4.nabble.com/OpenEJB-3-1-3-tp2076950p2126224.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: OpenEJB 3.1.3
Posted by Jean-Louis MONTEIRO <je...@atosorigin.com>.
Hey Daniel,
Daniel S. Haischt-3 wrote:
>
> Spring is Apache-licensed no? So the only issue might be with
> re-distributing EclipseLink cause the Eclipse-license got some quirks
> license-wise. But after all we would be just re-distributing it
> unmodified which shouldn't be much of an issue.
>
OK
Daniel S. Haischt-3 wrote:
>
> On the other hand
> wouldnt it be feasible to have an impl-agnostic adapter that would
> allow the end user to put whichever library into place?
>
It's actually the case (IMHO). You just need to drop OpenJPA jars from the
openejb war and put Hibernate or EclipseLink dependencies.
Jean-Louis
--
View this message in context: http://openejb.979440.n4.nabble.com/OpenEJB-3-1-3-tp2076950p2126284.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: OpenEJB 3.1.3
Posted by "Daniel S. Haischt" <da...@googlemail.com>.
Spring is Apache-licensed no? So the only issue might be with
re-distributing EclipseLink cause the Eclipse-license got some quirks
license-wise. But after all we would be just re-distributing it
unmodified which shouldn't be much of an issue. On the other hand
wouldnt it be feasible to have an impl-agnostic adapter that would
allow the end user to put whichever library into place?
On Tue, May 4, 2010 at 9:58 PM, Jean-Louis MONTEIRO
<je...@atosorigin.com> wrote:
>
> Don't know if it's relevant or not but i guess it won't be possible because
> of licensing issues.
> May be David (or Jon or Kevan) can give a more accurate answer.
>
> Jean-Louis
> --
> View this message in context: http://openejb.979440.n4.nabble.com/OpenEJB-3-1-3-tp2076950p2126226.html
> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
>
Re: OpenEJB 3.1.3
Posted by David Blevins <da...@visi.com>.
On May 5, 2010, at 12:38 AM, Jean-Louis MONTEIRO wrote:
>
>
> David Blevins wrote:
>>
>> could even generate some ant script or something to grab those jars.
>>
>
> David,
>
> I already have a profile in the openejb-tomcat-webapp to package the
> openejb.war using hibernate as the JPA provider.
>
> Do you think we can push that profile (with another eclipselink profile) in
> that pom so that end users can easily generate the openejb webapp with
> another JPA provider?
>
> Obviously, in my pom (and i should be the case if we add profiles), OpenJPA
> is the default provider (default activated profile).
Perfect. We can add those to the assembly section of the build and simply set them up to not deploy just like we do with the examples via this little config:
<distributionManagement>
<repository>
<id>localhost</id>
<url>file://${basedir}/target/repo/</url>
</repository>
<snapshotRepository>
<id>localhost</id>
<url>file://${basedir}/target/snapshot-repo/</url>
</snapshotRepository>
</distributionManagement>
Now if only we can get someone to fix up this script to test them and help us get it running in the build.
http://svn.apache.org/repos/asf/openejb/trunk/openejb3/assembly/test/build.xml
I've also been wondering if we shouldn't just put up a binary of Tomcat with OpenEJB already in it. Adam Bien mentioned via twitter that he gets asked that question all that time. Would certainly help simplify the above script and make it easier to test the integration in the build.
-David
Re: OpenEJB 3.1.3
Posted by Henri Gomez <he...@gmail.com>.
> I already have a profile in the openejb-tomcat-webapp to package the
> openejb.war using hibernate as the JPA provider.
Very good idea !
> Do you think we can push that profile (with another eclipselink profile) in
> that pom so that end users can easily generate the openejb webapp with
> another JPA provider?
+1
> Obviously, in my pom (and i should be the case if we add profiles), OpenJPA
> is the default provider (default activated profile).
Re: OpenEJB 3.1.3
Posted by Jean-Louis MONTEIRO <je...@atosorigin.com>.
David Blevins wrote:
>
> could even generate some ant script or something to grab those jars.
>
David,
I already have a profile in the openejb-tomcat-webapp to package the
openejb.war using hibernate as the JPA provider.
Do you think we can push that profile (with another eclipselink profile) in
that pom so that end users can easily generate the openejb webapp with
another JPA provider?
Obviously, in my pom (and i should be the case if we add profiles), OpenJPA
is the default provider (default activated profile).
Jean-Louis
--
View this message in context: http://openejb.979440.n4.nabble.com/OpenEJB-3-1-3-tp2076950p2130558.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: OpenEJB 3.1.3
Posted by "Daniel S. Haischt" <da...@googlemail.com>.
The only "issue" concerning the EPL I am aware of is that you have to
re-distribute modified source code or make it publicly available. But
in my previous mail I assumed that this is something we won't do (i.e.
we would re-distribute an unmodified version).
On Tue, May 4, 2010 at 11:20 PM, Henri Gomez <he...@gmail.com> wrote:
>> Right, we can't ship LGPL[1] code from Apache hardware, so that prevents us from shipping any Hibernate code.
>
> Argh right ;(
>
> EclipseLink is EPL and should be allowed. It's the RI and may be the
> good 'implem' to have ?
>
>> We could go as far as building one, testing it, and publishing the jar list -- could even generate some ant script or something to grab those jars.
>
> Providing specifics ant/pom to produce this 'alternate' packages would
> be a very good idea.
>
>> [1] http://www.apache.org/legal/3party.html
>>
>>
>
Re: OpenEJB 3.1.3
Posted by Henri Gomez <he...@gmail.com>.
> Right, we can't ship LGPL[1] code from Apache hardware, so that prevents us from shipping any Hibernate code.
Argh right ;(
EclipseLink is EPL and should be allowed. It's the RI and may be the
good 'implem' to have ?
> We could go as far as building one, testing it, and publishing the jar list -- could even generate some ant script or something to grab those jars.
Providing specifics ant/pom to produce this 'alternate' packages would
be a very good idea.
> [1] http://www.apache.org/legal/3party.html
>
>
Re: OpenEJB 3.1.3
Posted by David Blevins <da...@visi.com>.
On May 4, 2010, at 12:58 PM, Jean-Louis MONTEIRO wrote:
> Don't know if it's relevant or not but i guess it won't be possible because
> of licensing issues.
> May be David (or Jon or Kevan) can give a more accurate answer.
Right, we can't ship LGPL[1] code from Apache hardware, so that prevents us from shipping any Hibernate code.
We could go as far as building one, testing it, and publishing the jar list -- could even generate some ant script or something to grab those jars.
-David
[1] http://www.apache.org/legal/3party.html
Re: OpenEJB 3.1.3
Posted by Jean-Louis MONTEIRO <je...@atosorigin.com>.
Don't know if it's relevant or not but i guess it won't be possible because
of licensing issues.
May be David (or Jon or Kevan) can give a more accurate answer.
Jean-Louis
--
View this message in context: http://openejb.979440.n4.nabble.com/OpenEJB-3-1-3-tp2076950p2126226.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: OpenEJB 3.1.3
Posted by Henri Gomez <he...@gmail.com>.
> The default provider will be OpenJPA 2.0.
> But i'm used to use Hibernate in my company.
>
> Anyway, OpenEJB will be able to support OpenJPA as well as EclipseLink and
> Hibernate.
Good.
What about providing 3 war / packages, one with OpenJPA, another with
EclipseLink and the last one with Hibernate ?
Re: OpenEJB 3.1.3
Posted by Jean-Louis MONTEIRO <je...@atosorigin.com>.
Henri Gomez wrote:
>
> JPA 2.0 provider will be EclipseLink 2.0 or Hibernate 3.5 ?
>
The default provider will be OpenJPA 2.0.
But i'm used to use Hibernate in my company.
Anyway, OpenEJB will be able to support OpenJPA as well as EclipseLink and
Hibernate.
Jean-Louis
--
View this message in context: http://openejb.979440.n4.nabble.com/OpenEJB-3-1-3-tp2076950p2126206.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: OpenEJB 3.1.3
Posted by Henri Gomez <he...@gmail.com>.
> Hi Matthias, Henri,
Hello Jean-Louis.
> The binaries pushed are only a working version.
> There is still some tests failing so i need to work on a bit more.
>
> A new snapshot is being to be produced by Jonathan (today or may be
> tomorrow).
> Not sure this one will include JPA 2.0 support but as soon as i will achieve
> that work, i'll ping here.
Good
JPA 2.0 provider will be EclipseLink 2.0 or Hibernate 3.5 ?
Re: OpenEJB 3.1.3
Posted by Jean-Louis MONTEIRO <je...@atosorigin.com>.
Hi Matthias, Henri,
The binaries pushed are only a working version.
There is still some tests failing so i need to work on a bit more.
A new snapshot is being to be produced by Jonathan (today or may be
tomorrow).
Not sure this one will include JPA 2.0 support but as soon as i will achieve
that work, i'll ping here.
Jean-Louis
Henri Gomez wrote:
>
> Oups, just see you reply Matthias (gmail label/filter problem).
>
> I got it but wonder why there is Spring Core 2.5.6 included ?
>
> Regards
>
> 2010/4/30 Matthias Wessendorf <ma...@apache.org>:
>> Hi,
>>
>> I am using that too (3.1.3 SNAPSHOT) + OpenJPA2.
>>
>> JEan-Louis made "binary preview" available.
>>
>> Based on the patch:
>> https://issues.apache.org/jira/browse/OPENEJB-1257
>>
>> thread:
>> http://markmail.org/message/6bd5p5qz7z2i3jdj
>>
>> On Fri, Apr 30, 2010 at 6:51 AM, Henri Gomez <he...@gmail.com>
>> wrote:
>>> Hi to all,
>>>
>>> We're currently use OpenEJB 3.1.2 with Tomcat 6 and are very happy with
>>> it.
>>>
>>> We'll have to use JPA 2.0 and someone on the Facebook Fan Page told me
>>> it allready works and should be available in OpenEJB 3.1.3.
>>>
>>> When should be released OpenEJB 3.1.3 ?
>>>
>>> BTW, did there is a 3.1.3-SNAPSHOT build available somewhere ?
>>>
>>> Regards
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
--
View this message in context: http://openejb.979440.n4.nabble.com/OpenEJB-3-1-3-tp2076950p2126079.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.