There's a EMF injection (Spring understands the annotation as well). I'm not
sure about the problem but it throws a NPE and log4j appenders are not
configured. I've found a workaround renaming persistence.xml (somehow
Glassfish is fine with this) and setting the location directly to Spring.
On Wed, Sep 10, 2008 at 10:33 PM, Marina Vatkina <Marina.Vatkina_at_sun.com>wrote:
> If there are no EM/EMF injection or lookup, JPA should be ignored until
> used. What kind of deployment problems do you encounter?
>
> thanks,
> -marina
>
>
> Jose Noheda wrote:
>
>> Hi,
>>
>> While deploying a WAR file that includes a persistence.xml Glassfish
>> starts the JPA deployment. I'd like to use Spring JPA support instead this
>> time (because the production server does not support JEE yet..). This would
>> be no problem (other than an increased deployment time) if it wasn't for a
>> log4j init error that happens and leaves me with no traces. This of course
>> is a deal breaker so I'm wondering how can I disable the automatic discovery
>> of JPA.
>>
>> Regards
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>