[jboss-jira] [JBoss JIRA] Closed: (JBAS-6606) Specifying mdb-client-id in jboss.xml causes mdb deployments to fail

[Alexey Loubyansky (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Loubyansky closed JBAS-6606.
-----------------------------------

    Fix Version/s: JBossAS-6.0.0.Alpha1
       Resolution: Done


This is fixed. Thanks.

PS: as a consequence of JBAS-4666 and strictVerifier=true the testcase attached to this issue won't deploy due to deployment validation errors, i.e.

11:12:29,773 WARN  [verifier] EJB spec violation:
Bean   : TestBean
Section: 15.7.3
Warning: The message driven bean must declare one ejbCreate() method.

To make it deploy either fix the deployment or set strictVerifier=false in ejb-deployer-jboss-beans.xml.

> Specifying mdb-client-id in jboss.xml causes mdb deployments to fail
> --------------------------------------------------------------------
>
>                 Key: JBAS-6606
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6606
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: System service
>    Affects Versions: JBossAS-5.0.1.GA
>         Environment: Java5 Win32/Linux JBoss 5.0.1.GA
>            Reporter: Brent Atkinson
>            Assignee: Alexey Loubyansky
>             Fix For: JBossAS-5.1.0.CR1, JBossAS-6.0.0.Alpha1
>
>         Attachments: destinations-service.xml, JBAS-6606-Test-src.zip, jbas-6606-test.jar, JBAS-6606.patch
>
>
> Deploying MDBs with jboss.xml descriptor specifying the mdb-client-id causes the deployment to fail with an IntrospectionException. The problem is that line 87 in
> server/src/main/org/jboss/ejb/plugins/inflow/JBossJMSMessageEndpointFactory.java specifies the clientId property as clientID. Changing it to clientId fixes it.
> Caused by: java.beans.IntrospectionException: No property found for: clientID on JavaBean: org.jboss.resource.adapter.jms.inflow.JmsActivationSpec at d8c235(ra=null destination=null destinationType=null tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
>         at org.jboss.util.propertyeditor.PropertyEditors.mapJavaBeanProperties(PropertyEditors.java:354)
>         at org.jboss.util.propertyeditor.PropertyEditors.mapJavaBeanProperties(PropertyEditors.java:285)
>         at org.jboss.resource.deployment.ActivationSpecFactory.createActivationSpec(ActivationSpecFactory.java:129)
>         ... 137 more

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira