[jboss-jira] [JBoss JIRA] (AS7-6245) ClassNotFoundException if CMP2 entity-command is used

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/AS7-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799497#comment-12799497 ] 

RH Bugzilla Integration commented on AS7-6245:
----------------------------------------------

Jan Martiska <jmartisk at redhat.com> made a comment on [bug 901279|https://bugzilla.redhat.com/show_bug.cgi?id=901279]

This seems to be fixed since EAP 6.1.0, but never got past the NEW state.

[jmartisk at dhcp-4-171 jboss-eap]$ git tag --contains 49756911
7.2.0.Final
7.2.0.Final-prerelease1
8.0.0.Alpha1
8.0.0.Alpha2
8.0.0.Alpha3
8.0.0.Alpha4
EAP_6.1.0.GA-dev
EAP_6.1.1.ER1
EAP_6.1.1.ER2
EAP_6.1.1.ER3
EAP_6.1.1.ER4
EAP_6.1.1.ER5-dev
EAP_6.1.1.ER5.1-dev
EAP_6.1.1.ER6-dev
EAP_6.1.1.ER7-dev

Didn't reproduce the behavior. Anyway I see a little issue with the provided fix:

cmp/src/main/java/org/jboss/as/cmp/CmpMessages.java, line 604:
@Message(id = 18574, value = "Could not load org.jboss.resource.adapter.jdbc.StatementAccess")

This error message string should be updated to org.jboss.jca.adapters.jdbc.StatementAccess too, such error would be confusing to the user, if it references the wrong class.
                
> ClassNotFoundException if CMP2 entity-command is used
> -----------------------------------------------------
>
>                 Key: AS7-6245
>                 URL: https://issues.jboss.org/browse/AS7-6245
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB
>            Reporter: Wolf-Dieter Fink
>            Assignee: Wolf-Dieter Fink
>              Labels: cmp, ejb2
>             Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP)
>
>
> If a EJB2 - CMP2 EntityBean uses an entity-command 'mysql-get-generated-keys' to generate the primary key, the server deploy with an error message:
> Caused by: java.lang.RuntimeException: JBAS018572: Could not load driver class: com.mysql.jdbc.PreparedStatement
> This may happen for different entity-commands if other databases are used!
> If the datasource module is added to the org/jboss/as/cmp modules dependencies, the startup shows:
> MSC000001: Failed to start service ...  : JBAS010785: Failed start store manager
> Caused by: java.lang.RuntimeException: JBAS010732: Couldn't create entity command
> Caused by: java.lang.RuntimeException: JBAS018574: Could not load org.jboss.resource.adapter.jdbc.StatementAccess

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira