summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSimone Seurer2012-06-01 05:59:54 (EDT)
committer Stephan Born2012-06-15 10:41:26 (EDT)
commitf2a42c2b22240dca622998e53db36a2c99ae21a0 (patch)
treea0623b5dd532dc641204179fb728f5b6ed2e8d6b
parent25c6a48df31481d59f19034a3cdf9d356da27a99 (diff)
downloadorg.eclipse.stardust.documentation-f2a42c2b22240dca622998e53db36a2c99ae21a0.zip
org.eclipse.stardust.documentation-f2a42c2b22240dca622998e53db36a2c99ae21a0.tar.gz
org.eclipse.stardust.documentation-f2a42c2b22240dca622998e53db36a2c99ae21a0.tar.bz2
changed vendorname to productname for API and services.
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@56789 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.dev/html/handbooks/programming/pg-embedded-3.htm10
1 files changed, 5 insertions, 5 deletions
diff --git a/org.eclipse.stardust.docs.dev/html/handbooks/programming/pg-embedded-3.htm b/org.eclipse.stardust.docs.dev/html/handbooks/programming/pg-embedded-3.htm
index 7bdc669..21184bb 100644
--- a/org.eclipse.stardust.docs.dev/html/handbooks/programming/pg-embedded-3.htm
+++ b/org.eclipse.stardust.docs.dev/html/handbooks/programming/pg-embedded-3.htm
@@ -18,8 +18,8 @@
"pg-embedded-preface.htm","Embedded Usage");
-->
</script>
-<h1>@vendorname@ Services</h1>
-<p>The @vendorname@ API is organized along the concepts of specific services needed to
+<h1>@productname@ Services</h1>
+<p>The @productnameshort@ API is organized along the concepts of specific services needed to
perform common usage scenarios. While typical workflow usage will mainly involve worklist
introspection followed by process and activity execution, administrative operations or
reporting tasks usually need a completely different set of APIs.</p>
@@ -38,7 +38,7 @@ reporting tasks usually need a completely different set of APIs.</p>
<li><a href="#security">Service Security Check</a></li>
</ul>
<h2 id="references">Obtaining Service References</h2>
-<p>The initial entry point to the @vendorname@ API is the interface <a
+<p>The initial entry point to the @productnameshort@ API is the interface <a
href="../reference/api/engine/org/eclipse/stardust/engine/api/runtime/ServiceFactory.html">
org.eclipse.stardust.engine.api.runtime.ServiceFactory</a>.
Implementations of that interface allow you to centrally obtain (and optionally release)
@@ -69,7 +69,7 @@ local deployments to distributed EJB or Web deployments.</p>
</ul>
<p>The service factory obtained from the appropriate locator will ensure proper
-bootstrapping of @vendorname@ client code and install all necessary transparent treatment like
+bootstrapping of @productnameshort@ client code and install all necessary transparent treatment like
EJB exception unwrapping or security context management.</p>
<p>While essential in plain Java environments, use of such service factories is
optional in container environments like EJB or Web. As in the case of a plain Java usage,
@@ -77,7 +77,7 @@ scenario service bootstrapping includes both client-side as well as implementati
requirements (i.e. credential passing as well as resource binding), usage of a service
factory is downright required. In managed environments the implementation-side setup is
well served by the container itself, thus reducing the need for such extra efforts.<br>
-Depending on your needs you may safely continue directly using @vendorname@ Session Bean homes
+Depending on your needs you may safely continue directly using @productnameshort@ Session Bean homes
looked up via JNDI.</p>
<h3 id="credPassing">Credential Passing</h3>