Author: chirino
Date: Wed Sep 27 08:09:03 2006
New Revision: 450472
URL: http://svn.apache.org/viewvc?view=rev&rev=450472
Log:
Latest export from confluence
Modified:
incubator/servicemix/site/main/hello-world-se.html
Modified: incubator/servicemix/site/main/hello-world-se.html
URL:
http://svn.apache.org/viewvc/incubator/servicemix/site/main/hello-world-se.html?view=diff&rev=450472&r1=450471&r2=450472
==============================================================================
--- incubator/servicemix/site/main/hello-world-se.html (original)
+++ incubator/servicemix/site/main/hello-world-se.html Wed Sep 27 08:09:03 2006
@@ -125,25 +125,20 @@
<P>INS When to use this JBI Component<BR>
INS Using the component that you created</P>
-
<P>provide exact position in the SVN!<BR>
/samples/hello-world-SE-SU-SA/<BR>
integrate from SVN source like it is done at Configuration at <SPAN
class="nobr"><A href="http://www.servicemix.org/site/visualisation.html";
title="Visit page outside Confluence"
rel="nofollow">http://www.servicemix.org/site/visualisation.html<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>maybe moving the content of overlapping existing docus to this new tut and
- where appropriate - delete the old ones (only leaving a redirect).<BR>
<SPAN class="nobr"><A
href="http://www.servicemix.org/site/notes-on-creating-jbi-component-using-maven2.html";
title="Visit page outside Confluence"
rel="nofollow">http://www.servicemix.org/site/notes-on-creating-jbi-component-using-maven2.html<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><BR>
<SPAN class="nobr"><A
href="http://www.servicemix.org/site/creating-a-standard-jbi-component.html";
title="Visit page outside Confluence"
rel="nofollow">http://www.servicemix.org/site/creating-a-standard-jbi-component.html<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><BR>
is already fully incorporated, so delete content and point from there to
here</P>
-
<P>ServiceMix can be used as a protocol bridge. The following tutorial will
explain how to create a JBI Service Assembly (aka a JBI application) to bridge
two different protocols. In this example, we will bridge the HTTP/SOAP with the
JMS protocol using an InOnly MEP. We will also put between the two protocols an
XSLT transformation.<BR>
We will leverage ServiceMix archetypes and maven plugin (see <A
href="maven-jbi-plugin.html" title="Maven JBI plugin">Maven JBI plugin</A>).</P>
-
<P>provide additional reading<BR>
- <A href="creating-a-protocol-bridge.html" title="Creating a protocol
bridge">Creating a protocol bridge</A>.for a "bigger" example</P>
-
+<A href="creating-a-protocol-bridge.html" title="Creating a protocol
bridge">Creating a protocol bridge</A>.for a "bigger" example</P>
<P>Maybe add testing</P></TD></TR></TABLE>
@@ -169,7 +164,8 @@
<P><FONT color="#ff0000">Further reading: JSR 208</FONT></P>
-<H2><A name="HelloWorld-SE-CreatingtheSE"></A>Creating the SE</H2>
+<H2><A
name="HelloWorld-SE-CreatingthestuboftheSE%2CSU%2CSAandmainPOM"></A>Creating
the stub of the SE, SU, SA and main POM</H2>
+
<H3><A name="HelloWorld-SE-CreatingthestuboftheSE"></A>Creating the stub of
the SE</H3>
@@ -194,56 +190,111 @@
...<BR>
[INFO] <FONT color="#ff00ff">Defaulting package to group ID:
org.apache.servicemix.samples.helloWorldSE</FONT><BR>
...<BR>
-[INFO] *************<B>*</B>*<B>*</B>* End of debug info
from resources from generated POM
*<B>*</B>*******************<BR>
+[INFO] ***********<B>*</B>*<B>*</B>*<B>* End of debug
info from resources from generated POM
***</B>*******************<BR>
[INFO] <FONT color="#009900">Archetype created in dir:
C:\hello-world-SE-SU-SA\hello-world-SE</FONT><BR>
[INFO]
------------------------------------------------------------------------<BR>
[INFO] BUILD SUCCESSFUL<BR>
[INFO]
------------------------------------------------------------------------</P>
</DIV></DIV>
-<P>Maven creates a new folder having the same name as the artifact ID provided
(printed in <FONT color="#009900">green</FONT> in the command and output).
Inside this folder, a file called <EM>pom.xml</EM> is created. This contains
the Project Object Model providing Maven with all needed information for
building (see <SPAN class="nobr"><A
href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html";
title="Visit page outside Confluence" rel="nofollow">Introduction to the
POM<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> at the Maven
website). Moreover, Java source files and tests were created. The full
structure of files created by Maven looks like this (some directories are
grouped together for better readability):</P>
+<P>Maven creates a new folder having the same name as the artifact ID provided
(printed in <FONT color="#009900">green</FONT> in the command and output).
Inside this folder, a file called <EM>pom.xml</EM> is created. This contains
the Project Object Model providing Maven with all needed information for
building (see <SPAN class="nobr"><A
href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html";
title="Visit page outside Confluence" rel="nofollow">Introduction to the
POM<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> at the Maven
website). Moreover, Java source files and tests were created.</P>
+
+<H3><A name="HelloWorld-SE-CreatingthestuboftheSUandSA%26nbsp%3B"></A>Creating
the stub of the SU and SA </H3>
+
+<P>The archetypes for SUs and SAs do not contain much code, but rather help
with tasks related to Maven. Later, we will only need to adapt the POMs to our
project - just little work.</P>
+
+
+<P>In the directory <EM>hello-world-SE-SU-SA</EM> we execute the following
commands (they have to be one line but were split to be readable) for the SU</P>
<DIV class="preformatted"><DIV class="preformattedContent">
-<PRE>\hello-world-SE-SU-SA\hello-world-SE\
- pom.xml
- src\main\
- java\
- org\apache\servicemix\
- samples\helloWorldSE\
- MyBootstrap.java
- MyComponent.java
- MyDeployer.java
- MyEndpoint.java
- MyLifeCycle.java
- MySpringComponent.java
- test\
- java\
- org\apache\servicemix\
- samples\helloWorldSE\
- MySpringComponentTest.java
- resources\
- spring.xml
+<PRE>mvn archetype:create -DarchetypeGroupId=org.apache.servicemix.tooling
-DarchetypeArtifactId=servicemix-service-unit
+-DarchetypeVersion=3.0-incubating
-DgroupId=org.apache.servicemix.samples.helloWorldSE -DartifactId=hello-world-SU
</PRE>
</DIV></DIV>
-<P>All the classes have the word "My" prefixed to them due to the
template. We can just rename the prefix to whatever we want to, as long as we
make sure we change the corresponding resource files (all tests and the
<EM>pom.xml</EM>) as well.</P>
+<P>and the SU</P>
+<DIV class="preformatted"><DIV class="preformattedContent">
+<PRE>mvn archetype:create -DarchetypeGroupId=org.apache.servicemix.tooling
-DarchetypeArtifactId=servicemix-service-assembly
+-DarchetypeVersion=3.0-incubating
-DgroupId=org.apache.servicemix.samples.helloWorldSE -DartifactId=hello-world-SA
+</PRE>
+</DIV></DIV>
+<P>By now, the full structure of files is created by Maven and looks like
this:</P>
+<DIV class="preformatted"><DIV class="preformattedContent">
+<PRE>C:\hello-world-SE-SU-SA\hello-world-SA
+C:\hello-world-SE-SU-SA\hello-world-SA\pom.xml
+
+
+C:\hello-world-SE-SU-SA\hello-world-SE
+C:\hello-world-SE-SU-SA\hello-world-SE\pom.xml
+
+C:\hello-world-SE-SU-SA\hello-world-SE\src\main\java\org\apache\servicemix\samples\helloWorldSE
+C:\hello-world-SE-SU-SA\hello-world-SE\src\main\java\org\apache\servicemix\samples\helloWorldSE\MyBootstrap.java
+C:\hello-world-SE-SU-SA\hello-world-SE\src\main\java\org\apache\servicemix\samples\helloWorldSE\MyComponent.java
+C:\hello-world-SE-SU-SA\hello-world-SE\src\main\java\org\apache\servicemix\samples\helloWorldSE\MyDeployer.java
+C:\hello-world-SE-SU-SA\hello-world-SE\src\main\java\org\apache\servicemix\samples\helloWorldSE\MyEndpoint.java
+C:\hello-world-SE-SU-SA\hello-world-SE\src\main\java\org\apache\servicemix\samples\helloWorldSE\MyLifeCycle.java
+C:\hello-world-SE-SU-SA\hello-world-SE\src\main\java\org\apache\servicemix\samples\helloWorldSE\MySpringComponent.java
+
+C:\hello-world-SE-SU-SA\hello-world-SE\src\test\java\org\apache\servicemix\samples\helloWorldSE
+C:\hello-world-SE-SU-SA\hello-world-SE\src\test\java\org\apache\servicemix\samples\helloWorldSE\MySpringComponentTest.java
+
+C:\hello-world-SE-SU-SA\hello-world-SE\src\test\resources
+C:\hello-world-SE-SU-SA\hello-world-SE\src\test\resources\spring.xml
-<H3><A name="HelloWorld-SE-Compilingthecode"></A>Compiling the code</H3>
-<P>From now on, we can build the code by executing</P>
+C:\hello-world-SE-SU-SA\hello-world-SU
+C:\hello-world-SE-SU-SA\hello-world-SU\pom.xml
+C:\hello-world-SE-SU-SA\hello-world-SU\src\main\resources
+</PRE>
+</DIV></DIV>
+<P>According to the template rules, all the classes have the word
"My" prefixed to them. We can rename the prefix to whatever we want
to, as long as we make sure we change the corresponding resource files (all
tests and the <EM>pom.xml</EM>) as well.</P>
+
+<H3><A
name="HelloWorld-SE-IncorporatingtheSUandSAintothemainPOM"></A>Incorporating
the SU and SA into the main POM</H3>
+
+<P>Now that we have created the SU and SA structure, we incorporate them into
the main POM. We create a file called <EM>pom.xml</EM> in the
<EM>hello-world-SE-SU-SA</EM> directory and instert the following content:</P>
<DIV class="preformatted"><DIV class="preformattedContent">
-<PRE>cd hello-world-SE
+<PRE><project>
+ <modelVersion>4.0.0</modelVersion>
+ <groupId>org.apache.servicemix.samples</groupId>
+ <artifactId>helloWorldSE</artifactId>
+ <version>1.0-SNAPSHOT</version>
+ <packaging>pom</packaging>
+ <modules>
+ <module>hello-world-SA</module>
+ <module>hello-world-SU</module>
+ </modules>
+ <dependencies>
+ <dependency>
+
<groupId>org.apache.servicemix.samples.helloWorldSE</groupId>
+ <artifactId>hello-world-SU</artifactId>
+ <version>1.0-SNAPSHOT</version>
+ </dependency>
+ </dependencies>
+</project>
+</PRE>
+</DIV></DIV>
+<P>The <modules> entity defines which child projects belong to the main
project. The <dependencies> entity causes Maven to include the SU into
the SA.</P>
+
+<P><EM>Note:</EM> The content of <version> describes <EM>not</EM> the
version of ServiceMix but the project we create, thus we may choose any desired
version (e.g. <EM>3.0-final</EM>). Then you have to change it below as well.</P>
+
+<H2><A name="HelloWorld-SE-Mavencommands%26nbsp%3B"></A>Maven
commands </H2>
-mvn compile
+<P>By now, it is already possible to call Maven with the relevant goals.</P>
+
+<H3><A name="HelloWorld-SE-CompilingtheSE%27scode"></A>Compiling the SE's
code</H3>
+
+<P>We can build the code by executing</P>
+<DIV class="preformatted"><DIV class="preformattedContent">
+<PRE>mvn compile
</PRE>
</DIV></DIV>
-<P>which shall present us as one of the last lines of output</P>
+<P>in the <EM>hello-world-SE-SU-SA/hello-world-SE</EM> directory and Maven
shall present as one of the last lines of output</P>
<DIV class="preformatted"><DIV class="preformattedContent">
<PRE>[INFO] BUILD SUCCESSFUL
</PRE>
</DIV></DIV>
-<P>In case this success information is not appearing, the output shall give
further information on the reasons. Further information can be found in the <A
href="mailing-lists.html" title="Mailing Lists">ServiceMix mailing lists
archive</A> and the <SPAN class="nobr"><A href="http://maven.apache.org/";
title="Visit page outside Confluence" rel="nofollow">Maven website<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>In case this success information is not appearing, the output shall give
information on the reasons. Further information can be found in the <A
href="mailing-lists.html" title="Mailing Lists">ServiceMix mailing lists
archive</A> and the <SPAN class="nobr"><A href="http://maven.apache.org/";
title="Visit page outside Confluence" rel="nofollow">Maven website<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>
-<H3><A name="HelloWorld-SE-Testingthecode"></A>Testing the code</H3>
+<H3><A name="HelloWorld-SE-TestingtheSE%27scode"></A>Testing the SE's
code</H3>
-<P>Doing automated testing of the code is possible as well. As
ServiceMix' root POM disables testing, we have to be activate it for the
subprojects that shall be tested. To do so, the <build> entity of our
<EM>pom.xml</EM> has to be enriched by</P>
+<P>Doing automated testing of the code is possible as well. As
ServiceMix' root POM disables testing, we have to be activate it for the
subprojects that shall be tested. To do so, the <build> entity of our
<EM>hello-world-SE-SU-SA/hello-world-SE/</EM><EM>pom.xml</EM> has to be
enriched by</P>
<DIV class="preformatted"><DIV class="preformattedContent">
<PRE><pluginManagement>
<plugins>
@@ -288,80 +339,23 @@
</PRE>
</DIV></DIV>
-<H3><A name="HelloWorld-SE-AddingfunctionalitytothestuboftheSE"></A>Adding
functionality to the stub of the SE</H3>
+<H3><A name="HelloWorld-SE-GenerationanddeploymentoftheSA"></A>Generation and
deployment of the SA</H3>
-<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">TODO</B><BR>
-<P>The default implementation of the component accepts InOut MEPs and return
the input content as the out message.</P>
-
-<P>Using an IDE to add meat to the component. You can either use IDEA or
Eclipse, I tried it with Eclipse so I guess I am going to stick it for now.
<TODO></P>
-
-<P> This shall already include everything stated at<BR>
-<SPAN class="nobr"><A
href="http://www.servicemix.org/site/maven-jbi-plugin.html#MavenJBIplugin-GettingStarted";
title="Visit page outside Confluence"
rel="nofollow">http://www.servicemix.org/site/maven-jbi-plugin.html#MavenJBIplugin-GettingStarted<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><BR>
-and<BR>
-<SPAN class="nobr"><A
href="http://www.servicemix.org/site/working-with-components.html"; title="Visit
page outside Confluence"
rel="nofollow">http://www.servicemix.org/site/working-with-components.html<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></TD></TR></TABLE>
-
-<H2><A
name="HelloWorld-SE-CreatingtheSUandSAandincorporatingthemintothemainPOM"></A>Creating
the SU and SA and incorporating them into the main POM</H2>
-
-
-<P>The archetypes for SUs and SAs do not contain much code, but rather help
with tasks related to Maven. We will only need to adapt the POMs to our project
- just little work, but requiring some guidiance.</P>
-
-
-<H3><A name="HelloWorld-SE-CreatingtheSUandSA%26nbsp%3B"></A>Creating the SU
and SA </H3>
-
-<P>In the directory <EM>hello-world-SE-SU-SA</EM> we execute the following
commands (they have to be one line but were split to be readable) for the SU</P>
+<P>By running</P>
<DIV class="preformatted"><DIV class="preformattedContent">
-<PRE>mvn archetype:create -DarchetypeGroupId=org.apache.servicemix.tooling
-DarchetypeArtifactId=servicemix-service-unit
--DarchetypeVersion=3.0-incubating
-DgroupId=org.apache.servicemix.samples.helloWorldSE
-DartifactId=hello-world-SU
+<PRE>mvn install
</PRE>
</DIV></DIV>
-<P>and the SU</P>
+<P>from the <EM>hello-world-SE-SU-SA</EM> directory, the SA is generated in
the <EM>hello-world-SE-SU-SA/</EM><EM>hello-world-SA/target/</EM> directory. Of
course, it does not yet do anything, but we can already deploy the SA and
needed components to a running ServiceMix container by switching to the
<EM>hello-world-SE-SU-SA/hello-world-SA/</EM> directory and calling</P>
<DIV class="preformatted"><DIV class="preformattedContent">
-<PRE>mvn archetype:create -DarchetypeGroupId=org.apache.servicemix.tooling
-DarchetypeArtifactId=servicemix-service-assembly
--DarchetypeVersion=3.0-incubating
-DgroupId=org.apache.servicemix.samples.helloWorldSE
-DartifactId=hello-world-SA
+<PRE>mvn jbi:projectDeploy
</PRE>
</DIV></DIV>
-
-<H3><A
name="HelloWorld-SE-IncorporatingtheSUandSAintothemainPOM"></A>Incorporating
the SU and SA into the main POM</H3>
-
-<P>Now that we have created the SU and SA structure, we incorporate them into
the main <EM>pom.xml</EM>. We create a file called <EM>pom.xml</EM> in the
<EM>hello-world-SE-SU-SA</EM> directory and instert the following content:</P>
-
-<DIV class="preformatted"><DIV class="preformattedContent">
-<PRE><project>
- <modelVersion>4.0.0</modelVersion>
- <groupId>org.apache.servicemix.samples</groupId>
- <artifactId>helloWorldSE</artifactId>
- <version>1.0-SNAPSHOT</version>
- <packaging>pom</packaging>
- <modules>
- <module>hello-world-SA</module>
- <module>hello-world-SU</module>
- </modules>
- <dependencies>
- <dependency>
-
<groupId>org.apache.servicemix.samples.helloWorldSE</groupId>
- <artifactId>hello-world-SU</artifactId>
- <version>1.0-SNAPSHOT</version>
- </dependency>
- </dependencies>
-</project>
-</PRE>
-</DIV></DIV>
-<P>The <modules> entity defines which child projects belong to the main
project. The <dependencies> entity causes Maven to include the SU into
the SA.</P>
-
-<P><EM>Note:</EM> The content of <version> describes <EM>not</EM> the
version of ServiceMix but the project we create, thus we may choose any desired
version (e.g. <EM>3.0-final</EM>). Then you have to change it below as well.</P>
-
-<P>Now, we should be able to launch Maven and have the SA generated in the
<EM>hello-world-SE-SU-SA/</EM><EM>hello-world-SA/target/</EM> directory by
running the following command from the <EM>hello-world-SE-SU-SA</EM>
directory:mvn install<BR>
-Of course, it won't work if you deploy it and we now need to fill the
holes.</P>
-
-<P>Then, deploy the SA and needed components to a started ServiceMix
container:</P>
-
-<P>cd hello-world-SE-SU-SA/hello-world-SA/<BR>
-mvn jbi:projectDeploy</P>
+<P>it and we now need to fill the holes.</P>
<P>Then you can send an request to ...</P>
-
<H3><A
name="HelloWorld-SE-ConfiguringtheServiceAssembly%26nbsp%3B"></A>Configuring
the Service Assembly </H3>
<P>manually editing <SPAN class="nobr"><A
href="working-with-service-units.html" title="Visit page outside Confluence"
rel="nofollow">http://goopen.org/confluence/display/SM/Working+with+Service+Units<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><BR>
@@ -369,7 +363,19 @@
<P>use the SU archetype like in <SPAN class="nobr"><A
href="http://www.servicemix.org/site/creating-a-protocol-bridge.html";
title="Visit page outside Confluence"
rel="nofollow">http://www.servicemix.org/site/creating-a-protocol-bridge.html<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><BR>
use the SA archetype like in <SPAN class="nobr"><A
href="http://www.servicemix.org/site/creating-a-protocol-bridge.html";
title="Visit page outside Confluence"
rel="nofollow">http://www.servicemix.org/site/creating-a-protocol-bridge.html<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><BR>
- </P></DIV>
+ </P>
+
+<H3><A name="HelloWorld-SE-AddingfunctionalitytothestuboftheSE"></A>Adding
functionality to the stub of the SE</H3>
+
+<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">TODO</B><BR>
+<P>The default implementation of the component accepts InOut MEPs and return
the input content as the out message.</P>
+
+<P>Using an IDE to add meat to the component. You can either use IDEA or
Eclipse, I tried it with Eclipse so I guess I am going to stick it for now.
<TODO></P>
+
+<P> This shall already include everything stated at<BR>
+<SPAN class="nobr"><A
href="http://www.servicemix.org/site/maven-jbi-plugin.html#MavenJBIplugin-GettingStarted";
title="Visit page outside Confluence"
rel="nofollow">http://www.servicemix.org/site/maven-jbi-plugin.html#MavenJBIplugin-GettingStarted<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><BR>
+and<BR>
+<SPAN class="nobr"><A
href="http://www.servicemix.org/site/working-with-components.html"; title="Visit
page outside Confluence"
rel="nofollow">http://www.servicemix.org/site/working-with-components.html<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></TD></TR></TABLE></DIV>
</DIV>
</TD>
@@ -380,12 +386,12 @@
<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=georg_dembowski";>Georg
Dembowski</A> on Sep 27, 2006
- (<A
href="http://goopen.org/confluence/pages/diffpages.action?pageId=13823&originalId=13856";>view
change</A>)
+ (<A
href="http://goopen.org/confluence/pages/diffpages.action?pageId=13823&originalId=13857";>view
change</A>)
<SPAN id="show" class="inline-control-link"><A href=""
onclick="showComment(); return false;">show comment</A></SPAN>
<SPAN id="hide" class="inline-control-link" style="display:none;"><A
href="" onclick="hideComment(); return false;">hide comment</A></SPAN>
<DIV id="versionComment" class="noteMacro" style="display:none;
padding: 5px;">
<B>Comment:</B>
- INS further explanation/help<BR>
+ restructured<BR>
<SPAN class="smalltext"><A
href="http://goopen.org/confluence/pages/viewpreviouspageversions.action?pageId=13823";>View
page history</A></SPAN>
</DIV>
![http://goopen.org/confluence/images/icons/linkext7.gif"](http://goopen.org/confluence/images/icons/linkext7.gif"){kind=link}
![http://goopen.org/confluence/images/icons/emoticons/warning.gif"](http://goopen.org/confluence/images/icons/emoticons/warning.gif"){kind=link}