Moving this discussion to the persistence alias.
Peter, Tom, Gordon,
We have other properties which names may cause conflicts:
I know of the database-related names, like "jdbc.driver", etc.
Are there any others?
Do you see any problem, if they are changed?
thanks,
-marina
Ludovic Champenois wrote:
> Marina Vatkina wrote:
>
>> Mitesh Meswani wrote:
>>
>> > Please note that you can enable java2db through command line using
>> > "asadmin deploy --dropandcreatetables=true ......" or having a property in
>> > your persistence.xml as follows
>> >
>> > <?xml version="1.0" encoding="UTF-8"?>
>> > <persistence ..... >
>> > <persistence-unit name ="em" >
>> > <properties>
>> > <!-- for generating derby specific sql -->
>> > <property name="toplink.platform.class.name" value="oracle.toplink.essentials.platform.database.DerbyPlatform"/>
>> >
>> > <!-- To enable java2db Please note that this property name may change in future -->
>> > <property name="ddl-generation" value="dropandcreate"/>
>> >
>>
>> I think that we need to change the name to be something
>> that guaranteed to be unique. Even toplink.essentials.ddl-generation
>> is more definite.
>>
>> My $.02.
>>
>> -marina
>
> Yes, property names should try to be unique across vendors, otherwise
> developers using tools like Eclipse or NetBeans will not be able to switch
> back and forth quickly between server targets for the same Java EE5 project.
> The best way to achieve this is to use consistently some product specific
> prefix.
> Ludo