Difference between revisions of "EclipseLink/Examples/DBWS/ExistingMappingFiles"

From Eclipsepedia

Jump to: navigation, search
m (Use of pre-existing EclipseLink ORM and OXM mappings)
 
(4 intermediate revisions by one user not shown)
Line 1: Line 1:
 +
<css>
 +
  .source-java5 {padding:4px;border:1px solid black; background-color: white;}
 +
  .source-xml {padding:4px;border:1px solid black; background-color: white;}
 +
  .source-text {padding:4px;border:1px solid black; background-color: white;}
 +
</css>
 +
__NOTOC__
 +
 
== Use of pre-existing EclipseLink ORM and OXM mappings==
 
== Use of pre-existing EclipseLink ORM and OXM mappings==
  
A DBWS service may be constructed using pre-existing EclipseLink ORM and OXM maps (both Project classes and Project deployment XML are supported) with the following naming convention:
+
A DBWS service may be constructed using pre-existing EclipseLink ORM and OXM maps (both Project classes and Project deployment XML are supported) with identical case-sensitive aliases for Descriptors that are common between the projects
  
: identical case-sensitive aliases for Descriptors that are common between the projects
+
<source lang="xml" enclose="div">
 +
<?xml version="1.0" encoding="UTF-8"?>
 +
<object-persistence version="Eclipse Persistence Services - some version (some build date)" xmlns="http://www.eclipse.org/eclipselink/xsds/persistence" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:eclipselink="http://www.eclipse.org/eclipselink/xsds/persistence">
 +
  <name>SomeORProject</name>
 +
  <class-mapping-descriptors>
 +
      <class-mapping-descriptor xsi:type="relational-class-mapping-descriptor">
 +
        <class>some.package.SomeClass</class>
 +
        <alias>SomeAlias</alias>
 +
...
  
<source lang="xml">
+
<?xml version="1.0" encoding="UTF-8"?>
<class-mapping-descriptor xsi:type="relational-class-mapping-descriptor">
+
<object-persistence version="Eclipse Persistence Services - some version (some build date)" xmlns="http://www.eclipse.org/eclipselink/xsds/persistence" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:eclipselink="http://www.eclipse.org/eclipselink/xsds/persistence">
  <class>some.package.SomeClass</class>
+
  <name>SomeOXProject</name>
  <alias>SomeAlias</alias>
+
  <class-mapping-descriptor xsi:type="xml-class-mapping-descriptor">
  ...
+
      <class>some.package.SomeClass</class>
<class-mapping-descriptor xsi:type="xml-class-mapping-descriptor">
+
      <alias>SomeAlias</alias>
  <class>some.package.SomeClass</class>
+
...
  <alias>SomeAlias</alias>
+
 
</source>
 
</source>
  
Any existing named queries from the EclipseLink ORM map may be exposed as query operations for the EclipseLink DBWS service; additional Insert/Update/Delete/Query operations can be added. Pre-existing domain classes can be bundled with the service so that they are available at runtime.
+
 
 +
'''Note:''' When building a DBWS web service in this way (that is, without the <tt>DBWSBuilder</tt> Utility) be sure to create all the necessary deployment artifacts

Latest revision as of 08:48, 7 December 2011


[edit] Use of pre-existing EclipseLink ORM and OXM mappings

A DBWS service may be constructed using pre-existing EclipseLink ORM and OXM maps (both Project classes and Project deployment XML are supported) with identical case-sensitive aliases for Descriptors that are common between the projects

<?xml version="1.0" encoding="UTF-8"?>
<object-persistence version="Eclipse Persistence Services - some version (some build date)" xmlns="http://www.eclipse.org/eclipselink/xsds/persistence" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:eclipselink="http://www.eclipse.org/eclipselink/xsds/persistence">
   <name>SomeORProject</name>
   <class-mapping-descriptors>
      <class-mapping-descriptor xsi:type="relational-class-mapping-descriptor">
         <class>some.package.SomeClass</class>
         <alias>SomeAlias</alias>
...

<?xml version="1.0" encoding="UTF-8"?>
<object-persistence version="Eclipse Persistence Services - some version (some build date)" xmlns="http://www.eclipse.org/eclipselink/xsds/persistence" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:eclipselink="http://www.eclipse.org/eclipselink/xsds/persistence">
   <name>SomeOXProject</name>
   <class-mapping-descriptor xsi:type="xml-class-mapping-descriptor">
      <class>some.package.SomeClass</class>
      <alias>SomeAlias</alias>
...


Note: When building a DBWS web service in this way (that is, without the DBWSBuilder Utility) be sure to create all the necessary deployment artifacts