Hmm. Apparently, there's at least two people saying I'm using that file
incorrectly, so there's probably something to it. All that this .ear is
intended to do is deploy the session bean in bnpr.jar, which is a Java 5
EJB3 annotated session bean. The other jars listed are those required
to support the bean. As noted in my other email, which crossed this one
in the ether, based on what I've been able to dig up, that's how the
dependencies for the bean should be noted in the file.
--
Jason Lee
Programmer/Analyst
-----Original Message-----
From: vince kraemer [mailto:vince.kraemer_at_Sun.COM]
Sent: Wednesday, January 25, 2006 11:15 AM
To: users_at_glassfish.dev.java.net
Cc: dev_at_glassfish.dev.java.net
Subject: Re: EJB Session Bean Deployment
Wow!
That is a ton of application clients!
I would be interested in seeing the content of ejb-jar.xml that you have
in bnpr.jar....
Have you tried running your client?
Since GF supports Java Web Start for application clients, you may want
to think about using that instead of a out of container client....
One other thing you might want to try.... Change the application.xml to
tell the truth about the application... Your app is a 5.0 app, not a 1.4
app...
Jason Lee wrote:
> I'm having some issues getting my EJB3 session bean to deploy on
> Glassfish (nightly from 1/24). I have created the .ear with the
> session bean jar and the supporting jars. in META-INF/, I have
> MANIFEST.MF and application.xml, which looks like:
>
> <?xml version="1.0" encoding="UTF-8"?> <application
> xmlns="http://java.sun.com/xml/ns/j2ee" version="1.4"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com <http://java.sun.com/>
> /xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
> <display-name>BrandNameProductSessionBean</display-name>
> <description>Brand Name Product Sesssion Bean</description>
>
> <module><ejb>bnpr.jar</ejb></module>
> <module><java>commons-collections-3.1.jar</java></module>
> <module><java>commons-dbcp-1.2.1.jar</java></module>
> <module><java>commons-pool-1.2.jar</java></module>
> <module><java>concurrent-1.3.4.jar</java></module>
> <module><java>dom4j-1.6.1.jar</java></module>
> <module><java>jdom-1.0.jar</java></module>
> <module><java>postgresql-8.0-311.jdbc3.jar</java></module>
> <module><java>spring.jar</java></module>
> <module><java>whirlycache-0.7.1.jar</java></module>
> </application>
> Looking at the log files, it appears the GF successfully deploys the
> ear (I can send the log file if that would help), but I'm not seeing
> the bean show up in the JNDI browser. Don't shoot me, but when I
> deploy the same application under JBoss 4 (with the EJB jar renamed to
> .ejb3, as per JBoss requirements :| ), JBoss automagically adds
> com.iecokc.products.IBrandNameProduct to JNDI, by which my (out of
> container) client can look up the bean. No such luck under glassfish.
> It's my understanding that, with EJB3, I don't need the extra
> deployment descriptors for session beans, etc., so what am I doing
> wrong?
>
> On a side note, Ed Burns wanted me to mention ##jsf on
> irc.freenode.net. Ed (and I think one or two other JSF developers)
> spends time there as part of his JSF work, and I'm there as a JSF
> user. He wanted me to encourage GF devs to come there. It would help
> me (and others, I'm sure, a LOT! :).
>
> At any rate, I appreciate any help you can give me!
>
> --
> Jason Lee
> Programmer/Analyst
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net