Well,
I've started from zero again...
The first I made was to write the geronimo-application.xml. This descriptor
works in my assumption.
Then I created the openejb-jar.xml in the JAR/META-INF, but this is not being
deployed. The errors occuring are the following:
Using GERONIMO_BASE: C:\ApplicationServers\geronimo-1.1
Using GERONIMO_HOME: C:\ApplicationServers\geronimo-1.1
Using GERONIMO_TMPDIR: C:\ApplicationServers\geronimo-1.1\var\temp
Using JRE_HOME: C:\Programme\Java\jre1.5.0_06
Error: Unable to distribute connector.ear: Currently a Geronimo
deployment plan is required for an EJB module. Please provide a
plan as a deployer argument or packaged in the EJB JAR at
META-INF/openejb-jar.xml
#########################################################################
I'll post the openejb-jar.xml too:
<openejb-jar
xmlns="http://www.openejb.org/xml/ns/openejb-jar-2.1"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://www.openejb.org/xml/ns/openejb-jar-2.1"
schemaLocation="openejb-jar-2.1.xml" />
<enterprise-beans>
<session>
<ejb-name>IDocEJB</ejb-name>
<jndi-name>ManagerBeansJAR/IDocEJB</jndi-name>
</session>
<session>
<ejb-name>AdapterEJB</ejb-name>
<jndi-name>ManagerBeansJAR/AdapterEJB</jndi-name>
</session>
<session>
<ejb-name>FilesystemEJB</ejb-name>
<jndi-name>ManagerBeansJAR/FilesystemEJB</jndi-name>
</session>
<session>
<ejb-name>EJBClientInterfaceEJB</ejb-name>
<jndi-name>ClientInterfaceJAR/EJBClientInterfaceEJB</jndi-name>
</session>
<session>
<ejb-name>DbScannerEJB</ejb-name>
<jndi-name>ManagerBeansJAR/DbScannerEJB</jndi-name>
</session>
<session>
<ejb-name>AdministrationEJB</ejb-name>
<jndi-name>ManagerBeansJAR/AdministrationEJB</jndi-name>
</session>
</enterprise-beans>
</openejb-jar>
#########################################################################
And the jboss.xml, which is located in the same directory:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN"
"http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd">
<jboss>
<!-- specifiy the JAAS domain -->
<security-domain>java:/jaas/transconnect</security-domain>
<!-- bind the EJBs to JNDI -->
<enterprise-beans>
<session>
<ejb-name>IDocEJB</ejb-name>
<jndi-name>ManagerBeansJAR/IDocEJB</jndi-name>
</session>
<session>
<ejb-name>AdapterEJB</ejb-name>
<jndi-name>ManagerBeansJAR/AdapterEJB</jndi-name>
</session>
<session>
<ejb-name>FilesystemEJB</ejb-name>
<jndi-name>ManagerBeansJAR/FilesystemEJB</jndi-name>
</session>
<session>
<ejb-name>EJBClientInterfaceEJB</ejb-name>
<jndi-name>ClientInterfaceJAR/EJBClientInterfaceEJB</jndi-name>
</session>
<session>
<ejb-name>DbScannerEJB</ejb-name>
<jndi-name>ManagerBeansJAR/DbScannerEJB</jndi-name>
</session>
<session>
<ejb-name>AdministrationEJB</ejb-name>
<jndi-name>ManagerBeansJAR/AdministrationEJB</jndi-name>
</session>
</enterprise-beans>
</jboss>
#########################################################################
As I've read is the content in the openejb-jar.xml nearly the same like in
jboss.xml (thanks to Kanchana for the links).
You can also see, that I am using the schema 'openejb-jar-2.1'. I've traversed
through it and built the XML with the knowledge I won from traversing...
But why is the stack trace occuring?!?
FYI both XML's are in the META-INF directory of the JAR, which itself is
contained in the EAR. (for EAR-structure have a look at the beginning of this
thread)
Thanks, mika
--
Echte DSL-Flatrate dauerhaft für 0,- Euro*. Nur noch kurze Zeit!
"Feel free" mit GMX DSL: http://www.gmx.net/de/go/dsl