You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicemix.apache.org by ch...@apache.org on 2007/01/16 19:44:06 UTC
svn commit: r496816 - in /incubator/servicemix/site: hello-world-bc.html
hello-world-se.html
Author: chirino
Date: Tue Jan 16 10:44:05 2007
New Revision: 496816
URL: http://svn.apache.org/viewvc?view=rev&rev=496816
Log:
Latest export from confluence
Modified:
incubator/servicemix/site/hello-world-bc.html
incubator/servicemix/site/hello-world-se.html
Modified: incubator/servicemix/site/hello-world-bc.html
URL: http://svn.apache.org/viewvc/incubator/servicemix/site/hello-world-bc.html?view=diff&rev=496816&r1=496815&r2=496816
==============================================================================
--- incubator/servicemix/site/hello-world-bc.html (original)
+++ incubator/servicemix/site/hello-world-bc.html Tue Jan 16 10:44:05 2007
@@ -473,17 +473,17 @@
<UL>
- <LI><TT>MyConsumerEndpoint.java</TT> - Extends <SPAN class="nobr"><A href="http://fisheye3.cenqua.com/browse/servicemix/trunk/common/servicemix-common/src/main/java/org/apache/servicemix/common/endpoints/ConsumerEndpoint.java?r=trunk" title="Visit page outside Confluence" rel="nofollow"><TT>ConsumerEndpoint</TT><SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/linkext7.gif" height="0" width="0" align="absmiddle" alt="" border="0"></SUP></A></SPAN> and implements <TT>MyEndpointType</TT>.</LI>
+ <LI><TT>MyConsumerEndpoint.java</TT> - Extends <SPAN class="nobr"><A href="http://fisheye3.cenqua.com/browse/servicemix/trunk/common/servicemix-common/src/main/java/org/apache/servicemix/common/endpoints/ConsumerEndpoint.java?r=trunk" title="Visit page outside Confluence" rel="nofollow"><TT>ConsumerEndpoint</TT><SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/linkext7.gif" height="0" width="0" align="absmiddle" alt="" border="0"></SUP></A></SPAN> and implements <TT>MyEndpointType</TT>. If you'd like to create a BC that fulfills the consumer role, implement the <TT>process()</TT> method in this class.</LI>
</UL>
<UL>
- <LI><TT>MyEndpointType.java</TT> -</LI>
+ <LI><TT>MyEndpointType.java</TT> - This class is simply an interface marker for <SPAN class="nobr"><A href="http://geronimo.apache.org/xbean" title="Visit page outside Confluence" rel="nofollow">Apache XBean<SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/linkext7.gif" height="0" width="0" align="absmiddle" alt="" border="0"></SUP></A></SPAN> so it can generate an XML schema document.</LI>
</UL>
<UL>
- <LI><TT>MyProviderEndpoint.java</TT> - Extends <SPAN class="nobr"><A href="http://fisheye3.cenqua.com/browse/servicemix/trunk/common/servicemix-common/src/main/java/org/apache/servicemix/common/endpoints/ProviderEndpoint.java?r=trunk" title="Visit page outside Confluence" rel="nofollow"><TT>ProviderEndpoint</TT><SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/linkext7.gif" height="0" width="0" align="absmiddle" alt="" border="0"></SUP></A></SPAN> and implements <TT>MyEndpointType</TT>.</LI>
+ <LI><TT>MyProviderEndpoint.java</TT> - Extends <SPAN class="nobr"><A href="http://fisheye3.cenqua.com/browse/servicemix/trunk/common/servicemix-common/src/main/java/org/apache/servicemix/common/endpoints/ProviderEndpoint.java?r=trunk" title="Visit page outside Confluence" rel="nofollow"><TT>ProviderEndpoint</TT><SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/linkext7.gif" height="0" width="0" align="absmiddle" alt="" border="0"></SUP></A></SPAN> and implements <TT>MyEndpointType</TT>. If you'd like to create a BC that fulfills the provider role, depending on the MEP being supported, implement the <TT>processInOnly()</TT> method or the <TT>processInOut()</TT> method in this class.</LI>
</UL>
@@ -501,9 +501,17 @@
<H3><A name="HelloWorld-BC-AddingCustomFunctionality"></A>Adding Custom Functionality </H3>
+<P>Before creating custom functionality for the BC, you need to understand the role of a JBI BC. A BC is simply a binding to a service that is external to the JBI normalized message router (NMR) using some type of communications protocol (e.g., FTP, HTTP, JMS, etc.). It's also the responsibility of the BC to handle any conversion of the message format into <SPAN class="nobr"><A href="http://servicemix.org/site/5-jbi.html#5.JBI-Normalizedmessage" title="Visit page outside Confluence" rel="nofollow">Normalized Messages<SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/linkext7.gif" height="0" width="0" align="absmiddle" alt="" border="0"></SUP></A></SPAN> that can be sent along to the NMR. This is known as message normalization. </P>
+
+<P>For example, if we were to create a BC that uses <SPAN class="nobr"><A href="http://www.protocols.com/pbook/tcpip9.htm#SNMP" title="Visit page outside Confluence" rel="nofollow">SNMP<SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/linkext7.gif" height="0" width="0" align="absmiddle" alt="" border="0"></SUP></A></SPAN> as the application layer protocol, the SNMP RFC specifies the message format to be used with particular versions of SNMP. It would be the responsibility of the BC to handle not only the communication via the SNMP protocol but also to handling the marshalling of SNMP messages to/from JBI normalized messages. The BC would simply be a binding to a service external to the NMR that speaks SNMP messages via the SNMP protocol. </P>
+
+<P>More on this later in the tutorial. For now, let's proceed with the custom functionality. </P>
+
<TABLE cellpadding="5" width="85%" cellspacing="8px" class="noteMacro" border="0" align="center"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD valign="top"><IMG src="http://goopen.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B class="strong">Using an IDE</B><BR>
<P>It is at this stage that you should employ the use of an IDE. An IDE can dramatically reduce the work necessary to import clases, override methods and so much more. Because Maven can generate project files for Eclipse and IntelliJ IDEA, either one can be used. Throughout this tutorial, Eclipse will be used. To generate project files for Eclipse, execute the Maven <TT>eclipse:eclipse</TT> goal and then import the project into your Eclipse IDE. </P></TD></TR></TABLE>
+
+
<P><EM>This is a work in progress. I will finish this up very soon.</EM></P>
<H2><A name="HelloWorld-BC-TestingtheHelloWorldBindingComponent"></A>Testing the Hello World Binding Component</H2>
@@ -802,7 +810,7 @@
<DIV id="site-footer">
Added by <A href="http://goopen.org/confluence/users/viewuserprofile.action?username=bsnyder">Bruce Snyder</A>,
last edited by <A href="http://goopen.org/confluence/users/viewuserprofile.action?username=bsnyder">Bruce Snyder</A> on Jan 16, 2007
- (<A href="http://goopen.org/confluence/pages/diffpages.action?pageId=15306&originalId=15309">view change</A>)
+ (<A href="http://goopen.org/confluence/pages/diffpages.action?pageId=15306&originalId=15324">view change</A>)
(<A href="http://goopen.org/confluence/pages/editpage.action?pageId=15306">edit page</A>)
</DIV>
Modified: incubator/servicemix/site/hello-world-se.html
URL: http://svn.apache.org/viewvc/incubator/servicemix/site/hello-world-se.html?view=diff&rev=496816&r1=496815&r2=496816
==============================================================================
--- incubator/servicemix/site/hello-world-se.html (original)
+++ incubator/servicemix/site/hello-world-se.html Tue Jan 16 10:44:05 2007
@@ -482,7 +482,11 @@
<H3><A name="HelloWorld-SE-AddingCustomFunctionality"></A>Adding Custom Functionality </H3>
-<P>Before we proceed to creating some custom functionality for the SE, you need to understand the role a JBI SE is meant to fulfill. A SE is an engine that provides a service that is local to the JBI normalized message router (NMR). It does not communicate directly with anything external to the NMR. If communication needs to occur with a service that is external to the NMR, this should take place using a JBI binding component (see the <SPAN class="nobr"><A href="http://goopen.org/confluence/pages/createpage.action?spaceKey=SM&title=Hello%20World%20BC&linkCreation=true&fromPageId=13823" title="Create Page: Hello World BC" class="createlink">Hello World BC<SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/plus.gif" height="7" width="7" align="absmiddle" alt="" border="0"></SUP></A></SPAN> for a tutorial on creating a JBI binding component). The SE is deployed to the JBI container and provides a service directly to the NMR by communicating with the NMR
using <SPAN class="nobr"><A href="http://servicemix.org/site/5-jbi.html#5.JBI-Normalizedmessage" title="Visit page outside Confluence" rel="nofollow">Normalized Messages<SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/linkext7.gif" height="0" width="0" align="absmiddle" alt="" border="0"></SUP></A></SPAN>. More on this later in the tutorial. For now, let's proceed with the custom functionality. </P>
+<P>Before we proceed to creating some custom functionality for the SE, you need to understand the role a JBI SE is meant to fulfill. A SE is an engine that provides a service that is local to the JBI normalized message router (NMR). It does not communicate directly with anything external to the NMR. If communication needs to occur with a service that is external to the NMR, this should take place using a JBI binding component (see the <SPAN class="nobr"><A href="http://goopen.org/confluence/pages/createpage.action?spaceKey=SM&title=Hello%20World%20BC&linkCreation=true&fromPageId=13823" title="Create Page: Hello World BC" class="createlink">Hello World BC<SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/plus.gif" height="7" width="7" align="absmiddle" alt="" border="0"></SUP></A></SPAN> for a tutorial on creating a JBI binding component). The SE is deployed to the JBI container and provides a service directly to the NMR by communicating with the NMR
using <SPAN class="nobr"><A href="http://servicemix.org/site/5-jbi.html#5.JBI-Normalizedmessage" title="Visit page outside Confluence" rel="nofollow">Normalized Messages<SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/linkext7.gif" height="0" width="0" align="absmiddle" alt="" border="0"></SUP></A></SPAN>. </P>
+
+<P>For example, consider a BPEL engine like <SPAN class="nobr"><A href="http://incubator.apache.org/ode/" title="Visit page outside Confluence" rel="nofollow">Apache Ode<SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/linkext7.gif" height="0" width="0" align="absmiddle" alt="" border="0"></SUP></A></SPAN>. It's job is to handle the execution of BPEL processes. Ode can be deployed to the JBI container as a JBI SE through the use of the <A href="servicemix-bpe.html" title="servicemix-bpe">servicemix-bpe</A> SE. In this capacity, Ode communicates via JBI normalized messages. Ode handles all of the processing of a given BPEL flow via it's engine and to communicate outside the engine, it speaks normalized messages. It's the responsibility of the Ode SE to handle the execution of processes defined using BPEL and in its capacity as a JBI SE it only communicates outwardly via normalized messages. </P>
+
+<P>More on this later in the tutorial. For now, let's proceed with the custom functionality. </P>
<TABLE cellpadding="5" width="85%" cellspacing="8px" class="noteMacro" border="0" align="center"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD valign="top"><IMG src="http://goopen.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD><B class="strong">Using an IDE</B><BR>
<P>It is at this stage that you should employ the use of an IDE. An IDE can dramatically reduce the work necessary to import clases, override methods and so much more. Because Maven can generate project files for Eclipse and IntelliJ IDEA, either one can be used. Throughout this tutorial, Eclipse will be used. To generate project files for Eclipse, execute the Maven <TT>eclipse:eclipse</TT> goal and then import the project into your Eclipse IDE. </P></TD></TR></TABLE>
@@ -591,7 +595,7 @@
<P>These classes can be found in the <SPAN class="nobr"><A href="http://fisheye3.cenqua.com/browse/servicemix/trunk/servicemix-core/" title="Visit page outside Confluence" rel="nofollow">servicemix-core<SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/linkext7.gif" height="0" width="0" align="absmiddle" alt="" border="0"></SUP></A></SPAN> project.</P>
-<P>This method is the logic for the Hello World SE. We're not doing anything complex here at all in order to keep this tutorial very simple. Now it's time to test the component. </P>
+<P>This method is the custom functionality for the Hello World SE. We're not doing anything complex here at all in order to keep this tutorial very simple. Apache Ode was mentioned earlier as an example of an engine that can be deployed as a JBI SE, this class is where Ode would be referenced and called. If you're interested to see how Ode is called, see the <SPAN class="nobr"><A href="http://fisheye3.cenqua.com/browse/servicemix/trunk/deployables/serviceengines/servicemix-bpe/src/main/java/org/apache/servicemix/bpe/BPEEndpoint.java?r=trunk" title="Visit page outside Confluence" rel="nofollow">BPEEndpoint class<SUP><IMG class="rendericon" src="http://goopen.org/confluence/images/icons/linkext7.gif" height="0" width="0" align="absmiddle" alt="" border="0"></SUP></A></SPAN> for the details. Now it's time to test the Hello World SE. </P>
<H2><A name="HelloWorld-SE-TestingtheHelloWorldComponent"></A>Testing the Hello World Component</H2>
@@ -1116,7 +1120,7 @@
<DIV id="site-footer">
Added by <A href="http://goopen.org/confluence/users/viewuserprofile.action?username=georg_dembowski">Georg Dembowski</A>,
last edited by <A href="http://goopen.org/confluence/users/viewuserprofile.action?username=bsnyder">Bruce Snyder</A> on Jan 16, 2007
- (<A href="http://goopen.org/confluence/pages/diffpages.action?pageId=13823&originalId=15322">view change</A>)
+ (<A href="http://goopen.org/confluence/pages/diffpages.action?pageId=13823&originalId=15323">view change</A>)
(<A href="http://goopen.org/confluence/pages/editpage.action?pageId=13823">edit page</A>)
</DIV>