Author: steveh
Date: Wed May 11 14:50:01 2005
New Revision: 169701
URL: http://svn.apache.org/viewcvs?rev=169701&view=rev
Log:
Fix for BEEHIVE-662: Does "Weblogic Workshop Controls" mentioned in Controls
Overview mean Beehive Controls?
Modified:
incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsOverview.xml
Modified:
incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsOverview.xml
URL:
http://svn.apache.org/viewcvs/incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsOverview.xml?rev=169701&r1=169700&r2=169701&view=diff
==============================================================================
---
incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsOverview.xml
(original)
+++
incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsOverview.xml
Wed May 11 14:50:01 2005
@@ -85,15 +85,12 @@
Using a Control that exposes the Trader EJB in the earlier example, the code
to invoke the buy() method on this bean can become:</p>
<p>The TraderBean Control fully encapsulates the JNDI lookup
as well as the home/bean interface operations needed to get an instance of the
Trader EJB and invoke the buy() method on it, and exposes the JNDI name of the
EJB as a property that can be set either programmatic, via metadata, or using
an external deployment descriptor. </p>
<p>
-Controls also provide an extensibility model that allows customized view of a
resource to be constructed, with discrete operations defined as methods on the
control. For example, it is possible to define a custom operation on a Control
type representing a JMS queue resource, that uses metadata attributes to define
the format of the message, with message contents set from message parameters.
This enables the professional developer (or even the corporate developer) to
construct new customized facades for resource access with a minimum of effort.
</p>
- <p>Weblogic Workshop Controls can be considered a "proof of
concept" for the Controls architecture. Workshop Controls have used similar
techniques to provide a base mechanism for unified access to:</p>
- <ul>
- <li>Enterprise JavaBeans</li>
- <li>JMS Queues and Topics</li>
- <li>Web Services</li>
- <li>Database Access via JDBC</li>
- <li>Enterprise Resources via JCA</li>
- </ul>
+Controls also provide an extensibility model that allows customized view of a
resource to be
+constructed, with discrete operations defined as methods on the control. For
example, it is
+possible to define a custom operation on a Control type representing a JMS
queue resource,
+that uses metadata attributes to define the format of the message, with
message contents set
+from message parameters. This enables the professional developer (or even the
corporate
+developer) to construct new customized facades for resource access with a
minimum of effort. </p>
<p>
<strong>The goal of the Controls architecture is not to
define the standards for how specific resource types will be exposed; rather,
it is to guarantee that when exposed they will have a commonality in mechanism
that makes them easier to understand and use by developers.</strong>
</p>
