BTW, the reason I said you relied on a non-portable feature is because
the JPA 1.0 spec says the following in section #6.2:
/A persistence unit is defined by a persistence.xml file. The jar file
or directory whose META-INF
directory contains the persistence.xml file is termed the root of the
persistence unit. In Java EE,
the root of a persistence unit may be one of the following:
• an EJB-JAR file
• the WEB-INF/classes directory of a WAR file[40]
• a jar file in the WEB-INF/lib directory of a WAR file
• a jar file in the root of the EAR
• a jar file in the EAR library directory
• an application client jar file
/
Thanks,
Sahoo
Sahoo wrote:
> Then, you just relied on a non-portable feature of JBoss. You don't
> have to deploy to an application server to test if tables are created
> properly or not. You can just use JPA in standalone Java SE to test
> that. See GlassFish JPA webpage for more details.
>
>
> glassfish_at_javadesktop.org wrote:
>> you're right but it could be useful if you want to check tables are
>> created correctly. When I used JBoss last year, I created entities
>> without sessions.
>> [Message sent by forum member 'mstn' (mstn)]
>>
>> http://forums.java.net/jive/thread.jspa?messageID=345219
>>
>> ---------------------------------------------------------------------
>> 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
>