You're right, I forgot about the naming conventions. So if you take
a look at the //TODO I put on line 778 of EARConfigBuilder, we'll
still have to call to inspect the ejbjar candidate. As far as the
library support, I added it a while back see EARConfigBuilder line
500. lib is used if
but not yet a ejb-jar.xml application.xml free deploy
On Jan 23, 2007, at 9:54 PM, Prasad Kashyap wrote:
We can now have a ejb-jar.xml free deployment and openejb-jar.xml free
deployment.
-sachin
You mean geronimo-openejb free deploy.
The latest revisions do support ejb-jar.xml free deployments
Cheers
Prasad
On 1/24/07, Sachin Patel [EMAIL PROTECTED] wrote:
but not yet a ejb-jar.xml application.xml free deploy
On Jan 23, 2007, at 9:54 PM, Prasad Kashyap wrote:
We can now have a
No I mean an ear with no applicaiton.xml and the ear contains a
ejbjar, with no ejb-jar.xml
On Jan 24, 2007, at 4:06 PM, Prasad Kashyap wrote:
You mean geronimo-openejb free deploy.
The latest revisions do support ejb-jar.xml free deployments
Cheers
Prasad
On 1/24/07, Sachin Patel [EMAIL
As I mentioned before, what I think needs to be done is rename
EjbConfigBuilder.isEjbAnnotatedModule() to isAnnotatedModule(JarFile
jar) and introduce this in the ModuleBuilder interface since the
other ModuleBuilders will need to implement it. EARConfigBuilder can
then invoke the method
Only ejb modules are identified by scanning for annotations. IIRC
from the jee5 spec the following rules are used to identify modules:
Web - filenames ends with .war
Connector - filename ends with .rar
Persistence - contains META-INF/persistence.xml
EJB - scan for EJB annotations
AppClient -
David J. found a couple issues with the latest changes, both have
been fixed. Posting in case you ran into these.
One was a null pointer caused during deployment:
[WARNING] Caused by: java.lang.NullPointerException
[WARNING] at org.apache.xbean.finder.ClassFinder.readClassDef
David, I thought I had already fixed this... for my knowledge, what
else needed to be done?
On Jan 22, 2007, at 9:54 PM, David Jencks wrote:
Btw in somewhat related work I fixed GERONIMO-2769 so that now if
you deploy an ear without an application.xml you can get to all the
problems you
On Jan 23, 2007, at 6:56 AM, Sachin Patel wrote:
David, I thought I had already fixed this... for my knowledge, what
else needed to be done?
The code I started with only processed the geronimo application plan
if there was an application.xml. If the application.xml was missing
the
On 1/22/07, David Blevins [EMAIL PROTECTED] wrote:
Ok. All of these issues should be fixed.
I did a complete clean Geronimo ( OpenEJB) build. I am still having
issues here -
1) http://issues.apache.org/jira/browse/GERONIMO-2770.
An ejb-module with a missing ejb-jar.xml will not be recognized
Woops... responded just now to the wrong thread...
Ok, one other item we don't support is an ear with an ejbjar, with no
application.xml, nor an ejb-jar.xml. The EARConfigBuilder needs to
inspect classes for any ejb related annotations in order to classify
it as an ejbjar. Same goes for
For those interested and following this thread (D Jencks had a similar
NPE), both these issues are now resolved.
We can now have a ejb-jar.xml free deployment and openejb-jar.xml free
deployment.
Cheers
Prasad
On 1/23/07, Prasad Kashyap [EMAIL PROTECTED] wrote:
On 1/22/07, David Blevins
On Jan 21, 2007, at 1:03 PM, Prasad Kashyap wrote:
I was able to deploy the app successfully but only after using an
openejb-jar.xml.
Dain Blevins,
On the irc discussion on Sat, 01/20, we thought that an
openejb-jar.xml is not mandatory. I debugged the builder and realized
the contrary.
In
On Jan 22, 2007, at 4:46 PM, David Blevins wrote:
On Jan 21, 2007, at 1:03 PM, Prasad Kashyap wrote:
I was able to deploy the app successfully but only after using an
openejb-jar.xml.
Dain Blevins,
On the irc discussion on Sat, 01/20, we thought that an
openejb-jar.xml is not mandatory. I
Ok. All of these issues should be fixed.
-David
On Jan 22, 2007, at 4:46 PM, David Blevins wrote:
On Jan 21, 2007, at 1:03 PM, Prasad Kashyap wrote:
I was able to deploy the app successfully but only after using an
openejb-jar.xml.
Dain Blevins,
On the irc discussion on Sat, 01/20, we
I was able to deploy the app successfully but only after using an
openejb-jar.xml.
Dain Blevins,
On the irc discussion on Sat, 01/20, we thought that an
openejb-jar.xml is not mandatory. I debugged the builder and realized
the contrary.
In the EJBModuleBuilder.java, it doesn't check to see if
On Jan 21, 2007, at 1:03 PM, Prasad Kashyap wrote:
I was able to deploy the app successfully but only after using an
openejb-jar.xml.
Dain Blevins,
On the irc discussion on Sat, 01/20, we thought that an
openejb-jar.xml is not mandatory. I debugged the builder and realized
the contrary.
In
I have created a sample application out of the
calculator-stateless-pojo example in OpenEJB 3.0
It is checked in here -
http://svn.apache.org/viewvc/geronimo/samples/trunk/calculator-stateless-pojo/
The app tries to demonstrate dependency injection of the bean into a
servlet and obviates the
18 matches
Mail list logo
