Simple EJB deployment issue - help please.

[George]

I need some ideas here, I'm not getting good messages from the
software.

I'm trying to get a hello world deployed to weblogic 9.0, and I'm
getting a strange NPE from weblogic.Deployer, the top of which is:

java.lang.NullPointerException
at
weblogic.ejb20.deployer.SessionBeanInfoImpl.assignDefaultTXAttributes
IfNecessary(SessionBeanInfoImpl.java:323)
at
weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeTransaction
Attribute(MBeanDeploymentInfoImpl.java:818)
at
weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymen
tInfoImpl.java:229)
at
weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1165)
at
weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:344)
at
weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:90)

My ejb-jar.xml is:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.
0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">

<ejb-jar >
<enterprise-beans>
<session >
<ejb-name>hw</ejb-name>
<home>hw.hwHome</home>
<remote>hw.hw</remote>
<ejb-class>hw.hwSession</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor >
<container-transaction>
<method>
<ejb-name>hw</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

And for weblogic:
<?xml version="1.0"?>

<!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'>

<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>hw</ejb-name>
<jndi-name>hw-jndi</jndi-name>
<weblogic-enterprise-bean/>
<weblogic-ejb-jar/>

[a***@gmail.com]

What does your config.xml look like?

[George]

I haven't touched this, and the ejb jar I compiled from the weblogic
examples deploys fine, I'm currently making the dd look identical to
that of the example, but that didn't work either.
Must be something in the actual class file.

Here is the config.xml, you can see the example ejb that correctly
deployed there:

<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://www.bea.com/ns/weblogic/90/domain"
xmlns:sec="http://www.b
ea.com/ns/weblogic/90/security"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-inst
ance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls"
xsi:schemaLocat
ion="http://www.bea.com/ns/weblogic/90/domain.xsd">
<name>base_domain</name>
<security-configuration>
<name>base_domain</name>
<realm>
<sec:authentication-provider
xsi:type="wls:default-authenticatorType"></se
c:authentication-provider>
<sec:authentication-provider
xsi:type="wls:default-identity-asserterType">

<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper
xsi:type="wls:default-role-mapperType"></sec:role-mapper>

<sec:authorizer
xsi:type="wls:default-authorizerType"></sec:authorizer>
<sec:adjudicator
xsi:type="wls:default-adjudicatorType"></sec:adjudicator>

<sec:credential-mapper
xsi:type="wls:default-credential-mapperType"></sec:
credential-mapper>
<sec:cert-path-provider
xsi:type="wls:web-logic-cert-path-providerType"></
sec:cert-path-provider>

<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
</realm>
<default-realm>myrealm</default-realm>

<credential-encrypted>{3DES}JfArkRef6Ec5NBIwMhXp6uyNilzgZHvbxZz9c3OuL9pYTPaF
Hih+IRB6kqcZGU8zj4j1AqB8pccmBbpvQwURVd2XH1al5JeM</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>

<node-manager-password-encrypted>{3DES}Ny7PrqC2kf0H2spJ2laUlg==</node-manage
r-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<idle-connection-timeout>3600</idle-connection-timeout>
<listen-address></listen-address>
</server>
<embedded-ldap>
<name>base_domain</name>

<credential-encrypted>{3DES}ruvf+AcTQszGNBq76BOCgjEis3eEZ8VpW5yHaWmzipk=</cr
edential-encrypted>
</embedded-ldap>
<configuration-version>9.0.0.0</configuration-version>
<app-deployment>
<name>iiop_ejb_stateless</name>
<target>AdminServer</target>
<module-type>ejb</module-type>

<source-path>/home/gfinklang/agejb/bea/iiop_ejb_stateless.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<admin-server-name>AdminServer</admin-server-name>
</domain>

[George]

Turns out this was an issue with the EJBs I had that were generated by
JBOSS-Eclipse - the remote interface wasn't an interface. A cryptic
error message. Now I'm having a problem with appc, I'll post that
under a different title.