Deploying a J2EE web application in Oracle 10g

Question

Hi friends,
<br>
I had worked with Oracle9i 9.0.3 . But it's my first experience with Oracle 10g . I have installed Oracle 10g Infrastructure , Metadata Repository and one Middle tier - Forms and i hope i have followed The Oracle 10g installation guide Properly. Anyway installation is successful.
The problem is a J2EE web application which is deployed properly on Oracle9i 9.0.3 doesn't get deployed in Oracle 10g. The following is the exception :
<br>
Deployment failed: Nested exception
Root Cause: deploy failed!: ; nested exception is:
oracle.oc4j.admin.internal.DeployerException: Error initializing ejb-module; Exception Error in application Spom_Apps: Error loading package at file:/C:/Oracle/Ora9iASForms/j2ee/home/applications/Spom_Apps/JmsSubscriberMdb.jar, Error deploying file:/C:/Oracle/Ora9iASForms/j2ee/home/applications/Spom_Apps/JmsSubscriberMdb.jar homes: No location set for Topic resource MessageDrivenBean JmsReceiverMdb
<br>
<br>
where JmsReceiverMdb is the deployment file containing the message driven beans.
<br>
Thanks in advance,
paskal

Answer 1

Hi,
Thanks for responding . I am sending the file contents of ejb-jar.xml, orion-ejb-jar.xml, jms.xml.
Could you also check whether dtds versions of 10g and 9i in these xmls are conflicting? If you can specify your email-id i can send these file as attachments.
Hope you could strike the right spot.
ejb-jar.xml
<?xml version = '1.0' encoding = 'windows-1252'?>
<!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>
<description>Session Bean ( Stateless )</description>
<display-name>spomPmConfigSSB</display-name>
<ejb-name>spomPmConfigSSB</ejb-name>
<home>jnipackage.spomPmConfigSSBHome</home>
<remote>jnipackage.spomPmConfigSSB</remote>
<ejb-class>jnipackage.impl.spomPmConfigSSBBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<message-driven>
<description>Message Driven Bean</description>
<display-name>JmsReceiverMdb</display-name>
<ejb-name>JmsReceiverMdb</ejb-name>
<ejb-class>jnipackage.impl.JmsReceiverMdbBean</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<resource-ref>
<res-ref-name>jms/alarmTopicConnectionFactory</res-ref-name>
<res-type>javax.jms.TopicConnectionFactory</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>jms/alarmTopic</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
</resource-env-ref>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>JmsReceiverMdb</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>spomPmConfigSSB</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
Orion-ejb-jar.xml
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
<orion-ejb-jar>
<enterprise-beans>
<message-driven-deployment name="JmsReceiverMdb" max-instances="100" min-instances="0">
<resource-ref-mapping name="jms/alarmTopicConnectionFactory"/>
</message-driven-deployment>
<session-deployment name="spomPmConfigSSB"/>
</enterprise-beans>
<assembly-descriptor>
<default-method-access>
<security-role-mapping impliesAll="true" name="&lt;default-ejb-caller-role>"/>
</default-method-access>
</assembly-descriptor>
</orion-ejb-jar>
jms.xml
<?xml version="1.0" standalone='yes'?>
<!DOCTYPE jms-server PUBLIC "OC4J JMS server" "http://xmlns.oracle.com/ias/dtds/jms-server-9_04.dtd">
<jms-server port="9127">
<!-- Queue bindings, these queues will be bound to their respective
JNDI path for later retrieval -->
<queue name="Demo Queue" location="jms/demoQueue">
<description>A dummy queue</description>
</queue>
<!-- Topic bindings, these topic will be bound to their respective
JNDI path for later retrieval -->
<topic name="Demo Topic" location="jms/demoTopic">
<description>A dummy topic</description>
</topic>
<!-- Topic bindings, these topic will be bound to their respective
JNDI path for later retrieval -->
<topic name="AlarmQueue" location="jms/alarmTopic">
<description>A topic</description>
</topic>
<topic name="FaultTextQueue" location="jms/faultTextTopic">
<description>A topic</description>
</topic>
<topic name="FaultTopologyQueue" location="jms/faultTopologyTopic">
<description>A topic</description>
</topic>
<!-- path to the log-file where JMS-events/errors are stored -->
<log>
<file path="../log/jms.log"/>
<!-- Uncomment this if you want to use ODL logging capabilities
<odl path="../log/jms/" max-file-size="1000" max-directory-size="10000"/>
-->
</log>
<queue name="jms/OracleSyndicateQueue" location="jms/OracleSyndicateQueue">
<description>Oracle Syndication Services Queue</description>
</queue>
<!--
<queue-connection-factory name="jms/OracleSyndicateQueueConnectionFactory"
location="jms/OracleSyndicateQueueConnectionFactory"/>
-->
<queue-connection-factory location="jms/OracleSyndicateQueueConnectionFactory"/>
<queue name="jms/OracleUddiReplicationQueue"
location="jms/OracleUddiReplicationQueue">
<description>Queue for replication scheduler</description>
</queue>
<!--
<queue-connection-factory
name="jms/OracleUddiReplicationQueueConnectionFactory"
location="jms/OracleUddiReplicationQueueConnectionFactory"/>
-->
<queue-connection-factory location="jms/OracleUddiReplicationQueueConnectionFactory"/>
<queue name="jms/OracleWebClippingQueue"
location="jms/OracleWebClippingQueue">
<description>Queue for Web Clipping</description>
</queue>
<!--
<queue-connection-factory
name="jms/OracleWebClippingQueueConnectionFactory"
location="jms/OracleWebClippingQueueConnectionFactory"/>
-->
<queue-connection-factory location="jms/OracleWebClippingQueueConnectionFactory"/>
</jms-server>