It's a component and could be integrate with a variety of products, but the
huge data volume makes web service not a good candidate in such a case. While
lack of pointing to a different data source at deployment time, it is a big gap
to enable componentize in EJB3 environment. We do not expect t
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 origi
Frank,
Maybe my explaination is not clear enough. The problem I am having now is my
component does not know the data source JNDI name upfront until at deployment
time. I can not endure other products will deploy a data source with the JNDI
name exactly match what I defined in persistence.xml, b
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
SomeName.
That is the name under which the datasource registers itself.
That name is also used in the pe
Frank,
I can see this point, but I have no control how the data source named and JNDI
registered as they are from different products. All I can is let them tell my
component what is their datasources and where are them. Now even I got these
information, I have no way to inject into the EntityM
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
