[
https://issues.jboss.org/browse/AS7-6245?page=com.atlassian.jira.plugin.s...
]
Wolf-Dieter Fink moved JBPAPP6-1749 to AS7-6245:
------------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform
6)
Key: AS7-6245 (was: JBPAPP6-1749)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: (was: EAP 6.0.1)
(was: EAP 6.0.0)
Component/s: EJB
(was: EJB)
Security: (was: Public)
Docs QE Status: (was: NEW)
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
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