Ok Maurice,
The announcement is coming, but here is the release:
http://dist.codehaus.org/openejb/distributions/openejb-1.0-beta1.zip
And here is a demo of the new collapsed ear support:
http://demo1.openejb.org/moviefun/index.jsp
(to reset the demo visit ../moviefun/setup.jsp)
Took a little longer than expected, but I didn't want to ship the car
till I had driven a few miles in it myself first. It should be solid.
Give me a shout back and tell me what you like and don't like.
-David
On Aug 16, 2005, at 7:41 AM, Maurice Yarrow wrote:
Hello David
First, my thanks to you for addressing this issue.
So I will first consider your first reply concering the 0.9.2
approach.
To test this multiple jar / multiple database issue, I will again
need
to recreate a second database and the appropriate ejb jar deployment.
Over the next several days I will do some work on this and try to get
this going, and will respond again when I have results to report.
Now, with respect to your 1.0 approach, the stategy you have suggested
below looks fairly staightforward. Yes, it does look like what I am
trying to do. Could you give an loose estimate for when such a
set of experiments would be testable with the 1.0? (Any kind of
estimate, over-estimate, or whatever is fine: I know only too well
that everything takes longer than originally planned.) I would be
interested in testing such a methodology but will have to work it in
with my current development efforts.
- Maurice
David Blevins wrote:
Ok, so I am replying to this email twice as I want to discuss
some 1.0 stuff in relation to your apps without confusing things
(life in 0.9.2 vs. 1.0).
So if I understand your situation correctly, you have two webapps
and two ejb jars running in Tomcat 5.0.x and OpenEJB 0.9.2. In
essence, you have two unrelated apps; GetIMG and NPhoneCard. In
the 0.9.2 you have to smush the ejbs together into the same
openejb.conf because there is only one OpenEJB instance for all
of Tomcat and webapps. But in the 1.0 code you could actually
have two separately managed OpenEJB instances, which seems like
what you were trying to do.
How would a setup like the following suit your needs?
webapps/
GetIMG/
META-INF/ejb-jar.xml
META-INF/openejb.xml
META-INF/openejb-jar.xml
META-INF/postgresql.cmp_global_database.xml
META-INF/postgresql.cmp_local_database.xml
META-INF/postgresql.cmp_or_mapping.xml
WEB-INF/web.xml
WEB-INF/lib/openejb-loader-1.0.jar
WEB-INF/classes/<all your servlet and ejb classes>
NPhoneCard
META-INF/ejb-jar.xml
META-INF/openejb.xml
META-INF/openejb-jar.xml
META-INF/postgresql.cmp_global_database.xml
META-INF/postgresql.cmp_local_database.xml
META-INF/postgresql.cmp_or_mapping.xml
WEB-INF/web.xml
WEB-INF/lib/openejb-loader-1.0.jar
WEB-INF/classes/<all your servlet and ejb classes>
The idea expressed here is that each app is an independent mix of
servlets and ejbs. Tomcat manages the serlvets and OpenEJB
manages the ejbs. You might think of each app as a "collapsed"
ear; ejbs and servlets packaged together in the same archive and
run in the same classloader. I'm not sure if we can get Castor
to play nice with having the mapping files in your webapp, but
the rest is possible.
I'm working on code now to allow for this exact setup and looking
for someone to try it out. Seems you have a great use-case.
1) Is this close to what you are trying to do and 2) are you
interested in trying this out?
-David
