You're right, I had no resource-env-ref in my ejb-jar.xml.
I added this now to all my ejb's, declared in ejb-jar.xml, but I still got 3
warnings, 5 warning are resolved.
Here is my ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="...">
<description>application</description>
<display-name>name</display-name>
<enterprise-beans>
<message-driven>
<ejb-name>OutboundMessageListenerServiceImpl</ejb-name>
<ejb-class>...</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Bean</transaction-type>
<ejb-local-ref>
<ejb-ref-name>...</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local>...</local>
</ejb-local-ref>
<resource-env-ref>
<resource-env-ref-name>jms/import_2_owner_header</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>
</message-driven>
<message-driven>
<ejb-name>DocumentImportHeaderMessageListenerServiceImpl</ejb-name>
<ejb-class>...</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Bean</transaction-type>
<ejb-local-ref>
<ejb-ref-name>...</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local>...</local>
</ejb-local-ref>
<resource-env-ref>
<resource-env-ref-name>jms/import_2_owner_header</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>
</message-driven>
<message-driven>
<ejb-name>LotusDominoGatewayInboundMessageListenerServiceImpl</ejb-name>
<ejb-class>...</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Bean</transaction-type>
<ejb-local-ref>
<ejb-ref-name>...</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local>...</local>
</ejb-local-ref>
<resource-env-ref>
<resource-env-ref-name>jms/import_2_owner_header</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>
</message-driven>
</enterprise-beans>
</ejb-jar>
Here are the warnings again:
08:32:16,747 WARN [AdminObjectRefBuilder] Failed to build reference to
Admin object reference [jms/import_2_owner_header] defined in plan file,
reason - corresponding entry in deployment descriptor missing.
08:32:16,930 WARN [AdminObjectRefBuilder] Failed to build reference to
Admin object reference [jms/import_2_owner_header] defined in plan file,
reason - corresponding entry in deployment descriptor missing.
08:32:17,324 WARN [AdminObjectRefBuilder] Failed to build reference to
Admin object reference [jms/import_2_owner_header] defined in plan file,
reason - corresponding entry in deployment descriptor missing.
Is it possible, that I must also add an corresponding entry to my
openejb-jar.xml?
The open-ejb-jar.xml is the following:
<openejb-jar xmlns="...">
<enterprise-beans>
<session>
<ejb-name>OutboundMessageHandlerService</ejb-name>
<ejb-ref>
<ref-name>OutboundMessageHandlerService</ref-name>
<ejb-link>OutboundMessageHandlerService</ejb-link>
</ejb-ref>
</session>
<message-driven>
<ejb-name>OutboundMessageListenerServiceImpl</ejb-name>
<resource-adapter>
<resource-link>mq.resource.adapter</resource-link>
</resource-adapter>
<ejb-ref>
<ref-name>OutboundMessageListenerServiceImpl</ref-name>
<ejb-link>OutboundMessageListenerServiceImpl</ejb-link>
</ejb-ref>
</message-driven>
<message-driven>
<ejb-name>DocumentImportHeaderMessageListenerServiceImpl</ejb-name>
<resource-adapter>
<resource-link>mq.resource.adapter</resource-link>
</resource-adapter>
</message-driven>
<message-driven>
<ejb-name>LotusDominoGatewayInboundMessageListenerServiceImpl</ejb-name>
<resource-adapter>
<resource-link>mq.resource.adapter</resource-link>
</resource-adapter>
</message-driven>
</enterprise-beans>
</openejb-jar>
--
View this message in context:
http://www.nabble.com/WARN---AdminObjectRefBuilder--Failed-to-build-reference-to-Admin-object-reference-tp20892287s134p20930397.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
