[Russ]

I am porting my code from WSAD 5.1.1 to MyEclipse 5.1. I have stripped out all the IBM specifc bindings and starting from scratch. One of the first things I am doing is in the EJB Project, I am letting the XDoclet Tool within MyEclipse generate the Stubs and Skeltons for the EJBs. Presently, the XDoclet tool likes my Session beans, but the XDoclet tools fails when it gets to my MDBs. I base this on the fact the ejb-jar.xml file is stopped at the point where the MDBs would go.

This is the xdoclet commands I have in the MDB:

  @weblogic.message-driven
       @destination@
        @connection@

   @jboss.destination-jndi-name="queue/GETCREATEWORKTC"
   @weblogic.transaction-descriptor trans-timeout-seconds="270"
  
   @weblogic.pool
       initial-beans-in-free-pool="10"
       max-beans-in-free-pool="10"
  
   @weblogic.enable-call-by-reference True
   @weblogic.run-as-identity-principal True
  
   @ejb.bean
        transaction-type="Container"
        acknowledge-mode="Auto-acknowledge"
        destination-type="javax.jms.Queue"
        subscription-durability="Durable"
        
        
   @ejb.transaction type="Required"
  
   @ejb.ejb-external-ref
        view-type="remote"
        link="WorkFlowEJB"
        ref-name="ejb/WorkFlowEJBHome"
        type="Session"
        home="com.company.dept.product.ejb.workflow.WorkFlowEJBRemoteHome"
        business="com.company.dept.product.ejb.workflow.WorkFlowEJBRemote"
   
   @ejb.resource-ref res-ref-name = "jms/MQTC"
                     res-type = "javax.jms.QueueConnectionFactory"
                     res-auth = "Container"
                        res-sharing-scope="Shareable"
   
   @ejb.resource-ref res-ref-name = "jms/MQERROR"
                     res-type = "javax.jms.QueueConnectionFactory"
                     res-auth = "Container"
                        res-sharing-scope="Shareable"
   
   @ejb.resource-env-ref  name="jms/ACKTOTC"
                             type="javax.jms.Queue"
   
   @ejb.resource-env-ref  name="jms/ERRORQ"
                             type="javax.jms.Queue"
   
   @weblogic:resource-description res-ref-name = "jms/MQTC"
                          jndi-name = "jms.MQTC"
   
   @weblogic:resource-description res-ref-name = "jms/MQERROR"
                          jndi-name = "jms.MQERROR"
   
   @weblogic:resource-env-description  res-env-ref-name="jms/ACKTOTC"
                             jndi-name="jms.ACKTOTC"
   
   @weblogic:resource-env-description  res-env-ref-name="jms/ERRORQ"
                             jndi-name="jms.ERRORQ"

This is the error message I get from running the XDoclet command from within MyEclipse:

[ejbdoclet] Generating EJB deployment descriptor (ejb-jar.xml).
[ejbdoclet] (XDocletMain.start                   53  ) Running XDoclet failed.
[ejbdoclet] (XDocletMain.start                   54  ) <<class_not_abstract arguments: [Ljava.lang.String;@2af8f5>>
[ejbdoclet] C:\PivotWorkSpaceForMyEclipse\PowerImageEJB\.xdoclet-build.tmp.xml:53: XDoclet failed.
[ejbdoclet] at xdoclet.DocletTask.start(DocletTask.java:471)
[ejbdoclet] at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:105)
[ejbdoclet] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)

Some of the things I tried to debug this error was:

[1] Remove the company specific XDoclet commandes, such as @weblogic
[2] Remove all JavaDoc comments, such as @author
[3] Double check each ejb command to ensure all references are properly used.
[4] Check to see if an outstaning issue is documented with XDoclet.

I am still getting the error and I am at a lost on what could be causing this error.

Any help would be greatly appreciated. We really like the MyEclipse tool and want to make it work for all of our developers.

Thanks as always for great support and comments from this forum.

Russ

[Russ]

The reason why JBoss does not like my MDB is because XDoclet command for jboss is in correct!

It should be:

              @jboss.destination-jndi-name
                  name="queue/GETCREATEWORKTC"           
     

Just sharing with others so they don’t have the same problem.

Russ

[Greg]

Thanks for posting the resolution.

[Author]

Posts