The missing class tpg/commons/exceptions/BusinessEntityFindException is part of your succesfully deployed jar and TPGApp.jar is the one failing?

Classes are not shared between deployment units.

You have to explecitly define a dependency. The easiest option is to define this when building your jar by adding this to your manifest file like I did here:

For questions about JBoss AS7 you should use the forum named so.

This question is not related to JBossWeb as far as I can see.

I'm using apache ant to build.

The manifest file contains version, ant-version and java-version:

Manifest-Version: 1.0

Ant-Version: Apache Ant 1.8.3

Created-By: 1.6.0_32-b05 (Sun Microsystems Inc.)

So you probably use something different, but may be it helps you to see how I'm doing this.

Within my ant build script my ear-file is build this way:

The name of the modules the current one depends on are always "deployment.<file name>".

You add only the deployment unit in your manifest as dependenciy.

For TPGApp.jar this means you add "Dependencies: deployment.TPGCommons.jar" to the manifest file.

TPGApp.jar contains META-INF/persistence.xml containing persistence-unit with name "TPGAppPU"?

Where is "TPG connection" coming from?

To few information to really help you.

Looks good.

Only you might use version 2.0:

<persistence xmlns="http://java.sun.com/xml/ns/persistence"

             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

             xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd"

             version="2.0">

...

And it's located in META-INF folder?

Of which file? App? Commons?

Is the PU detected and activated according to the server.log / console output?

I have no experience with -ds.xml file inside jar.

Either put it into standalone.xml or as a seperate file into the deployments folder.

But as far as I understand, you now have it twice. I think this is no good idea.

It might be a good idea to provide your standalone.xml file and your server.log file.

BTW, your using standalone.xml as base or standalone-full.xml?

And perhaps a "jar -tvf" of each of your three deployment files.

It would be nice if you let me/us know, what the problem was that you fixed now.

My datasource section looks like this:

The mentioned names (ifxjdbc_all.jar, ojdbc6.jar, sqljdbc4.jar) reference the JDBC drivers also simply deployed by putting the files into the deployments directory.

No experience with mysql from my side.

Did you create a module for the mysql-driver under $JBOSS_HOME/modules/com/mysql/? If not, rename the driver and erase the module attribute.

Or did you also drop mysql*.jar into deployments folder? Or is it part of your deployment unit (TPGApp.jar)?

To mention the xa-datasource-class is only needed when you're going to use it. I use it, you don't.

If the used JDBC driver is JDBC4 compliant, the datasource-class (non-XA) is automatically detected.

My DefaultDS is deployed as a file named DefaultDS-ds.xml in the deployments folder.:

<?xml version="1.0" encoding="UTF-8"?>

<datasources xmlns="http://www.jboss.org/ironjacamar/schema">

  <datasource jndi-name="DefaultDS" enabled="true" use-java-context="true" pool-name="DefaultDS">

    <connection-url>jdbc:informix-sqli://sb2000:9088/jboss7:INFORMIXSERVER=sb2000_net;NEWCODESET=8859_15,8859-1,819;LOBCACHE=-1</connection-url>

    <driver>ifxjdbc_all.jar</driver>

    <security>

      <user-name>mbi</user-name>

      <password>XXXXXX</password>

    </security>

  </datasource>

</datasources>

The syntax in standalone.xml is the same.

But because of the Illegal Argument Invalid value specification TPG connection I'd try to define the JNDI name without spaces.

Maybe also for the pool-name.

Why "jta=false"? The persistence.xml file you showed had transaction-type JTA and references a jta-data-source.

And the name of the jta-data-source in persistence.xml should certainly be the same as in your datasource definition.

So the error message from before is back again? I get irritated.

So let's start at the beginning.

For every database driver 2 options are available: module or deployment. There are pros and cons for both.

I preferred the deployment option. But only use one of them!

The module option is described so many times, e.g. at https://zorq.net/b/2011/07/12/adding-a-mysql-datasource-to-jboss-as-7/.

As you see, it's no sufficient to have the jar file in this folder, you also have to provide a module.xml file.

I downloaded mysql-connector-java-5.1.20-bin.jar and simply dropped it to the deployments folder.

On console output and in server.log I see then:

18:36:43,228 INFO  [org.jboss.as.server.deployment#start] JBAS015876: Starting deployment of "mysql-connector-java-5.1.20-bin.jar"

18:36:43,388 INFO  [org.jboss.as.connector.deployers.jdbc#deploy] JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)

18:36:43,558 INFO  [org.jboss.as.server#execute] JBAS018559: Deployed "mysql-connector-java-5.1.20-bin.jar"

Creating the module as described in the article and removing the jar file from the deployments folder I see:

18:50:03,627 INFO  [org.jboss.as.connector.subsystems.datasources#startDriverServices] JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)

So when you start your clean JBoss (unmodified standalone.xml, no deployments, ...) with either the added module or the jar file in the deployments folder do you see success message like the one above?

If yes, then proceed with step 2, add your datasource as described in the mentioned article to your standalone.xml.

Do you see the "Bound data source" message then?

Then add your TPGCommons.jar to the deployments folder. Deploying OK? Check server.log.

If yes,  then add TPGApp.jar to the deployments folder.

If you get the same error as before, (about the PU), then check the server.log file. There are additonal messages to help you, only the last lines is not enough to help.

Add the whole server.log file as an attachment to your response. The links to the gif files your provided before where not accessible for me.