[jira] Commented: (OPENEJB-701) EJB 2.0 depricated message-driven-destination tag not supported

["David Blevins (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OPENEJB-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531959 ] 

David Blevins commented on OPENEJB-701:
---------------------------------------

The correct way around this is to convert that element to the EJB 2.1 and higher activation-config.

{code:xml}
<message-driven>
  <activation-config>
     <activation-config-property>
       <activation-config-property-name>destinationType</activation-config-property-name>
       <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
     </activation-config-property>
  </activation-config>
</message-driven>
{code}

> EJB 2.0 depricated message-driven-destination tag not supported
> ---------------------------------------------------------------
>
>                 Key: OPENEJB-701
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-701
>             Project: OpenEJB
>          Issue Type: Bug
>    Affects Versions: 3.0-beta-1
>            Reporter: David Blevins
>             Fix For: 3.0-beta-2
>
>
> <?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> ...
>          <message-driven> ...
>          	<message-driven-destination>
> <destination-type>javax.jms.Queue</destination-type>
>          	</message-driven-destination>
> At deployment the following error is produced:
> ... Caused by: javax.xml.bind.UnmarshalException: unexpected element
> (uri:"http://java.sun.com/xml/ns/javaee",
> local:"message-driven-destination").

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.