Re: [eclipselink-users] JPA and MOXy

[Shaun Smith <shaun.smith@xxxxxxxxxx>]

Hi Roger,

   I'd do my JPA mapping with an orm.xml (or eclipselink-orm.xml) file. This way, you can recompile your schema without losing your JPA mappings.  Also, I'd use Dali to create my JPA mappings.  It provides UI to let you avoid hand coding the JPA xml mapping file.  And if you update your schema and break your JPA mappings Dali will detect the problems and give you errors.

    Shaun

Roger wrote:

I've had my first attempt at using MOXy and have successfully generated a set 
of .java classes from an .xsd file which are full of @XML Annotations that I'm 
going to have to work on to understand.

Is it possible or even wise to add JPA @Entity annotations to my @XML 
annotated classes so I can persist the classes and vice versa back to XML, or 
would I be better off having a seperate set of @Entity classes and manually 
move the data from one set to  the other?

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

--

Shaun Smith | Principal Product Manager
Phone: +19055023094
Oracle Server Technologies, Oracle TopLink
ORACLE Canada | 110 Matheson Boulevard West, Suite 100, Mississauga, Ontario | L5R 3P4
Oracle is committed to developing practices and products that help protect the environment