diff options
authorVrishali Doke2013-03-01 06:41:43 -0500
committerSven Rottstock2013-03-11 07:39:16 -0400
commitceb619a7dc4ec02a807351c56d3961e06f284f46 (patch)
parent6a649c80bd856400bdb396dc3540ceb6fb6bff9e (diff)
CRNT-28108 - Added relative uri details
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@63394 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
1 files changed, 46 insertions, 0 deletions
diff --git a/ b/
index 15c69ce..40dc171 100644
--- a/
+++ b/
@@ -45,6 +45,7 @@ You can define two types of structured types in the web-based modeling:</p>
<li><a href="#def">Defining Structured Types</a></li>
<li><a href="#imp">Importing Type Declarations</a></li>
<li><a href="#ref">Working with Referenced Structured Type</a></li>
+ <li><a href="#exsd">Working with External XSDs</a></li>
@@ -189,6 +190,8 @@ node in the <strong>My Process Models</strong> panel.</p>
<strong>Figure:</strong> Imported Type Declaration</p>
<p>The imported type declaration is represented using this <img src="images/imp-type-icon.png"> icon.</p>
<h2 id="ref">Working with Referenced Structured Type</h2>
<p>If the Public Visibility property is selected for the structured type in the referenced model then you
can refer the structured type in another model.
@@ -205,7 +208,50 @@ To refer the structure type:
<p>For more information, please refer to the section
<a href="pep-pools-lanes.htm#ele">Dragging and Dropping of Elements</a> of the chapter <a href="pep-pools-lanes.htm">Swim Lanes Usage</a>.</p>
+<h2 id="exsd">Working with External XSDs</h2>
+<p>If you upload a model created in Eclipse-based modeler referring local XSD file
+ in web-based modeler; then the following approach ensures that models loaded in the web modeler are able to
+ locate the referenced schemas.</p>
+ <li>If the external xsd is referenced with a relative path such as <tt>/schemas/mySchema.xsd</tt> in the XPDL file,
+ then in the <tt>root</tt> folder of the
+ <span class="showReference">
+ <a href="PLUGINS_ROOT/">
+ Document Repository</a></span>
+ <!-- link from inside Portal Documentation jar -->
+ <span class="hideReference"> of the
+ <a href="../../execution-clients/admin-portal/views/admin-portal-repository.html">
+ Document Repository</a></span>
+ <span class="showReference">
+ <a href="PLUGINS_ROOT/">
+ </a></span>
+ <!-- link from inside Portal Documentation jar -->
+ <span class="hideReference">
+ <a href="../../execution-clients/admin-portal/admin-portal.html">Administration perspective</a></span>
+ view, create a folder named <tt>schemas</tt>, then upload <tt>mySchema.xsd</tt>
+ to the newly created folder.
+ </li>
+ <li>If the external xsd is referenced, for example, <tt>/mySchema.xsd</tt> in XPDL file then directly upload <tt>mySchema.xsd</tt> to
+ the <tt>root</tt> of the document repository. Alternatively, make a jar containing <tt>mySchema.xsd</tt> and add
+ the jar to the model classpath.</li>
+ </ul>
+<p>Note that these external structured types are read-only.</p>
+<h3>Relative URIs</h3>
+<p>The URI indicates the modeler where an external schema can be found, the location of it
+and the location can be absolute (a specific file in the file system or some remote location) or relative
+(relative paths may be safely used when the external schema is located in the classpath).
+<p>For web-based modeling, relative URIs are resolved first against the classpath as if it is the absolute URI <tt>classpath:/&lt;relative URI&gt;</tt>,
+and if no resource is found then it searches in the repository
+as if it is the absolute URI <tt>jcr:/&lt;relative URI&gt;</tt>. Other accepted URIs are "file:/", "http:/", "https:/".
<script language="JavaScript" type="text/javascript">