Oh, please don't tell me that EJB3 still requires that you bake
configuration into the deployed artifact. :(
I generally would use a JNDI based lookup for the connection that would
always be the same inside the code/configuration, and then you just need
to configure your server depending on wh
Hi,
I have a use case where I am trying to figure what might be an ideal (if
not best) way to deal with it.
For an EJB3 project I need to toy around with a
"META-INF/persistence.xml" which contains all the entity mappings.
There are two constraints:
1) Developers using Eclipse should not
