In JBoss EAP 5.x every JAR shipped by it will be signed. You can check the files (META-INF/
JBOSSCOD.SF, META-INF/JBOSSCOD.SF) indicating that those are signed:
In your case as you are using "org.hibernate.dialect.DMSQLDialect" class, Which definitely be extending the "org.hibernate.dialect.Dialect" As the class "org.hibernate.dialect.Dialect" is loaded as part of "$JBOSS_HOME/common/lib/hibernate-core.jar" with signature (as this JAR is signed) and Your application JAR which is having class "org.hibernate.dialect.DMSQLDialect" is either not signed or signed with a different key hence you are getting this "signer information" mismatch error.
So either you will need to make sure that either your application does not see any Hibernate specific classes loaded by JBoss EAP5.
(Not Much recommended way, but this should work). Take a backup of the above mentioned hibernate-core.jar which is provided by JBoss. You will need to make sure that the JBoss EAP 5 jars are not signed. So remove the signature information from it :
zip -d $JBOSS_HOME/common/lib/hibernate-core.jar META-INF/JBOSSCOD.*
Now try running your application to see if it works.
Thanks for your response.
Its working after removing "META-INF/JBOSSCOD.*" files in following hibernate jar files
Is it OK to leave these files without signed in production because "org.hibernate.dialect.DMSQLDialect" class in third party jar files which we don't have source code to correct what you suggested to change package structure.