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 ch
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 <[EMAIL PROTECTED]> wrote:
> David,
>
> I am releasing the
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 <[EMAIL PROTECTED]> 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
> c
On 8/15/06, Matt Hogstrom <[EMAIL PROTECTED]> 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
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
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
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 conso
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
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 <[EMAIL P
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 wa
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
11 matches
Mail list logo
