Author: buildbot
Date: Tue May 27 10:51:58 2014
New Revision: 910093
Log:
Staging update by buildbot for olingo
Modified:
websites/staging/olingo/trunk/content/ (props changed)
websites/staging/olingo/trunk/content/doc/tutorials/jparedefinemetadata.html
Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue May 27 10:51:58 2014
@@ -1 +1 @@
-1597742
+1597743
Modified:
websites/staging/olingo/trunk/content/doc/tutorials/jparedefinemetadata.html
==============================================================================
---
websites/staging/olingo/trunk/content/doc/tutorials/jparedefinemetadata.html
(original)
+++
websites/staging/olingo/trunk/content/doc/tutorials/jparedefinemetadata.html
Tue May 27 10:51:58 2014
@@ -94,7 +94,7 @@
<h4 id="steps-to-redefine-the-metadata">Steps to Redefine the Metadata</h4>
<ol>
<li>Create a JPA EDM Mapping model XML according to the schema given below. In
the XML, maintain the mapping only for those elements that needs to be
redefined. For example, if JPA Entity Type A's name has to be redefined, then
maintain an EDM name for the same.
- Link to <a
href="https://cms.apache.org/olingo/wc/browse/deepa-udCb40/trunk/content/resources/RedefiningTheMetadataSchema";>Schema</a>.</li>
+ Link to <a
href="http://olingo.apache.org/resources/RedefiningTheMetadataSchema";>Schema</a>.</li>
<li>Deploy the JPA EDM Mapping model XML file in the root directory of your
web application archive (store it in the same directory as 'WEB-INF').</li>
<li>
<p>Pass the XML name into <em>ODataJPAContext</em>. In the method
<em>initializeODataJPAContext</em>, pass the name of the XML document as shown
below:</p>
