That should not be a problem if you make sure to have your data sources configured with one unique jndi-name.

Yes, the jndi name in the persistence.xml is static, but it does a name lookup and as long as your *-ds.xml maps the database to the same name, it could just work.

Just note that this presumes that only *one* *-ds.xml uses that jndi name.

Actually you can change the names to whatever you want.
They just have to match in the areas I have listed below.

Check your [database]-ds.xml (located in your deploy dir) and look for a tag <jndi-name>SomeName</jndi-name>.

That is the name under which the datasource registers itself.

That name is also used in the persistence.xml located under .
<jta-data-source>java:/SomeName</jta-data-source>

Just make sure the two names are the same (copy & paste it .. trust me ;) ).

Or, maybe I am not getting it. Just to verify the setup:
You have a [database]-ds.xml in your deploy directory and a persistance.xml in your [project]/META-INF/ dir.

It is also probably also just have two *-ds.xmls in your deploy directory giving you access to the database. Just tried it and at least they both register themselves.

You can even have a per-database-level in the *-ds.xml.

Make sure the file name and the JNDI names are different then the first.

Dumb question and not trying to be a jerk, but why do you have to wait until deployment time?

Who is the 'other products'?

So if I understand you correctly, you only supply the component and otherwise have zero access or control over the rest of the jboss?

Then that is not so good ;)

My original idea was to have you hardcode your jndi source name and then add a *-ds.xml to the deployment.

A brute force might be to write your own *-ds.xml into the deploy dir, but I have no idea if that is even possible.

I have similar issues, but I need to switch data sources at runtime.

I think we need some kind of dynamic data source system.

Sorry for the lack of help.