On 6/18/2010 5:41 PM, Sanjeeb Sahoo wrote:
> Perhaps this can be achieved by @DataSourceDefinition, can't it? I
> know it currently does work in context of JPA, but that's a bug I guess.
The end user will still need to open up the archive to edit something,
isn't it? If we can provide an override on command line during
deployment, it would be more user friendly. What do you think?
Thanks,
Mitesh
>
> Sahoo
> On Friday 18 June 2010 11:38 PM, Mitesh Meswani wrote:
>> Please file an RFE against enetity-persistence component to track this.
>>
>> Thanks,
>> Mitesh
>> On 6/18/2010 1:35 AM, glassfish_at_javadesktop.org wrote:
>>> Situation: I have a WAR containing a persistence.xml, where a PU is
>>> defined and where the jta-data-source is set and points to a jdbc
>>> resource.
>>>
>>> The issue I have is that I need multiple instances of this WAR for
>>> different purposes, and each of these instances should point to a
>>> different jdbc resource.
>>>
>>> I am wondering if this is something that can be done at deploy-time
>>> (e.g. like deploying a war on a specific contextoor). Currently, I
>>> have to open the WAR, change the persistence.xml, rebuild it, and
>>> repeat this process for every instance. It would be nice if I can
>>> specify the jta-data-source of a persistence-unit at deploy time.
>>>
>>> Any ideas?
>>> [Message sent by forum member 'johanvos']
>>>
>>> http://forums.java.net/jive/thread.jspa?messageID=474789
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>