dev@glassfish.java.net

Re: EJB Session Bean Deployment

From: Bill Shannon <bill.shannon_at_sun.com>
Date: Wed, 25 Jan 2006 13:47:37 -0800

In Java EE 5, your life will be much simpler if you don't bother
with the application.xml file. Just create an ear file that
contains bnpr.jar, along with all the other jar files in a "lib"
subdirectory. Nothing else, no application.xml, no special
MANIFEST.MF (just the one the jar tool creates for you by default).


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
>