On Aug 11, 2006, at 2:41 PM, David Blevins wrote:
On Aug 9, 2006, at 1:21 AM, David Blevins wrote:
I'm going to start a branch tomorrow to experiment with JPA stuff
Done. Got a branch up here:
- Revision 430900: /geronimo/branches/jpa-plugin
Didn't turn out to need this as I'm not
On Aug 12, 2006, at 2:52 PM, David Blevins wrote:
Seems like I'm walking in mid-conversation, but I hope I can add
some details.
Geez, I just had *seven* missing emails in this thread show up in my
mailbox. Not sure what's going on with the mail, but that explains
the strange gaps.
On Aug 12, 2006, at 10:03 PM, Jeff Genender wrote:
David Blevins wrote:
Seems like I'm walking in mid-conversation, but I hope I can add some
details.
On Aug 11, 2006, at 8:30 PM, Aaron Mulder wrote:
On 8/11/06, Jeff Genender [EMAIL PROTECTED] wrote:
Ok, I understand where you are going
This isn't a problem. The spec actually says that the web app should
be able to see both persistence units. Also, we are just creating a
map of the persistent units visible, the user still has to choose
which ones to lookup using our magic namespace which is way out side
the
On Aug 11, 2006, at 8:30 PM, Aaron Mulder wrote:
On 8/11/06, Jeff Genender [EMAIL PROTECTED] wrote:
Ok, I understand where you are going with this. I totally agree with
your thinking here. But...IIUC...in the web app, if you are
including
your own PU, you likely wouldn't be using the JNDI
Seems like I'm walking in mid-conversation, but I hope I can add some
details.
On Aug 11, 2006, at 8:30 PM, Aaron Mulder wrote:
On 8/11/06, Jeff Genender [EMAIL PROTECTED] wrote:
Ok, I understand where you are going with this. I totally agree with
your thinking here. But...IIUC...in the
David Blevins wrote:
Seems like I'm walking in mid-conversation, but I hope I can add some
details.
On Aug 11, 2006, at 8:30 PM, Aaron Mulder wrote:
On 8/11/06, Jeff Genender [EMAIL PROTECTED] wrote:
Ok, I understand where you are going with this. I totally agree with
your thinking
On Aug 9, 2006, at 1:21 AM, David Blevins wrote:
I'm going to start a branch tomorrow to experiment with JPA stuff
Done. Got a branch up here:
- Revision 430900: /geronimo/branches/jpa-plugin
Also threw up a wiki page:
- http://cwiki.apache.org/confluence/display/GMOxSBOX/JPA+Plugin
I
On Aug 8, 2006, at 12:22 PM, Jeff Genender wrote:
Aaron,
Please look at the openejb3-persistence module as it does a
majority of
what you described below...
1) Takes a classloader
2) looks for persistence.xml files
3) parses found persistence.xml files
4) Creates EntityManagerFactories
David Blevins wrote:
On Aug 8, 2006, at 12:22 PM, Jeff Genender wrote:
Aaron,
Please look at the openejb3-persistence module as it does a majority of
what you described below...
1) Takes a classloader
2) looks for persistence.xml files
3) parses found persistence.xml files
4)
On Aug 8, 2006, at 11:52 AM, Aaron Mulder wrote:
So far the idea is to put an EntityManagerFactory in JNDI for each
persistence unit at java:comp/env/jpa/(persistence-unit-name) . The
problem is that every component type in Geronimo uses a different
GBean and attribute to hold the JNDI
Weird, but possible, I guess. :)
Thanks,
Aaron
On 8/11/06, David Blevins [EMAIL PROTECTED] wrote:
So check this idea out -- you'll flip. What if we use the
context.xml to override the class that registers the root java: jndi
provider :) Dain and I were going back and forth on what would
So what happens if an EJB JAR has a persistence.xml and a web app in
the same EAR has a separate persistence.xml? If we just look in the
class loader, when we go to deploy the web app, we'll see them both
because the EJB JAR is added to the parent classpath of the WAR. Is
there a good way to
Isn't this the same problem we (and other app servers) have with Spring
and Commons Logging? If you are duplicating the persistence units, then
it should be handled the same way its handled for Spring, yes?
Aaron Mulder wrote:
So what happens if an EJB JAR has a persistence.xml and a web app in
On 8/11/06, Jeff Genender [EMAIL PROTECTED] wrote:
Isn't this the same problem we (and other app servers) have with Spring
and Commons Logging? If you are duplicating the persistence units, then
it should be handled the same way its handled for Spring, yes?
What way is that?
Thanks,
Aaron Mulder wrote:
On 8/11/06, Jeff Genender [EMAIL PROTECTED] wrote:
Isn't this the same problem we (and other app servers) have with Spring
and Commons Logging? If you are duplicating the persistence units, then
it should be handled the same way its handled for Spring, yes?
What way is
On 8/11/06, Jeff Genender [EMAIL PROTECTED] wrote:
With regard to duplicating PUs, in theory, it shouldn't make a
difference if the PU was already loaded in a parent loader.
I think it does. The web app is not necessarily supposed to see JPA
configurations in an EJB JAR, only JPA
Aaron Mulder wrote:
On 8/11/06, Jeff Genender [EMAIL PROTECTED] wrote:
With regard to duplicating PUs, in theory, it shouldn't make a
difference if the PU was already loaded in a parent loader.
I think it does. The web app is not necessarily supposed to see JPA
configurations in an EJB
On 8/11/06, Jeff Genender [EMAIL PROTECTED] wrote:
Ok, I understand where you are going with this. I totally agree with
your thinking here. But...IIUC...in the web app, if you are including
your own PU, you likely wouldn't be using the JNDI (and thus the
container) for this and would be
Aaron Mulder wrote:
On 8/11/06, Jeff Genender [EMAIL PROTECTED] wrote:
Ok, I understand where you are going with this. I totally agree with
your thinking here. But...IIUC...in the web app, if you are including
your own PU, you likely wouldn't be using the JNDI (and thus the
container) for
Personally, I'm happy that Aaron still wants to work on Geronimo at
all. If he wants to work out on SourceForge, that's really his
decision no matter what the reasons. I don't see an upside to
pushing the topic.
As long as he doesn't get upset that others are working on
potentially the
On Aug 8, 2006, at 11:10 AM, Aaron Mulder wrote:
On 8/8/06, David Blevins [EMAIL PROTECTED] wrote:
I'm hacking away at some way to allow people to use OpenJPA in their
apps -- don't know how that will turnout just yet -- and was thinking
a plugin would be best for that as it wouldn't force
Can't speak for Aaron, but I guess this is not so much the code
referencing provider-specific API, but configuration including
provider jars... ant testing that it works of course :-)
Andrus
On Aug 8, 2006, at 2:26 PM, David Blevins wrote:
On Aug 8, 2006, at 11:10 AM, Aaron Mulder wrote:
On 8/8/06, David Blevins [EMAIL PROTECTED] wrote:
What approach are you taking to get this done? I was thinking to do
App-managed EntityManagers, the EntityManagerFactories looked up
through JNDI, and available to both web apps and ejbs.
First of all, the work I'm doing on this is mostly
I forgot to mention -- it seems that every JPA provider has been
compiled against a different version of the JPA spec, which is a
little obnoxious. :)
Thanks,
Aaron
On 8/8/06, Aaron Mulder [EMAIL PROTECTED] wrote:
On 8/8/06, David Blevins [EMAIL PROTECTED] wrote:
What approach are you
Aaron,
Please look at the openejb3-persistence module as it does a majority of
what you described below...
1) Takes a classloader
2) looks for persistence.xml files
3) parses found persistence.xml files
4) Creates EntityManagerFactories based on the persistence.xml file
specifications.
5) Loads
Is that code in the incubator at Apache now?
Jeff Genender wrote:
Aaron,
Please look at the openejb3-persistence module as it does a majority of
what you described below...
1) Takes a classloader
2) looks for persistence.xml files
3) parses found persistence.xml files
4) Creates
Unfortunately, that code is not particularly applicable to Geronimo
1.1 web applications. Just to give a tiny example, a web app never
has an InitialContext to store JNDI data, only a Map. I'm guessing
you also have some special hooking during EJB deployment to invoke the
PersistenceDeployer,
So who is we and why SourceForge? I can certainly see having
Hibernate provider plugins and stuff there, but I definitely intend
on writing the core bits in Geronimo svn.
More bellow... but in a different order.
On Aug 8, 2006, at 11:52 AM, Aaron Mulder wrote:
In the mean time, have you
On Aug 8, 2006, at 12:23 PM, Matt Hogstrom wrote:
Is that code in the incubator at Apache now?
/me hopes matt knew the answer to that question when he did an
OpenEJB release yesterday
:)
Jeff Genender wrote:
Aaron,
Please look at the openejb3-persistence module as it does a
majority
On 8/8/06, David Blevins [EMAIL PROTECTED] wrote:
So who is we and why SourceForge? I can certainly see having
Hibernate provider plugins and stuff there, but I definitely intend
on writing the core bits in Geronimo svn.
we is myself and some folks at Chariot. At SourceForge because 1)
we
:)
David Blevins wrote:
On Aug 8, 2006, at 12:23 PM, Matt Hogstrom wrote:
Is that code in the incubator at Apache now?
/me hopes matt knew the answer to that question when he did an OpenEJB
release yesterday
:)
Jeff Genender wrote:
Aaron,
Please look at the openejb3-persistence
On Aug 8, 2006, at 12:47 PM, Aaron Mulder wrote:
On 8/8/06, David Blevins [EMAIL PROTECTED] wrote:
So who is we and why SourceForge? I can certainly see having
Hibernate provider plugins and stuff there, but I definitely intend
on writing the core bits in Geronimo svn.
we is myself and
On Aug 8, 2006, at 1:43 PM, David Blevins wrote:
On Aug 8, 2006, at 12:47 PM, Aaron Mulder wrote:
On 8/8/06, David Blevins [EMAIL PROTECTED] wrote:
So who is we and why SourceForge? I can certainly see having
Hibernate provider plugins and stuff there, but I definitely intend
on writing
On 8/8/06, Kevan Miller [EMAIL PROTECTED] wrote:
On Aug 8, 2006, at 3:47 PM, Aaron Mulder wrote:
On 8/8/06, David Blevins [EMAIL PROTECTED] wrote:
So who is we and why SourceForge? I can certainly see having
Hibernate provider plugins and stuff there, but I definitely intend
on writing
On Aug 8, 2006, at 2:52 PM, Aaron Mulder wrote:
On 8/8/06, Kevan Miller [EMAIL PROTECTED] wrote:
On Aug 8, 2006, at 3:47 PM, Aaron Mulder wrote:
On 8/8/06, David Blevins [EMAIL PROTECTED] wrote:
So who is we and why SourceForge? I can certainly see having
Hibernate provider plugins and
Aaron,
I didn't disagree with your conclusion. You gave 3 reasons for not
performing the work at Apache. All you needed was one -- licensing
issues prevent this work from occurring at Apache. Maybe so, but so
far only you have made that evaluation. I'm not intimating that you
are wrong,
37 matches
Mail list logo
