You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Aaron Mulder <am...@alumni.princeton.edu> on 2006/08/14 05:24:38 UTC
JPA Plugin Status
The code for the app-managed-JPA-for-web-apps plugin is up at SVN
https://svn.sourceforge.net/svnroot/gplugins/jpa/trunk
So far, it's just got a TopLink provider, but if people want to copy
that to create providers for Cayenne or OpenJPA or whatever, that
would be great. It basically just needs to have a customized name and
ClassPath, though I'm assuming any provider we integrate with will be
compatible with the Geronimo JPA spec JAR (currently
org.apache.geronimo.specs/geronimo-jpa_3.0_spec/1.0-SNAPSHOT/jar)
If you try to build and run this, you'll be held up by a couple things:
* It needs the latest car-maven-plugin, and I'm not sure whether
Jason has pushed a fresh snapshot since the last changes to it
* It needs Geronimo 1.1 CARs in the M2 repo, and Matt has said
posting those is on his to-do list
* It only runs in Geronimo 1.1.1 due to reference resolution bugs in
G 1.1, and currently the G 1.1.1 build is broken
But if you get past all that (or comment out the plugins child from
the main POM to avoid the first two issues) and run your server under
Java 5, you can deploy web apps using JPA. :)
My goal is to have a release of this plugin with sufficient user
documentation when G 1.1.1 is released. It would be great to have
some open source JPA providers for that release too.
I also started talking to David B about the JPA work being done in
OpenEJB, and I think we're agreed that we probably don't need two such
plugins for G 1.1.x, so hopefully we can work toward a unification as
we move forward.
Thanks,
Aaron
Re: JPA Plugin Status
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
On 8/15/06, Matt Hogstrom <ma...@hogstrom.org> wrote:
> David,
>
> I am releasing the specs as a 1.1.1 release due to some changes in jacc. Do you want to include the
> changes to JPA there?
For my 2 cents, that would be great!
Thanks,
Aaron
> David Blevins wrote:
> > I got OpenJPA to run with my JPA code. So we're looking real good.
> >
> > On Aug 13, 2006, at 8:24 PM, Aaron Mulder wrote:
> >
> >> So far, it's just got a TopLink provider, but if people want to copy
> >> that to create providers for Cayenne or OpenJPA or whatever, that
> >> would be great. It basically just needs to have a customized name and
> >> ClassPath, though I'm assuming any provider we integrate with will be
> >> compatible with the Geronimo JPA spec JAR (currently
> >> org.apache.geronimo.specs/geronimo-jpa_3.0_spec/1.0-SNAPSHOT/jar)
> >
> > OpenJPA and the Geronimo JPA spec jar weren't happy. Our JPA jar had
> > some bad signatures and was missing a few exception classes. I fixed
> > those and managed to get OpenJPA to compile and run with our JPA jar
> > rather than the CDDL version they use.
> >
> >> If you try to build and run this, you'll be held up by a couple things:
> >
> > For me its:
> > - Still missing the some JNDI stuff Dain is working on (mentioned
> > earlier in the thread).
> > - Need the plugin goop
> >
> > But when that is there, this should run for ejbs or servlets in 1.1.1
> > and maybe 1.1 (should work).
> >
> >> My goal is to have a release of this plugin with sufficient user
> >> documentation when G 1.1.1 is released. It would be great to have
> >> some open source JPA providers for that release too.
> >>
> >> I also started talking to David B about the JPA work being done in
> >> OpenEJB, and I think we're agreed that we probably don't need two such
> >> plugins for G 1.1.x, so hopefully we can work toward a unification as
> >> we move forward.
> >
> > I'm sure we can figure something out. I'll give it some more thought
> > tomorrow, time for bed now....zzzzZZZZ
> >
> > -David
> >
> >
> >
> >
>
Re: JPA Plugin Status
Posted by Matt Hogstrom <ma...@hogstrom.org>.
David,
I am releasing the specs as a 1.1.1 release due to some changes in jacc. Do you want to include the
changes to JPA there?
David Blevins wrote:
> I got OpenJPA to run with my JPA code. So we're looking real good.
>
> On Aug 13, 2006, at 8:24 PM, Aaron Mulder wrote:
>
>> So far, it's just got a TopLink provider, but if people want to copy
>> that to create providers for Cayenne or OpenJPA or whatever, that
>> would be great. It basically just needs to have a customized name and
>> ClassPath, though I'm assuming any provider we integrate with will be
>> compatible with the Geronimo JPA spec JAR (currently
>> org.apache.geronimo.specs/geronimo-jpa_3.0_spec/1.0-SNAPSHOT/jar)
>
> OpenJPA and the Geronimo JPA spec jar weren't happy. Our JPA jar had
> some bad signatures and was missing a few exception classes. I fixed
> those and managed to get OpenJPA to compile and run with our JPA jar
> rather than the CDDL version they use.
>
>> If you try to build and run this, you'll be held up by a couple things:
>
> For me its:
> - Still missing the some JNDI stuff Dain is working on (mentioned
> earlier in the thread).
> - Need the plugin goop
>
> But when that is there, this should run for ejbs or servlets in 1.1.1
> and maybe 1.1 (should work).
>
>> My goal is to have a release of this plugin with sufficient user
>> documentation when G 1.1.1 is released. It would be great to have
>> some open source JPA providers for that release too.
>>
>> I also started talking to David B about the JPA work being done in
>> OpenEJB, and I think we're agreed that we probably don't need two such
>> plugins for G 1.1.x, so hopefully we can work toward a unification as
>> we move forward.
>
> I'm sure we can figure something out. I'll give it some more thought
> tomorrow, time for bed now....zzzzZZZZ
>
> -David
>
>
>
>
Re: JPA Plugin Status
Posted by David Blevins <da...@visi.com>.
On Aug 16, 2006, at 8:01 AM, Matt Hogstrom wrote:
> I'm releasing out of branches/1_1_1. Is your stuff in trunk ?
No it's in a branch, so we'd have to vote it into trunk. If you were
thinking it was in branches/1.1.1, don't worry about it.
Probably best to let Jason get his spec layout change in first.
-David
>
> David Blevins wrote:
>> Grrr, I'm missing mail again -- pulled it from the archives.
>> Thanks, Dain, for pointing out there was a message for me.
>> On 8/15/06, Matt Hogstrom <ma...@hogstrom.org> wrote:
>> > David,
>> >
>> > I am releasing the specs as a 1.1.1 release due to some changes
>> in jacc. Do you want to include the
>> > changes to JPA there?
>> That would be great. In fact all the jee5_exp specs could be
>> released. The related specifications went final so we should be
>> good to go.
>> -David
>> On Aug 15, 2006, at 4:17 AM, David Blevins wrote:
>>> I got OpenJPA to run with my JPA code. So we're looking real good.
>>>
>>> On Aug 13, 2006, at 8:24 PM, Aaron Mulder wrote:
>>>
>>>> So far, it's just got a TopLink provider, but if people want to
>>>> copy
>>>> that to create providers for Cayenne or OpenJPA or whatever, that
>>>> would be great. It basically just needs to have a customized
>>>> name and
>>>> ClassPath, though I'm assuming any provider we integrate with
>>>> will be
>>>> compatible with the Geronimo JPA spec JAR (currently
>>>> org.apache.geronimo.specs/geronimo-jpa_3.0_spec/1.0-SNAPSHOT/jar)
>>>
>>> OpenJPA and the Geronimo JPA spec jar weren't happy. Our JPA jar
>>> had some bad signatures and was missing a few exception classes.
>>> I fixed those and managed to get OpenJPA to compile and run with
>>> our JPA jar rather than the CDDL version they use.
>>>
>>>> If you try to build and run this, you'll be held up by a couple
>>>> things:
>>>
>>> For me its:
>>> - Still missing the some JNDI stuff Dain is working on
>>> (mentioned earlier in the thread).
>>> - Need the plugin goop
>>>
>>> But when that is there, this should run for ejbs or servlets in
>>> 1.1.1 and maybe 1.1 (should work).
>>>
>>>> My goal is to have a release of this plugin with sufficient user
>>>> documentation when G 1.1.1 is released. It would be great to have
>>>> some open source JPA providers for that release too.
>>>>
>>>> I also started talking to David B about the JPA work being done in
>>>> OpenEJB, and I think we're agreed that we probably don't need
>>>> two such
>>>> plugins for G 1.1.x, so hopefully we can work toward a
>>>> unification as
>>>> we move forward.
>>>
>>> I'm sure we can figure something out. I'll give it some more
>>> thought tomorrow, time for bed now....zzzzZZZZ
>>>
>>> -David
>>>
>
Re: JPA Plugin Status
Posted by Matt Hogstrom <ma...@hogstrom.org>.
I'm releasing out of branches/1_1_1. Is your stuff in trunk ?
David Blevins wrote:
> Grrr, I'm missing mail again -- pulled it from the archives. Thanks,
> Dain, for pointing out there was a message for me.
>
> On 8/15/06, Matt Hogstrom <ma...@hogstrom.org> wrote:
> > David,
> >
> > I am releasing the specs as a 1.1.1 release due to some changes in
> jacc. Do you want to include the
> > changes to JPA there?
>
> That would be great. In fact all the jee5_exp specs could be released.
> The related specifications went final so we should be good to go.
>
> -David
>
> On Aug 15, 2006, at 4:17 AM, David Blevins wrote:
>
>> I got OpenJPA to run with my JPA code. So we're looking real good.
>>
>> On Aug 13, 2006, at 8:24 PM, Aaron Mulder wrote:
>>
>>> So far, it's just got a TopLink provider, but if people want to copy
>>> that to create providers for Cayenne or OpenJPA or whatever, that
>>> would be great. It basically just needs to have a customized name and
>>> ClassPath, though I'm assuming any provider we integrate with will be
>>> compatible with the Geronimo JPA spec JAR (currently
>>> org.apache.geronimo.specs/geronimo-jpa_3.0_spec/1.0-SNAPSHOT/jar)
>>
>> OpenJPA and the Geronimo JPA spec jar weren't happy. Our JPA jar had
>> some bad signatures and was missing a few exception classes. I fixed
>> those and managed to get OpenJPA to compile and run with our JPA jar
>> rather than the CDDL version they use.
>>
>>> If you try to build and run this, you'll be held up by a couple things:
>>
>> For me its:
>> - Still missing the some JNDI stuff Dain is working on (mentioned
>> earlier in the thread).
>> - Need the plugin goop
>>
>> But when that is there, this should run for ejbs or servlets in 1.1.1
>> and maybe 1.1 (should work).
>>
>>> My goal is to have a release of this plugin with sufficient user
>>> documentation when G 1.1.1 is released. It would be great to have
>>> some open source JPA providers for that release too.
>>>
>>> I also started talking to David B about the JPA work being done in
>>> OpenEJB, and I think we're agreed that we probably don't need two such
>>> plugins for G 1.1.x, so hopefully we can work toward a unification as
>>> we move forward.
>>
>> I'm sure we can figure something out. I'll give it some more thought
>> tomorrow, time for bed now....zzzzZZZZ
>>
>> -David
>>
>
>
>
>
Re: JPA Plugin Status
Posted by David Blevins <da...@visi.com>.
Grrr, I'm missing mail again -- pulled it from the archives.
Thanks, Dain, for pointing out there was a message for me.
On 8/15/06, Matt Hogstrom <ma...@hogstrom.org> wrote:
> David,
>
> I am releasing the specs as a 1.1.1 release due to some changes in
jacc. Do you want to include the
> changes to JPA there?
That would be great. In fact all the jee5_exp specs could be
released. The related specifications went final so we should be good
to go.
-David
On Aug 15, 2006, at 4:17 AM, David Blevins wrote:
> I got OpenJPA to run with my JPA code. So we're looking real good.
>
> On Aug 13, 2006, at 8:24 PM, Aaron Mulder wrote:
>
>> So far, it's just got a TopLink provider, but if people want to copy
>> that to create providers for Cayenne or OpenJPA or whatever, that
>> would be great. It basically just needs to have a customized name
>> and
>> ClassPath, though I'm assuming any provider we integrate with will be
>> compatible with the Geronimo JPA spec JAR (currently
>> org.apache.geronimo.specs/geronimo-jpa_3.0_spec/1.0-SNAPSHOT/jar)
>
> OpenJPA and the Geronimo JPA spec jar weren't happy. Our JPA jar
> had some bad signatures and was missing a few exception classes. I
> fixed those and managed to get OpenJPA to compile and run with our
> JPA jar rather than the CDDL version they use.
>
>> If you try to build and run this, you'll be held up by a couple
>> things:
>
> For me its:
> - Still missing the some JNDI stuff Dain is working on (mentioned
> earlier in the thread).
> - Need the plugin goop
>
> But when that is there, this should run for ejbs or servlets in
> 1.1.1 and maybe 1.1 (should work).
>
>> My goal is to have a release of this plugin with sufficient user
>> documentation when G 1.1.1 is released. It would be great to have
>> some open source JPA providers for that release too.
>>
>> I also started talking to David B about the JPA work being done in
>> OpenEJB, and I think we're agreed that we probably don't need two
>> such
>> plugins for G 1.1.x, so hopefully we can work toward a unification as
>> we move forward.
>
> I'm sure we can figure something out. I'll give it some more
> thought tomorrow, time for bed now....zzzzZZZZ
>
> -David
>
Re: JPA Plugin Status
Posted by David Blevins <da...@visi.com>.
I got OpenJPA to run with my JPA code. So we're looking real good.
On Aug 13, 2006, at 8:24 PM, Aaron Mulder wrote:
> So far, it's just got a TopLink provider, but if people want to copy
> that to create providers for Cayenne or OpenJPA or whatever, that
> would be great. It basically just needs to have a customized name and
> ClassPath, though I'm assuming any provider we integrate with will be
> compatible with the Geronimo JPA spec JAR (currently
> org.apache.geronimo.specs/geronimo-jpa_3.0_spec/1.0-SNAPSHOT/jar)
OpenJPA and the Geronimo JPA spec jar weren't happy. Our JPA jar had
some bad signatures and was missing a few exception classes. I fixed
those and managed to get OpenJPA to compile and run with our JPA jar
rather than the CDDL version they use.
> If you try to build and run this, you'll be held up by a couple
> things:
For me its:
- Still missing the some JNDI stuff Dain is working on (mentioned
earlier in the thread).
- Need the plugin goop
But when that is there, this should run for ejbs or servlets in 1.1.1
and maybe 1.1 (should work).
> My goal is to have a release of this plugin with sufficient user
> documentation when G 1.1.1 is released. It would be great to have
> some open source JPA providers for that release too.
>
> I also started talking to David B about the JPA work being done in
> OpenEJB, and I think we're agreed that we probably don't need two such
> plugins for G 1.1.x, so hopefully we can work toward a unification as
> we move forward.
I'm sure we can figure something out. I'll give it some more thought
tomorrow, time for bed now....zzzzZZZZ
-David
Re: JPA Plugin Status
Posted by Jeff Genender <jg...@apache.org>.
Excellent!
Aaron Mulder wrote:
> OK, now it should work if you don't set up a provider but just bundle
> all the needed stuff in your WAR or set up your dependencies right.
> I'd still prefer to use the provider registry for the ones we know of,
> since then we can let you manage them in the console, perhaps support
> default properties to be applied to all apps for that provider, etc.
>
> Thanks,
> Aaron
>
> On 8/14/06, Jeff Genender <jg...@apache.org> wrote:
>> Aaron,
>>
>> Why do you need to have vendor code? Why can't this be a bit more
>> dynamic? Long term, I think its a bad idea to have to declare a vendor
>> wrapped API when our competitors just need to dump the provider jars in
>> a directory somewhere or include them in a deployment. Basically,
>> anyone who wants to use a provider that we haven't supported has to
>> write vendor G-only code...right? If this is the case, I think that is
>> a bit burdensome. Thoughts?
>>
>> Jeff
>>
>> Aaron Mulder wrote:
>> > The code for the app-managed-JPA-for-web-apps plugin is up at SVN
>> > https://svn.sourceforge.net/svnroot/gplugins/jpa/trunk
>> >
>> > So far, it's just got a TopLink provider, but if people want to copy
>> > that to create providers for Cayenne or OpenJPA or whatever, that
>> > would be great. It basically just needs to have a customized name and
>> > ClassPath, though I'm assuming any provider we integrate with will be
>> > compatible with the Geronimo JPA spec JAR (currently
>> > org.apache.geronimo.specs/geronimo-jpa_3.0_spec/1.0-SNAPSHOT/jar)
>> >
>> > If you try to build and run this, you'll be held up by a couple things:
>> > * It needs the latest car-maven-plugin, and I'm not sure whether
>> > Jason has pushed a fresh snapshot since the last changes to it
>> > * It needs Geronimo 1.1 CARs in the M2 repo, and Matt has said
>> > posting those is on his to-do list
>> > * It only runs in Geronimo 1.1.1 due to reference resolution bugs in
>> > G 1.1, and currently the G 1.1.1 build is broken
>> >
>> > But if you get past all that (or comment out the plugins child from
>> > the main POM to avoid the first two issues) and run your server under
>> > Java 5, you can deploy web apps using JPA. :)
>> >
>> > My goal is to have a release of this plugin with sufficient user
>> > documentation when G 1.1.1 is released. It would be great to have
>> > some open source JPA providers for that release too.
>> >
>> > I also started talking to David B about the JPA work being done in
>> > OpenEJB, and I think we're agreed that we probably don't need two such
>> > plugins for G 1.1.x, so hopefully we can work toward a unification as
>> > we move forward.
>> >
>> > Thanks,
>> > Aaron
>>
Re: JPA Plugin Status
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
OK, now it should work if you don't set up a provider but just bundle
all the needed stuff in your WAR or set up your dependencies right.
I'd still prefer to use the provider registry for the ones we know of,
since then we can let you manage them in the console, perhaps support
default properties to be applied to all apps for that provider, etc.
Thanks,
Aaron
On 8/14/06, Jeff Genender <jg...@apache.org> wrote:
> Aaron,
>
> Why do you need to have vendor code? Why can't this be a bit more
> dynamic? Long term, I think its a bad idea to have to declare a vendor
> wrapped API when our competitors just need to dump the provider jars in
> a directory somewhere or include them in a deployment. Basically,
> anyone who wants to use a provider that we haven't supported has to
> write vendor G-only code...right? If this is the case, I think that is
> a bit burdensome. Thoughts?
>
> Jeff
>
> Aaron Mulder wrote:
> > The code for the app-managed-JPA-for-web-apps plugin is up at SVN
> > https://svn.sourceforge.net/svnroot/gplugins/jpa/trunk
> >
> > So far, it's just got a TopLink provider, but if people want to copy
> > that to create providers for Cayenne or OpenJPA or whatever, that
> > would be great. It basically just needs to have a customized name and
> > ClassPath, though I'm assuming any provider we integrate with will be
> > compatible with the Geronimo JPA spec JAR (currently
> > org.apache.geronimo.specs/geronimo-jpa_3.0_spec/1.0-SNAPSHOT/jar)
> >
> > If you try to build and run this, you'll be held up by a couple things:
> > * It needs the latest car-maven-plugin, and I'm not sure whether
> > Jason has pushed a fresh snapshot since the last changes to it
> > * It needs Geronimo 1.1 CARs in the M2 repo, and Matt has said
> > posting those is on his to-do list
> > * It only runs in Geronimo 1.1.1 due to reference resolution bugs in
> > G 1.1, and currently the G 1.1.1 build is broken
> >
> > But if you get past all that (or comment out the plugins child from
> > the main POM to avoid the first two issues) and run your server under
> > Java 5, you can deploy web apps using JPA. :)
> >
> > My goal is to have a release of this plugin with sufficient user
> > documentation when G 1.1.1 is released. It would be great to have
> > some open source JPA providers for that release too.
> >
> > I also started talking to David B about the JPA work being done in
> > OpenEJB, and I think we're agreed that we probably don't need two such
> > plugins for G 1.1.x, so hopefully we can work toward a unification as
> > we move forward.
> >
> > Thanks,
> > Aaron
>
Re: JPA Plugin Status
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
I'm open, but how do you set up the class path if the vendor needs
more than a single JAR? I don't think it's so onerous to write a
single glue class when there are only a handful of vendors out there,
but I'm certainly willing to revisit it.
Thanks,
Aaron
On 8/14/06, Jeff Genender <jg...@apache.org> wrote:
> Aaron,
>
> Why do you need to have vendor code? Why can't this be a bit more
> dynamic? Long term, I think its a bad idea to have to declare a vendor
> wrapped API when our competitors just need to dump the provider jars in
> a directory somewhere or include them in a deployment. Basically,
> anyone who wants to use a provider that we haven't supported has to
> write vendor G-only code...right? If this is the case, I think that is
> a bit burdensome. Thoughts?
>
> Jeff
>
> Aaron Mulder wrote:
> > The code for the app-managed-JPA-for-web-apps plugin is up at SVN
> > https://svn.sourceforge.net/svnroot/gplugins/jpa/trunk
> >
> > So far, it's just got a TopLink provider, but if people want to copy
> > that to create providers for Cayenne or OpenJPA or whatever, that
> > would be great. It basically just needs to have a customized name and
> > ClassPath, though I'm assuming any provider we integrate with will be
> > compatible with the Geronimo JPA spec JAR (currently
> > org.apache.geronimo.specs/geronimo-jpa_3.0_spec/1.0-SNAPSHOT/jar)
> >
> > If you try to build and run this, you'll be held up by a couple things:
> > * It needs the latest car-maven-plugin, and I'm not sure whether
> > Jason has pushed a fresh snapshot since the last changes to it
> > * It needs Geronimo 1.1 CARs in the M2 repo, and Matt has said
> > posting those is on his to-do list
> > * It only runs in Geronimo 1.1.1 due to reference resolution bugs in
> > G 1.1, and currently the G 1.1.1 build is broken
> >
> > But if you get past all that (or comment out the plugins child from
> > the main POM to avoid the first two issues) and run your server under
> > Java 5, you can deploy web apps using JPA. :)
> >
> > My goal is to have a release of this plugin with sufficient user
> > documentation when G 1.1.1 is released. It would be great to have
> > some open source JPA providers for that release too.
> >
> > I also started talking to David B about the JPA work being done in
> > OpenEJB, and I think we're agreed that we probably don't need two such
> > plugins for G 1.1.x, so hopefully we can work toward a unification as
> > we move forward.
> >
> > Thanks,
> > Aaron
>
Re: JPA Plugin Status
Posted by Jeff Genender <jg...@apache.org>.
Aaron,
Why do you need to have vendor code? Why can't this be a bit more
dynamic? Long term, I think its a bad idea to have to declare a vendor
wrapped API when our competitors just need to dump the provider jars in
a directory somewhere or include them in a deployment. Basically,
anyone who wants to use a provider that we haven't supported has to
write vendor G-only code...right? If this is the case, I think that is
a bit burdensome. Thoughts?
Jeff
Aaron Mulder wrote:
> The code for the app-managed-JPA-for-web-apps plugin is up at SVN
> https://svn.sourceforge.net/svnroot/gplugins/jpa/trunk
>
> So far, it's just got a TopLink provider, but if people want to copy
> that to create providers for Cayenne or OpenJPA or whatever, that
> would be great. It basically just needs to have a customized name and
> ClassPath, though I'm assuming any provider we integrate with will be
> compatible with the Geronimo JPA spec JAR (currently
> org.apache.geronimo.specs/geronimo-jpa_3.0_spec/1.0-SNAPSHOT/jar)
>
> If you try to build and run this, you'll be held up by a couple things:
> * It needs the latest car-maven-plugin, and I'm not sure whether
> Jason has pushed a fresh snapshot since the last changes to it
> * It needs Geronimo 1.1 CARs in the M2 repo, and Matt has said
> posting those is on his to-do list
> * It only runs in Geronimo 1.1.1 due to reference resolution bugs in
> G 1.1, and currently the G 1.1.1 build is broken
>
> But if you get past all that (or comment out the plugins child from
> the main POM to avoid the first two issues) and run your server under
> Java 5, you can deploy web apps using JPA. :)
>
> My goal is to have a release of this plugin with sufficient user
> documentation when G 1.1.1 is released. It would be great to have
> some open source JPA providers for that release too.
>
> I also started talking to David B about the JPA work being done in
> OpenEJB, and I think we're agreed that we probably don't need two such
> plugins for G 1.1.x, so hopefully we can work toward a unification as
> we move forward.
>
> Thanks,
> Aaron