Author: deepa
Date: Tue May 27 05:10:09 2014
New Revision: 1597700
URL: http://svn.apache.org/r1597700
Log:
CMS commit to olingo by deepa
Modified:
olingo/site/trunk/content/doc/tutorials/jparedefinemetadata.mdtext
Modified: olingo/site/trunk/content/doc/tutorials/jparedefinemetadata.mdtext
URL:
http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/tutorials/jparedefinemetadata.mdtext?rev=1597700&r1=1597699&r2=1597700&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/tutorials/jparedefinemetadata.mdtext
(original)
+++ olingo/site/trunk/content/doc/tutorials/jparedefinemetadata.mdtext Tue May
27 05:10:09 2014
@@ -184,10 +184,10 @@ The OData JPA Processor Library applies
</xs:schema
-2. Store the JPA EDM Mapping model XML in *webapp* folder of Java web
application. Make sure the file is placed under the applications root folder
(relative to class path *../../WEB-INF/*classes) when the application is
deployed on web server.
+2. 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').
3. Pass the XML name into *ODataJPAContext*. In the method
*initializeODataJPAContext*, pass the name of the XML document as shown below:
- oDataJPAContext.setJPAEdmNameMappingModel(<name of xml file>);
+ oDataJPAContext.setJPAEdmNameMappingModel(<mapping XML filename
with XML extension>);
4. Compile, deploy and run the web application in a web server. A sample JPA
EDM Mapping Model is provided as an example below:
