Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] JVM properties vs persistence.xml

The EntityManagerFactory creation methods both in APPLICATION managed and JTA modes take a list of properties. That list can be used to override any of the properties defined in persistence.xml.

-Tom

On 02/12/2011 12:48 PM, Mark Robinson wrote:
Could you use a deployment descriptor file to change the value in
persistence.xml without having to rebuild?

Mark

On Fri, Dec 2, 2011 at 9:25 AM, Nathan Drew <Nathan.Drew@xxxxxxxxxxxxxxxxxxxxx
<mailto:Nathan.Drew@xxxxxxxxxxxxxxxxxxxxx>> wrote:

    Hi,____

    __ __

    Having gone through the process of needing to vary the logging levels for
    EclipseLink, and thinking of the case when we might have to support a
    customer using our application and want to get more debug information from
    them without rebuilding our application from scratch… shouldn’t the JVM
    property for eclipselink.logging.level override the value set in
    persistence.xml?____

    __ __

    That’s the general model in most JEE things - configure in the app, then
    allow the "deployer" to override values.____

    __ __

    Was this the case for Toplink Essentials?____

    __ __

    Kind Regards____

    Nathan____

    __ __


    _______________________________________________
    eclipselink-users mailing list
    eclipselink-users@xxxxxxxxxxx <mailto:eclipselink-users@xxxxxxxxxxx>
    https://dev.eclipse.org/mailman/listinfo/eclipselink-users




_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users


Back to the top