Hi , I am encountering a strange exception while deploying a stateful bean in weblogic using appc . The following is the error
java.lang.NullPointerException at weblogic.ejb20.deployer.SessionBeanInfoImpl.assignDefaultTXAttributes IfNecessary()V(SessionBeanInfoImpl.java:295) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeTransaction Attribute(Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean V(MBeanD eploymentInfoImpl.java:807) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(Lweblogic.mana
The following is my ejb-jar.xml
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN' 'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
Below is an example from one of our SLSB deployment descriptors (we don't use much SFSB but they have a lot in common):
And as you can see right from the beginning your document root tag must be <ejb-jar> and not <weblogic-ejb-jar>. Also you notice that the session bean is defined within a <session> tag, entity beans will be defined within an <entity> tag, etc. Point is that I cannot tell you from the top of my head which part of your configuration settings are wrong, because we use XDoclet for generating our deployment descriptors and therefore I don't even know if your example will ever work following this format. You can check BEA's online documentation for more information about deployment descriptors. I only want to point out to you that you might consider other tools, like XDoclet or BEA's ejbgen in order to generate your deployment descriptors automatically and never bother about their format again. Regards.
I think, therefore I exist -- Rene Descartes
Joined: Mar 09, 2005
Apologize for posting wrong ejb-jar.xml . cut& paste error .errrr Please find below my descriptor xmls
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
As far as I can tell, your deployment descriptors look fine to me. There is only one more hint that I can give you: try to specify the session attributes for every method rather than using the global asterisk (*) notation. The reason I�m saying this is first because this is how we do with our SLSB and the second is because from what I remember the session beans do not allow specifying transaction attributes with create methods. Who knows, maybe WebLogic got confused, although I doubt. Beside that I�m clueless just like you Best regards.