March 2010 - jbosstools-commits - Jboss List Archives

JBoss Tools SVN: r20721 - trunk/download.jboss.org/jbosstools/updates.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2010-03-09 23:11:50 -0500 (Tue, 09 Mar 2010) New Revision: 20721 Modified: trunk/download.jboss.org/jbosstools/updates/index.html Log: split stable link into 3.0.x and 3.1.x Modified: trunk/download.jboss.org/jbosstools/updates/index.html =================================================================== --- trunk/download.jboss.org/jbosstools/updates/index.html 2010-03-10 04:08:01 UTC (rev 20720) +++ trunk/download.jboss.org/jbosstools/updates/index.html 2010-03-10 04:11:50 UTC (rev 20721) @@ -53,7 +53,9 @@ <li><a class=link href=JBossTools-3.0.3.GA.zip>JBossTools-3.0.3.GA.zip</a></li> <li><a class=link href=JBossTools-3.1.0.GA>JBossTools-3.1.0.GA</a></li> <br/> -<li><a class=link href=stable>Stable Releases</a></li> +<li><a class=link href=stable/ganymede>JBoss Tools 3.0.x, Eclipse 3.4.2 (Ganymede)</a></li> +<li><a class=link href=stable/galileo>JBoss Tools 3.1.x, Eclipse 3.5.2 (Galileo)</a></li> +<br/> <li><a class=link href=development>Development Milestones</a></li> <li><a class=link href=nightly>Nightly Builds</a></li> </ul>

14 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r20720 - trunk/download.jboss.org/jbosstools/updates.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2010-03-09 23:08:01 -0500 (Tue, 09 Mar 2010) New Revision: 20720 Modified: trunk/download.jboss.org/jbosstools/updates/index.html Log: add 3.1.0.GA Modified: trunk/download.jboss.org/jbosstools/updates/index.html =================================================================== --- trunk/download.jboss.org/jbosstools/updates/index.html 2010-03-10 00:34:57 UTC (rev 20719) +++ trunk/download.jboss.org/jbosstools/updates/index.html 2010-03-10 04:08:01 UTC (rev 20720) @@ -51,8 +51,7 @@ <li><a class=link href=JBossTools-2.1.2.GA>JBossTools-2.1.2.GA</a></li> <li><a class=link href=JBossTools-3.0.3.GA>JBossTools-3.0.3.GA</a></li> <li><a class=link href=JBossTools-3.0.3.GA.zip>JBossTools-3.0.3.GA.zip</a></li> -<li><a class=link href=JBossTools-3.1.0.CR1>JBossTools-3.1.0.CR1</a></li> -<li><a class=link href=JBossTools-3.1.0.CR2>JBossTools-3.1.0.CR2</a></li> +<li><a class=link href=JBossTools-3.1.0.GA>JBossTools-3.1.0.GA</a></li> <br/> <li><a class=link href=stable>Stable Releases</a></li> <li><a class=link href=development>Development Milestones</a></li>

14 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r20719 - in trunk/smooks/docs/reference: en-US and 8 other directories.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2010-03-09 19:34:57 -0500 (Tue, 09 Mar 2010) New Revision: 20719 Added: trunk/smooks/docs/reference/en-US/ trunk/smooks/docs/reference/en-US/Author_Group.xml trunk/smooks/docs/reference/en-US/Book_Info.xml trunk/smooks/docs/reference/en-US/Preface.xml trunk/smooks/docs/reference/en-US/Revision_History.xml trunk/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.ent trunk/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.xml trunk/smooks/docs/reference/en-US/images/ trunk/smooks/docs/reference/en-US/images/config_page/ trunk/smooks/docs/reference/en-US/images/config_page/config_page1.png trunk/smooks/docs/reference/en-US/images/config_page/config_page2.png trunk/smooks/docs/reference/en-US/images/config_page/config_page2a.png trunk/smooks/docs/reference/en-US/images/config_page/config_page2b.png trunk/smooks/docs/reference/en-US/images/config_page/config_page3.png trunk/smooks/docs/reference/en-US/images/config_page/config_page3a.png trunk/smooks/docs/reference/en-US/images/config_page/config_page6.png trunk/smooks/docs/reference/en-US/images/config_page/config_page7.png trunk/smooks/docs/reference/en-US/images/config_page/config_page8.png trunk/smooks/docs/reference/en-US/images/config_page/config_page9.png trunk/smooks/docs/reference/en-US/images/favicon.ico trunk/smooks/docs/reference/en-US/images/graph_editor/ trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor1.png trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor1a.png trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor2.png trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor3.png trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor4.png trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor5.png trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor6.png trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor7.png trunk/smooks/docs/reference/en-US/images/introduction/ trunk/smooks/docs/reference/en-US/images/introduction/introduction1.png trunk/smooks/docs/reference/en-US/images/introduction/introduction2.png trunk/smooks/docs/reference/en-US/images/jbosstools_logo.png trunk/smooks/docs/reference/en-US/images/process_page/ trunk/smooks/docs/reference/en-US/images/process_page/process1.png trunk/smooks/docs/reference/en-US/images/process_page/process2.png trunk/smooks/docs/reference/en-US/images/process_page/process3.png trunk/smooks/docs/reference/en-US/images/process_page/process4.png trunk/smooks/docs/reference/en-US/images/process_page/process5.png trunk/smooks/docs/reference/en-US/images/process_page/process6.png trunk/smooks/docs/reference/en-US/images/process_page/process7.png trunk/smooks/docs/reference/en-US/images/process_page/process7a.png trunk/smooks/docs/reference/en-US/images/process_page/process7b.png trunk/smooks/docs/reference/en-US/images/process_page/process7c.png trunk/smooks/docs/reference/en-US/images/process_page/process8.png trunk/smooks/docs/reference/en-US/images/quick_start/ trunk/smooks/docs/reference/en-US/images/quick_start/quick_start1.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start10.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start11.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start12.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start13a.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start2.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start6.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start7.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start8.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start9.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start9a.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start9b.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start9c.png trunk/smooks/docs/reference/en-US/images/quick_start/quick_start_6a.png trunk/smooks/docs/reference/en-US/images/quick_start/sourcemodel_structured.jpg trunk/smooks/docs/reference/en-US/images/quick_start/targetmodel_structured.jpg trunk/smooks/docs/reference/en-US/images/reference/ trunk/smooks/docs/reference/en-US/images/reference/reference_1.png trunk/smooks/docs/reference/en-US/images/reference/reference_10.png trunk/smooks/docs/reference/en-US/images/reference/reference_11.png trunk/smooks/docs/reference/en-US/images/reference/reference_2.png trunk/smooks/docs/reference/en-US/images/reference/reference_3.png trunk/smooks/docs/reference/en-US/images/reference/reference_4.png trunk/smooks/docs/reference/en-US/images/reference/reference_5.png trunk/smooks/docs/reference/en-US/images/reference/reference_6.png trunk/smooks/docs/reference/en-US/images/reference/reference_7.png trunk/smooks/docs/reference/en-US/images/reference/reference_7a.png trunk/smooks/docs/reference/en-US/images/reference/reference_8.png trunk/smooks/docs/reference/en-US/images/reference/reference_9.png trunk/smooks/docs/reference/en-US/images/source_editor/ trunk/smooks/docs/reference/en-US/images/source_editor/smooks_conf_validator.png trunk/smooks/docs/reference/en-US/images/source_editor/smooks_conf_validator_settings.png trunk/smooks/docs/reference/en-US/images/source_editor/source_editor1.png trunk/smooks/docs/reference/en-US/images/source_editor/source_editor2.png trunk/smooks/docs/reference/en-US/introduction.xml trunk/smooks/docs/reference/en-US/master.xml trunk/smooks/docs/reference/en-US/master_output.xml trunk/smooks/docs/reference/en-US/options_page.xml trunk/smooks/docs/reference/en-US/process_page.xml trunk/smooks/docs/reference/en-US/quick_start.xml trunk/smooks/docs/reference/en-US/references.xml trunk/smooks/docs/reference/en-US/smooksformeditor_configurationpage.xml trunk/smooks/docs/reference/en-US/smooksformeditor_graphicalpage.xml trunk/smooks/docs/reference/en-US/smooksformeditor_sourcepage.xml trunk/smooks/docs/reference/en-US/summary.xml trunk/smooks/docs/reference/en-US/tasks.xml trunk/smooks/docs/reference/publican.cfg Removed: trunk/smooks/docs/reference/en/ Modified: trunk/smooks/docs/reference/pom.xml Log: modified book to build with publican and maven Added: trunk/smooks/docs/reference/en-US/Author_Group.xml =================================================================== --- trunk/smooks/docs/reference/en-US/Author_Group.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/Author_Group.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,7 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<authorgroup><author> + <firstname>Xue(Dart)</firstname> + <surname>Peng</surname> + </author></authorgroup> Added: trunk/smooks/docs/reference/en-US/Book_Info.xml =================================================================== --- trunk/smooks/docs/reference/en-US/Book_Info.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/Book_Info.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<bookinfo><title>Smooks Developer Tools Reference Guide</title><subtitle>Provides information relating to the Smooks Tools module.</subtitle><productname>JBoss Developer Studio</productname><productnumber>3.0</productnumber><edition>1.0</edition><pubsnumber>0</pubsnumber><abstract><para>The Smooks Developer Tools Reference Guide explains how to use Smooks Tools to graphically edit Smooks configuration files.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo> Added: trunk/smooks/docs/reference/en-US/Preface.xml =================================================================== --- trunk/smooks/docs/reference/en-US/Preface.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/Preface.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<preface><title>Preface</title><xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></xi:fallback></xi:include></preface> Added: trunk/smooks/docs/reference/en-US/Revision_History.xml =================================================================== --- trunk/smooks/docs/reference/en-US/Revision_History.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/Revision_History.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<appendix><title>Revision History</title><simpara><revhistory><revision><revnumber>0</revnumber><date>Fri Nov 20 2009</date><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email></author><revdescription><simplelist><member>Initial creation of book by publican</member></simplelist></revdescription></revision></revhistory></simpara></appendix> Added: trunk/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.ent =================================================================== --- trunk/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.ent (rev 0) +++ trunk/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.ent 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,4 @@ +<!ENTITY PRODUCT "JBoss"> +<!ENTITY BOOKID "Smooks_Developer_Tools_Reference_Guide"> +<!ENTITY YEAR "2010"> +<!ENTITY HOLDER "Red Hat"> Added: trunk/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.xml =================================================================== --- trunk/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,12 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<book> +<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="tasks.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="references.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="summary.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +</book> Added: trunk/smooks/docs/reference/en-US/images/config_page/config_page1.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/config_page/config_page1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/config_page/config_page2.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/config_page/config_page2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/config_page/config_page2a.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/config_page/config_page2a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/config_page/config_page2b.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/config_page/config_page2b.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/config_page/config_page3.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/config_page/config_page3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/config_page/config_page3a.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/config_page/config_page3a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/config_page/config_page6.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/config_page/config_page6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/config_page/config_page7.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/config_page/config_page7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/config_page/config_page8.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/config_page/config_page8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/config_page/config_page9.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/config_page/config_page9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/favicon.ico =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/favicon.ico ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor1.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor1a.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor1a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor2.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor3.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor4.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor5.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor6.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor7.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/graph_editor/graph_editor7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/introduction/introduction1.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/introduction/introduction1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/introduction/introduction2.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/introduction/introduction2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/jbosstools_logo.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/jbosstools_logo.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/process_page/process1.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/process_page/process1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/process_page/process2.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/process_page/process2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/process_page/process3.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/process_page/process3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/process_page/process4.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/process_page/process4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/process_page/process5.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/process_page/process5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/process_page/process6.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/process_page/process6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/process_page/process7.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/process_page/process7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/process_page/process7a.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/process_page/process7a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/process_page/process7b.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/process_page/process7b.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/process_page/process7c.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/process_page/process7c.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/process_page/process8.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/process_page/process8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start1.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start10.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start10.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start11.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start11.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start12.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start12.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start13a.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start13a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start2.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start6.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start7.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start8.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start9.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start9a.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start9a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start9b.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start9b.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start9c.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start9c.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start_6a.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/quick_start_6a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/sourcemodel_structured.jpg =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/sourcemodel_structured.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/quick_start/targetmodel_structured.jpg =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/quick_start/targetmodel_structured.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/reference/reference_1.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/reference/reference_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/reference/reference_10.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/reference/reference_10.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/reference/reference_11.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/reference/reference_11.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/reference/reference_2.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/reference/reference_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/reference/reference_3.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/reference/reference_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/reference/reference_4.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/reference/reference_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/reference/reference_5.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/reference/reference_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/reference/reference_6.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/reference/reference_6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/reference/reference_7.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/reference/reference_7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/reference/reference_7a.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/reference/reference_7a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/reference/reference_8.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/reference/reference_8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/reference/reference_9.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/reference/reference_9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/source_editor/smooks_conf_validator.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/source_editor/smooks_conf_validator.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/source_editor/smooks_conf_validator_settings.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/source_editor/smooks_conf_validator_settings.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/source_editor/source_editor1.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/source_editor/source_editor1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/images/source_editor/source_editor2.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en-US/images/source_editor/source_editor2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en-US/introduction.xml =================================================================== --- trunk/smooks/docs/reference/en-US/introduction.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/introduction.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,195 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="introduction"> + <?dbhtml filename="introduction.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Introduction</title> + <para>This chapter gives you a short introduction to Smooks, Smooks tools and its installation.</para> + <para>First, have a look at the key features of Smooks tools:</para> + <section> + <title>Key Features of Smooks Tools</title> + <para>Here, we provide you with a key functionality which is integrated in Smooks tools.</para> + <table> + + <title>Key Functionality for Smooks Tools</title> + <tgroup cols="3"> + + <colspec colnum="1" align="left" colwidth="2*"/> + <colspec colnum="2" colwidth="4*"/> + <colspec colnum="3" align="left" colwidth="2*"/> + + <thead> + <row> + <entry>Feature</entry> + <entry>Benefit</entry> + <entry>Chapter</entry> + </row> + </thead> + + <tbody> + + <row> + <entry><para>Smooks Configuration File Wizard</para></entry> + <entry><para>Smooks tools allows to create/edit the Smooks configuration file for Java2Java data transformation.</para></entry> + <entry> + <link linkend="config_file_wizzard">Smooks Configuration File Wizard</link> + </entry> + </row> + + <row> + <entry><para>Smooks Editor</para></entry> + <entry><para>Smooks Editor helps configure the created Smooks configuration file.</para></entry> + <entry> + <link linkend="process_tab">Smooks Editor</link> + </entry> + </row> + + </tbody> + + </tgroup> + </table> + + + + </section> + + + + <section> + <title>What is Smooks?</title> + + <para><property>Smooks</property> is a Java Framework/Engine for processing XML and non XML + data (CSV, EDI, Java, JSON etc).It provides: </para> + <para/> + <para> + <orderedlist numeration="upperroman" inheritnum="inherit"> + <listitem> + <para><emphasis role="bold">Transformation</emphasis>: Perform a wide range of + Data Transforms. Supports many different Source and Result types + -XML/CSV/EDI/Java/JSON to XML/CSV/EDI/Java/JSON.</para> + </listitem> + <listitem> + <para><emphasis role="bold">Java Binding</emphasis>: Bind into a Java Object + Model from any data source (CSV, EDI, XML, Java, JSON etc). </para> + </listitem> + + <listitem> + <para><emphasis role="bold">Huge Message Processing</emphasis>: Process huge + messages (GBs) - Split, Transform and Route message fragments to JMS, File, + Database etc destinations. Route multiple message formats to multiple + destinations in a single pass over a message. </para> + </listitem> + + <listitem> + <para><emphasis role="bold">Message Enrichment</emphasis>: Enrich a message with + data from a Database, or other Datasources. </para> + </listitem> + + <listitem> + <para><emphasis role="bold">Combine</emphasis>: Combine the above features in + different ways e.g. add Message Enrichment as part of a Splitting and + Routing process. </para> + </listitem> + </orderedlist> + </para> + <figure> + <title>Smooks</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/introduction/introduction1.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para> For more informations about <property>Smooks</property>, please visit <ulink + url="http://www.smooks.org">Smooks official site</ulink>.</para> + </section> + <section> + <title>What is Smooks Tools?</title> + + <para>Smooks tools is a set of graphical tools for editing Smooks configuration file + based on Eclipse.</para> + <figure> + <title>Smooks Form editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/introduction/introduction2.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> +  + </section> + <section> + <title>Adding Smooks jars</title> + + <para>During your development, you probably will be faced with the + necessity to include some additional Smooks jars to your project. + This problem can be solved in such a way:</para> + <itemizedlist> + <listitem><para>Create the folder named "lib" inside your project,if it doesn't exist yet. + Copy all the Smooks jars you need to include into the <emphasis><property>lib</property></emphasis> directory. + </para></listitem> + <listitem><para>Right-click on the project and select Properties.</para></listitem> + <listitem><para>Select the "Java Build Path" item in the Properties list, then the Libraries tab, and click "Add JARs". + </para></listitem> + <listitem><para>In the Jar Selection dialog, select all the jars in the "lib" directory you want to include and click OK.</para></listitem> + <listitem><para> + Now you should see all the jars + included to your project hierarchy. </para></listitem> + </itemizedlist> + + <figure> + <title>Smooks Form editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/introduction/introduction2.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> +  + </section> +  +</chapter> Added: trunk/smooks/docs/reference/en-US/master.xml =================================================================== --- trunk/smooks/docs/reference/en-US/master.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/master.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,53 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" +"http://www.docbook.org/xml/4.3/docbookx.dtd" + +[ +<!ENTITY introduction SYSTEM "introduction.xml"> +<!ENTITY tasks SYSTEM "tasks.xml"> +<!ENTITY references SYSTEM "references.xml"> +<!ENTITY summary SYSTEM "summary.xml"> +]> +<book> + + <bookinfo> + + <title>Smooks Developer Tools Reference Guide</title> + <corpauthor> + <inlinemediaobject> + <imageobject role="fo"> + <imagedata format="PNG" fileref="images/jbosstools_logo.png" /> + </imageobject> + <imageobject role="html"> + <imagedata/> + </imageobject> + </inlinemediaobject> + </corpauthor> + <author> + <firstname>Xue(Dart)</firstname> + <surname>Peng</surname> + </author> + <copyright> + <year>2009,2010</year> + <holder>JBoss by Red Hat</holder> + </copyright> + <releaseinfo> + Version: 1.1.0.GA + </releaseinfo> + + <abstract> + <title/> + <para> + <ulink + url="http://download.jboss.org/jbosstools/nightly-docs/en/smooks/pdf/Smooks_Re...">PDF version</ulink> + </para> + </abstract> + + + </bookinfo> + <toc/> + &introduction; + &tasks; + &references; + &summary; +</book> Added: trunk/smooks/docs/reference/en-US/master_output.xml =================================================================== --- trunk/smooks/docs/reference/en-US/master_output.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/master_output.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,939 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" +"http://www.docbook.org/xml/4.3/docbookx.dtd" + +[ +<!ENTITY introduction SYSTEM "modules/introduction.xml"> +<!ENTITY tasks SYSTEM "modules/tasks.xml"> +<!ENTITY references SYSTEM "modules/references.xml"> +<!ENTITY summary SYSTEM "modules/summary.xml"> +]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff"> + + <bookinfo> + + <title>Smooks Dev Tools Reference Guide</title> + <corpauthor> + <inlinemediaobject> + <imageobject role="fo"> + <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata> + </imageobject> + <imageobject role="html"> + <imagedata></imagedata> + </imageobject> + </inlinemediaobject> + </corpauthor> + <author> + <firstname>Xue(Dart)</firstname> + <surname>Peng</surname> + </author> + <copyright> + <year>2009,2010</year> + <holder>JBoss by Red Hat</holder> + </copyright> + <releaseinfo><diffmk:wrapper diffmk:change="changed"> + Version: 1.1.0.GA + </diffmk:wrapper></releaseinfo> + + <abstract> + <title></title> + <para> + <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/smooks/pdf/Smooks_Re...">PDF version</ulink> + </para> + </abstract> + + + </bookinfo> + <toc></toc> + +<chapter id="introduction" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/smooks/docs/reference/en/modules/introduction.xml"> + <?dbhtml filename="introduction.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Introduction</title> + <para>This chapter gives you a short introduction to Smooks, Smooks tools and its installation.</para> + <para>First, have a look at the key features of Smooks tools:</para> + <section> + <title>Key Features of Smooks Tools</title> + <para>Here, we provide you with a key functionality which is integrated in Smooks tools.</para> + <table> + + <title>Key Functionality for Smooks Tools</title> + <tgroup cols="3"> + + <colspec align="left" colnum="1" colwidth="2*"></colspec> + <colspec colnum="2" colwidth="4*"></colspec> + <colspec align="left" colnum="3" colwidth="2*"></colspec> + + <thead> + <row> + <entry>Feature</entry> + <entry>Benefit</entry> + <entry>Chapter</entry> + </row> + </thead> + + <tbody> + + <row> + <entry><para>Smooks Configuration File Wizard</para></entry> + <entry><para>Smooks tools allows to create/edit the Smooks configuration file for Java2Java data transformation.</para></entry> + <entry> + <link linkend="config_file_wizzard">Smooks Configuration File Wizard</link> + </entry> + </row> + + <row> + <entry><para>Smooks Editor</para></entry> + <entry><para>Smooks Editor helps configure the created Smooks configuration file.</para></entry> + <entry> + <link linkend="process_tab">Smooks Editor</link> + </entry> + </row> + + </tbody> + + </tgroup> + </table> + + + + </section> + + + + <section> + <title>What is Smooks?</title> + + <para><property moreinfo="none">Smooks</property> is a Java Framework/Engine for processing XML and non XML + data (CSV, EDI, Java, JSON etc).</para> + <para></para> + <para> + <orderedlist continuation="restarts" inheritnum="inherit" numeration="upperroman"> + <listitem> + <para><emphasis role="bold">Transformation</emphasis>: Perform a wide range of + Data Transforms. Supports many different Source and Result types + -XML/CSV/EDI/Java/JSON to XML/CSV/EDI/Java/JSON.</para> + </listitem> + <listitem> + <para><emphasis role="bold">Java Binding</emphasis>: Bind into a Java Object + Model from any data source (CSV, EDI, XML, Java, JSON etc). </para> + </listitem> + + <listitem> + <para><emphasis role="bold">Huge Message Processing</emphasis>: Process huge + messages (GBs) - Split, Transform and Route message fragments to JMS, File, + Database etc destinations. Route multiple message formats to multiple + destinations in a single pass over a message. </para> + </listitem> + + <listitem> + <para><emphasis role="bold">Message Enrichment</emphasis>: Enrich a message with + data from a Database, or other Datasources. </para> + </listitem> + + <listitem> + <para><emphasis role="bold">Combine</emphasis>: Combine the above features in + different ways e.g. add Message Enrichment as part of a Splitting and + Routing process. </para> + </listitem> + </orderedlist> + </para> + <figure float="0"> + <title>Smooks</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/introduction/introduction1.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para> For more informations about <property moreinfo="none">Smooks</property>, please visit <ulink url="http://www.smooks.org">Smooks official site</ulink>.</para> + </section> + <section> + <title>What is Smooks Tools?</title> + + <para>Smooks tools is a set of graphical tools for editing Smooks configuration file + based on Eclipse.</para> + <figure float="0"> + <title>Smooks Form editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/introduction/introduction2.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The easiest way to use the Smooks Configuration Editor is to create a project + (Java project, an ESB project, etc.), right-click on it and select <property moreinfo="none">New -> Other</property> + to open the New wizard. Drill into <property moreinfo="none">Smooks -> Smooks Configuration File</property> + and continue through the wizard. We recommend using a minimum Smooks level of 1.1 or 1.2, but if you're using it in a deployed service, it depends on what version your runtime supports. + Once the file is created, it will open in the Smooks Configuration Editor.</para> + </section> + <section> + <title>How to install Smooks dev tools?</title> + + <para> The Smooks tools was included by the <property moreinfo="none">JBoss Tools</property> since 3.0.0 + Beta1 version. You can download the <property moreinfo="none">JBoss Tools</property> from <ulink url="http://jboss.org/tools/download.html">JBoss download site</ulink>.</para> + <para> Smooks tools (<property moreinfo="none">JBoss Tools</property>) run with the latest Eclipse and + other required plug-ins (GEF, EMF, etc.).</para> + <para> You should download the latest IDE for Java EE developers from <ulink url="http://www.eclipse.org/downloads/"> Eclipse site</ulink>. It contains many plug-ins ( + GEF, EMF, etc. ) required by Smooks dev tools. </para> + <para>The Smooks Configuration depends on having all of the appropriate Smooks runtime jars in the path of the Eclipse Plug-in or Java Project in the Eclipse workspace. + + The easiest solution is to do the following: + <itemizedlist> + <listitem><para>1) Download the Smooks distribution from here: http://www.smooks.org/mediawiki/index.php?title=Downloads . + Grab the latest "ALL" distribution (as of today, it is the Smooks v.1.2.2 "ALL" distribution) and it will include binaries, examples, etc.</para></listitem> + <listitem><para>2) Extract files from the archive somewhere on your machine.</para></listitem> + <listitem><para>3) In your Eclipse workspace, copy the Smooks jars into a directory of your Eclipse plug-in or Java project named "lib".</para></listitem> + <listitem><para>4) For your Eclipse Plug-in or Java Project, right-click on the project and select Properties.</para></listitem> + <listitem><para>5) Select the "Java Build Path" item in the Properties list, select the Libraries tab, and click "Add JARs" + </para></listitem> + <listitem><para>6) In the Jar Selection dialog, select all the jars in the "lib" directory mentioned in step 3 and click <property moreinfo="none">OK</property>. + </para></listitem> + <listitem><para>7) Click <property moreinfo="none">OK</property> to close the Properties dialog. Now you should see a "Referenced Libraries" node that appeared in your project hierarchy in Eclipse. + </para></listitem> + </itemizedlist> + + </para> + <para>Now let's progress to more advanced topics.</para> + </section> + +</chapter> + + +<chapter id="process_page" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/smooks/docs/reference/en/modules/tasks.xml"> + <?dbhtml filename="tasks.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Tasks</title> + <para>This chapter describes the main tasks a user can be faced during Smooks tools usage.</para> + <section id="config_file_wizzard"> + <title>New Smooks Configuration File Creation</title> + <para>Select the project where you want to create new Smooks Configuration File and right-click on it, + select in the menu <emphasis><property moreinfo="none">New > Other</property>,</emphasis> then find + <emphasis><property moreinfo="none">Smooks > Smooks Configuration File</property>.</emphasis> + Click the <emphasis> + <property moreinfo="none">Next</property> + </emphasis> button. </para> + <figure float="0"> + <title>Selecting Smooks Configuration File Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start1.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The first wizard page is a file path creation page. Select the <emphasis> + <property moreinfo="none">src</property> + </emphasis> folder to be the files container, and input the name + <emphasis><property moreinfo="none">smooks-config.xml</property>.</emphasis> Click + <emphasis><property moreinfo="none">Next</property>.</emphasis></para> + <figure float="0"> + <title>Choosing the configuration file container and the file name</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start2.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The second wizard page allow you to select Smooks configuration file version. Select the appropriate one and click <emphasis><property moreinfo="none">Finish</property></emphasis> to complete the wizard.</para> + </section> + <section> + <title>Input Task Configuring</title> + <para> + <property moreinfo="none">Input task configuring</property> is an obligatory step for your smooks project creation. + You can configure it on the Process page of the editor: look for the "Input Task" in the Process Map at the top of the page. + </para> + <figure float="0"> + <title>Input Task Configuring</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process1.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>Select it and you will see all the properties to set for the Input reader of your Smooks configuration. + "Input type" corresponds to the type of data that you will be working with. + For example, to work with incoming CSV (Comma-separated Values) data, you would specify "CSV" in the drop-down list. + Each reader type has slightly different configuration details that must be set in the "Input configuration" area. + For instance, the CSV reader requires you to specify details such as the encoding, quote character, separator character, and the list of incoming fields. + The EDI reader requires the encoding and the path to the Mapping Model describing the incoming data. + In the <emphasis>Input data</emphasis> section, you specify some sample data that conforms to your reader configuration. + </para> + + <para> + Once you've specified your reader configuration and sample data, you can see the input model rendered in a tree form in the <emphasis>Input model</emphasis> section. + On the picture below you can see the correct configuration of some XML input task. + </para> + <figure float="0"> + <title>Input Task Configuring</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process2.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>"Java Mapping" or "Apply Template"?</title> + + <para>Though there are many options in Smooks as far as what you can do with input + data such as transformation, routing, and persistence, this version + of the Smooks Configuration Editor focuses only on these areas: + mapping to java and applying templates to create different output formats. + If you have a set of Java classes you want to use the incoming data for, + you can use the "Java Mapping" task to specify those classes and use drag and + drop to map between the input model generated by the reader and elements in the output model. + Or if you simply want to transform your output to one or more formats, you can use the "Apply Template" + task to map it to a CSV file, XML or XSD file (and other formats in the future). + <note><title>Note</title> + <para>Now you can't transform your output directly, + using only Input and Template tasks. + You should use Mapping as an interagent between these tasks.</para> + </note> + </para> + </section> + <section id="mapping"> + <title>Java Mapping Task</title> + + <para> + If you decide to do Java Mapping, you need to make sure that your Input reader has been set up and you have some sample data specified. + Then you should select <emphasis>Input Task</emphasis> in the Process tab and click the plus (+) sign to the right of the icon. + Select <emphasis>Java Mapping</emphasis> from the popup menu and it will appear to the right, connected to <emphasis>Input Task</emphasis>. Then select <emphasis>Java Mapping</emphasis> task. + </para> + <figure float="0"> + <title>Java Mapping configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>Another method of adding <emphasis>Java Mapping</emphasis> element + to the canvas in the Processing Tasks section is to right click Input Task + element and select <emphasis>Java Mapping</emphasis> in the popup menu </para> + <figure float="0"> + <title>Java Mapping configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para> + Right-click on the canvas in an empty space and select "Add ->Java Class". + </para> + <figure float="0"> + <title>Java Mapping configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para> + <emphasis>Java Bean Creation</emphasis> wizard appears. + Specify a unique identifier for the new class, the class path, + whether it's an array or not, and if it is a collection, also specify the collection class. + If the Java class is specified, you'll see a list of the properties in the box below. + Click <emphasis>Finish</emphasis> when you're done. + Now with the input and output models on the canvas, you can click and drag + from the various input elements to corresponding output elements. + Make sure to connect collection elements to corresponding collection elements. + Finally your mapping should look nearly like the one on the picture below. + </para> + <figure float="0"> + <title>Final Mapping schema</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process6.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>Apply Template Task</title> + + <para>The "Apply Template" task works very similarly to the <link linkend="mapping">"Java Mapping" task</link>, where you map between an input model and an output model. + Select the <emphasis>Java Mapping</emphasis> task you want to use as the input model in the Process Map pane and click the plus (+) sign to the right of the icon. + </para> + <figure float="0"> + <title>Apply Template configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process7.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para> + Select "Apply Template" from the popup menu and it will appear to the right, connected to the task you created it from. Then select the "Apply Template" task. + Once you've defined your template model, you can click and drag from the various input elements to corresponding output elements in the template. Make sure to connect collection elements to corresponding collection elements + </para> + </section> + <section> + <title>Smooks Configuration testing using Smooks Run Configuration</title> + + <para>This option is intended to view the results of Smooks transforming procedure. + For more detailed information about this option please go <ulink url="http://community.jboss.org/wiki/UsingtheSmooksRunConfigurationtotestSmook...">here</ulink>.</para> + </section> +</chapter> + + + +<chapter id="reference" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/smooks/docs/reference/en/modules/references.xml"> + <?dbhtml filename="reference.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Reference</title> + <para>This chapter includes detailed reference information about Smooks Tools.</para> + <section> + <title>Smooks Configuration Editor</title> + <para>This chapter describes the following tabs of the Smooks Configuration Editor:</para> + + <itemizedlist> + <listitem><para><link linkend="process_tab">Process tab</link></para></listitem> + <listitem><para><link linkend="options_tab">Options tab</link></para></listitem> + <listitem><para><link linkend="smooksformeditor_sourcetab">Source tab</link></para></listitem> + </itemizedlist> + <section id="process_tab"> + <title>Process tab</title> + <para>The Process tab of the Smooks Configuration Editor helps to configure different types of transformations. + By default smooks configuration file is opened in this editor.If you have another default settings for editor opening + you should left click smooks configuration file and select:<emphasis>Open With->Smooks Configuration Editor</emphasis>.</para> + <para>The Process tab has two sections:</para> + <itemizedlist> + <listitem><para><link linkend="processing_task_section">Processing Task section</link></para></listitem> + <listitem><para><link linkend="selected_task_details">Selected Task Details section</link></para></listitem> + </itemizedlist> + <para>You can see them on the picture below.</para> + <figure float="0"> + <title>Two Sections of the Process tab.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_1.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <section id="processing_task_section"> + <title>Processing Task section</title> + <para>Using the popup menu in the Processing Task section you + can select which types of technologies(templating or mapping ones) you will use for transofmation: </para> + <para>The descriptions of the popup menu options are in the following table.</para> + <table> + <title>Process Tab. Processing Task section.</title> + <tgroup cols="3"> + <colspec align="left" colnum="1" colwidth="1*"></colspec> + <colspec align="left" colnum="2" colwidth="3*"></colspec> + <colspec align="left" colnum="3" colwidth="1*"></colspec> + + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + <row> + <entry>Add Task</entry> + <entry>Select one of the following tasks according to the necessary type of Source and Result types of the files: + <itemizedlist> + <listitem><para><emphasis>Input</emphasis> -this task is required and + appears automatically when Smooks config file is created. + You should just configure it properly.</para></listitem> + <listitem><para><emphasis>Java Mapping</emphasis></para></listitem> + <listitem><para><emphasis>Apply Template</emphasis></para></listitem> + </itemizedlist> + </entry> + <entry></entry> + </row> + + <row> + <entry>Delete</entry> + <entry>Click this option if you want to delete some task from the section. + Note:you can't delete input task because it's required.</entry> + <entry></entry> + + </row> + + <row> + <entry>Input Methods</entry> + <entry>Choose one of the following methods: + <itemizedlist> + <listitem><para>System</para></listitem> + <listitem><para>Simple</para></listitem> + <listitem><para>Amharic(EZ+)</para></listitem> + <listitem><para>Cedilla</para></listitem> + <listitem><para>Cyrillic</para></listitem> + <listitem><para>Inuktitut</para></listitem> + <listitem><para>IPA</para></listitem> + <listitem><para>Multipress</para></listitem> + <listitem><para>SCIM Bridge Input Method</para></listitem> + <listitem><para>SCIM Input Method</para></listitem> + <listitem><para>Thai-Lio</para></listitem> + <listitem><para>Tigrigna-Eritrean(EZ+)</para></listitem> + <listitem><para>Tigrigna-Ethiopian(EZ+)</para></listitem> + <listitem><para>Vietnamese</para></listitem> + <listitem><para>X input Method</para></listitem> + </itemizedlist> + </entry> + <entry>System</entry> + </row> + </tbody> + </tgroup> + </table> + </section> + <section id="selected_task_details"> + <title>Selected Task Details Section</title> + <para>The options of this section depends on the selected task in the Processing Task section. + Because there are 3 types of tasks there are 3 different sets of its options in the Selected Task Details Section. + They will be described one by one. </para> + <section> + <title>Selected Task Details Section for Input Task.</title> + <para>On the picture below you can find an example of Selected Task Details Section view + if XML is selected as input type.</para> + + <figure float="0"> + <title>Selected Task Details Section for Input XML Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_2.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>As you can see on the picture above Input Configuration section is empty for XML input file. + But this section has special configuration options for CSV,EDI,JSON,Custom input files.</para> + + <para>Here are the screens of these configuration options:</para> + <itemizedlist> + <listitem><para>CSV:</para> + <figure float="0"> + <title>Selected Task Details Section for Input CSV Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem><para>EDI:</para> + <figure float="0"> + <title>Selected Task Details Section for Input EDI Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem><para>JSON:</para> + <figure float="0"> + <title>Selected Task Details Section for Input JSON Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem><para>Custom:</para> + <figure float="0"> + <title>Selected Task Details Section for Input Custom Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_6.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <para>All the input task configuration positions can be found in the table below:</para> + <table> + <title>Selected Task Details Section. Options for Input Task.</title> + <tgroup cols="3"> + <colspec align="left" colnum="1" colwidth="1*"></colspec> + <colspec align="left" colnum="2" colwidth="3*"></colspec> + <colspec align="left" colnum="3" colwidth="1*"></colspec> + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + <row> + <entry>Input type</entry> + <entry>Select your type of input file. + If don't find your type in the list,you should use Custom type: + <itemizedlist> + <listitem><para>No Input</para></listitem> + <listitem><para>XML</para></listitem> + <listitem><para>Java</para></listitem> + <listitem><para>XSD/WSDL</para></listitem> + <listitem><para>CSV</para></listitem> + <listitem><para>EDI</para></listitem> + <listitem><para>JSON</para></listitem> + <listitem><para>Custom</para></listitem> + </itemizedlist> + </entry> + <entry>XML</entry> + </row> + + <row> + <entry>Input configuration + + </entry> + <entry> + <itemizedlist> + <listitem><para><emphasis>No Input</emphasis> -no info required</para></listitem> + <listitem><para><emphasis>XML</emphasis> -no info required</para></listitem> + <listitem><para><emphasis>Java</emphasis> -no info required</para></listitem> + <listitem><para><emphasis>XSD/WSDL</emphasis> -no info required</para></listitem> + <listitem><para><emphasis>CSV</emphasis></para><itemizedlist> + <listitem><para><emphasis>Fields</emphasis> -Comma separated list of CSV record field names + </para></listitem> + <listitem><para><emphasis>Separator Character</emphasis> -Field separator character. Default of ','. + </para></listitem> + <listitem><para><emphasis>Quote Character</emphasis> -Quote character. Default of '"'. + </para></listitem> + <listitem><para><emphasis>Record Name</emphasis> -Name of csv record element.Default:csv-record</para></listitem> + <listitem><para><emphasis>Root Name</emphasis> -Name of csv root element.Default:csv-set</para></listitem> + <listitem><para><emphasis>indent</emphasis> -Add indentation character data to the generated event stream. This simply makes + the generated event stream easier to read in its serialized form. Useful for + testing etc.Default:true + </para></listitem> + <listitem><para><emphasis>Skip Lines</emphasis> -Number of lines to skip before processing starts. Default of 0. + + </para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>EDI</emphasis></para> + <itemizedlist> + <listitem><para><emphasis>Target Profile</emphasis> -Defines the target profile + </para></listitem> + <listitem><para><emphasis>Encoding</emphasis> -The character encoding. Default "UTF-8"</para></listitem> + <listitem><para><emphasis>Mapping Model</emphasis> -Defines the EDI Mapping Model configuration for processing the + EDI message stream to a stream of SAX events that can be processed by Smooks.</para></listitem> + <listitem><para><emphasis>Validate</emphasis> -This attribute turns on/off datatype validation in the EDI Parser. + Validation is on by default. + It makes sense to turn datatype validation off on the EDI Reader + if the EDI data is being bound into a Java Object model. + </para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>JSON</emphasis></para> + <itemizedlist> + <listitem><para><emphasis>Target Profile</emphasis> -Defines the target profile</para></listitem> + <listitem><para><emphasis>Array Element Name</emphasis> -The element name of a array element. Default of 'element'. + </para></listitem> + <listitem><para><emphasis>Encoding</emphasis> -encoding: The default encoding of any JSON message + InputStream processed by this Reader. Default of 'UTF-8'.</para></listitem> + <listitem><para><emphasis>Illegal Element Name Char Replacement</emphasis> -If illegal characters are encountered in a JSON element name then they are replaced with this value. + By default this is not defined, so that the reader doesn't doesn't search for illegal characters. + </para></listitem> + <listitem><para><emphasis>Indent</emphasis> -Add indentation character data to the generated event stream. This simply makes + the generated event stream easier to read in its serialized form. Useful for + testing etc.Default:false. + </para></listitem> + <listitem><para><emphasis>Key Prefix on Numeric</emphasis> -The prefix character to add if the JSON node name starts with a number. + By default this is not defined, so that the reader doesn't search for element names that start with a number. + </para></listitem> + <listitem><para><emphasis>Key Whitespace Replacement</emphasis> -The replacement character for whitespaces in a JSON map key. + By default this not defined, so that the reader doesn't search for whitespaces. + </para></listitem> + <listitem><para><emphasis>Null Value Replacement</emphasis> -The replacement string for JSON NULL values. Default is ""(an empty string). </para></listitem> + <listitem><para><emphasis>Root Name</emphasis> -The element name of the document root. Default of 'json'. + </para></listitem> + <listitem><para><emphasis>Key Maps</emphasis> -Defines a JSON element name mapping + The "from" key will be replaced with the "to" key or the contents of the element. + </para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>Custom</emphasis></para> + <itemizedlist> + <listitem><para><emphasis>Target Profile</emphasis> -</para></listitem> + <listitem><para><emphasis>Class</emphasis> -Custom reader class.</para></listitem> + <listitem><para><emphasis>Handlers</emphasis> -Set a handler on the reader instance e.g. an EntityResolver, ErrorHandler etc. + </para></listitem> + <listitem><para><emphasis>Features</emphasis> -Reader Features List</para></listitem> + <listitem><para><emphasis>Parametres</emphasis> -Resource Parameters</para></listitem> + + </itemizedlist> + </listitem> + </itemizedlist></entry> + <entry><itemizedlist> + <listitem><para><emphasis>CSV</emphasis></para><itemizedlist> + <listitem><para>not defined</para></listitem> + <listitem><para>','</para></listitem> + <listitem><para>'"'</para></listitem> + <listitem><para>csv-record</para></listitem> + <listitem><para>csv-set</para></listitem> + <listitem><para>true</para></listitem> + <listitem><para>0</para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>EDI</emphasis></para> + <itemizedlist> + <listitem><para>not defined</para></listitem> + <listitem><para>UTF-8</para></listitem> + <listitem><para>not defined</para></listitem> + <listitem><para>true</para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>JSON</emphasis></para> + <itemizedlist> + <listitem><para>not defined</para></listitem> + <listitem><para>element</para></listitem> + <listitem><para>UTF-8</para></listitem> + <listitem><para>not defined</para></listitem> + <listitem><para>false</para></listitem> + <listitem><para>not defined</para></listitem> + <listitem><para>not defined</para></listitem> + <listitem><para>""(an empty string)</para></listitem> + <listitem><para>'json'</para></listitem> + <listitem><para>not defined</para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>Custom</emphasis></para> + <itemizedlist> + <listitem><para>no defaults</para></listitem> + + </itemizedlist> + </listitem> + </itemizedlist></entry> + </row> + <row> + <entry>Input Data</entry> + <entry>You should select a data file using <emphasis>Add</emphasis> and <emphasis>Delete</emphasis> buttons</entry> + <entry></entry> + </row> + <row> + <entry>Input Model View</entry> + <entry>Using this view you can see the structure of your input file.If the file has been changed, to see the changes + click <emphasis>Refresh</emphasis>link.</entry> + <entry></entry> + </row> + </tbody> + </tgroup> + </table> + </section> + <section id="mapping_task"><title>Selected Task Details section for Java Mapping Task.</title> + <para>Selected Task Details section for this task is presented by the graf, + that lighten the process of java mapping. </para> + <figure float="0"> + <title>Selected Task Details Section for Mapping Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_7.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para> This graphical editor allow you to perform drug/drop operations with the nodes of transform data to map the source data to target data. + When you save the changes in the graphical editor the correct Smooks configuration file content will be generated. </para> + + </section> + <section><title>Selected Task Details section for Template Task.</title> + <para>Selected Task Details section for this task is presented by the graf, + that is similar to the one in the <link linkend="mapping_task">previous section</link>. + </para> + <figure float="0"> + <title>Selected Task Details Section for Template Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_7a.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + </section> + </section> + + </section> + <section id="options_tab"> + <title>Options Tab</title> + <para>This section describes Options tab of the Smooks Configuration File editor, gives short recommendations how this tab can be used during the project configuring.</para> + <figure float="0"> + <title> Options tab of the Smooks Configuration File editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_8.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <section> + <title>Smooks Configuration section</title> + <para> + In the <property moreinfo="none">Smooks Configuration</property> section of <property moreinfo="none">Options Tab</property> + only one element is availible:Smooks Platform Version + </para> + <figure float="0"> + <title>Smooks Configuration section of Options tab</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_9.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>This parameter is not rechangable, + and is set according to the vesion of the Smooks libraries that are added to the project. + </para> + </section> + + <section> + <title>Filter Settings Filter section</title> + <para> + In Filter Settings section you can set + the following global options responsible for Smooks filtering configuring:</para> + <figure float="0"> + <title>Filter Settings section of Options tab</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_10.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>This behavior can be turned off using this global configuration parameter and can be overriden on a per fragment basis by targetting a Visitor implementation at that fragment that takes ownership of the Result writer (in the case of SAX filtering), or simply modifies the DOM (in the case of DOM filtering). As an example of this, see the FreeMarkerTemplateProcessor. + </para> + <table> + <title>Options Tab. Filter Settings section.</title> + <tgroup cols="3"> + <colspec align="left" colnum="1" colwidth="1*"></colspec> + <colspec align="left" colnum="2" colwidth="3*"></colspec> + <colspec align="left" colnum="3" colwidth="1*"></colspec> + + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + <row> + <entry>Stream Filter Type</entry> + <entry>Determines the type of processing model that will be used. + Please refer to <ulink url="http://www.smooks.org/mediawiki/index.php?title=V1.2:Smooks_v1.2_User_Gui..."> + Filtering Process Selection section</ulink> + of the official Smooks User Guide for more information about these models: + <itemizedlist> + <listitem><para><emphasis>SAX</emphasis></para></listitem> + <listitem><para><emphasis>DOM</emphasis></para></listitem> + </itemizedlist> + </entry> + <entry>DOM</entry> + </row> + + <row> + <entry>Default Serialization is On</entry> + <entry>Defines whether default serialization should be switched on. + Default serialization being turned on leads to locating StreamResult/DOMResult + to the Result objects provided to the Smooks.filterSource method and to + serialization all the events to that Result.</entry> + <entry>true</entry> + + </row> + </tbody> + </tgroup> + </table> + </section> + </section> + <section id="smooksformeditor_sourcetab" xreflabel="Smooks Source Tab"> + + <title>Source Tab</title> + <para>This section provides information about Smooks Source Editor Page.</para> + <section> + <title>XML Source Editor</title> + <para>You can use this editor to edit the Smooks Configuration file directly. </para> + <figure float="0"> + <title>Graphical Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/source_editor1.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>Error underlining in Graphical Editor</title> + <para>If the <property moreinfo="none">Smooks tools</property> can't understand the configuration + file or the configuration file is illegal (XML structure isn't right for Smooks + Configuration file, etc.), the error is underlined.</para> + <figure float="0"> + <title>Graphical Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_11.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + + </section> + + <section> + <title>Smooks Configuration File Validator</title> + <para>Smooks configuration file validator will validate your Smooks configuration file. Just right-click on the file and then click on the <property moreinfo="none">Validate</property> button. The validator can be enabled/disabled in <emphasis><property moreinfo="none">Window -> Preferences -> Validation</property></emphasis>:</para> + + <figure float="0"> + <title>Validation: Smooks Configuration File Validator</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/smooks_conf_validator.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>You can set up your Smooks validator to include, exclude groups to validate and specify rules for validation. Just click on the <property moreinfo="none">Settings</property> button and use the options provided:</para> + + <figure float="0"> + <title>Smooks Configuration File Validator Settings</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/smooks_conf_validator_settings.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + + + </section> + </section> + </section> +</chapter> + + +<chapter xml:base="file:///home/vchukhutsina/repos/ochik_jboss/smooks/docs/reference/en/modules/summary.xml"> + <?dbhtml filename="summary.html"?> + <title>Summary</title> + <para>In conclusion, with this document you know all the capabilities of Smooks Tools and could easily start with them. + The chapters above walked you through the steps on how to create and configure some XML to JAVA mapping project. + If you have questions or suggestions concerned both the documentation and tools behavior, + you are welcome to JBoss Tools Users forum. + Please, use Jira to report bugs and requests on documentation.</para> + + <section> + <title>Other relevant resources on the topic</title> + <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at + <ulink url="http://docs.jboss.org/tools">http://docs.jboss.org/tools</ulink> in the corresponding release directory. + </para> + <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs">http://download.jboss.org/jbosstools/nightly-docs</ulink>. </para> +<para>For more information about Smooks technology please visit + <ulink url="http://www.smooks.org/mediawiki/index.php?title=Main_Page"> + Smooks Technology Home Page</ulink></para> + + </section> +</chapter> + +</book> Added: trunk/smooks/docs/reference/en-US/options_page.xml =================================================================== --- trunk/smooks/docs/reference/en-US/options_page.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/options_page.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,97 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="options_page"> + <?dbhtml filename="options_page.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Options Tab</title> + <para>This chapter describes Options tab of the Smooks Configuration File editor, gives short recommendations how this tab can be used during the project configuring.</para> + <figure> + <title> Options tab of the Smooks Configuration File editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_10.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <section> + <title>Smooks Configuration section</title> + <para> + In the <property>Smooks Configuration</property> section of <property>Options Tab</property> + only one element is availible:Smooks Platform Version + </para> + <figure> + <title>Smooks Configuration section of Options tab</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_9.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>This parameter is not rechangable, + and is set according to the vesion of the Smooks libraries that are added to the project. + </para> + </section> + <section> + <title>Filter Settings Filter section</title> + <para> + In Filter Settings section you can set + the following global options responsible for Smooks filtering configuring:</para> + <figure> + <title>Filter Settings section of Options tab</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_1.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>This behavior can be turned off using this global configuration parameter and can be overriden on a per fragment basis by targetting a Visitor implementation at that fragment that takes ownership of the Result writer (in the case of SAX filtering), or simply modifies the DOM (in the case of DOM filtering). As an example of this, see the FreeMarkerTemplateProcessor. + </para> + <table> + <title>Options Tab. Filter Settings section.</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" align="left" colwidth="3*"/> + <colspec colnum="3" align="left" colwidth="1*"/> + + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + <row> + <entry>Stream Filter Type</entry> + <entry>Determines the type of processing model that will be used. + Please refer to <ulink url="http://www.smooks.org/mediawiki/index.php?title=V1.2:Smooks_v1.2_User_Gui..."> + Filtering Process Selection section</ulink> + of the official Smooks User Guide for more information about these models: + <itemizedlist> + <listitem><para><emphasis>SAX</emphasis></para></listitem> + <listitem><para><emphasis>DOM</emphasis></para></listitem> + </itemizedlist> + </entry> + <entry>DOM</entry> + </row> + + <row> + <entry>Default Serialization is On</entry> + <entry>Defines whether default serialization should be switched on. + Default serialization being turned on leads to locating StreamResult/DOMResult + to the Result objects provided to the Smooks.filterSource method and to + serialization all the events to that Result.</entry> + <entry>true</entry> + + </row> + </tbody> + </tgroup> + </table> + </section> +</chapter> + Property changes on: trunk/smooks/docs/reference/en-US/options_page.xml ___________________________________________________________________ Name: svn:executable + * Added: trunk/smooks/docs/reference/en-US/process_page.xml =================================================================== --- trunk/smooks/docs/reference/en-US/process_page.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/process_page.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,140 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="process_page"> + <?dbhtml filename="process_page.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Process Page</title> + <para>This chapter describes Process tab of the Smooks Configuration File editor, gives short recommendations how this tab can be used during the project configuring.</para> + + <section> + <title>Input Task Configuring</title> + <para> + <property>Input task configuring</property> is an obligatory step for your smooks project creation. + You can do this on the Process page of the editor: look for the "Input Task" in the Process Map at the top of the page. + </para> + <figure> + <title>Input Task Configuring</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process1.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>Select it and you will see all the properties to set for the Input reader of your Smooks configuration. + "Input type" corresponds to the type of data that you will be working with. + For example, to work with incoming CSV (Comma-separated Values) data, you would specify "CSV" in the drop-down list. + Each reader type has slightly different configuration details that must be set in the "Input configuration" area. + For instance, the CSV reader requires you to specify details such as the encoding, quote character, separator character, and the list of incoming fields. + The EDI reader requires the encoding and the path to the Mapping Model describing the incoming data. + In the "Input data" section, you specify some sample data that conforms to your reader configuration. + </para> + + <para> + Once you've specified your reader configuration and sample data, you can see the input model rendered in a tree form in the "Input model" section. + On the picture below you can see the correct configuration of some XML input task. + </para> + <figure> + <title>Input Task Configuring</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process2.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + </section> + + + + <section> + <title>"Java Mapping" or "Apply Template"?</title> + + <para>Though there are many options in Smooks as far as what you can do with input + data such as transformation, routing, and persistence, the first release + of the Smooks Configuration Editor focuses on just a couple of areas: + mapping to java and applying templates to create different output formats. + If you have a set of Java classes you want to use the incoming data for, + you can use the "Java Mapping" task to specify those classes and use drag and + drop to map between the input model generated by the reader and elements in the output model. + Or if you simply want to transform your output to one or more formats, you can use the "Apply Template" + task to map it to a CSV file, XML or XSD file (and other formats in the future). + </para> + </section> + <section id="mapping"> + <title>Java Mapping</title> + + <para> + If you decide to do Java Mapping, you need to make sure that your Input reader has been set up and you have some sample data specified. + Then you should select the "Input Task" in the Process tab and click the plus (+) sign to the right of the icon. + Select "Java Mapping" from the popup menu and it will appear to the right, connected to the "Input Task". Then select the "Java Mapping" task. + </para> + <figure> + <title>Java Mapping configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Another method of adding "Java Mapping" element to the canvas in the Processing Tasks section is to right click Input Task element and select in the popup menu </para> + <figure> + <title>Java Mapping configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process4.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + Right-click on the canvas in an empty space and select "Add ->Java Class". + </para> + <figure> + <title>Java Mapping configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process5.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + The "Java Bean Creation" wizard appears. + Specify a unique identifier for the new class, the class path, whether it's an array or not, and if it is a collection, also specify the collection class. + If the Java class is specified, you'll see a list of the properties in the box below. + Click Finish when you're done. + Now with the input and output models on the canvas, you can click and drag from the various input elements to corresponding output elements. Make sure to connect collection elements to corresponding collection elements. + Finally your mapping should look nearly like the one on the picture below. + </para> + <figure> + <title>Final Mapping schema</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process6.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>"Apply Template" task</title> + + <para>The "Apply Template" task works very similarly to the <link linkend="mapping">"Java Mapping" task</link>, where you map between an input model and an output model. + Select the "Input Task" or "Java Mapping" task you want to use as the input model in the Process Map pane and click the plus (+) sign to the right of the icon. + </para> + <figure> + <title>"Apply Template" task opening</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process7.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + Select "Apply Template" from the popup menu and it will appear to the right, connected to the task you created it from. Then select the "Apply Template" task. + Once you've defined your template model, you can click and drag from the various input elements to corresponding output elements in the template. Make sure to connect collection elements to corresponding collection elements + </para> + </section> +</chapter> + Added: trunk/smooks/docs/reference/en-US/quick_start.xml =================================================================== --- trunk/smooks/docs/reference/en-US/quick_start.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/quick_start.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,590 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="quickstart" xreflabel="Quick Start" role="updated"> + <?dbhtml filename="quick_start.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + <keyword>java</keyword> + </keywordset> + </chapterinfo> + <title>Quick Start</title> + <para> This "Quick Start" will show how to use the <property>Smooks tools</property> to create/edit the Smooks + configuration file for Java2Java data transformation.</para> + <para> This chapter gives you a brief understanding of the <property>Smooks tools</property>.</para> + <section> + <title>Download Smooks Java-to-Java Example</title> + <para> Visit <ulink + url="http://www.blogjava.net/Files/reloadcn/smooks_java_java.zip" + >smooks examples page</ulink> to download the "java-to-java" example project. </para> + <tip> + <title>Tip:</title> + + <para> The example project is based on Maven, we suggest you to create a new eclipse + Java project, copy the example code and .jar files from the example project and paste + them into the eclipse Java project. </para> + </tip> + </section> + <section> + <title>Mapping rules</title> + <para>At the begining of working with Smooks tools, + we need to understand the Java-to-Java mapping rules of this example. + The transform input Java class is <emphasis><property>example.sourcemodel.Order</property></emphasis> , its structure looks like this : + </para> + <figure> + <title>Order class</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/sourcemodel_structured.jpg" /> + </imageobject> + </mediaobject> + </figure> + <para>Let's describe the structure of <emphasis><property>example.sourcemodel.Order</property></emphasis> in short:</para> + <itemizedlist> + <listitem><para>Order class contains a <property>Header</property> class and a <property>List</property> class.</para></listitem> + <listitem><para>The <property>Header</property> class has <property>customerName</property>,<property>customerNumber</property>,<property>priority</property> as properties.</para></listitem> + <listitem><para>In Order class the objects of the OrderItem class are stored in the List.</para></listitem> + <listitem><para>OrderItem has <property>price</property>,<property>productId</property>,<property>quantity</property> as its properties.</para></listitem> + </itemizedlist> + <para>Let's look at the transform target Java class : <emphasis><property>LineOrder</property></emphasis>.</para> + <para>On the screen below you can see its structure:</para> + <figure> + <title>LineOrder class</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/targetmodel_structured.jpg" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem><para><property>LineOrder</property> class contains 3 properties:<property>customerId</property>,<property>customerName</property>,<property>priority</property> and an array of lineItems.</para></listitem> + <listitem><para>The <property>Header</property> class has <property>customerName</property>,<property>customerNumber</property>,<property>priority</property> as its properties.</para></listitem> + <listitem><para>OrderItem objects are stored in a List.</para></listitem> + </itemizedlist> + <para>Now it's the time to define the mapping rules to transform the input source java class to the target java class:</para> + <itemizedlist> + <listitem><para>Each instance of the Order class should be mapped with an instance of the LineOrder class.</para></listitem> + <listitem><para>The value of <property>customerName</property> of the Header class should be assigned to the <property>customerName</property> property of a LineOrder instance.</para></listitem> + <listitem><para>The value of <property>customerNumber</property> of the Header class should be assigned to the <property>customerId</property> property of a LineOrder instance.</para></listitem> + <listitem><para>The value of <property>priority</property> of the Header class should be assigned to the <property>priority</property> property of LineOrder instance.</para></listitem> + <listitem><para>For the <property>orderitems</property> List of the Order instance, it's necessary to map a new lineItems array instance of LineOrder , + and each OrderItem instance in the orderItems List should be transformed to a LineItem instance, + those instances will be put into the lineItems array.</para></listitem> + <listitem><para>The value of <property>productId</property> of the OrderItem instance should be assigned to the 'productCode' of LineItem.</para></listitem> + <listitem><para>The value of <property>price</property> of OrderItem should be assigned to the <property>unitPrice</property> of LineItem.</para></listitem> + + </itemizedlist> + </section> + + <section id="config_file_wizzard"> + <title>Smooks Configuration File Wizard</title> + <para>Select the Smooks Java-to-Java example project that you created and right-click, + select the menu <emphasis><property>New > Other</property>,</emphasis> then find + <emphasis><property>Smooks > Smooks Configuration File</property>.</emphasis> + Click the <emphasis> + <property>Next</property> + </emphasis> button. </para> + <figure> + <title>Selecting Smooks Configuration File Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start1.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>The first wizard page is a file path creation page. Select the <emphasis> + <property>src</property> + </emphasis> folder to be the files container, and input the name + <emphasis><property>smooks-config.xml</property>.</emphasis> Click + <emphasis><property>Next</property>.</emphasis></para> + <figure> + <title>Choosing the configuration file container and the file name</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start2.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>The second wizard page is allows you to select Smooks configuration file version. Select the appropriate one and click <emphasis><property>Finish</property></emphasis> to complete the wizard.</para> + + + +  + </section> + <section id="quickstart_formeditor"> + <title>Smooks Editor</title> + + <para>When all the wizard steps are passed, a new Smooks Configuration file is created and + the <property>Smooks Configuration Editor</property> will be opened automatically:</para> + <figure> + <title>Smooks Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start6.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>On the bottom of this editor there are 5 tabs, they are : + + Overview, Reader, Message Filter, Graph, Source.</para> + <section id="graphicaleditor_datalink"> + <title>Adding the input data</title> + <para>At first, we need to add the Order class as the input data. + To do this, click the Reader tab, swich to the Reader/Input editor page</para> + +  + + + <para>To choose the transform data you should open <emphasis> + <property>Reader</property></emphasis> tab and click <emphasis> + <property>Add</property></emphasis> button in the Input Data section.</para> + <figure> + <title>Input Data section</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_6a.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>After clicking the button the <property>Data Type Selection wizard</property> is + opened, and there are many data types in the list: Java, XML etc.</para> + <note> + <title>Note</title> + <para> There will become more and more data types on the list as the development goes on. + </para> + </note> + + <figure> + <title>Data Type Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start7.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + + <para>Select the <emphasis> + <property>Java</property> + </emphasis> data type and click <emphasis><property>Next</property>,</emphasis> you will + see the JavaBean class selection page:</para> + + <figure> + <title>JavaBean Data Selection</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start8.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + + <para> Let's select the Order class from the example project as the source JavaBean class.After that click <emphasis> + <property>Finish</property> + </emphasis> and you should see the just added java class, being displayed in the Input Data Section. + </para> + <figure> + <title>Displaying the Structure of the Transformed Data</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start9.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>Adding the target Bean</title> + <para>After adding the input data, let's switch to the Message Filter page:</para> + <figure> + <title>Displaying the Structure of the Transformed Data</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start9a.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>Click the <property>Add</property> button, the <property>Add Child</property> wizard page will be shown, let's select the <property>Java Binding v1.2 -> Bean v1.2</property> and click <emphasis><property>OK</property></emphasis> to add the Bean : + </para> + <figure> + <title>Add Child wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start9b.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>Then we can find on the Message Filter page the <property>Bean v1.2</property> item added, click on it ,a Bean v1.2 section should appear to the right of the page. + The section represents a GUI for editing <property>Bean v1.2</property> properties:</para> + <figure> + <title>Bean v1.2 section</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start9c.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>You should input <property> + lineOrder</property> as the Bean's id in the "Bean Id" field.Then you should click <property>Browse</property> button + near the <property>Class</property> textfield and select LineOrder as the Bean's class.</para> + <note> + <para> + When you enter a value for the <property>Class</property> text field, + you can type 'Alt + /' and the content assist pop dialog will be shown, + so it's will increase the efficiency. If 'Alt + /' doesn't work, + try to use the 'Ctrl + space'('Key Assist' of Eclipse). + </para> + </note> + <para>Let's click the <property>Add Binding</property> link at the bottom of this page, + it will show a dialog to ask the binding of what Bean properties you will prefer to add. + Select all and click OK, you will see a list of Binding elements added under the Bean item.</para> + <para>Then you should add an array of beans called <property>lineItems</property> and a Bean LineItem.These two classes and Id values are:</para> + <para>Array Bean:</para> + <itemizedlist> + <listitem><para>BeanId : lineItems;</para></listitem> + <listitem><para>Class : example.trgmodel.LineItem[]</para></listitem> + </itemizedlist> + <para>LineItem Bean :</para> + <itemizedlist> + <listitem><para>BeanId : lineItem;</para></listitem> + <listitem><para>Class : example.trgmodel.LineItem</para></listitem> + </itemizedlist> + <note> + <para> + In Smooks , to be an array of Beans , the class value should end with '[]'. This means that this bean is an array type. + + </para> + </note> + <para>To finish this work, use the <property>Add Binding</property> link to add all the bindings for the Bean.</para> + </section> + + + </section> + <section id="quickstart_mapping"> + <title>Mapping</title> + + + <para>How to map the java class just added?</para> + + <para>First, you should know what to transform:</para> + + <orderedlist numeration="loweralpha" inheritnum="inherit"> + <listitem> + <para>Bind the <emphasis> + <property>"customerName"</property> + </emphasis> property of the <property>Order#header</property> to the <emphasis> + <property>"customerName"</property> + </emphasis> property of <property>LineOrder</property>.</para> + </listitem> + <listitem> + <para>Bind the <emphasis> + <property>"customerNumber"</property> + </emphasis> property of the <property>Order#header</property> to the <emphasis> + <property>"customerId"</property> + </emphasis> property of <property>LineOrder</property>.</para> + </listitem> + <listitem> + <para>Bind the <emphasis> + <property>"price"</property> + </emphasis> property of the <property>OrderItem</property> to the <emphasis> + <property>"unitPrice"</property> + </emphasis> property of <property>LineItem</property>.</para> + </listitem> + <listitem> + <para>Bind the <emphasis> + <property>"productId"</property> + </emphasis> property of the <property>OrderItem</property> to the <emphasis> + <property>"productCode"</property> + </emphasis> property of <property>LineItem</property>.</para> + </listitem> + <listitem> + <para>Bind the <emphasis> + <property>"quantity"</property> + </emphasis> property of the <property>OrderItem</property> to the <emphasis> + <property>"unitQuantity"</property> + </emphasis> property of <property>LineItem</property>.</para> + </listitem> + </orderedlist> + + <para> Make sense? + You should open Design tab and click Add button. In opened Add Child Wizard,please, select <emphasis> + <property>Add Smooks Resource>Java Binding>Bindings</property></emphasis>. + </para> + <para>First of all, you should bind <emphasis> + <property>Order</property></emphasis> to <emphasis> + <property>LineOrder</property></emphasis>. To do this one <emphasis> + <property>Bindings</property></emphasis> Item should be added to the Resource List.</para> + <figure> + <title>Mapping</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start10.png" scale="90"/> + </imageobject> + </mediaobject> + </figure><para>Click on it and you should see <emphasis> + <property>Bindings</property></emphasis> Section to the right of <emphasis> + <property>Message Filtering Resources</property></emphasis>.Write <emphasis> <property>lineOrder</property></emphasis> in the <emphasis> + <property>Bean id</property></emphasis> field.</para> + <para>Select <emphasis> + <property>example.trgmodel.LineOrder</property></emphasis> in the <emphasis> + <property>Class</property></emphasis> field and <emphasis> + <property>example.srcmodel.Order</property></emphasis> in the <emphasis> + <property>Name</property></emphasis> field.Your <emphasis> <property>Smooks Configuration Editor</property></emphasis> should look like this: </para> + <figure> + <title>Mapping</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start11.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + + <para>Now you should bind two values <emphasis> <property>"customerNumber"</property> + </emphasis> property of the <property>Order#header</property> to the <emphasis> + <property>"customerId"</property> + </emphasis> property of <property>LineOrder</property>.To do this right click your just created <emphasis> + <property>Bindings Item >Add Smooks Resource>Value</property></emphasis> + .</para> + + <figure> + <title> Mapping Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start12.png" scale="90"/> + </imageobject> + </mediaobject> + </figure><note> + <title>Note:</title> + <para>Please, remember that the root nodes of the source data and target data *MUST* be + connected.</para> + <para>This rule is not only for Java-to-Java, but also is relevant for + XML-to-Java </para> + </note> + <para> Do the same operation with the + other properties in this and other classes.</para> + <para>It's also necessary to bind <emphasis> + <property>orderItems</property></emphasis> property of the <emphasis> + <property>Order</property></emphasis> to <emphasis> + <property>lineItems</property></emphasis> property of <emphasis> + <property>LineOrder</property></emphasis>.The difference from the previous steps is that the <emphasis> + <property>orderItems</property></emphasis> is presented by the list of <emphasis> + <property>Order</property></emphasis> and <emphasis> + <property>lineItems</property></emphasis> is the massive of <emphasis> + <property>LineItem</property></emphasis> .To do the binding,you should use <emphasis> + <property>Wiring Item</property></emphasis>.First you should create a new Binding item. This is a configuration that allows you to construct an object graph .Select <emphasis> + <property>example.trgmodel.LineItem[]</property></emphasis> in the Class field and orderItems in the Name field,in bean Id write lineItems. + Your Smooks Configuration Editor should look like this: + </para> + <figure> + <title> Creating Wiring Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start13a.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para> Then you should right click <emphasis> + <property>lineOrder</property></emphasis> binding item<emphasis> + <property>>Add Smooks Resource>Wiring</property></emphasis>.Select <emphasis> + <property>lineItem</property></emphasis> in <emphasis> + <property>Bean id Ref</property></emphasis>. + </para> + <para>The final step is to add new Wiring item to lineOrder <property>Binding</property>.In the <property>Bean id Ref</property> select <emphasis> + <property>lineItems</property></emphasis> and in <emphasis> + <property>Property</property></emphasis> select <emphasis> + <property>lineItems</property></emphasis>.</para> + + <para>Now, you should save the file and the <property>Smooks tools</property> generate the correct + configuration file content.</para> + <para>OK, let run the test class: <property>example.Main</property>. (Please, make sure that the Smooks engine + loads the correct configuration file).</para> + <para>Success!</para> + </section> +</chapter> Added: trunk/smooks/docs/reference/en-US/references.xml =================================================================== --- trunk/smooks/docs/reference/en-US/references.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/references.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,515 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="reference"> + <?dbhtml filename="reference.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Reference</title> + <para>This chapter includes detailed reference information about all tabs of the Smooks Configuration Editor.</para> + <section id="process_tab"> + <title>Process tab</title> + <para>The Process tab of the Smooks Configuration Editor helps to configure different types of transformations. + By default smooks configuration file is opened in this editor.If you have another default settings for editor opening + you should left click smooks configuration file and select:<emphasis>Open With->Smooks Configuration Editor</emphasis>.</para> + <para>The Process tab has two sections:</para> + <itemizedlist> + <listitem><para><link linkend="processing_task_section">Processing Task section</link></para></listitem> + <listitem><para><link linkend="selected_task_details">Selected Task Details section</link></para></listitem> + </itemizedlist> + <para>You can see them on the picture below.</para> + <figure> + <title>Two Sections of the Process tab.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_1.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <section id="processing_task_section"> + <title>Processing Task section</title> + <para>Using the popup menu in the Processing Task section you + can select which types of technologies(templating or mapping ones) you will use for transofmation: </para> + <para>The descriptions of the popup menu options are in the following table.</para> + <table> + <title>Process Tab. Processing Task section.</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" align="left" colwidth="3*"/> + <colspec colnum="3" align="left" colwidth="1*"/> + + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + <row> + <entry>Add Task</entry> + <entry>Select one of the following tasks according to the necessary type of Source and Result types of the files: + <itemizedlist> + <listitem><para><emphasis>Input</emphasis> - this task is required and + appears automatically when Smooks config file is created. + You should just configure it properly.</para></listitem> + <listitem><para><emphasis>Java Mapping</emphasis></para></listitem> + <listitem><para><emphasis>Apply Template</emphasis></para></listitem> + </itemizedlist> + </entry> + <entry></entry> + </row> + + <row> + <entry>Delete</entry> + <entry>Click this option if you want to delete some task from the section. + Note:you can't delete input task because it's required.</entry> + <entry></entry> + + </row> + + <row> + <entry>Input Methods</entry> + <entry>Choose one of the following methods: + <itemizedlist> + <listitem><para>System</para></listitem> + <listitem><para>Simple</para></listitem> + <listitem><para>Amharic(EZ+)</para></listitem> + <listitem><para>Cedilla</para></listitem> + <listitem><para>Cyrillic</para></listitem> + <listitem><para>Inuktitut</para></listitem> + <listitem><para>IPA</para></listitem> + <listitem><para>Multipress</para></listitem> + <listitem><para>SCIM Bridge Input Method</para></listitem> + <listitem><para>SCIM Input Method</para></listitem> + <listitem><para>Thai-Lio</para></listitem> + <listitem><para>Tigrigna-Eritrean(EZ+)</para></listitem> + <listitem><para>Tigrigna-Ethiopian(EZ+)</para></listitem> + <listitem><para>Vietnamese</para></listitem> + <listitem><para>X input Method</para></listitem> + </itemizedlist> + </entry> + <entry>System</entry> + </row> + </tbody> + </tgroup> + </table> + </section> + <section id="selected_task_details"> + <title>Selected Task Details Section</title> + <para>The options of this section depends on the selected task in the Processing Task section. + Because there are 3 types of tasks there are 3 different sets of its options in the Selected Task Details Section. + They will be described one by one. </para> + <section> + <title>Selected Task Details Section for Input Task.</title> + <para>On the picture below you can find an example of Selected Task Details Section view + if XML is selected as input type.</para> + + <figure> + <title>Selected Task Details Section for Input XML Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_2.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>As you can see on the picture above Input Configuration section is empty for XML input file. + But this section has special configuration options for CSV,EDI,JSON,Custom input files.</para> + + <para>Here are the screens of these configuration options:</para> + <itemizedlist> + <listitem><para>CSV:</para> + <figure> + <title>Selected Task Details Section for Input CSV Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_3.png" /> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem><para>EDI:</para> + <figure> + <title>Selected Task Details Section for Input EDI Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_4.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem><para>JSON:</para> + <figure> + <title>Selected Task Details Section for Input JSON Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_5.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem><para>Custom:</para> + <figure> + <title>Selected Task Details Section for Input Custom Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_6.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <para>All the input task configuration positions can be found in the table below:</para> + <table> + <title>Selected Task Details Section. Options for Input Task.</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" align="left" colwidth="3*"/> + <colspec colnum="3" align="left" colwidth="1*"/> + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + <row> + <entry>Input type</entry> + <entry>Select your type of input file. + If don't find your type in the list,you should use Custom type: + <itemizedlist> + <listitem><para>No Input</para></listitem> + <listitem><para>XML</para></listitem> + <listitem><para>Java</para></listitem> + <listitem><para>XSD/WSDL</para></listitem> + <listitem><para>CSV</para></listitem> + <listitem><para>EDI</para></listitem> + <listitem><para>JSON</para></listitem> + <listitem><para>Custom</para></listitem> + </itemizedlist> + </entry> + <entry>XML</entry> + </row> + + <row> + <entry>Input configuration + + </entry> + <entry> + <itemizedlist> + <listitem><para><emphasis>No Input</emphasis> - no info required</para></listitem> + <listitem><para><emphasis>XML</emphasis> - no info required</para></listitem> + <listitem><para><emphasis>Java</emphasis> - no info required</para></listitem> + <listitem><para><emphasis>XSD/WSDL</emphasis> - no info required</para></listitem> + <listitem><para><emphasis>CSV</emphasis></para><itemizedlist> + <listitem><para><emphasis>Fields</emphasis> - Comma separated list of CSV record field names + </para></listitem> + <listitem><para><emphasis>Separator Character</emphasis> - Field separator character. Default of ','. + </para></listitem> + <listitem><para><emphasis>Quote Character</emphasis> - Quote character. Default of '"'. + </para></listitem> + <listitem><para><emphasis>Record Name</emphasis> - Name of csv record element.Default:csv-record</para></listitem> + <listitem><para><emphasis>Root Name</emphasis> - Name of csv root element.Default:csv-set</para></listitem> + <listitem><para><emphasis>indent</emphasis> - Add indentation character data to the generated event stream. This simply makes + the generated event stream easier to read in its serialized form. Useful for + testing etc.Default:true + </para></listitem> + <listitem><para><emphasis>Skip Lines</emphasis> - Number of lines to skip before processing starts. Default of 0. + + </para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>EDI</emphasis></para> + <itemizedlist> + <listitem><para><emphasis>Target Profile</emphasis> - Defines the target profile + </para></listitem> + <listitem><para><emphasis>Encoding</emphasis> - The character encoding. Default "UTF-8"</para></listitem> + <listitem><para><emphasis>Mapping Model</emphasis> - Defines the EDI Mapping Model configuration for processing the + EDI message stream to a stream of SAX events that can be processed by Smooks.</para></listitem> + <listitem><para><emphasis>Validate</emphasis> - This attribute turns on/off datatype validation in the EDI Parser. + Validation is on by default. + It makes sense to turn datatype validation off on the EDI Reader + if the EDI data is being bound into a Java Object model. + </para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>JSON</emphasis></para> + <itemizedlist> + <listitem><para><emphasis>Target Profile</emphasis> - Defines the output transformation profile</para></listitem> + <listitem><para><emphasis>Array Element Name</emphasis> - The element name of a array element. Default of 'element'. + </para></listitem> + <listitem><para><emphasis>Encoding</emphasis> - encoding: The default encoding of any JSON message + InputStream processed by this Reader. Default of 'UTF-8'.</para></listitem> + <listitem><para><emphasis>Illegal Element Name Char Replacement</emphasis> - If illegal characters are encountered in a JSON element name then they are replaced with this value. + By default this is not defined, so that the reader doesn't doesn't search for illegal characters. + </para></listitem> + <listitem><para><emphasis>Indent</emphasis> - Add indentation character data to the generated event stream. This simply makes + the generated event stream easier to read in its serialized form. Useful for + testing etc.Default:false. + </para></listitem> + <listitem><para><emphasis>Key Prefix on Numeric</emphasis> - The prefix character to add if the JSON node name starts with a number. + By default this is not defined, so that the reader doesn't search for element names that start with a number. + </para></listitem> + <listitem><para><emphasis>Key Whitespace Replacement</emphasis> - The replacement character for whitespaces in a JSON map key. + By default this not defined, so that the reader doesn't search for whitespaces. + </para></listitem> + <listitem><para><emphasis>Null Value Replacement</emphasis> - The replacement string for JSON NULL values. Default is ""(an empty string). </para></listitem> + <listitem><para><emphasis>Root Name</emphasis> - The element name of the document root. Default of 'json'. + </para></listitem> + <listitem><para><emphasis>Key Maps</emphasis> - Defines a JSON element name mapping + The "from" key will be replaced with the "to" key or the contents of the element. + </para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>Custom</emphasis></para> + <itemizedlist> + <listitem><para><emphasis>Target Profile</emphasis> - Defines the output transformation profile</para></listitem> + <listitem><para><emphasis>Class</emphasis> - Custom reader class.</para></listitem> + <listitem><para><emphasis>Handlers</emphasis> - Set a handler on the reader instance e.g. an EntityResolver, ErrorHandler etc. + </para></listitem> + <listitem><para><emphasis>Features</emphasis> - Reader Features List</para></listitem> + <listitem><para><emphasis>Parametres</emphasis> - Resource Parameters</para></listitem> + + </itemizedlist> + </listitem> + </itemizedlist></entry> + <entry><itemizedlist> + <listitem><para><emphasis>CSV</emphasis></para><itemizedlist> + <listitem><para>not defined</para></listitem> + <listitem><para>','</para></listitem> + <listitem><para>'"'</para></listitem> + <listitem><para>csv-record</para></listitem> + <listitem><para>csv-set</para></listitem> + <listitem><para>true</para></listitem> + <listitem><para>0</para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>EDI</emphasis></para> + <itemizedlist> + <listitem><para>not defined</para></listitem> + <listitem><para>UTF-8</para></listitem> + <listitem><para>not defined</para></listitem> + <listitem><para>true</para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>JSON</emphasis></para> + <itemizedlist> + <listitem><para>not defined</para></listitem> + <listitem><para>element</para></listitem> + <listitem><para>UTF-8</para></listitem> + <listitem><para>not defined</para></listitem> + <listitem><para>false</para></listitem> + <listitem><para>not defined</para></listitem> + <listitem><para>not defined</para></listitem> + <listitem><para>""(an empty string)</para></listitem> + <listitem><para>'json'</para></listitem> + <listitem><para>not defined</para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>Custom</emphasis></para> + <itemizedlist> + <listitem><para>no defaults</para></listitem> + + </itemizedlist> + </listitem> + </itemizedlist></entry> + </row> + <row> + <entry>Input Data</entry> + <entry>You should select a data file using <emphasis>Add</emphasis> and <emphasis>Delete</emphasis> buttons</entry> + <entry></entry> + </row> + <row> + <entry>Input Model View</entry> + <entry>Using this view you can see the structure of your input file.If the file has been changed, to see the changes + click <emphasis>Refresh</emphasis>link.</entry> + <entry></entry> + </row> + </tbody> + </tgroup> + </table> + </section> + <section id="mapping_task"><title>Selected Task Details section for Java Mapping Task.</title> + <para>Selected Task Details section for this task is presented by the graf, + that lighten the process of java mapping. </para> + <figure> + <title>Selected Task Details Section for Mapping Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_7.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>This graphical editor allows you to perform drag&drop operation with the nodes of transformed data to map the source data to target data. + When you save the changes in the graphical editor the correct Smooks configuration file content will be generated. </para> + + </section> + <section><title>Selected Task Details section for Template Task.</title> + <para>Selected Task Details section for this task is presented by the graf, + that is similar to the one in the <link linkend="mapping_task">previous section</link>. + </para> + <figure> + <title>Selected Task Details Section for Template Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_7a.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> + + </section> + <section id="options_tab"> + <title>Options Tab</title> + <para>This section describes Options tab of the Smooks Configuration File editor, gives short recommendations how this tab can be used during the project configuring.</para> + <figure> + <title> Options tab of the Smooks Configuration File editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_8.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <section> + <title>Smooks Configuration section</title> + <para> + In the <property>Smooks Configuration</property> section of <property>Options Tab</property> + only one element is availible:Smooks Platform Version + </para> + <figure> + <title>Smooks Configuration section of Options tab</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_9.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>This parameter is not rechangable, + and is set according to the vesion of the Smooks libraries that are added to the project. + </para> + </section> + + <section> + <title>Filter Settings Filter section</title> + <para> + In Filter Settings section you can set + the following global options responsible for Smooks filtering configuring:</para> + <figure> + <title>Filter Settings section of Options tab</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_10.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>This behavior can be turned off using this global configuration parameter and can be overriden on a per fragment basis by targetting a Visitor implementation at that fragment that takes ownership of the Result writer (in the case of SAX filtering), or simply modifies the DOM (in the case of DOM filtering). As an example of this, see the FreeMarkerTemplateProcessor. + </para> + <table> + <title>Options Tab. Filter Settings section.</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" align="left" colwidth="3*"/> + <colspec colnum="3" align="left" colwidth="1*"/> + + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + <row> + <entry>Stream Filter Type</entry> + <entry>Determines the type of processing model that will be used. + Please refer to <ulink url="http://www.smooks.org/mediawiki/index.php?title=V1.2:Smooks_v1.2_User_Gui..."> + Filtering Process Selection section</ulink> + of the official Smooks User Guide for more information about these models: + <itemizedlist> + <listitem><para><emphasis>SAX</emphasis></para></listitem> + <listitem><para><emphasis>DOM</emphasis></para></listitem> + </itemizedlist> + </entry> + <entry>SAX</entry> + </row> + + <row> + <entry>Default Serialization is On</entry> + <entry>Defines whether default serialization should be switched on. + Default serialization being turned on leads to locating StreamResult/DOMResult + to the Result objects provided to the Smooks.filterSource method and to + serialization all the events to that Result.</entry> + <entry>false</entry> + + </row> + </tbody> + </tgroup> + </table> + </section> + </section> + <section id="smooksformeditor_sourcetab" xreflabel="Smooks Source Tab"> + + <title>Source Tab</title> + <para>This section provides information about Smooks Source Editor Page.</para> + <section> + <title>XML Source Editor</title> + <para>You can use this editor to edit the Smooks Configuration file directly. </para> + <figure> + <title>Graphical Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/source_editor1.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>Error underlining in Graphical Editor</title> + <para>If the <property>Smooks tools</property> can't understand the configuration + file or the configuration file is illegal (XML structure isn't right for Smooks + Configuration file, etc.), the error is underlined.</para> + <figure> + <title>Graphical Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_11.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + + </section> + + <section> + <title>Smooks Configuration File Validator</title> + <para>Smooks configuration file validator will validate your Smooks configuration file. Just right-click on the file and then click on the <property>Validate</property> button. The validator can be enabled/disabled in <emphasis><property>Window -> Preferences -> Validation</property></emphasis>:</para> + + <figure> + <title>Validation: Smooks Configuration File Validator</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/smooks_conf_validator.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + + <para>You can set up your Smooks validator to include, exclude groups to validate and specify rules for validation. Just click on the <property>Settings</property> button and use the options provided:</para> + + <figure> + <title>Smooks Configuration File Validator Settings</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/smooks_conf_validator_settings.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + + + </section> + </section> + +</chapter> Property changes on: trunk/smooks/docs/reference/en-US/references.xml ___________________________________________________________________ Name: svn:executable + * Added: trunk/smooks/docs/reference/en-US/smooksformeditor_configurationpage.xml =================================================================== --- trunk/smooks/docs/reference/en-US/smooksformeditor_configurationpage.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/smooksformeditor_configurationpage.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,270 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="smooksformeditor_configurationtab" xreflabel="Smooks Configuration Editor Page"> + <?dbhtml filename="smooks_form_editor_configurationtab.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Smooks Design Page</title> + <para>In this section you will explore the details of Smooks Design Page usage.</para> + <para><property>Smooks Design Page</property> is one tab of the <property>Smooks Editor</property>. </para> + <figure> + <title>Design Page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/config_page/config_page1.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>This page consists of 3 sections: Message Filtering Resources, Input Data and the section devoted to the configurations of a selected in a Message Filtering Resources section Item.</para> + <para> You can bind classes <link linkend="quickstart_mapping">using Bindings item + </link> on the Design page of the <property>Smooks Editor</property>. </para> + <para><emphasis> + <property>Resource list</property></emphasis> item in <emphasis> + <property>Message Filtering Resources</property></emphasis> corresponds to the root element of the <emphasis> + <property>smooks-config.xml</property></emphasis> file.You can configurate the next four properties using corresponding fields:</para> + <itemizedlist> + <listitem><para><emphasis> + <property>default-selector</property></emphasis>:Defines the selector that will be applied to all resource-config elements in the <emphasis> + <property>smooks-config.xml</property></emphasis>, where a selector is not defined. </para></listitem> + <listitem><para><emphasis> + <property>default-selector-namespace</property></emphasis>:Defines the default selector namespace. </para></listitem> + <listitem><para><emphasis> + <property>default-target-profile</property></emphasis>: Defines the default target profile that will be applied to all resources in the smooks-config.xml. </para></listitem> + <listitem><para><emphasis> + <property>default-condition-ref</property></emphasis>:The condition is applied to resources where an empty "condition" element (i.e. <code><condition/></code>)is defined.The condition element does not reference a globally defined condition. </para></listitem> + </itemizedlist> + <para> The configuration editor also edits the <link linkend="configurationpage_parsetype">Smooks parse + type</link> and manages the <link linkend="configurationpage_importfile">Import + Files</link>.</para> + <section id="selector-dialog"> + <title>Selector generate dialog</title> + <para>Using <emphasis> + <property>Selector generate dialog</property></emphasis> you can allow the user to select a node for generation <property>"selector"</property> for smooks-config file. + To open the dialog you should left click <property>Browse</property> button in <emphasis> + <property>Default Selector</property></emphasis> section. + </para> + <figure> + <title>Selector generate dialog</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/config_page/config_page2a.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para> When the dialog is opened you should click <property>"Click to add input data"</property>to set the selector. + In the opened <emphasis> + <property>Data Type Selection</property></emphasis> Wizard you should choose the type of the file and the file itself you want to load to the <emphasis> + <property>Selector generate dialog</property></emphasis>.After that your dialog should look nearly like that:</para> + <figure> + <title>Selector generate dialog after adding Input Data</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/config_page/config_page2b.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>The final step is to choose the node you want to make a selector for <emphasis> + <property>smooks-config.xml</property></emphasis>.</para> + </section> + <section id="configurationpage_parsetype"> + + <title>Smooks Parse Type</title> + <para>If your config file doesn't contain <emphasis> + <property>Global Parametres</property></emphasis> item yet, you should add it by right click <emphasis> + <property>Resource List>Add Smooks Resource>Global Parametres</property></emphasis>.After this step you should add <emphasis> + <property>Param</property></emphasis> to just created <emphasis> + <property>Global Parametres</property></emphasis>. </para> + <figure> + <title>Adding Param to created Global Parametres</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/config_page/config_page2.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>Then left click <emphasis> + <property>Param</property> + </emphasis>and in the Param section, you will see a set of text fields: <emphasis> + <property>Name</property></emphasis>,<emphasis> + <property>Type</property></emphasis> and <emphasis> + <property>Text</property></emphasis>.<emphasis> + <property>Name</property></emphasis> value is required. To set a parse type you should write SAX/DOM to the + <emphasis> + <property>Text</property></emphasis> field.</para> + + <figure> + <title>Filling Param section field Name and Text Value for set a Parse Type</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/config_page/config_page3.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>To apply changes to the <emphasis> + <property>smooks-config.xml</property></emphasis> click <emphasis> + <property>Save</property></emphasis> button (<emphasis> + <property>Ctrl+S</property></emphasis>). </para> + </section> + <section id="configurationpage_importfile"> + + <title>Import Smooks Configuration page</title> + <para> Right click <emphasis> + <property>Resource List>Add Smooks Resource>Import Smooks Configuration</property> + </emphasis>, then you should see a new <emphasis> + <property>Import Smooks Configuration</property> + </emphasis>item in the list (see the figure below).</para> + + <figure> + <title>Import Data</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/config_page/config_page3a.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>Left click the added item and to the left of <emphasis> + <property>Message Filtering Resources Import Smooks Configuration </property></emphasis> section should appear. Click the <emphasis> + <property>Browse</property> + </emphasis> button and select the file you want to import(see <link linkend="file_selection">File selection</link> section). </para> + <para>Click <emphasis> + <property>Save</property></emphasis> and the <code><import></code> tag with the corresponding file path as a <emphasis> + <property>file</property></emphasis> property will be added to the <emphasis> + <property>smooks-config.xml</property></emphasis>.</para> + </section > + <section id="file_selection"> + <title>File selection</title> + <para>Some attributes in Smooks elements should store path to a file as a value + (e.g. attribute <emphasis><property>"mappingModel"</property></emphasis> of the element <emphasis><property>"edi:reader"</property></emphasis>). + You can see a Browse button near the fields, that set such a value to the attribute + (e.g. <emphasis><property>"Mapping Model"</property></emphasis> field set a value to the <emphasis><property>"mappingModel"</property></emphasis> attribute). + </para> + <figure> + <title>EDI:Reader element</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/config_page/config_page6.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para> + When you click <emphasis><property>Browse</property></emphasis>, the dialog prompts you click one of two buttons: + <emphasis><property>Browse File System</property></emphasis> and <emphasis><property>Browse WorkSpace</property></emphasis>. + </para> + <figure> + <title>Browse dialog</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/config_page/config_page7.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>Using the buttons you can locate the file you need. If you click <emphasis> + <property>Browse File System</property></emphasis> button you specify the path of, or browse to, a file system directory. + </para> + <figure> + <title>Browse file system</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/config_page/config_page8.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para> + If you click <emphasis><property>Browse WorkSpace</property></emphasis> button, you specify the path of, or browse to, a workspace relative working directory. + </para> + <figure> + <title>Browse Workspace</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/config_page/config_page9.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + </section> +  +</chapter> Added: trunk/smooks/docs/reference/en-US/smooksformeditor_graphicalpage.xml =================================================================== --- trunk/smooks/docs/reference/en-US/smooksformeditor_graphicalpage.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/smooksformeditor_graphicalpage.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,172 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="smooksformeditor_graphicaltab" xreflabel="Smooks Graphical Editor Page" role="updated"> + <?dbhtml filename="smooks_form_editor_graphicaltab.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Smooks Graphical Editor Page</title> + <para>This chapter is packed with useful information about Smooks Graphical Editor Page usage</para> + <para>Smooks Graphical Editor page is one tab of the <property>Smooks Editor</property>.</para> + <figure> + <title>Graphical Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/graph_editor/graph_editor1.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + + <para> This <property>Graphical editor</property> allows you to perform drug/drop operations + with the nodes of transform data to map the source data to target data. </para> + <para> When you save the changes in the <property>Graphical editor</property> the correct Smooks + Configuration file content is generated. </para> + + <para>To adjust the properties of the connection lines in the editor, you should use the <link + linkend="graphicalpage_propertiesview">Properties view</link> (activate it by following + to <emphasis> + <property>Window > Show View > Other > General > Properties</property>).</emphasis></para> + + <para>For example, if you defined a date decoder in the <link + linkend="configurationpage_datedecoder">Smooks Configuration Editor</link>, in the <property>Properties view</property> you can + select it as a Mapping type for the "Date" type element.</para> + + <figure> + <title>Browsing Custom Type for the Date Type Element</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/graph_editor/graph_editor1a.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <section> + + <title>Introducing the areas of graphical editor</title> + <para>Information on the topic could be found in the <link linkend="quickstart_formeditor" + >Quick Start/Smooks Editor</link> section.</para> + </section> + <section> + + <title>Load Source/Target Data</title> + <para> Click the links under the data view, the <property>Data Type Selection + wizard</property> page will be shown.</para> + <figure> + <title>Data Type Selection Wizard Page</title> + <mediaobject> + <imageobject> + + <imagedata fileref="images/graph_editor/graph_editor2.png" scale="90"/> + + </imageobject> + </mediaobject> + </figure> + + <para> There are sets of transform data type on the wizard page, select one type and click + <emphasis><property>Next</property>,</emphasis> the data source selection wizard + page will be shown.</para> + + <tip> + <title>Note:</title> + <para>For different data type, the Data source selection wizard are different too. + </para> + </tip> + <figure> + <title>Java Data Source Selection Wizard Page</title> + <mediaobject> + <imageobject> + + <imagedata fileref="images/graph_editor/graph_editor3.png" scale="90"/> + + </imageobject> + </mediaobject> + </figure> + + <figure> + <title>XML File Path Selection Wizard Page</title> + <mediaobject> + <imageobject> + + <imagedata fileref="images/graph_editor/graph_editor4.png" scale="90"/> + + </imageobject> + </mediaobject> + </figure> + + <para> When you finish the data selection (file path selection), click + <emphasis><property>Finish</property>,</emphasis> the data view displays the + selected data structure.</para> + </section> + <section> + + <title>Using Graphical Editor for Mapping</title> + <para>To get information on the topic please, read the <link linkend="quickstart_mapping" + >Quick Start/Mapping</link> section. </para> + </section> + <section> + + <title>Error Messages</title> + <para>When you do any mapping operations, the <property>Smooks tools</property> validate the + file content with "Mapping Logic". If there are any errors of the configuration file + content, error messages are shown in the <link linkend="quickstart_formeditor">Problems + area</link>.</para> + <para> Please, read the <link linkend="quickstart_mapping">Quick Start/Mapping</link> + section to find how to fix the errors.</para> + </section> + <section id="graphicalpage_propertiesview"> + <title>Properties View</title> + + <para> You can edit the properties of the connection lines with the <property>Properties + view</property>.</para> + <para>Navigate to <emphasis><property>Window > Show View > Other > + Properties</property>,</emphasis> to open the <property>Properties + view</property>.</para> + <para> When you select the connection line, the <property>Properties view</property> will + show a set of section GUI for editing its properties.</para> + <tip> + + <title>Tip:</title> + <para>This GUI on the <property>Properties view</property> is displayed when the Smooks + Graphical editor is active, if not, the <property>Properties view</property> + displays empty GUI.</para> + <para>If the source data type of the selected connection line is + "XML", the <property>Properties view</property> shows an XML + Properties section GUI.</para> + <para>But if the source data type of the selected connection line is + "Java", the XML Properties section GUI isn't + displayed.</para> + <para>It means that if the source/target data type of the selected connection line is + different, the <property>Properties view</property> shows a different GUI.</para> + </tip> + <figure> + <title>JavaBean Properties Section</title> + <mediaobject> + <imageobject> + + <imagedata fileref="images/graph_editor/graph_editor5.png" scale="90"/> + + </imageobject> + </mediaobject> + </figure> + <figure> + <title>XML Properties Section</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/graph_editor/graph_editor6.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <figure> + <title>Mapping Properties Section</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/graph_editor/graph_editor7.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + + <para>To discover about other Editor pages, read the next chapters</para> + </section> +</chapter> Added: trunk/smooks/docs/reference/en-US/smooksformeditor_sourcepage.xml =================================================================== --- trunk/smooks/docs/reference/en-US/smooksformeditor_sourcepage.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/smooksformeditor_sourcepage.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,83 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="smooksformeditor_sourcetab" xreflabel="Smooks Source Editor Page"> + <?dbhtml filename="smooks_form_editor_sourcetab.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Smooks Source Editor Page</title> + <para>This section provides information about Smooks Source Editor Page.</para> + <section> + <title>XML Source Editor</title> + <para>You can use this editor to edit the Smooks Configuration file directly. </para> + <figure> + <title>Graphical Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/source_editor1.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>Error underlining in Graphical Editor</title> + <para>If the <property>Smooks tools</property> can't understand the configuration + file or the configuration file is illegal (XML structure isn't right for Smooks + Configuration file, etc.), the error is underlined.</para> + <figure> + <title>Graphical Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/source_editor2.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> +  + + + + </section> + + <section> + <title>Smooks Configuration File Validator</title> + <para>Smooks configuration file validator will validate your Smooks configuration file. Just right-click on the file and then click on the <property>Validate</property> button. The validator can be enabled/disabled in <emphasis><property>Window -> Preferences -> Validation</property></emphasis>:</para> + + <figure> + <title>Validation: Smooks Configuration File Validator</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/smooks_conf_validator.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + + <para>You can set up your Smooks validator to include, exclude groups to validate and specify rules for validation. Just click on the <property>Settings</property> button and use the options provided:</para> + + <figure> + <title>Smooks Configuration File Validator Settings</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/smooks_conf_validator_settings.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + + + <para>We hope, our guide will help you to get started with JBoss Smooks Tools. Besides, for additional information you are welcome on <ulink + url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para> + + </section> + + + + +</chapter> Added: trunk/smooks/docs/reference/en-US/summary.xml =================================================================== --- trunk/smooks/docs/reference/en-US/summary.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/summary.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,22 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<chapter> + <?dbhtml filename="summary.html"?> + <title>Summary</title> + <para>In conclusion, with this document you know all the capabilities of Smooks Tools and could easily start with them. + The chapters above walked you through the steps on how to create and configure some XML to JAVA mapping project. + If you have questions or suggestions concerned both the documentation and tools behavior, + you are welcome to JBoss Tools Users forum. + Please, use Jira to report bugs and requests on documentation.</para> + + <section> + <title>Other relevant resources on the topic</title> + <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at + <ulink url="http://docs.jboss.org/tools">http://docs.jboss.org/tools</ulink> in the corresponding release directory. + </para> + <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs">http://download.jboss.org/jbosstools/nightly-docs</ulink>. </para> +<para>For more information about Smooks technology please visit + <ulink url="http://www.smooks.org/mediawiki/index.php?title=Main_Page"> + Smooks Technology Home Page</ulink></para> + + </section> +</chapter> Added: trunk/smooks/docs/reference/en-US/tasks.xml =================================================================== --- trunk/smooks/docs/reference/en-US/tasks.xml (rev 0) +++ trunk/smooks/docs/reference/en-US/tasks.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,262 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="process_page"> + <?dbhtml filename="tasks.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Tasks</title> + <para>This chapter describes the main tasks a user can be faced during Smooks tools usage. + Here we use the example that can be downloaded from <ulink url="http://sourceforge.net/projects/smooks/files/Smooks%20v1.2/Smooks%20v1.2/...">here</ulink> </para> + <section id="config_file_wizzard"> + <title>New Smooks Configuration File Creation</title> + <para>Select the project where you want to create new Smooks Configuration File and right-click on it, + select in the menu <emphasis><property>New > Other</property>,</emphasis> then find + <emphasis><property>Smooks > Smooks Configuration File</property>.</emphasis> + Click the <emphasis> + <property>Next</property> + </emphasis> button. </para> + <figure> + <title>Selecting Smooks Configuration File Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start1.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>The wizard page is a file path creation page. Select the <emphasis> + <property>src</property> + </emphasis> folder to be the files container, and input the name + <emphasis><property>smooks-config.xml</property>.</emphasis> Click + <emphasis><property>Next</property>.</emphasis></para> + <figure> + <title>Choosing the configuration file container and the file name</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start2.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + + </section> + <section> + <title>Input Task Configuring</title> + <para> + <property>Input task configuring</property> is an obligatory step for your smooks project creation. + You can configure it on the Process page of the editor: look for the "Input Task" in the Process Map at the top of the page. + </para> + <figure> + <title>Input Task Configuring</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process1.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + <para>Select it and you will see all the properties to set for the Input reader of your Smooks configuration. + "Input type" corresponds to the type of data that you will be working with. + For example, to work with incoming CSV (Comma-separated Values) data, you would specify "CSV" in the drop-down list. + Each reader type has slightly different configuration details that must be set in the "Input configuration" area. + For instance, the CSV reader requires you to specify details such as the encoding, quote character, separator character, and the list of incoming fields. + The EDI reader requires the encoding and the path to the Mapping Model describing the incoming data. + In the <emphasis>Input data</emphasis> section, you specify some sample data that conforms to your reader configuration. + </para> + + <para> + Once you've specified your reader configuration and sample data, you can see the input model rendered in a tree form in the <emphasis>Input model</emphasis> section. + On the picture below you can see the correct configuration of some XML input task where <emphasis><property>input-message.xml</property></emphasis> is set as an input data file. + </para> + <figure> + <title>Input Task Configuring</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process2.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>"Java Mapping" or "Apply Template"?</title> + + <para>Though there are many options in Smooks as far as what you can do with input + data such as transformation, routing, and persistence, this version + of the Smooks Configuration Editor focuses only on these areas: + mapping to java and applying templates to create different output formats. + If you have a set of Java classes you want to use the incoming data for, + you can use the "Java Mapping" task to specify those classes and use drag and + drop to map between the input model generated by the reader and elements in the output model. + Or if you simply want to transform your output to one or more formats, you can use the "Apply Template" + task to map it to a CSV file, XML or XSD file (and other formats in the future). + <note><title>Note</title> + <para>Now you can't transform your output directly, + using only Input and Template tasks. + You should use Mapping as an interagent between these tasks.</para> + </note> + </para> + </section> + <section id="mapping"> + <title>Java Mapping Task</title> + + <para> + If you decide to do Java Mapping, you need to make sure that your Input reader has been set up and you have some sample data specified. + Then you should select <emphasis>Input Task</emphasis> in the Process tab and click the plus (+) sign to the right of the icon. + Select <emphasis>Java Mapping</emphasis> from the popup menu and it will appear to the right, connected to <emphasis>Input Task</emphasis>. Then select <emphasis>Java Mapping</emphasis> task. + </para> + <figure> + <title>Java Mapping configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Another method of adding <emphasis>Java Mapping</emphasis> element + to the canvas in the Processing Tasks section is to right click Input Task + element and select <emphasis>Java Mapping</emphasis> in the popup menu. </para> + <figure> + <title>Java Mapping configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process4.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + Right-click on the canvas in an empty space and select "Add ->Java Class". + </para> + <figure> + <title>Java Mapping configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process5.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + <emphasis>Java Bean Creation</emphasis> wizard appears. + Specify a unique identifier for the new class, the class path. + If the Java class is specified, you'll see a list of the properties in the box below. + Click <emphasis>Finish</emphasis> when you're done. + Now with the input and output models on the canvas, you can click and drag + from the various input elements to corresponding output elements. + Make sure to connect collection elements to corresponding collection elements. + Finally your mapping should look nearly like the one on the picture below. + </para> + <figure> + <title>Final Mapping schema</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process6.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>Apply Template Task</title> + + <para>The "Apply Template" task works very similarly to the <link linkend="mapping">"Java Mapping" task</link>, where you map between an input model and an output model. + Select the <emphasis>Java Mapping</emphasis> task you want to use as the input model in the Process Map pane and click the plus (+) sign to the right of the icon. + </para> + <figure> + <title>Apply Template configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process7.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + The <property>Message Type Selection</property> wizard will appear. + In our example we will transfer our data to csv output format,so you should select <emphasis><property>CSV</property></emphasis> and click <property>Next</property>.</para> + <figure> + <title>Message Type Selection</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process7a.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + On the next wizard page put the following string into the Fields,select Output fields Names and click <property>Finish</property>.</para> + <figure> + <title>CSV output message configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process7b.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + After these steps "Apply Template" task will appear to the right, connected to the task you created it from. + To continue the process of configuration you should click on it and find <emphasis>CSV Template</emphasis> + item with entered fields on the canvas.Now you can click and drag from various input elements to corresponding output elements + in the template. Make sure to connect collection elements to corresponding <emphasis>csv-record</emphasis> + In our example we transfer into CSV output only the elements of orderItems collection(see picture below) + </para> + <figure> + <title>Relations between input and output models</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process7c.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>Smooks Configuration testing using Smooks Run Configuration</title> + + <para>This option is intended to view the results of Smooks transforming procedure. + To do the testing you should select your <emphasis>Smooks Configuration file</emphasis> you want to transfer in the Project Navigator or open it in + the Smooks Configuration Editor and then select "Run As..." from the <emphasis><property>Run</property></emphasis> + toolbar button + or <emphasis><property>Run->Smooks Run Configuration</property></emphasis> option in the top menu bar. And Smooks Configuration file will be run automatically. + </para> + <figure> + <title>Smooks Configuration testing</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process8.png"/> + </imageobject> + </mediaobject> + </figure> + <para>If any errors or warnings appear, they will pop up in a dialog. + The output of the test will appear in the Console view. + In our case the following streaming output will appear:</para> + <programlisting role="JAVA"><![CDATA[[Stream Templating Result ...] + |-- + |"productId","quantity","price" + |"111","2","8.9" + |"222","7","5.2" + |-- + +[Java Mapping Results...] + |-- + |> order (beanId = "order") + | > header (beanId = "header") + | > date = "2006-11-15 20:45:28.0 EET" + | > customerNumber = 123123L + | > customerName = "Joe" + | > orderItems (beanId = "orderItems") + | > example.model.OrderItem (beanId = "orderItem") + | > productId = 111L + | > quantity = 2I + | > price = 8.9D + | > example.model.OrderItem (beanId = "orderItem") + | > productId = 222L + | > quantity = 7I + | > price = 5.2D + |-- +]]></programlisting> + <para>If the test runs but doesn't generate any streaming output the Console output will be the following: + </para> + <programlisting role="JAVA"><![CDATA[ Nothing to Display: + - No Java Mappings. + - No Templates Applied.]]> + </programlisting> + + </section> +</chapter> + Modified: trunk/smooks/docs/reference/pom.xml =================================================================== --- trunk/smooks/docs/reference/pom.xml 2010-03-09 23:47:35 UTC (rev 20718) +++ trunk/smooks/docs/reference/pom.xml 2010-03-10 00:34:57 UTC (rev 20719) @@ -95,9 +95,9 @@ <configuration> <sourceDocumentName>${master}</sourceDocumentName> - <sourceDirectory>${pom.basedir}/en</sourceDirectory> + <sourceDirectory>${pom.basedir}/en-US</sourceDirectory> <imageResource> - <directory>${pom.basedir}/en</directory> + <directory>${pom.basedir}/en-US</directory> <includes> <include>images/**/*</include> </includes> Added: trunk/smooks/docs/reference/publican.cfg =================================================================== --- trunk/smooks/docs/reference/publican.cfg (rev 0) +++ trunk/smooks/docs/reference/publican.cfg 2010-03-10 00:34:57 UTC (rev 20719) @@ -0,0 +1,7 @@ +# Config::Simple 4.59 +# Fri Nov 20 13:19:45 2009 + +xml_lang: en-US +type: Book +brand: JBoss +

14 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r20718 - in trunk/documentation/guides/MigrationGuide: en-US and 1 other directories.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2010-03-09 18:47:35 -0500 (Tue, 09 Mar 2010) New Revision: 20718 Added: trunk/documentation/guides/MigrationGuide/en-US/ trunk/documentation/guides/MigrationGuide/en-US/Author_Group.xml trunk/documentation/guides/MigrationGuide/en-US/Book_Info.xml trunk/documentation/guides/MigrationGuide/en-US/Migration_Guide.ent trunk/documentation/guides/MigrationGuide/en-US/Migration_Guide.xml trunk/documentation/guides/MigrationGuide/en-US/Preface.xml trunk/documentation/guides/MigrationGuide/en-US/Revision_History.xml trunk/documentation/guides/MigrationGuide/en-US/images/ trunk/documentation/guides/MigrationGuide/en-US/images/jdbs2.png trunk/documentation/guides/MigrationGuide/en-US/images/jdbs4.png trunk/documentation/guides/MigrationGuide/en-US/images/migration-guide-step-1.png trunk/documentation/guides/MigrationGuide/en-US/introduction.xml trunk/documentation/guides/MigrationGuide/en-US/issues.xml trunk/documentation/guides/MigrationGuide/en-US/master.xml trunk/documentation/guides/MigrationGuide/en-US/migration.xml trunk/documentation/guides/MigrationGuide/publican.cfg Removed: trunk/documentation/guides/MigrationGuide/en/ Modified: trunk/documentation/guides/MigrationGuide/pom.xml Log: updated book to build with publican and maven Added: trunk/documentation/guides/MigrationGuide/en-US/Author_Group.xml =================================================================== --- trunk/documentation/guides/MigrationGuide/en-US/Author_Group.xml (rev 0) +++ trunk/documentation/guides/MigrationGuide/en-US/Author_Group.xml 2010-03-09 23:47:35 UTC (rev 20718) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<authorgroup><author><firstname>JBoss Tools Team</firstname></author></authorgroup> Added: trunk/documentation/guides/MigrationGuide/en-US/Book_Info.xml =================================================================== --- trunk/documentation/guides/MigrationGuide/en-US/Book_Info.xml (rev 0) +++ trunk/documentation/guides/MigrationGuide/en-US/Book_Info.xml 2010-03-09 23:47:35 UTC (rev 20718) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<bookinfo><title>Migration Guide</title><subtitle>JBoss Developer Studio 2.1 to 3.0.</subtitle><productname>JBoss Developer Studio</productname><productnumber>3.0</productnumber><edition>1.0</edition><pubsnumber>0</pubsnumber><abstract><para>The JBoss Developer Studio Migration Guide explains how to migrate from the previous version of the JBoss Developer Studio to the latest version.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo> Added: trunk/documentation/guides/MigrationGuide/en-US/Migration_Guide.ent =================================================================== --- trunk/documentation/guides/MigrationGuide/en-US/Migration_Guide.ent (rev 0) +++ trunk/documentation/guides/MigrationGuide/en-US/Migration_Guide.ent 2010-03-09 23:47:35 UTC (rev 20718) @@ -0,0 +1,4 @@ +<!ENTITY PRODUCT "JBoss"> +<!ENTITY BOOKID "Migration_Guide"> +<!ENTITY YEAR "2010"> +<!ENTITY HOLDER "Red Hat"> Added: trunk/documentation/guides/MigrationGuide/en-US/Migration_Guide.xml =================================================================== --- trunk/documentation/guides/MigrationGuide/en-US/Migration_Guide.xml (rev 0) +++ trunk/documentation/guides/MigrationGuide/en-US/Migration_Guide.xml 2010-03-09 23:47:35 UTC (rev 20718) @@ -0,0 +1,11 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<book> +<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="migration.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +</book> Added: trunk/documentation/guides/MigrationGuide/en-US/Preface.xml =================================================================== --- trunk/documentation/guides/MigrationGuide/en-US/Preface.xml (rev 0) +++ trunk/documentation/guides/MigrationGuide/en-US/Preface.xml 2010-03-09 23:47:35 UTC (rev 20718) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<preface><title>Preface</title><xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></xi:fallback></xi:include></preface> Added: trunk/documentation/guides/MigrationGuide/en-US/Revision_History.xml =================================================================== --- trunk/documentation/guides/MigrationGuide/en-US/Revision_History.xml (rev 0) +++ trunk/documentation/guides/MigrationGuide/en-US/Revision_History.xml 2010-03-09 23:47:35 UTC (rev 20718) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<appendix><title>Revision History</title><simpara><revhistory><revision><revnumber>0</revnumber><date>Fri Nov 20 2009</date><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email></author><revdescription><simplelist><member>Initial creation of book by publican</member></simplelist></revdescription></revision></revhistory></simpara></appendix> Added: trunk/documentation/guides/MigrationGuide/en-US/images/jdbs2.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/MigrationGuide/en-US/images/jdbs2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/MigrationGuide/en-US/images/jdbs4.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/MigrationGuide/en-US/images/jdbs4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/MigrationGuide/en-US/images/migration-guide-step-1.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/MigrationGuide/en-US/images/migration-guide-step-1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/MigrationGuide/en-US/introduction.xml =================================================================== --- trunk/documentation/guides/MigrationGuide/en-US/introduction.xml (rev 0) +++ trunk/documentation/guides/MigrationGuide/en-US/introduction.xml 2010-03-09 23:47:35 UTC (rev 20718) @@ -0,0 +1,27 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="introduction" xreflabel="introduction"> + <?dbhtml filename="introduction.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>JBDS</keyword> + <keyword>Exadel Studio Pro</keyword> + </keywordset> + </chapterinfo> + + <title>Introduction </title> + <para>This document is intended to help you to easily migrate from 2.1 to 3.0.0 + <property>JBoss Developer Studio</property>. + It also describes some popular issues that can appear while the process of migration, + as well as the methods of their solving. </para> + + + <section> + <title>Other relevant resources on the topic</title> + <para>All JBoss Developer Studio release documentation you can find at <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/">http://www.redhat.com/docs/en-US/JBoss_Developer_Studio</ulink> in the corresponding release directory.</para> + <para>For more information about JBoss Developer Studio please visit + <ulink url="http://www.jboss.com/products/devstudio/">http://www.jboss.com/products/devstudio/</ulink>.</para> + <para>If your problem is not described in the guide or you have questions or suggestions concerned both the documentation and studio behavior, you are welcome at <ulink url="http://community.jboss.org/en/jbossdevstudio?view=discussions">JBoss Users forum</ulink>. + </para> + </section> +</chapter> Property changes on: trunk/documentation/guides/MigrationGuide/en-US/introduction.xml ___________________________________________________________________ Name: svn:executable + * Added: trunk/documentation/guides/MigrationGuide/en-US/issues.xml =================================================================== --- trunk/documentation/guides/MigrationGuide/en-US/issues.xml (rev 0) +++ trunk/documentation/guides/MigrationGuide/en-US/issues.xml 2010-03-09 23:47:35 UTC (rev 20718) @@ -0,0 +1,59 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="issues" xreflabel="issues"> + <?dbhtml filename="introduction.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>JBDS</keyword> + <keyword>Exadel Studio Pro</keyword> + </keywordset> + </chapterinfo> + + <title>Possible issues</title> + <para>In this chapter you will find a list of most popular + issues that can appear while the process of migration. + </para> + + + <section> + <title>Visual Editor starts with "Missing Natures" message dialog</title> + <para>While opening existing projects or creating new ones + with some standard eclipse wizards this message can appear:</para> + <figure> + <title>"Missing Natures" message</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jbds4.png" /> + </imageobject> + </mediaobject> + </figure> + <para>This message shows that some functionality of Visual Editor may not work if a project + doesn't have org.jboss.tools.jsf.jsfnature or org.jboss.tools.jst.web.kb.kbnature + in .project configuration. To fix this problem and turn off the message box execute the following steps:</para> + <itemizedlist> + <listitem><para>Right click the project in Package Explorer.</para></listitem> + <listitem><para>Select <property>Configure -> Add JSF Capabilities</property> from the context menu.</para></listitem> + <listitem><para>Configure your project using Add JSF Capabilities wizard and press <property>Finish</property></para></listitem> + </itemizedlist> + </section> + + + <section> + <title>Visual Editor doesn't start and "XPCOM error -2147467259" appears</title> + <para>This error shows that you have problems with your buildin XULRunner plugin.To resolve the issue,please: </para> + <itemizedlist> + <listitem><para>Open <property>Help -> About JBoss Developer Studio-> Installation Details... -> Configuration</property></para></listitem> + <listitem><para>find org.eclipse.swt.browser.XULRunnerPath and open this path in terminal</para></listitem> + <listitem><para>try xulrunner.exe -version or ./xulrunner -version command and you will see what is needed for XULRunner to work</para></listitem> + </itemizedlist> + </section> + <section> + <title>Problems with <emphasis>not "JBDS"</emphasis> plugins</title> + <para>Some additional plugins that are not supplied by JBDS and work on JBDS 2.X may not work on 3.0.0.GA</para> + <itemizedlist> + <listitem><para>To solve the problem check whether the plugin is compatible with Eclipse 3.5.</para></listitem> + <listitem><para>But because such pugins are not supported by JBDS, we can not guarantee its proper work.</para></listitem> + </itemizedlist> + </section> + +</chapter> Added: trunk/documentation/guides/MigrationGuide/en-US/master.xml =================================================================== --- trunk/documentation/guides/MigrationGuide/en-US/master.xml (rev 0) +++ trunk/documentation/guides/MigrationGuide/en-US/master.xml 2010-03-09 23:47:35 UTC (rev 20718) @@ -0,0 +1,30 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" +"http://www.docbook.org/xml/4.3/docbookx.dtd" + +[<!ENTITY introduction SYSTEM "introduction.xml"> +<!ENTITY migration SYSTEM "migration.xml"> +<!ENTITY issues SYSTEM "issues.xml"> +<!ENTITY gsglink "../../GettingStartedGuide/html_single/index.html"> + +]> + +<book> + <bookinfo> + <title>JBoss Developer Studio 2.1 to 3.0 Migration Guide</title> + + + <copyright> + <year>2010</year> + <holder>JBoss by Red Hat</holder> + </copyright> + <releaseinfo> +Version: 3.0.0.GA +</releaseinfo> + </bookinfo> + + <toc/> +&introduction; +&migration; +&issues; +</book> Property changes on: trunk/documentation/guides/MigrationGuide/en-US/master.xml ___________________________________________________________________ Name: svn:executable + * Added: trunk/documentation/guides/MigrationGuide/en-US/migration.xml =================================================================== --- trunk/documentation/guides/MigrationGuide/en-US/migration.xml (rev 0) +++ trunk/documentation/guides/MigrationGuide/en-US/migration.xml 2010-03-09 23:47:35 UTC (rev 20718) @@ -0,0 +1,56 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="jsf_struts" xreflabel="jsf_struts"> + <?dbhtml filename="jsf_struts.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>JBDS</keyword> + <keyword>Exadel Studio Pro</keyword> + <keyword>Migration</keyword> + </keywordset> + </chapterinfo> + + <title>Migration Process</title> + <para>In this chapter you can find concise description of JBoss Developer Studio migration from + 2.1.0 to 3.0.0 version.</para> + <section id="migration"> + <title>How to migrate from 2.1 to 3.0.0 JBoss Developer Studio</title> + <para></para> + <para>To migrate from 2.1 to 3.0.0 you have to install a fresh JBDS 3.0.0 and go through all the steps of + installation process that is fully described in + <ulink url="gsglink">Getting Started with JBoss Developer Studio</ulink> guide.</para> + <figure> + <title>Process of JBDS 3.0.0 installation </title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jbds2.png" /> + </imageobject> + </mediaobject> + </figure> + <para>Now you can not update your JBDS 2.X to 3.0.0 using update site (https://devstudio.jboss.com/updates/3.0/ ), as it was available in previous versions:</para> + <figure> + <title>Installation from the update site</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/migration-guide-step-1.png" /> + </imageobject> + </mediaobject> + </figure> + <para>The reason is that JBDS 3.0 uses Eclipse 3.5, whereas JBDS 2.x uses Eclipse 3.4. + Because of this platform change, a full installation is required to migrate. </para> + <para>When the installation process is complete you can point your JBDS 3.0.0 at your old workspace directory and continue working with your projects created using previous + JBDS/Tools versions, or create a new one and import old projects into the new workspace. + </para> + + <note> + <title>Note:</title> + <para>In JBDS 3.0.0 Linux users no longer need to install the library libstdc+.so.5 on their mashines. + Now this library is not required and can be removed from the system. + </para> + </note> + </section> + + +</chapter> Modified: trunk/documentation/guides/MigrationGuide/pom.xml =================================================================== --- trunk/documentation/guides/MigrationGuide/pom.xml 2010-03-09 21:06:09 UTC (rev 20717) +++ trunk/documentation/guides/MigrationGuide/pom.xml 2010-03-09 23:47:35 UTC (rev 20718) @@ -89,9 +89,9 @@ </dependencies> <configuration> <sourceDocumentName>${master}</sourceDocumentName> - <sourceDirectory>${pom.basedir}/en</sourceDirectory> + <sourceDirectory>${pom.basedir}/en-US</sourceDirectory> <imageResource> - <directory>${pom.basedir}/en</directory> + <directory>${pom.basedir}/en-US</directory> <includes> <include>images/**/*</include> </includes> Added: trunk/documentation/guides/MigrationGuide/publican.cfg =================================================================== --- trunk/documentation/guides/MigrationGuide/publican.cfg (rev 0) +++ trunk/documentation/guides/MigrationGuide/publican.cfg 2010-03-09 23:47:35 UTC (rev 20718) @@ -0,0 +1,7 @@ +# Config::Simple 4.59 +# Fri Nov 20 13:19:45 2009 + +xml_lang: en-US +type: Book +brand: JBoss +

14 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r20717 - trunk/cdi/tests/org.jboss.tools.cdi.core.test/src/org/jboss/tools/cdi/core/test/tck.

by jbosstools-commits＠lists.jboss.org

Author: akazakov Date: 2010-03-09 16:06:09 -0500 (Tue, 09 Mar 2010) New Revision: 20717 Modified: trunk/cdi/tests/org.jboss.tools.cdi.core.test/src/org/jboss/tools/cdi/core/test/tck/BeanDefinitionTest.java Log: https://jira.jboss.org/jira/browse/JBIDE-5808 Modified: trunk/cdi/tests/org.jboss.tools.cdi.core.test/src/org/jboss/tools/cdi/core/test/tck/BeanDefinitionTest.java =================================================================== --- trunk/cdi/tests/org.jboss.tools.cdi.core.test/src/org/jboss/tools/cdi/core/test/tck/BeanDefinitionTest.java 2010-03-09 19:04:54 UTC (rev 20716) +++ trunk/cdi/tests/org.jboss.tools.cdi.core.test/src/org/jboss/tools/cdi/core/test/tck/BeanDefinitionTest.java 2010-03-09 21:06:09 UTC (rev 20717) @@ -55,7 +55,7 @@ // IFile file = tckProject.getFile("JavaSource/org/jboss/jsr299/tck/tests/definition/bean/RedSnapper.java"); // Set<IBean> beans = cdiProject.getBeans(file.getFullPath()); Set<IBean> beans = getBeans("org.jboss.jsr299.tck.tests.definition.bean.RedSnapper"); - + assertEquals("There should be the only bean in org.jboss.jsr299.tck.tests.definition.bean.RedSnapper", 1, beans.size()); Set<IQualifier> qs = beans.iterator().next().getQualifiers(); assertTrue("No qualifiers were found for org.jboss.jsr299.tck.tests.definition.bean.RedSnapper bean.", qs.size() > 0); @@ -95,6 +95,7 @@ // IFile file = tckProject.getFile("JavaSource/org/jboss/jsr299/tck/tests/definition/bean/RedSnapper.java"); // Set<IBean> beans = cdiProject.getBeans(file.getFullPath()); Set<IBean> beans = getBeans("org.jboss.jsr299.tck.tests.definition.bean.RedSnapper"); + assertEquals("There should be the only bean in org.jboss.jsr299.tck.tests.definition.bean.RedSnapper", 1, beans.size()); IBean bean = beans.iterator().next(); IScope scope = bean.getScope(); assertNotNull("org.jboss.jsr299.tck.tests.definition.bean.RedSnapper bean desn't have a scope.", scope); @@ -137,11 +138,31 @@ Set<ITypeDeclaration> declarations = bean.getAllTypeDeclarations(); assertEquals("There should be three type declarations in org.jboss.jsr299.tck.tests.definition.bean.Tarantula bean.", declarations.size(), 3); - // TODO use real start position instead of 0. - assertLocationEquals(declarations, 0, 9); - assertLocationEquals(declarations, 0, 6); - assertLocationEquals(declarations, 0, 12); + assertLocationEquals(declarations, 859, 9); + assertLocationEquals(declarations, 877, 6); + assertLocationEquals(declarations, 895, 12); + } + /** + * section 2.2.1 c) + * + * @throws JavaModelException + */ + public void testAbstractApiType() throws JavaModelException { + Set<IBean> beans = getBeans("org.jboss.jsr299.tck.tests.definition.bean.FriendlyAntelope"); + assertEquals("There should be the only bean in org.jboss.jsr299.tck.tests.definition.bean.FriendlyAntelope", 1, beans.size()); + IBean bean = beans.iterator().next(); + Set<IParametedType> types = bean.getLegalTypes(); + assertEquals("Wrong number of legal types were found for org.jboss.jsr299.tck.tests.definition.bean.FriendlyAntelope bean.", 4, types.size()); + assertContainsBeanType(bean, "org.jboss.jsr299.tck.tests.definition.bean.FriendlyAntelope"); + assertContainsBeanType(bean, "org.jboss.jsr299.tck.tests.definition.bean.AbstractAntelope"); + assertContainsBeanType(bean, "org.jboss.jsr299.tck.tests.definition.bean.Animal"); + assertContainsBeanType(bean, "java.lang.Object"); + + Set<ITypeDeclaration> declarations = bean.getAllTypeDeclarations(); + assertEquals("There should be three type declarations in org.jboss.jsr299.tck.tests.definition.bean.FriendlyAntelope bean.", declarations.size(), 2); + assertLocationEquals(declarations, 842, 16); + assertLocationEquals(declarations, 867, 16); } /**

14 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r20716 - trunk/smooks/docs/reference/en/images/process_page.

by jbosstools-commits＠lists.jboss.org

Author: ochikvina Date: 2010-03-09 14:04:54 -0500 (Tue, 09 Mar 2010) New Revision: 20716 Added: trunk/smooks/docs/reference/en/images/process_page/process7a.png trunk/smooks/docs/reference/en/images/process_page/process7b.png trunk/smooks/docs/reference/en/images/process_page/process7c.png trunk/smooks/docs/reference/en/images/process_page/process8.png Log: <html><head><meta name="qrichtext" content="1" /></head><body style="font-size:9pt;font-family:Sans Serif"> <p>https://jira.jboss.org/jira/browse/JBDS-1133 - corrected the issues of Smooks guide reported by Jiri Peterka.Updated "Apply Template" section and "Smooks Configuration testing using Smooks Run Configuration" section.</p> </body></html> Added: trunk/smooks/docs/reference/en/images/process_page/process7a.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en/images/process_page/process7a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en/images/process_page/process7b.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en/images/process_page/process7b.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en/images/process_page/process7c.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en/images/process_page/process7c.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/smooks/docs/reference/en/images/process_page/process8.png =================================================================== (Binary files differ) Property changes on: trunk/smooks/docs/reference/en/images/process_page/process8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream

14 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r20715 - in trunk/smooks/docs/reference/en: modules and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: ochikvina Date: 2010-03-09 13:55:57 -0500 (Tue, 09 Mar 2010) New Revision: 20715 Modified: trunk/smooks/docs/reference/en/master_output.xml trunk/smooks/docs/reference/en/modules/introduction.xml trunk/smooks/docs/reference/en/modules/references.xml trunk/smooks/docs/reference/en/modules/tasks.xml Log: <html><head><meta name="qrichtext" content="1" /></head><body style="font-size:9pt;font-family:Sans Serif"> <p>https://jira.jboss.org/jira/browse/JBDS-1133 - corrected the issues of Smooks guide reported by Jiri Peterka.Updated "Apply Template" section and "Smooks Configuration testing using Smooks Run Configuration" section.</p> </body></html> Modified: trunk/smooks/docs/reference/en/master_output.xml =================================================================== --- trunk/smooks/docs/reference/en/master_output.xml 2010-03-09 18:24:28 UTC (rev 20714) +++ trunk/smooks/docs/reference/en/master_output.xml 2010-03-09 18:55:57 UTC (rev 20715) @@ -7,929 +7,933 @@ <!ENTITY tasks SYSTEM "modules/tasks.xml"> <!ENTITY references SYSTEM "modules/references.xml"> <!ENTITY summary SYSTEM "modules/summary.xml"> -]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff"> - - <bookinfo> - - <title>Smooks Dev Tools Reference Guide</title> - <corpauthor> - <inlinemediaobject> - <imageobject role="fo"> - <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata> - </imageobject> - <imageobject role="html"> - <imagedata></imagedata> - </imageobject> - </inlinemediaobject> - </corpauthor> - <author> - <firstname>Xue(Dart)</firstname> - <surname>Peng</surname> - </author> - <copyright> - <year><diffmk:wrapper diffmk:change="changed">2009,2010</diffmk:wrapper></year> - <holder>JBoss by Red Hat</holder> - </copyright> - <releaseinfo><diffmk:wrapper diffmk:change="changed"> - Version: 1.1.0.CR2 - </diffmk:wrapper></releaseinfo> - - <abstract> - <title></title> - <para> - <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/smooks/pdf/Smooks_Re...">PDF version</ulink> - </para> - </abstract> - - - </bookinfo> - <toc></toc> - -<chapter id="introduction" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/smooks/docs/reference/en/modules/introduction.xml"> - <?dbhtml filename="introduction.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Tools</keyword> - <keyword>Smooks</keyword> - <keyword>JBDS</keyword> - </keywordset> - </chapterinfo> - <title>Introduction</title> - <para>This chapter gives you a short introduction to Smooks, Smooks tools and its installation.</para> - <para>First, have a look at the key features of Smooks tools:</para> - <section> - <title>Key Features of Smooks Tools</title> - <para>Here, we provide you with a key functionality which is integrated in Smooks tools.</para> - <table> - - <title>Key Functionality for Smooks Tools</title> - <tgroup cols="3"> - - <colspec align="left" colnum="1" colwidth="2*"></colspec> - <colspec colnum="2" colwidth="4*"></colspec> - <colspec align="left" colnum="3" colwidth="2*"></colspec> - - <thead> - <row> - <entry>Feature</entry> - <entry>Benefit</entry> - <entry>Chapter</entry> - </row> - </thead> - - <tbody> - - <row> - <entry><para>Smooks Configuration File Wizard</para></entry> - <entry><para>Smooks tools allows to create/edit the Smooks configuration file for Java2Java data transformation.</para></entry> - <entry> - <link linkend="config_file_wizzard">Smooks Configuration File Wizard</link> - </entry> - </row> - - <row> - <entry><para>Smooks Editor</para></entry> - <entry><para>Smooks Editor helps configure the created Smooks configuration file.</para></entry> - <entry> - <link linkend="process_tab">Smooks Editor</link> - </entry> - </row> - - </tbody> - - </tgroup> - </table> - - - - </section> - - - - <section> - <title>What is Smooks?</title> - - <para><property moreinfo="none">Smooks</property> is a Java Framework/Engine for processing XML and non XML - data (CSV, EDI, Java, JSON etc).</para> - <para></para> - <para> - <orderedlist continuation="restarts" inheritnum="inherit" numeration="upperroman"> - <listitem> - <para><emphasis role="bold">Transformation</emphasis>: Perform a wide range of - Data Transforms. Supports many different Source and Result types - -XML/CSV/EDI/Java/JSON to XML/CSV/EDI/Java/JSON.</para> - </listitem> - <listitem> - <para><emphasis role="bold">Java Binding</emphasis>: Bind into a Java Object - Model from any data source (CSV, EDI, XML, Java, JSON etc). </para> - </listitem> - - <listitem> - <para><emphasis role="bold">Huge Message Processing</emphasis>: Process huge - messages (GBs) - Split, Transform and Route message fragments to JMS, File, - Database etc destinations. Route multiple message formats to multiple - destinations in a single pass over a message. </para> - </listitem> - - <listitem> - <para><emphasis role="bold">Message Enrichment</emphasis>: Enrich a message with - data from a Database, or other Datasources. </para> - </listitem> - - <listitem> - <para><emphasis role="bold">Combine</emphasis>: Combine the above features in - different ways e.g. add Message Enrichment as part of a Splitting and - Routing process. </para> - </listitem> - </orderedlist> - </para> - <figure float="0"> - <title>Smooks</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/introduction/introduction1.png" scale="90"></imagedata> - </imageobject> - </mediaobject> - </figure> - <para><diffmk:wrapper diffmk:change="changed"> For more informations about </diffmk:wrapper><property moreinfo="none">Smooks</property>, please visit <ulink url="http://www.smooks.org">Smooks official site</ulink>.</para> - </section> - <section> - <title>What is Smooks Tools?</title> - - <para>Smooks tools is a set of graphical tools for editing Smooks configuration file - based on Eclipse.</para> - <figure float="0"> - <title>Smooks Form editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/introduction/introduction2.png" scale="90"></imagedata> - </imageobject> - </mediaobject> - </figure> - <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">The easiest way to use the Smooks Configuration Editor is to create a project - (Java project, an ESB project, etc.), right-click on it and select </diffmk:wrapper><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">New -> Other</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added"> - to open the New wizard. Drill into </diffmk:wrapper><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Smooks -> Smooks Configuration File</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added"> - and continue through the wizard. We recommend using a minimum Smooks level of 1.1 or 1.2, but if you're using it in a deployed service, it depends on what version your runtime supports. - Once the file is created, it will open in the Smooks Configuration Editor.</diffmk:wrapper></para> - </section> - <section> - <title>How to install Smooks dev tools?</title> - - <para> The Smooks tools was included by the <property moreinfo="none">JBoss Tools</property> since 3.0.0 - Beta1 version. You can download the <property moreinfo="none">JBoss Tools</property> from <ulink url="http://jboss.org/tools/download.html">JBoss download site</ulink>.</para> - <para> Smooks tools (<property moreinfo="none">JBoss Tools</property>) run with the latest Eclipse and - other required plug-ins (GEF, EMF, etc.).</para> - <para> You should download the latest IDE for Java EE developers from <ulink url="http://www.eclipse.org/downloads/"> Eclipse site</ulink>. It contains many plug-ins ( - GEF, EMF, etc. ) required by Smooks dev tools. </para> - <para><diffmk:wrapper diffmk:change="added">The Smooks Configuration depends on having all of the appropriate Smooks runtime jars in the path of the Eclipse Plug-in or Java Project in the Eclipse workspace. - - The easiest solution is to do the following: - </diffmk:wrapper><itemizedlist> - <listitem><para><diffmk:wrapper diffmk:change="added">1) Download the Smooks distribution from here: http://www.smooks.org/mediawiki/index.php?title=Downloads . - Grab the latest "ALL" distribution (as of today, it is the Smooks v.1.2.2 "ALL" distribution) and it will include binaries, examples, etc.</diffmk:wrapper></para></listitem> - <listitem><para><diffmk:wrapper diffmk:change="changed">2) Extract files from the archive somewhere on your machine.</diffmk:wrapper></para></listitem> - <listitem><para><diffmk:wrapper diffmk:change="changed">3) In your Eclipse workspace, copy the Smooks jars into a directory of your Eclipse plug-in or Java project named "lib".</diffmk:wrapper></para></listitem> - <listitem><para><diffmk:wrapper diffmk:change="added">4) For your Eclipse Plug-in or Java Project, right-click on the project and select Properties.</diffmk:wrapper></para></listitem> - <listitem><para><diffmk:wrapper diffmk:change="added">5) Select the "Java Build Path" item in the Properties list, select the Libraries tab, and click "Add JARs" - </diffmk:wrapper></para></listitem> - <listitem><para><diffmk:wrapper diffmk:change="changed">6) In the Jar Selection dialog, select all the jars in the "lib" directory mentioned in step 3 and click </diffmk:wrapper><property moreinfo="none"><diffmk:wrapper diffmk:change="added">OK</diffmk:wrapper></property><diffmk:wrapper diffmk:change="changed">. - </diffmk:wrapper></para></listitem> - <listitem><para><diffmk:wrapper diffmk:change="changed">7) Click </diffmk:wrapper><property moreinfo="none"><diffmk:wrapper diffmk:change="changed">OK</diffmk:wrapper></property><diffmk:wrapper diffmk:change="changed"> to close the Properties dialog. Now you should see a "Referenced Libraries" node that appeared in your project hierarchy in Eclipse. - </diffmk:wrapper></para></listitem> - </itemizedlist> - - </para> - <para><diffmk:wrapper diffmk:change="added">Now let's progress to more advanced topics.</diffmk:wrapper></para> - </section> - -</chapter> - - -<chapter diffmk:change="added" id="process_page" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/smooks/docs/reference/en/modules/tasks.xml"> - <?dbhtml filename="tasks.html"?> - <chapterinfo diffmk:change="added"> - <keywordset diffmk:change="added"> - <keyword diffmk:change="added"><diffmk:wrapper diffmk:change="added">JBoss Tools</diffmk:wrapper></keyword> - <keyword diffmk:change="added"><diffmk:wrapper diffmk:change="added">Smooks</diffmk:wrapper></keyword> - <keyword diffmk:change="added"><diffmk:wrapper diffmk:change="added">JBDS</diffmk:wrapper></keyword> - </keywordset> - </chapterinfo> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Tasks</diffmk:wrapper></title> - <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">This chapter describes the main tasks a user can be faced during Smooks tools usage.</diffmk:wrapper></para> - <section id="config_file_wizzard"> - <title><diffmk:wrapper diffmk:change="changed">New Smooks Configuration File Creation</diffmk:wrapper></title> - <para><diffmk:wrapper diffmk:change="changed">Select the project where you want to create new Smooks Configuration File and right-click on it, - select in the menu </diffmk:wrapper><emphasis><property moreinfo="none">New > Other</property>,</emphasis><diffmk:wrapper diffmk:change="changed"> then find - </diffmk:wrapper><emphasis><property moreinfo="none">Smooks > Smooks Configuration File</property>.</emphasis><diffmk:wrapper diffmk:change="changed"> - Click the </diffmk:wrapper><emphasis> - <property moreinfo="none">Next</property> - </emphasis> button. </para> - <figure float="0"> - <title>Selecting Smooks Configuration File Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/quick_start/quick_start1.png" scale="90"></imagedata> - </imageobject> - </mediaobject> - </figure> - <para>The first wizard page is a file path creation page. Select the <emphasis> - <property moreinfo="none">src</property> - </emphasis><diffmk:wrapper diffmk:change="changed"> folder to be the files container, and input the name - </diffmk:wrapper><emphasis><property moreinfo="none">smooks-config.xml</property>.</emphasis><diffmk:wrapper diffmk:change="changed"> Click - </diffmk:wrapper><emphasis><property moreinfo="none">Next</property>.</emphasis></para> - <figure float="0"> - <title>Choosing the configuration file container and the file name</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/quick_start/quick_start2.png" scale="90"></imagedata> - </imageobject> - </mediaobject> - </figure> - <para><diffmk:wrapper diffmk:change="changed">The second wizard page allow you to select Smooks configuration file version. Select the appropriate one and click </diffmk:wrapper><emphasis><property moreinfo="none">Finish</property></emphasis> to complete the wizard.</para> - </section> - <section diffmk:change="added"> - <title><diffmk:wrapper diffmk:change="changed">Input Task Configuring</diffmk:wrapper></title> - <para> - <property moreinfo="none"><diffmk:wrapper diffmk:change="changed">Input task configuring</diffmk:wrapper></property><diffmk:wrapper diffmk:change="changed"> is an obligatory step for your smooks project creation. - You can configure it on the Process page of the editor: look for the "Input Task" in the Process Map at the top of the page. - </diffmk:wrapper></para> - <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Input Task Configuring</diffmk:wrapper></title> - <mediaobject> - <imageobject> - <imagedata fileref="images/process_page/process1.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - <para><diffmk:wrapper diffmk:change="added">Select it and you will see all the properties to set for the Input reader of your Smooks configuration. - "Input type" corresponds to the type of data that you will be working with. - For example, to work with incoming CSV (Comma-separated Values) data, you would specify "CSV" in the drop-down list. - Each reader type has slightly different configuration details that must be set in the "Input configuration" area. - For instance, the CSV reader requires you to specify details such as the encoding, quote character, separator character, and the list of incoming fields. - The EDI reader requires the encoding and the path to the Mapping Model describing the incoming data. - In the </diffmk:wrapper><emphasis><diffmk:wrapper diffmk:change="added">Input data</diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="added"> section, you specify some sample data that conforms to your reader configuration. - </diffmk:wrapper></para> - - <para diffmk:change="added"><diffmk:wrapper diffmk:change="added"> - Once you've specified your reader configuration and sample data, you can see the input model rendered in a tree form in the </diffmk:wrapper><emphasis><diffmk:wrapper diffmk:change="added">Input model</diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="changed"> section. - On the picture below you can see the correct configuration of some XML input task. - </diffmk:wrapper></para> - <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Input Task Configuring</diffmk:wrapper></title> - <mediaobject> - <imageobject> - <imagedata fileref="images/process_page/process2.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section diffmk:change="added"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">"Java Mapping" or "Apply Template"?</diffmk:wrapper></title> - - <para><diffmk:wrapper diffmk:change="added">Though there are many options in Smooks as far as what you can do with input - data such as transformation, routing, and persistence, this version - of the Smooks Configuration Editor focuses only on these areas: - mapping to java and applying templates to create different output formats. - If you have a set of Java classes you want to use the incoming data for, - you can use the "Java Mapping" task to specify those classes and use drag and - drop to map between the input model generated by the reader and elements in the output model. - Or if you simply want to transform your output to one or more formats, you can use the "Apply Template" - task to map it to a CSV file, XML or XSD file (and other formats in the future). - </diffmk:wrapper><note><title>Note</title> - <para><diffmk:wrapper diffmk:change="changed">Now you can't transform your output directly, - using only Input and Template tasks. - You should use Mapping as an interagent between these tasks.</diffmk:wrapper></para> - </note> - </para> - </section> - <section diffmk:change="added" id="mapping"> - <title><diffmk:wrapper diffmk:change="changed">Java Mapping Task</diffmk:wrapper></title> - - <para><diffmk:wrapper diffmk:change="changed"> - If you decide to do Java Mapping, you need to make sure that your Input reader has been set up and you have some sample data specified. - Then you should select </diffmk:wrapper><emphasis><diffmk:wrapper diffmk:change="added">Input Task</diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="changed"> in the Process tab and click the plus (+) sign to the right of the icon. - Select </diffmk:wrapper><emphasis><diffmk:wrapper diffmk:change="added">Java Mapping</diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="added"> from the popup menu and it will appear to the right, connected to </diffmk:wrapper><emphasis diffmk:change="added"><diffmk:wrapper diffmk:change="added">Input Task</diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="added">. Then select </diffmk:wrapper><emphasis diffmk:change="added"><diffmk:wrapper diffmk:change="added">Java Mapping</diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="changed"> task. - </diffmk:wrapper></para> - <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Java Mapping configuration</diffmk:wrapper></title> - <mediaobject> - <imageobject> - <imagedata fileref="images/process_page/process3.png"/> - </imageobject> - </mediaobject> - </figure> - <para><diffmk:wrapper diffmk:change="changed">Another method of adding </diffmk:wrapper><emphasis><diffmk:wrapper diffmk:change="added">Java Mapping</diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="added"> element - to the canvas in the Processing Tasks section is to right click Input Task - element and select </diffmk:wrapper><emphasis diffmk:change="added"><diffmk:wrapper diffmk:change="added">Java Mapping</diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="changed"> in the popup menu </diffmk:wrapper></para> - <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Java Mapping configuration</diffmk:wrapper></title> - <mediaobject> - <imageobject> - <imagedata fileref="images/process_page/process4.png"/> - </imageobject> - </mediaobject> - </figure> - <para><diffmk:wrapper diffmk:change="changed"> - Right-click on the canvas in an empty space and select "Add ->Java Class". - </diffmk:wrapper></para> - <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Java Mapping configuration</diffmk:wrapper></title> - <mediaobject> - <imageobject> - <imagedata fileref="images/process_page/process5.png"/> - </imageobject> - </mediaobject> - </figure> - <para> - <emphasis><diffmk:wrapper diffmk:change="added">Java Bean Creation</diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="added"> wizard appears. - Specify a unique identifier for the new class, the class path, - whether it's an array or not, and if it is a collection, also specify the collection class. - If the Java class is specified, you'll see a list of the properties in the box below. - Click </diffmk:wrapper><emphasis diffmk:change="added"><diffmk:wrapper diffmk:change="added">Finish</diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="changed"> when you're done. - Now with the input and output models on the canvas, you can click and drag - from the various input elements to corresponding output elements. - Make sure to connect collection elements to corresponding collection elements. - Finally your mapping should look nearly like the one on the picture below. - </diffmk:wrapper></para> - <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Final Mapping schema</diffmk:wrapper></title> - <mediaobject> - <imageobject> - <imagedata fileref="images/process_page/process6.png"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section diffmk:change="added"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Apply Template Task</diffmk:wrapper></title> - - <para><diffmk:wrapper diffmk:change="added">The "Apply Template" task works very similarly to the </diffmk:wrapper><link diffmk:change="added" linkend="mapping"><diffmk:wrapper diffmk:change="added">"Java Mapping" task</diffmk:wrapper></link><diffmk:wrapper diffmk:change="added">, where you map between an input model and an output model. - Select the </diffmk:wrapper><emphasis diffmk:change="added"><diffmk:wrapper diffmk:change="added">Java Mapping</diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="added"> task you want to use as the input model in the Process Map pane and click the plus (+) sign to the right of the icon. - </diffmk:wrapper></para> - <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Apply Template configuration</diffmk:wrapper></title> - <mediaobject> - <imageobject> - <imagedata fileref="images/process_page/process7.png"/> - </imageobject> - </mediaobject> - </figure> - <para><diffmk:wrapper diffmk:change="added"> - Select "Apply Template" from the popup menu and it will appear to the right, connected to the task you created it from. Then select the "Apply Template" task. - Once you've defined your template model, you can click and drag from the various input elements to corresponding output elements in the template. Make sure to connect collection elements to corresponding collection elements - </diffmk:wrapper></para> - </section> - <section diffmk:change="added"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Smooks Configuration testing using Smooks Run Configuration</diffmk:wrapper></title> - - <para><diffmk:wrapper diffmk:change="added">This option is intended to view the results of Smooks transforming procedure. - For more detailed information about this option please go </diffmk:wrapper><ulink diffmk:change="added" url="http://community.jboss.org/wiki/UsingtheSmooksRunConfigurationtotestSmook..."><diffmk:wrapper diffmk:change="added">here</diffmk:wrapper></ulink><diffmk:wrapper diffmk:change="added">.</diffmk:wrapper></para> - </section> -</chapter> -<chapter id="reference" diffmk:change="added" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/smooks/docs/reference/en/modules/references.xml"> - <?dbhtml filename="reference.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Tools</keyword> - <keyword>Smooks</keyword> - <keyword>JBDS</keyword> - </keywordset> - </chapterinfo> - <title>Reference</title> - <para>This chapter includes detailed reference information about Smooks Tools.</para> - <section> - <title>Smooks Configuration Editor</title> - <para>This chapter describes the following tabs of the Smooks Configuration Editor:</para> - - <itemizedlist> - <listitem><para><link linkend="process_tab">Process tab</link></para></listitem> - <listitem><para><link linkend="options_tab">Options tab</link></para></listitem> - <listitem><para><link linkend="smooksformeditor_sourcetab">Source tab</link></para></listitem> - </itemizedlist> - <section id="process_tab"> - <title>Process tab</title> - <para>The Process tab of the Smooks Configuration Editor helps to configure different types of transformations. - By default smooks configuration file is opened in this editor.If you have another default settings for editor opening - you should left click smooks configuration file and select:<emphasis>Open With->Smooks Configuration Editor</emphasis>.</para> - <para>The Process tab has two sections:</para> - <itemizedlist> - <listitem><para><link linkend="processing_task_section">Processing Task section</link></para></listitem> - <listitem><para><link linkend="selected_task_details">Selected Task Details section</link></para></listitem> - </itemizedlist> - <para>You can see them on the picture below.</para> - <figure> - <title>Two Sections of the Process tab.</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/reference_1.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - <section id="processing_task_section"> - <title>Processing Task section</title> - <para>Using the popup menu in the Processing Task section you - can select which types of technologies(templating or mapping ones) you will use for transofmation: </para> - <para>The descriptions of the popup menu options are in the following table.</para> - <table> - <title>Process Tab. Processing Task section.</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" align="left" colwidth="3*"/> - <colspec colnum="3" align="left" colwidth="1*"/> - - <thead> - <row> - <entry>Option</entry> - <entry>Description</entry> - <entry>Default</entry> - </row> - </thead> - <tbody> - <row> - <entry>Add Task</entry> - <entry>Select one of the following tasks according to the necessary type of Source and Result types of the files: - <itemizedlist> - <listitem><para><emphasis>Input</emphasis> -this task is required and - appears automatically when Smooks config file is created. - You should just configure it properly.</para></listitem> - <listitem><para><emphasis>Java Mapping</emphasis></para></listitem> - <listitem><para><emphasis>Apply Template</emphasis></para></listitem> - </itemizedlist> - </entry> - <entry></entry> - </row> - - <row> - <entry>Delete</entry> - <entry>Click this option if you want to delete some task from the section. - Note:you can't delete input task because it's required.</entry> - <entry></entry> - - </row> - - <row> - <entry>Input Methods</entry> - <entry>Choose one of the following methods: - <itemizedlist> - <listitem><para>System</para></listitem> - <listitem><para>Simple</para></listitem> - <listitem><para>Amharic(EZ+)</para></listitem> - <listitem><para>Cedilla</para></listitem> - <listitem><para>Cyrillic</para></listitem> - <listitem><para>Inuktitut</para></listitem> - <listitem><para>IPA</para></listitem> - <listitem><para>Multipress</para></listitem> - <listitem><para>SCIM Bridge Input Method</para></listitem> - <listitem><para>SCIM Input Method</para></listitem> - <listitem><para>Thai-Lio</para></listitem> - <listitem><para>Tigrigna-Eritrean(EZ+)</para></listitem> - <listitem><para>Tigrigna-Ethiopian(EZ+)</para></listitem> - <listitem><para>Vietnamese</para></listitem> - <listitem><para>X input Method</para></listitem> - </itemizedlist> - </entry> - <entry>System</entry> - </row> - </tbody> - </tgroup> - </table> - </section> - <section id="selected_task_details"> - <title>Selected Task Details Section</title> - <para>The options of this section depends on the selected task in the Processing Task section. - Because there are 3 types of tasks there are 3 different sets of its options in the Selected Task Details Section. - They will be described one by one. </para> - <section> - <title>Selected Task Details Section for Input Task.</title> - <para>On the picture below you can find an example of Selected Task Details Section view - if XML is selected as input type.</para> - - <figure> - <title>Selected Task Details Section for Input XML Task.</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/reference_2.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - <para>As you can see on the picture above Input Configuration section is empty for XML input file. - But this section has special configuration options for CSV,EDI,JSON,Custom input files.</para> - - <para>Here are the screens of these configuration options:</para> - <itemizedlist> - <listitem><para>CSV:</para> - <figure> - <title>Selected Task Details Section for Input CSV Task.</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/reference_3.png" /> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem><para>EDI:</para> - <figure> - <title>Selected Task Details Section for Input EDI Task.</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/reference_4.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem><para>JSON:</para> - <figure> - <title>Selected Task Details Section for Input JSON Task.</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/reference_5.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem><para>Custom:</para> - <figure> - <title>Selected Task Details Section for Input Custom Task.</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/reference_6.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </itemizedlist> - <para>All the input task configuration positions can be found in the table below:</para> - <table> - <title>Selected Task Details Section. Options for Input Task.</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" align="left" colwidth="3*"/> - <colspec colnum="3" align="left" colwidth="1*"/> - <thead> - <row> - <entry>Option</entry> - <entry>Description</entry> - <entry>Default</entry> - </row> - </thead> - <tbody> - <row> - <entry>Input type</entry> - <entry>Select your type of input file. - If don't find your type in the list,you should use Custom type: - <itemizedlist> - <listitem><para>No Input</para></listitem> - <listitem><para>XML</para></listitem> - <listitem><para>Java</para></listitem> - <listitem><para>XSD/WSDL</para></listitem> - <listitem><para>CSV</para></listitem> - <listitem><para>EDI</para></listitem> - <listitem><para>JSON</para></listitem> - <listitem><para>Custom</para></listitem> - </itemizedlist> - </entry> - <entry>XML</entry> - </row> - - <row> - <entry>Input configuration - - </entry> - <entry> - <itemizedlist> - <listitem><para><emphasis>No Input</emphasis> -no info required</para></listitem> - <listitem><para><emphasis>XML</emphasis> -no info required</para></listitem> - <listitem><para><emphasis>Java</emphasis> -no info required</para></listitem> - <listitem><para><emphasis>XSD/WSDL</emphasis> -no info required</para></listitem> - <listitem><para><emphasis>CSV</emphasis></para><itemizedlist> - <listitem><para><emphasis>Fields</emphasis> -Comma separated list of CSV record field names - </para></listitem> - <listitem><para><emphasis>Separator Character</emphasis> -Field separator character. Default of ','. - </para></listitem> - <listitem><para><emphasis>Quote Character</emphasis> -Quote character. Default of '"'. - </para></listitem> - <listitem><para><emphasis>Record Name</emphasis> -Name of csv record element.Default:csv-record</para></listitem> - <listitem><para><emphasis>Root Name</emphasis> -Name of csv root element.Default:csv-set</para></listitem> - <listitem><para><emphasis>indent</emphasis> -Add indentation character data to the generated event stream. This simply makes - the generated event stream easier to read in its serialized form. Useful for - testing etc.Default:true - </para></listitem> - <listitem><para><emphasis>Skip Lines</emphasis> -Number of lines to skip before processing starts. Default of 0. - - </para></listitem> - </itemizedlist> - </listitem> - <listitem><para><emphasis>EDI</emphasis></para> - <itemizedlist> - <listitem><para><emphasis>Target Profile</emphasis> -Defines the target profile - </para></listitem> - <listitem><para><emphasis>Encoding</emphasis> -The character encoding. Default "UTF-8"</para></listitem> - <listitem><para><emphasis>Mapping Model</emphasis> -Defines the EDI Mapping Model configuration for processing the - EDI message stream to a stream of SAX events that can be processed by Smooks.</para></listitem> - <listitem><para><emphasis>Validate</emphasis> -This attribute turns on/off datatype validation in the EDI Parser. - Validation is on by default. - It makes sense to turn datatype validation off on the EDI Reader - if the EDI data is being bound into a Java Object model. - </para></listitem> - </itemizedlist> - </listitem> - <listitem><para><emphasis>JSON</emphasis></para> - <itemizedlist> - <listitem><para><emphasis>Target Profile</emphasis> -Defines the target profile</para></listitem> - <listitem><para><emphasis>Array Element Name</emphasis> -The element name of a array element. Default of 'element'. - </para></listitem> - <listitem><para><emphasis>Encoding</emphasis> -encoding: The default encoding of any JSON message - InputStream processed by this Reader. Default of 'UTF-8'.</para></listitem> - <listitem><para><emphasis>Illegal Element Name Char Replacement</emphasis> -If illegal characters are encountered in a JSON element name then they are replaced with this value. - By default this is not defined, so that the reader doesn't doesn't search for illegal characters. - </para></listitem> - <listitem><para><emphasis>Indent</emphasis> -Add indentation character data to the generated event stream. This simply makes - the generated event stream easier to read in its serialized form. Useful for - testing etc.Default:false. - </para></listitem> - <listitem><para><emphasis>Key Prefix on Numeric</emphasis> -The prefix character to add if the JSON node name starts with a number. - By default this is not defined, so that the reader doesn't search for element names that start with a number. - </para></listitem> - <listitem><para><emphasis>Key Whitespace Replacement</emphasis> -The replacement character for whitespaces in a JSON map key. - By default this not defined, so that the reader doesn't search for whitespaces. - </para></listitem> - <listitem><para><emphasis>Null Value Replacement</emphasis> -The replacement string for JSON NULL values. Default is ""(an empty string). </para></listitem> - <listitem><para><emphasis>Root Name</emphasis> -The element name of the document root. Default of 'json'. - </para></listitem> - <listitem><para><emphasis>Key Maps</emphasis> -Defines a JSON element name mapping - The "from" key will be replaced with the "to" key or the contents of the element. - </para></listitem> - </itemizedlist> - </listitem> - <listitem><para><emphasis>Custom</emphasis></para> - <itemizedlist> - <listitem><para><emphasis>Target Profile</emphasis> -</para></listitem> - <listitem><para><emphasis>Class</emphasis> -Custom reader class.</para></listitem> - <listitem><para><emphasis>Handlers</emphasis> -Set a handler on the reader instance e.g. an EntityResolver, ErrorHandler etc. - </para></listitem> - <listitem><para><emphasis>Features</emphasis> -Reader Features List</para></listitem> - <listitem><para><emphasis>Parametres</emphasis> -Resource Parameters</para></listitem> - - </itemizedlist> - </listitem> - </itemizedlist></entry> - <entry><itemizedlist> - <listitem><para><emphasis>CSV</emphasis></para><itemizedlist> - <listitem><para>not defined</para></listitem> - <listitem><para>','</para></listitem> - <listitem><para>'"'</para></listitem> - <listitem><para>csv-record</para></listitem> - <listitem><para>csv-set</para></listitem> - <listitem><para>true</para></listitem> - <listitem><para>0</para></listitem> - </itemizedlist> - </listitem> - <listitem><para><emphasis>EDI</emphasis></para> - <itemizedlist> - <listitem><para>not defined</para></listitem> - <listitem><para>UTF-8</para></listitem> - <listitem><para>not defined</para></listitem> - <listitem><para>true</para></listitem> - </itemizedlist> - </listitem> - <listitem><para><emphasis>JSON</emphasis></para> - <itemizedlist> - <listitem><para>not defined</para></listitem> - <listitem><para>element</para></listitem> - <listitem><para>UTF-8</para></listitem> - <listitem><para>not defined</para></listitem> - <listitem><para>false</para></listitem> - <listitem><para>not defined</para></listitem> - <listitem><para>not defined</para></listitem> - <listitem><para>""(an empty string)</para></listitem> - <listitem><para>'json'</para></listitem> - <listitem><para>not defined</para></listitem> - </itemizedlist> - </listitem> - <listitem><para><emphasis>Custom</emphasis></para> - <itemizedlist> - <listitem><para>no defaults</para></listitem> - - </itemizedlist> - </listitem> - </itemizedlist></entry> - </row> - <row> - <entry>Input Data</entry> - <entry>You should select a data file using <emphasis>Add</emphasis> and <emphasis>Delete</emphasis> buttons</entry> - <entry></entry> - </row> - <row> - <entry>Input Model View</entry> - <entry>Using this view you can see the structure of your input file.If the file has been changed, to see the changes - click <emphasis>Refresh</emphasis>link.</entry> - <entry></entry> - </row> - </tbody> - </tgroup> - </table> - </section> - <section id="mapping_task"><title>Selected Task Details section for Java Mapping Task.</title> - <para>Selected Task Details section for this task is presented by the graf, - that lighten the process of java mapping. </para> - <figure> - <title>Selected Task Details Section for Mapping Task.</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/reference_7.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - <para> This graphical editor allow you to perform drug/drop operations with the nodes of transform data to map the source data to target data. - When you save the changes in the graphical editor the correct Smooks configuration file content will be generated. </para> - - </section> - <section><title>Selected Task Details section for Template Task.</title> - <para>Selected Task Details section for this task is presented by the graf, - that is similar to the one in the <link linkend="mapping_task">previous section</link>. - </para> - <figure> - <title>Selected Task Details Section for Template Task.</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/reference_7a.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - </section> - </section> - - </section> - <section id="options_tab"> - <title>Options Tab</title> - <para>This section describes Options tab of the Smooks Configuration File editor, gives short recommendations how this tab can be used during the project configuring.</para> - <figure> - <title> Options tab of the Smooks Configuration File editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/reference_8.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - <section> - <title>Smooks Configuration section</title> - <para> - In the <property>Smooks Configuration</property> section of <property>Options Tab</property> - only one element is availible:Smooks Platform Version - </para> - <figure> - <title>Smooks Configuration section of Options tab</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/reference_9.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - <para>This parameter is not rechangable, - and is set according to the vesion of the Smooks libraries that are added to the project. - </para> - </section> - - <section> - <title>Filter Settings Filter section</title> - <para> - In Filter Settings section you can set - the following global options responsible for Smooks filtering configuring:</para> - <figure> - <title>Filter Settings section of Options tab</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/reference_10.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - <para>This behavior can be turned off using this global configuration parameter and can be overriden on a per fragment basis by targetting a Visitor implementation at that fragment that takes ownership of the Result writer (in the case of SAX filtering), or simply modifies the DOM (in the case of DOM filtering). As an example of this, see the FreeMarkerTemplateProcessor. - </para> - <table> - <title>Options Tab. Filter Settings section.</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" align="left" colwidth="3*"/> - <colspec colnum="3" align="left" colwidth="1*"/> - - <thead> - <row> - <entry>Option</entry> - <entry>Description</entry> - <entry>Default</entry> - </row> - </thead> - <tbody> - <row> - <entry>Stream Filter Type</entry> - <entry>Determines the type of processing model that will be used. - Please refer to <ulink url="http://www.smooks.org/mediawiki/index.php?title=V1.2:Smooks_v1.2_User_Gui..."> - Filtering Process Selection section</ulink> - of the official Smooks User Guide for more information about these models: - <itemizedlist> - <listitem><para><emphasis>SAX</emphasis></para></listitem> - <listitem><para><emphasis>DOM</emphasis></para></listitem> - </itemizedlist> - </entry> - <entry>DOM</entry> - </row> - - <row> - <entry>Default Serialization is On</entry> - <entry>Defines whether default serialization should be switched on. - Default serialization being turned on leads to locating StreamResult/DOMResult - to the Result objects provided to the Smooks.filterSource method and to - serialization all the events to that Result.</entry> - <entry>true</entry> - - </row> - </tbody> - </tgroup> - </table> - </section> - </section> - <section id="smooksformeditor_sourcetab" xreflabel="Smooks Source Tab"> - - <title>Source Tab</title> - <para>This section provides information about Smooks Source Editor Page.</para> - <section> - <title>XML Source Editor</title> - <para>You can use this editor to edit the Smooks Configuration file directly. </para> - <figure> - <title>Graphical Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/source_editor/source_editor1.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section> - <title>Error underlining in Graphical Editor</title> - <para>If the <property>Smooks tools</property> can't understand the configuration - file or the configuration file is illegal (XML structure isn't right for Smooks - Configuration file, etc.), the error is underlined.</para> - <figure> - <title>Graphical Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/reference_11.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - - </section> - - <section> - <title>Smooks Configuration File Validator</title> - <para>Smooks configuration file validator will validate your Smooks configuration file. Just right-click on the file and then click on the <property>Validate</property> button. The validator can be enabled/disabled in <emphasis><property>Window -> Preferences -> Validation</property></emphasis>:</para> - - <figure> - <title>Validation: Smooks Configuration File Validator</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/source_editor/smooks_conf_validator.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - - <para>You can set up your Smooks validator to include, exclude groups to validate and specify rules for validation. Just click on the <property>Settings</property> button and use the options provided:</para> - - <figure> - <title>Smooks Configuration File Validator Settings</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/source_editor/smooks_conf_validator_settings.png" scale="90"/> - </imageobject> - </mediaobject> - </figure> - - - </section> - </section> - </section> -</chapter> - -<chapter diffmk:change="added" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/smooks/docs/reference/en/modules/summary.xml"> - <?dbhtml filename="summary.html"?> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Summary</diffmk:wrapper></title> - <para><diffmk:wrapper diffmk:change="added">In conclusion, with this document you know all the capabilities of Smooks Tools and could easily start with them. - The chapters above walked you through the steps on how to create and configure some XML to JAVA mapping project. - If you have questions or suggestions concerned both the documentation and tools behavior, - you are welcome to JBoss Tools Users forum. - Please, use Jira to report bugs and requests on documentation.</diffmk:wrapper></para> - - <section diffmk:change="added"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Other relevant resources on the topic</diffmk:wrapper></title> - <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">All JBoss Developer Studio/JBoss Tools release documentation you can find at - </diffmk:wrapper><ulink diffmk:change="added" url="http://docs.jboss.org/tools"><diffmk:wrapper diffmk:change="added">http://docs.jboss.org/tools</diffmk:wrapper></ulink><diffmk:wrapper diffmk:change="added"> in the corresponding release directory. - </diffmk:wrapper></para> - <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">The latest documentation builds are available at </diffmk:wrapper><ulink diffmk:change="added" url="http://download.jboss.org/jbosstools/nightly-docs"><diffmk:wrapper diffmk:change="added">http://download.jboss.org/jbosstools/nightly-docs</diffmk:wrapper></ulink><diffmk:wrapper diffmk:change="added">. </diffmk:wrapper></para> -<para diffmk:change="added"><diffmk:wrapper diffmk:change="added">For more information about Smooks technology please visit - </diffmk:wrapper><ulink diffmk:change="added" url="http://www.smooks.org/mediawiki/index.php?title=Main_Page"><diffmk:wrapper diffmk:change="added"> - Smooks Technology Home Page</diffmk:wrapper></ulink></para> - - </section> -</chapter> - -</book> +]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff"> + + <bookinfo> + + <title>Smooks Dev Tools Reference Guide</title> + <corpauthor> + <inlinemediaobject> + <imageobject role="fo"> + <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata> + </imageobject> + <imageobject role="html"> + <imagedata></imagedata> + </imageobject> + </inlinemediaobject> + </corpauthor> + <author> + <firstname>Xue(Dart)</firstname> + <surname>Peng</surname> + </author> + <copyright> + <year>2009,2010</year> + <holder>JBoss by Red Hat</holder> + </copyright> + <releaseinfo><diffmk:wrapper diffmk:change="changed"> + Version: 1.1.0.GA + </diffmk:wrapper></releaseinfo> + + <abstract> + <title></title> + <para> + <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/smooks/pdf/Smooks_Re...">PDF version</ulink> + </para> + </abstract> + + + </bookinfo> + <toc></toc> + +<chapter id="introduction" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/smooks/docs/reference/en/modules/introduction.xml"> + <?dbhtml filename="introduction.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Introduction</title> + <para>This chapter gives you a short introduction to Smooks, Smooks tools and its installation.</para> + <para>First, have a look at the key features of Smooks tools:</para> + <section> + <title>Key Features of Smooks Tools</title> + <para>Here, we provide you with a key functionality which is integrated in Smooks tools.</para> + <table> + + <title>Key Functionality for Smooks Tools</title> + <tgroup cols="3"> + + <colspec align="left" colnum="1" colwidth="2*"></colspec> + <colspec colnum="2" colwidth="4*"></colspec> + <colspec align="left" colnum="3" colwidth="2*"></colspec> + + <thead> + <row> + <entry>Feature</entry> + <entry>Benefit</entry> + <entry>Chapter</entry> + </row> + </thead> + + <tbody> + + <row> + <entry><para>Smooks Configuration File Wizard</para></entry> + <entry><para>Smooks tools allows to create/edit the Smooks configuration file for Java2Java data transformation.</para></entry> + <entry> + <link linkend="config_file_wizzard">Smooks Configuration File Wizard</link> + </entry> + </row> + + <row> + <entry><para>Smooks Editor</para></entry> + <entry><para>Smooks Editor helps configure the created Smooks configuration file.</para></entry> + <entry> + <link linkend="process_tab">Smooks Editor</link> + </entry> + </row> + + </tbody> + + </tgroup> + </table> + + + + </section> + + + + <section> + <title>What is Smooks?</title> + + <para><property moreinfo="none">Smooks</property> is a Java Framework/Engine for processing XML and non XML + data (CSV, EDI, Java, JSON etc).</para> + <para></para> + <para> + <orderedlist continuation="restarts" inheritnum="inherit" numeration="upperroman"> + <listitem> + <para><emphasis role="bold">Transformation</emphasis>: Perform a wide range of + Data Transforms. Supports many different Source and Result types + -XML/CSV/EDI/Java/JSON to XML/CSV/EDI/Java/JSON.</para> + </listitem> + <listitem> + <para><emphasis role="bold">Java Binding</emphasis>: Bind into a Java Object + Model from any data source (CSV, EDI, XML, Java, JSON etc). </para> + </listitem> + + <listitem> + <para><emphasis role="bold">Huge Message Processing</emphasis>: Process huge + messages (GBs) - Split, Transform and Route message fragments to JMS, File, + Database etc destinations. Route multiple message formats to multiple + destinations in a single pass over a message. </para> + </listitem> + + <listitem> + <para><emphasis role="bold">Message Enrichment</emphasis>: Enrich a message with + data from a Database, or other Datasources. </para> + </listitem> + + <listitem> + <para><emphasis role="bold">Combine</emphasis>: Combine the above features in + different ways e.g. add Message Enrichment as part of a Splitting and + Routing process. </para> + </listitem> + </orderedlist> + </para> + <figure float="0"> + <title>Smooks</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/introduction/introduction1.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para> For more informations about <property moreinfo="none">Smooks</property>, please visit <ulink url="http://www.smooks.org">Smooks official site</ulink>.</para> + </section> + <section> + <title>What is Smooks Tools?</title> + + <para>Smooks tools is a set of graphical tools for editing Smooks configuration file + based on Eclipse.</para> + <figure float="0"> + <title>Smooks Form editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/introduction/introduction2.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The easiest way to use the Smooks Configuration Editor is to create a project + (Java project, an ESB project, etc.), right-click on it and select <property moreinfo="none">New -> Other</property> + to open the New wizard. Drill into <property moreinfo="none">Smooks -> Smooks Configuration File</property> + and continue through the wizard. We recommend using a minimum Smooks level of 1.1 or 1.2, but if you're using it in a deployed service, it depends on what version your runtime supports. + Once the file is created, it will open in the Smooks Configuration Editor.</para> + </section> + <section> + <title>How to install Smooks dev tools?</title> + + <para> The Smooks tools was included by the <property moreinfo="none">JBoss Tools</property> since 3.0.0 + Beta1 version. You can download the <property moreinfo="none">JBoss Tools</property> from <ulink url="http://jboss.org/tools/download.html">JBoss download site</ulink>.</para> + <para> Smooks tools (<property moreinfo="none">JBoss Tools</property>) run with the latest Eclipse and + other required plug-ins (GEF, EMF, etc.).</para> + <para> You should download the latest IDE for Java EE developers from <ulink url="http://www.eclipse.org/downloads/"> Eclipse site</ulink>. It contains many plug-ins ( + GEF, EMF, etc. ) required by Smooks dev tools. </para> + <para>The Smooks Configuration depends on having all of the appropriate Smooks runtime jars in the path of the Eclipse Plug-in or Java Project in the Eclipse workspace. + + The easiest solution is to do the following: + <itemizedlist> + <listitem><para>1) Download the Smooks distribution from here: http://www.smooks.org/mediawiki/index.php?title=Downloads . + Grab the latest "ALL" distribution (as of today, it is the Smooks v.1.2.2 "ALL" distribution) and it will include binaries, examples, etc.</para></listitem> + <listitem><para>2) Extract files from the archive somewhere on your machine.</para></listitem> + <listitem><para>3) In your Eclipse workspace, copy the Smooks jars into a directory of your Eclipse plug-in or Java project named "lib".</para></listitem> + <listitem><para>4) For your Eclipse Plug-in or Java Project, right-click on the project and select Properties.</para></listitem> + <listitem><para>5) Select the "Java Build Path" item in the Properties list, select the Libraries tab, and click "Add JARs" + </para></listitem> + <listitem><para>6) In the Jar Selection dialog, select all the jars in the "lib" directory mentioned in step 3 and click <property moreinfo="none">OK</property>. + </para></listitem> + <listitem><para>7) Click <property moreinfo="none">OK</property> to close the Properties dialog. Now you should see a "Referenced Libraries" node that appeared in your project hierarchy in Eclipse. + </para></listitem> + </itemizedlist> + + </para> + <para>Now let's progress to more advanced topics.</para> + </section> + +</chapter> + + +<chapter id="process_page" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/smooks/docs/reference/en/modules/tasks.xml"> + <?dbhtml filename="tasks.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Tasks</title> + <para>This chapter describes the main tasks a user can be faced during Smooks tools usage.</para> + <section id="config_file_wizzard"> + <title>New Smooks Configuration File Creation</title> + <para>Select the project where you want to create new Smooks Configuration File and right-click on it, + select in the menu <emphasis><property moreinfo="none">New > Other</property>,</emphasis> then find + <emphasis><property moreinfo="none">Smooks > Smooks Configuration File</property>.</emphasis> + Click the <emphasis> + <property moreinfo="none">Next</property> + </emphasis> button. </para> + <figure float="0"> + <title>Selecting Smooks Configuration File Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start1.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The first wizard page is a file path creation page. Select the <emphasis> + <property moreinfo="none">src</property> + </emphasis> folder to be the files container, and input the name + <emphasis><property moreinfo="none">smooks-config.xml</property>.</emphasis> Click + <emphasis><property moreinfo="none">Next</property>.</emphasis></para> + <figure float="0"> + <title>Choosing the configuration file container and the file name</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start2.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The second wizard page allow you to select Smooks configuration file version. Select the appropriate one and click <emphasis><property moreinfo="none">Finish</property></emphasis> to complete the wizard.</para> + </section> + <section> + <title>Input Task Configuring</title> + <para> + <property moreinfo="none">Input task configuring</property> is an obligatory step for your smooks project creation. + You can configure it on the Process page of the editor: look for the "Input Task" in the Process Map at the top of the page. + </para> + <figure float="0"> + <title>Input Task Configuring</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process1.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>Select it and you will see all the properties to set for the Input reader of your Smooks configuration. + "Input type" corresponds to the type of data that you will be working with. + For example, to work with incoming CSV (Comma-separated Values) data, you would specify "CSV" in the drop-down list. + Each reader type has slightly different configuration details that must be set in the "Input configuration" area. + For instance, the CSV reader requires you to specify details such as the encoding, quote character, separator character, and the list of incoming fields. + The EDI reader requires the encoding and the path to the Mapping Model describing the incoming data. + In the <emphasis>Input data</emphasis> section, you specify some sample data that conforms to your reader configuration. + </para> + + <para> + Once you've specified your reader configuration and sample data, you can see the input model rendered in a tree form in the <emphasis>Input model</emphasis> section. + On the picture below you can see the correct configuration of some XML input task. + </para> + <figure float="0"> + <title>Input Task Configuring</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process2.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>"Java Mapping" or "Apply Template"?</title> + + <para>Though there are many options in Smooks as far as what you can do with input + data such as transformation, routing, and persistence, this version + of the Smooks Configuration Editor focuses only on these areas: + mapping to java and applying templates to create different output formats. + If you have a set of Java classes you want to use the incoming data for, + you can use the "Java Mapping" task to specify those classes and use drag and + drop to map between the input model generated by the reader and elements in the output model. + Or if you simply want to transform your output to one or more formats, you can use the "Apply Template" + task to map it to a CSV file, XML or XSD file (and other formats in the future). + <note><title>Note</title> + <para>Now you can't transform your output directly, + using only Input and Template tasks. + You should use Mapping as an interagent between these tasks.</para> + </note> + </para> + </section> + <section id="mapping"> + <title>Java Mapping Task</title> + + <para> + If you decide to do Java Mapping, you need to make sure that your Input reader has been set up and you have some sample data specified. + Then you should select <emphasis>Input Task</emphasis> in the Process tab and click the plus (+) sign to the right of the icon. + Select <emphasis>Java Mapping</emphasis> from the popup menu and it will appear to the right, connected to <emphasis>Input Task</emphasis>. Then select <emphasis>Java Mapping</emphasis> task. + </para> + <figure float="0"> + <title>Java Mapping configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>Another method of adding <emphasis>Java Mapping</emphasis> element + to the canvas in the Processing Tasks section is to right click Input Task + element and select <emphasis>Java Mapping</emphasis> in the popup menu </para> + <figure float="0"> + <title>Java Mapping configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para> + Right-click on the canvas in an empty space and select "Add ->Java Class". + </para> + <figure float="0"> + <title>Java Mapping configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para> + <emphasis>Java Bean Creation</emphasis> wizard appears. + Specify a unique identifier for the new class, the class path, + whether it's an array or not, and if it is a collection, also specify the collection class. + If the Java class is specified, you'll see a list of the properties in the box below. + Click <emphasis>Finish</emphasis> when you're done. + Now with the input and output models on the canvas, you can click and drag + from the various input elements to corresponding output elements. + Make sure to connect collection elements to corresponding collection elements. + Finally your mapping should look nearly like the one on the picture below. + </para> + <figure float="0"> + <title>Final Mapping schema</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process6.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>Apply Template Task</title> + + <para>The "Apply Template" task works very similarly to the <link linkend="mapping">"Java Mapping" task</link>, where you map between an input model and an output model. + Select the <emphasis>Java Mapping</emphasis> task you want to use as the input model in the Process Map pane and click the plus (+) sign to the right of the icon. + </para> + <figure float="0"> + <title>Apply Template configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process7.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para> + Select "Apply Template" from the popup menu and it will appear to the right, connected to the task you created it from. Then select the "Apply Template" task. + Once you've defined your template model, you can click and drag from the various input elements to corresponding output elements in the template. Make sure to connect collection elements to corresponding collection elements + </para> + </section> + <section> + <title>Smooks Configuration testing using Smooks Run Configuration</title> + + <para>This option is intended to view the results of Smooks transforming procedure. + For more detailed information about this option please go <ulink url="http://community.jboss.org/wiki/UsingtheSmooksRunConfigurationtotestSmook...">here</ulink>.</para> + </section> +</chapter> + + + +<chapter id="reference" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/smooks/docs/reference/en/modules/references.xml"> + <?dbhtml filename="reference.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Smooks</keyword> + <keyword>JBDS</keyword> + </keywordset> + </chapterinfo> + <title>Reference</title> + <para>This chapter includes detailed reference information about Smooks Tools.</para> + <section> + <title>Smooks Configuration Editor</title> + <para>This chapter describes the following tabs of the Smooks Configuration Editor:</para> + + <itemizedlist> + <listitem><para><link linkend="process_tab">Process tab</link></para></listitem> + <listitem><para><link linkend="options_tab">Options tab</link></para></listitem> + <listitem><para><link linkend="smooksformeditor_sourcetab">Source tab</link></para></listitem> + </itemizedlist> + <section id="process_tab"> + <title>Process tab</title> + <para>The Process tab of the Smooks Configuration Editor helps to configure different types of transformations. + By default smooks configuration file is opened in this editor.If you have another default settings for editor opening + you should left click smooks configuration file and select:<emphasis>Open With->Smooks Configuration Editor</emphasis>.</para> + <para>The Process tab has two sections:</para> + <itemizedlist> + <listitem><para><link linkend="processing_task_section">Processing Task section</link></para></listitem> + <listitem><para><link linkend="selected_task_details">Selected Task Details section</link></para></listitem> + </itemizedlist> + <para>You can see them on the picture below.</para> + <figure float="0"> + <title>Two Sections of the Process tab.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_1.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <section id="processing_task_section"> + <title>Processing Task section</title> + <para>Using the popup menu in the Processing Task section you + can select which types of technologies(templating or mapping ones) you will use for transofmation: </para> + <para>The descriptions of the popup menu options are in the following table.</para> + <table> + <title>Process Tab. Processing Task section.</title> + <tgroup cols="3"> + <colspec align="left" colnum="1" colwidth="1*"></colspec> + <colspec align="left" colnum="2" colwidth="3*"></colspec> + <colspec align="left" colnum="3" colwidth="1*"></colspec> + + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + <row> + <entry>Add Task</entry> + <entry>Select one of the following tasks according to the necessary type of Source and Result types of the files: + <itemizedlist> + <listitem><para><emphasis>Input</emphasis> -this task is required and + appears automatically when Smooks config file is created. + You should just configure it properly.</para></listitem> + <listitem><para><emphasis>Java Mapping</emphasis></para></listitem> + <listitem><para><emphasis>Apply Template</emphasis></para></listitem> + </itemizedlist> + </entry> + <entry></entry> + </row> + + <row> + <entry>Delete</entry> + <entry>Click this option if you want to delete some task from the section. + Note:you can't delete input task because it's required.</entry> + <entry></entry> + + </row> + + <row> + <entry>Input Methods</entry> + <entry>Choose one of the following methods: + <itemizedlist> + <listitem><para>System</para></listitem> + <listitem><para>Simple</para></listitem> + <listitem><para>Amharic(EZ+)</para></listitem> + <listitem><para>Cedilla</para></listitem> + <listitem><para>Cyrillic</para></listitem> + <listitem><para>Inuktitut</para></listitem> + <listitem><para>IPA</para></listitem> + <listitem><para>Multipress</para></listitem> + <listitem><para>SCIM Bridge Input Method</para></listitem> + <listitem><para>SCIM Input Method</para></listitem> + <listitem><para>Thai-Lio</para></listitem> + <listitem><para>Tigrigna-Eritrean(EZ+)</para></listitem> + <listitem><para>Tigrigna-Ethiopian(EZ+)</para></listitem> + <listitem><para>Vietnamese</para></listitem> + <listitem><para>X input Method</para></listitem> + </itemizedlist> + </entry> + <entry>System</entry> + </row> + </tbody> + </tgroup> + </table> + </section> + <section id="selected_task_details"> + <title>Selected Task Details Section</title> + <para>The options of this section depends on the selected task in the Processing Task section. + Because there are 3 types of tasks there are 3 different sets of its options in the Selected Task Details Section. + They will be described one by one. </para> + <section> + <title>Selected Task Details Section for Input Task.</title> + <para>On the picture below you can find an example of Selected Task Details Section view + if XML is selected as input type.</para> + + <figure float="0"> + <title>Selected Task Details Section for Input XML Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_2.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>As you can see on the picture above Input Configuration section is empty for XML input file. + But this section has special configuration options for CSV,EDI,JSON,Custom input files.</para> + + <para>Here are the screens of these configuration options:</para> + <itemizedlist> + <listitem><para>CSV:</para> + <figure float="0"> + <title>Selected Task Details Section for Input CSV Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem><para>EDI:</para> + <figure float="0"> + <title>Selected Task Details Section for Input EDI Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem><para>JSON:</para> + <figure float="0"> + <title>Selected Task Details Section for Input JSON Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem><para>Custom:</para> + <figure float="0"> + <title>Selected Task Details Section for Input Custom Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_6.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <para>All the input task configuration positions can be found in the table below:</para> + <table> + <title>Selected Task Details Section. Options for Input Task.</title> + <tgroup cols="3"> + <colspec align="left" colnum="1" colwidth="1*"></colspec> + <colspec align="left" colnum="2" colwidth="3*"></colspec> + <colspec align="left" colnum="3" colwidth="1*"></colspec> + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + <row> + <entry>Input type</entry> + <entry>Select your type of input file. + If don't find your type in the list,you should use Custom type: + <itemizedlist> + <listitem><para>No Input</para></listitem> + <listitem><para>XML</para></listitem> + <listitem><para>Java</para></listitem> + <listitem><para>XSD/WSDL</para></listitem> + <listitem><para>CSV</para></listitem> + <listitem><para>EDI</para></listitem> + <listitem><para>JSON</para></listitem> + <listitem><para>Custom</para></listitem> + </itemizedlist> + </entry> + <entry>XML</entry> + </row> + + <row> + <entry>Input configuration + + </entry> + <entry> + <itemizedlist> + <listitem><para><emphasis>No Input</emphasis> -no info required</para></listitem> + <listitem><para><emphasis>XML</emphasis> -no info required</para></listitem> + <listitem><para><emphasis>Java</emphasis> -no info required</para></listitem> + <listitem><para><emphasis>XSD/WSDL</emphasis> -no info required</para></listitem> + <listitem><para><emphasis>CSV</emphasis></para><itemizedlist> + <listitem><para><emphasis>Fields</emphasis> -Comma separated list of CSV record field names + </para></listitem> + <listitem><para><emphasis>Separator Character</emphasis> -Field separator character. Default of ','. + </para></listitem> + <listitem><para><emphasis>Quote Character</emphasis> -Quote character. Default of '"'. + </para></listitem> + <listitem><para><emphasis>Record Name</emphasis> -Name of csv record element.Default:csv-record</para></listitem> + <listitem><para><emphasis>Root Name</emphasis> -Name of csv root element.Default:csv-set</para></listitem> + <listitem><para><emphasis>indent</emphasis> -Add indentation character data to the generated event stream. This simply makes + the generated event stream easier to read in its serialized form. Useful for + testing etc.Default:true + </para></listitem> + <listitem><para><emphasis>Skip Lines</emphasis> -Number of lines to skip before processing starts. Default of 0. + + </para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>EDI</emphasis></para> + <itemizedlist> + <listitem><para><emphasis>Target Profile</emphasis> -Defines the target profile + </para></listitem> + <listitem><para><emphasis>Encoding</emphasis> -The character encoding. Default "UTF-8"</para></listitem> + <listitem><para><emphasis>Mapping Model</emphasis> -Defines the EDI Mapping Model configuration for processing the + EDI message stream to a stream of SAX events that can be processed by Smooks.</para></listitem> + <listitem><para><emphasis>Validate</emphasis> -This attribute turns on/off datatype validation in the EDI Parser. + Validation is on by default. + It makes sense to turn datatype validation off on the EDI Reader + if the EDI data is being bound into a Java Object model. + </para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>JSON</emphasis></para> + <itemizedlist> + <listitem><para><emphasis>Target Profile</emphasis> -Defines the target profile</para></listitem> + <listitem><para><emphasis>Array Element Name</emphasis> -The element name of a array element. Default of 'element'. + </para></listitem> + <listitem><para><emphasis>Encoding</emphasis> -encoding: The default encoding of any JSON message + InputStream processed by this Reader. Default of 'UTF-8'.</para></listitem> + <listitem><para><emphasis>Illegal Element Name Char Replacement</emphasis> -If illegal characters are encountered in a JSON element name then they are replaced with this value. + By default this is not defined, so that the reader doesn't doesn't search for illegal characters. + </para></listitem> + <listitem><para><emphasis>Indent</emphasis> -Add indentation character data to the generated event stream. This simply makes + the generated event stream easier to read in its serialized form. Useful for + testing etc.Default:false. + </para></listitem> + <listitem><para><emphasis>Key Prefix on Numeric</emphasis> -The prefix character to add if the JSON node name starts with a number. + By default this is not defined, so that the reader doesn't search for element names that start with a number. + </para></listitem> + <listitem><para><emphasis>Key Whitespace Replacement</emphasis> -The replacement character for whitespaces in a JSON map key. + By default this not defined, so that the reader doesn't search for whitespaces. + </para></listitem> + <listitem><para><emphasis>Null Value Replacement</emphasis> -The replacement string for JSON NULL values. Default is ""(an empty string). </para></listitem> + <listitem><para><emphasis>Root Name</emphasis> -The element name of the document root. Default of 'json'. + </para></listitem> + <listitem><para><emphasis>Key Maps</emphasis> -Defines a JSON element name mapping + The "from" key will be replaced with the "to" key or the contents of the element. + </para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>Custom</emphasis></para> + <itemizedlist> + <listitem><para><emphasis>Target Profile</emphasis> -</para></listitem> + <listitem><para><emphasis>Class</emphasis> -Custom reader class.</para></listitem> + <listitem><para><emphasis>Handlers</emphasis> -Set a handler on the reader instance e.g. an EntityResolver, ErrorHandler etc. + </para></listitem> + <listitem><para><emphasis>Features</emphasis> -Reader Features List</para></listitem> + <listitem><para><emphasis>Parametres</emphasis> -Resource Parameters</para></listitem> + + </itemizedlist> + </listitem> + </itemizedlist></entry> + <entry><itemizedlist> + <listitem><para><emphasis>CSV</emphasis></para><itemizedlist> + <listitem><para>not defined</para></listitem> + <listitem><para>','</para></listitem> + <listitem><para>'"'</para></listitem> + <listitem><para>csv-record</para></listitem> + <listitem><para>csv-set</para></listitem> + <listitem><para>true</para></listitem> + <listitem><para>0</para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>EDI</emphasis></para> + <itemizedlist> + <listitem><para>not defined</para></listitem> + <listitem><para>UTF-8</para></listitem> + <listitem><para>not defined</para></listitem> + <listitem><para>true</para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>JSON</emphasis></para> + <itemizedlist> + <listitem><para>not defined</para></listitem> + <listitem><para>element</para></listitem> + <listitem><para>UTF-8</para></listitem> + <listitem><para>not defined</para></listitem> + <listitem><para>false</para></listitem> + <listitem><para>not defined</para></listitem> + <listitem><para>not defined</para></listitem> + <listitem><para>""(an empty string)</para></listitem> + <listitem><para>'json'</para></listitem> + <listitem><para>not defined</para></listitem> + </itemizedlist> + </listitem> + <listitem><para><emphasis>Custom</emphasis></para> + <itemizedlist> + <listitem><para>no defaults</para></listitem> + + </itemizedlist> + </listitem> + </itemizedlist></entry> + </row> + <row> + <entry>Input Data</entry> + <entry>You should select a data file using <emphasis>Add</emphasis> and <emphasis>Delete</emphasis> buttons</entry> + <entry></entry> + </row> + <row> + <entry>Input Model View</entry> + <entry>Using this view you can see the structure of your input file.If the file has been changed, to see the changes + click <emphasis>Refresh</emphasis>link.</entry> + <entry></entry> + </row> + </tbody> + </tgroup> + </table> + </section> + <section id="mapping_task"><title>Selected Task Details section for Java Mapping Task.</title> + <para>Selected Task Details section for this task is presented by the graf, + that lighten the process of java mapping. </para> + <figure float="0"> + <title>Selected Task Details Section for Mapping Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_7.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para> This graphical editor allow you to perform drug/drop operations with the nodes of transform data to map the source data to target data. + When you save the changes in the graphical editor the correct Smooks configuration file content will be generated. </para> + + </section> + <section><title>Selected Task Details section for Template Task.</title> + <para>Selected Task Details section for this task is presented by the graf, + that is similar to the one in the <link linkend="mapping_task">previous section</link>. + </para> + <figure float="0"> + <title>Selected Task Details Section for Template Task.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_7a.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + </section> + </section> + + </section> + <section id="options_tab"> + <title>Options Tab</title> + <para>This section describes Options tab of the Smooks Configuration File editor, gives short recommendations how this tab can be used during the project configuring.</para> + <figure float="0"> + <title> Options tab of the Smooks Configuration File editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_8.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <section> + <title>Smooks Configuration section</title> + <para> + In the <property moreinfo="none">Smooks Configuration</property> section of <property moreinfo="none">Options Tab</property> + only one element is availible:Smooks Platform Version + </para> + <figure float="0"> + <title>Smooks Configuration section of Options tab</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_9.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>This parameter is not rechangable, + and is set according to the vesion of the Smooks libraries that are added to the project. + </para> + </section> + + <section> + <title>Filter Settings Filter section</title> + <para> + In Filter Settings section you can set + the following global options responsible for Smooks filtering configuring:</para> + <figure float="0"> + <title>Filter Settings section of Options tab</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_10.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>This behavior can be turned off using this global configuration parameter and can be overriden on a per fragment basis by targetting a Visitor implementation at that fragment that takes ownership of the Result writer (in the case of SAX filtering), or simply modifies the DOM (in the case of DOM filtering). As an example of this, see the FreeMarkerTemplateProcessor. + </para> + <table> + <title>Options Tab. Filter Settings section.</title> + <tgroup cols="3"> + <colspec align="left" colnum="1" colwidth="1*"></colspec> + <colspec align="left" colnum="2" colwidth="3*"></colspec> + <colspec align="left" colnum="3" colwidth="1*"></colspec> + + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + <row> + <entry>Stream Filter Type</entry> + <entry>Determines the type of processing model that will be used. + Please refer to <ulink url="http://www.smooks.org/mediawiki/index.php?title=V1.2:Smooks_v1.2_User_Gui..."> + Filtering Process Selection section</ulink> + of the official Smooks User Guide for more information about these models: + <itemizedlist> + <listitem><para><emphasis>SAX</emphasis></para></listitem> + <listitem><para><emphasis>DOM</emphasis></para></listitem> + </itemizedlist> + </entry> + <entry>DOM</entry> + </row> + + <row> + <entry>Default Serialization is On</entry> + <entry>Defines whether default serialization should be switched on. + Default serialization being turned on leads to locating StreamResult/DOMResult + to the Result objects provided to the Smooks.filterSource method and to + serialization all the events to that Result.</entry> + <entry>true</entry> + + </row> + </tbody> + </tgroup> + </table> + </section> + </section> + <section id="smooksformeditor_sourcetab" xreflabel="Smooks Source Tab"> + + <title>Source Tab</title> + <para>This section provides information about Smooks Source Editor Page.</para> + <section> + <title>XML Source Editor</title> + <para>You can use this editor to edit the Smooks Configuration file directly. </para> + <figure float="0"> + <title>Graphical Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/source_editor1.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>Error underlining in Graphical Editor</title> + <para>If the <property moreinfo="none">Smooks tools</property> can't understand the configuration + file or the configuration file is illegal (XML structure isn't right for Smooks + Configuration file, etc.), the error is underlined.</para> + <figure float="0"> + <title>Graphical Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/reference_11.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + + </section> + + <section> + <title>Smooks Configuration File Validator</title> + <para>Smooks configuration file validator will validate your Smooks configuration file. Just right-click on the file and then click on the <property moreinfo="none">Validate</property> button. The validator can be enabled/disabled in <emphasis><property moreinfo="none">Window -> Preferences -> Validation</property></emphasis>:</para> + + <figure float="0"> + <title>Validation: Smooks Configuration File Validator</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/smooks_conf_validator.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>You can set up your Smooks validator to include, exclude groups to validate and specify rules for validation. Just click on the <property moreinfo="none">Settings</property> button and use the options provided:</para> + + <figure float="0"> + <title>Smooks Configuration File Validator Settings</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/source_editor/smooks_conf_validator_settings.png" scale="90"></imagedata> + </imageobject> + </mediaobject> + </figure> + + + </section> + </section> + </section> +</chapter> + + +<chapter xml:base="file:///home/vchukhutsina/repos/ochik_jboss/smooks/docs/reference/en/modules/summary.xml"> + <?dbhtml filename="summary.html"?> + <title>Summary</title> + <para>In conclusion, with this document you know all the capabilities of Smooks Tools and could easily start with them. + The chapters above walked you through the steps on how to create and configure some XML to JAVA mapping project. + If you have questions or suggestions concerned both the documentation and tools behavior, + you are welcome to JBoss Tools Users forum. + Please, use Jira to report bugs and requests on documentation.</para> + + <section> + <title>Other relevant resources on the topic</title> + <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at + <ulink url="http://docs.jboss.org/tools">http://docs.jboss.org/tools</ulink> in the corresponding release directory. + </para> + <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs">http://download.jboss.org/jbosstools/nightly-docs</ulink>. </para> +<para>For more information about Smooks technology please visit + <ulink url="http://www.smooks.org/mediawiki/index.php?title=Main_Page"> + Smooks Technology Home Page</ulink></para> + + </section> +</chapter> + +</book> Modified: trunk/smooks/docs/reference/en/modules/introduction.xml =================================================================== --- trunk/smooks/docs/reference/en/modules/introduction.xml 2010-03-09 18:24:28 UTC (rev 20714) +++ trunk/smooks/docs/reference/en/modules/introduction.xml 2010-03-09 18:55:57 UTC (rev 20715) @@ -45,7 +45,7 @@ <entry><para>Smooks Editor</para></entry> <entry><para>Smooks Editor helps configure the created Smooks configuration file.</para></entry> <entry> - <link linkend="quickstart_formeditor">Smooks Editor</link> + <link linkend="process_tab">Smooks Editor</link> </entry> </row> @@ -64,7 +64,7 @@ <title>What is Smooks?</title> <para><property>Smooks</property> is a Java Framework/Engine for processing XML and non XML - data (CSV, EDI, Java, JSON etc).</para> + data (CSV, EDI, Java, JSON etc).It provides: </para> <para/> <para> <orderedlist numeration="upperroman" inheritnum="inherit"> @@ -121,13 +121,46 @@ </imageobject> </mediaobject> </figure> - <para>The easiest way to use the Smooks Configuration Editor is to create a project +  </section> <section> + <title>Adding Smooks jars</title> + + <para>During your development, you probably will be faced with the + necessity to include some additional Smooks jars to your project. + This problem can be solved in such a way:</para> + <itemizedlist> + <listitem><para>Create the folder named "lib" inside your project,if it doesn't exist yet. + Copy all the Smooks jars you need to include into the <emphasis><property>lib</property></emphasis> directory. + </para></listitem> + <listitem><para>Right-click on the project and select Properties.</para></listitem> + <listitem><para>Select the "Java Build Path" item in the Properties list, then the Libraries tab, and click "Add JARs". + </para></listitem> + <listitem><para>In the Jar Selection dialog, select all the jars in the "lib" directory you want to include and click OK.</para></listitem> + <listitem><para> + Now you should see all the jars + included to your project hierarchy. </para></listitem> + </itemizedlist> + + <figure> + <title>Smooks Form editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/introduction/introduction2.png" scale="90"/> + </imageobject> + </mediaobject> + </figure> +  + </section> +  </chapter> Modified: trunk/smooks/docs/reference/en/modules/references.xml =================================================================== --- trunk/smooks/docs/reference/en/modules/references.xml 2010-03-09 18:24:28 UTC (rev 20714) +++ trunk/smooks/docs/reference/en/modules/references.xml 2010-03-09 18:55:57 UTC (rev 20715) @@ -9,17 +9,8 @@ </keywordset> </chapterinfo> <title>Reference</title> - <para>This chapter includes detailed reference information about Smooks Tools.</para> - <section> - <title>Smooks Configuration Editor</title> - <para>This chapter describes the following tabs of the Smooks Configuration Editor:</para> - - <itemizedlist> - <listitem><para><link linkend="process_tab">Process tab</link></para></listitem> - <listitem><para><link linkend="options_tab">Options tab</link></para></listitem> - <listitem><para><link linkend="smooksformeditor_sourcetab">Source tab</link></para></listitem> - </itemizedlist> - <section id="process_tab"> + <para>This chapter includes detailed reference information about all tabs of the Smooks Configuration Editor.</para> + <section id="process_tab"> <title>Process tab</title> <para>The Process tab of the Smooks Configuration Editor helps to configure different types of transformations. By default smooks configuration file is opened in this editor.If you have another default settings for editor opening @@ -62,7 +53,7 @@ <entry>Add Task</entry> <entry>Select one of the following tasks according to the necessary type of Source and Result types of the files: <itemizedlist> - <listitem><para><emphasis>Input</emphasis> -this task is required and + <listitem><para><emphasis>Input</emphasis> - this task is required and appears automatically when Smooks config file is created. You should just configure it properly.</para></listitem> <listitem><para><emphasis>Java Mapping</emphasis></para></listitem> @@ -210,36 +201,36 @@ </entry> <entry> <itemizedlist> - <listitem><para><emphasis>No Input</emphasis> -no info required</para></listitem> - <listitem><para><emphasis>XML</emphasis> -no info required</para></listitem> - <listitem><para><emphasis>Java</emphasis> -no info required</para></listitem> - <listitem><para><emphasis>XSD/WSDL</emphasis> -no info required</para></listitem> + <listitem><para><emphasis>No Input</emphasis> - no info required</para></listitem> + <listitem><para><emphasis>XML</emphasis> - no info required</para></listitem> + <listitem><para><emphasis>Java</emphasis> - no info required</para></listitem> + <listitem><para><emphasis>XSD/WSDL</emphasis> - no info required</para></listitem> <listitem><para><emphasis>CSV</emphasis></para><itemizedlist> - <listitem><para><emphasis>Fields</emphasis> -Comma separated list of CSV record field names + <listitem><para><emphasis>Fields</emphasis> - Comma separated list of CSV record field names </para></listitem> - <listitem><para><emphasis>Separator Character</emphasis> -Field separator character. Default of ','. + <listitem><para><emphasis>Separator Character</emphasis> - Field separator character. Default of ','. </para></listitem> - <listitem><para><emphasis>Quote Character</emphasis> -Quote character. Default of '"'. + <listitem><para><emphasis>Quote Character</emphasis> - Quote character. Default of '"'. </para></listitem> - <listitem><para><emphasis>Record Name</emphasis> -Name of csv record element.Default:csv-record</para></listitem> - <listitem><para><emphasis>Root Name</emphasis> -Name of csv root element.Default:csv-set</para></listitem> - <listitem><para><emphasis>indent</emphasis> -Add indentation character data to the generated event stream. This simply makes + <listitem><para><emphasis>Record Name</emphasis> - Name of csv record element.Default:csv-record</para></listitem> + <listitem><para><emphasis>Root Name</emphasis> - Name of csv root element.Default:csv-set</para></listitem> + <listitem><para><emphasis>indent</emphasis> - Add indentation character data to the generated event stream. This simply makes the generated event stream easier to read in its serialized form. Useful for testing etc.Default:true </para></listitem> - <listitem><para><emphasis>Skip Lines</emphasis> -Number of lines to skip before processing starts. Default of 0. + <listitem><para><emphasis>Skip Lines</emphasis> - Number of lines to skip before processing starts. Default of 0. </para></listitem> </itemizedlist> </listitem> <listitem><para><emphasis>EDI</emphasis></para> <itemizedlist> - <listitem><para><emphasis>Target Profile</emphasis> -Defines the target profile + <listitem><para><emphasis>Target Profile</emphasis> - Defines the target profile </para></listitem> - <listitem><para><emphasis>Encoding</emphasis> -The character encoding. Default "UTF-8"</para></listitem> - <listitem><para><emphasis>Mapping Model</emphasis> -Defines the EDI Mapping Model configuration for processing the + <listitem><para><emphasis>Encoding</emphasis> - The character encoding. Default "UTF-8"</para></listitem> + <listitem><para><emphasis>Mapping Model</emphasis> - Defines the EDI Mapping Model configuration for processing the EDI message stream to a stream of SAX events that can be processed by Smooks.</para></listitem> - <listitem><para><emphasis>Validate</emphasis> -This attribute turns on/off datatype validation in the EDI Parser. + <listitem><para><emphasis>Validate</emphasis> - This attribute turns on/off datatype validation in the EDI Parser. Validation is on by default. It makes sense to turn datatype validation off on the EDI Reader if the EDI data is being bound into a Java Object model. @@ -248,40 +239,40 @@ </listitem> <listitem><para><emphasis>JSON</emphasis></para> <itemizedlist> - <listitem><para><emphasis>Target Profile</emphasis> -Defines the target profile</para></listitem> - <listitem><para><emphasis>Array Element Name</emphasis> -The element name of a array element. Default of 'element'. + <listitem><para><emphasis>Target Profile</emphasis> - Defines the output transformation profile</para></listitem> + <listitem><para><emphasis>Array Element Name</emphasis> - The element name of a array element. Default of 'element'. </para></listitem> - <listitem><para><emphasis>Encoding</emphasis> -encoding: The default encoding of any JSON message + <listitem><para><emphasis>Encoding</emphasis> - encoding: The default encoding of any JSON message InputStream processed by this Reader. Default of 'UTF-8'.</para></listitem> - <listitem><para><emphasis>Illegal Element Name Char Replacement</emphasis> -If illegal characters are encountered in a JSON element name then they are replaced with this value. + <listitem><para><emphasis>Illegal Element Name Char Replacement</emphasis> - If illegal characters are encountered in a JSON element name then they are replaced with this value. By default this is not defined, so that the reader doesn't doesn't search for illegal characters. </para></listitem> - <listitem><para><emphasis>Indent</emphasis> -Add indentation character data to the generated event stream. This simply makes + <listitem><para><emphasis>Indent</emphasis> - Add indentation character data to the generated event stream. This simply makes the generated event stream easier to read in its serialized form. Useful for testing etc.Default:false. </para></listitem> - <listitem><para><emphasis>Key Prefix on Numeric</emphasis> -The prefix character to add if the JSON node name starts with a number. + <listitem><para><emphasis>Key Prefix on Numeric</emphasis> - The prefix character to add if the JSON node name starts with a number. By default this is not defined, so that the reader doesn't search for element names that start with a number. </para></listitem> - <listitem><para><emphasis>Key Whitespace Replacement</emphasis> -The replacement character for whitespaces in a JSON map key. + <listitem><para><emphasis>Key Whitespace Replacement</emphasis> - The replacement character for whitespaces in a JSON map key. By default this not defined, so that the reader doesn't search for whitespaces. </para></listitem> - <listitem><para><emphasis>Null Value Replacement</emphasis> -The replacement string for JSON NULL values. Default is ""(an empty string). </para></listitem> - <listitem><para><emphasis>Root Name</emphasis> -The element name of the document root. Default of 'json'. + <listitem><para><emphasis>Null Value Replacement</emphasis> - The replacement string for JSON NULL values. Default is ""(an empty string). </para></listitem> + <listitem><para><emphasis>Root Name</emphasis> - The element name of the document root. Default of 'json'. </para></listitem> - <listitem><para><emphasis>Key Maps</emphasis> -Defines a JSON element name mapping + <listitem><para><emphasis>Key Maps</emphasis> - Defines a JSON element name mapping The "from" key will be replaced with the "to" key or the contents of the element. </para></listitem> </itemizedlist> </listitem> <listitem><para><emphasis>Custom</emphasis></para> <itemizedlist> - <listitem><para><emphasis>Target Profile</emphasis> -</para></listitem> - <listitem><para><emphasis>Class</emphasis> -Custom reader class.</para></listitem> - <listitem><para><emphasis>Handlers</emphasis> -Set a handler on the reader instance e.g. an EntityResolver, ErrorHandler etc. + <listitem><para><emphasis>Target Profile</emphasis> - Defines the output transformation profile</para></listitem> + <listitem><para><emphasis>Class</emphasis> - Custom reader class.</para></listitem> + <listitem><para><emphasis>Handlers</emphasis> - Set a handler on the reader instance e.g. an EntityResolver, ErrorHandler etc. </para></listitem> - <listitem><para><emphasis>Features</emphasis> -Reader Features List</para></listitem> - <listitem><para><emphasis>Parametres</emphasis> -Resource Parameters</para></listitem> + <listitem><para><emphasis>Features</emphasis> - Reader Features List</para></listitem> + <listitem><para><emphasis>Parametres</emphasis> - Resource Parameters</para></listitem> </itemizedlist> </listitem> @@ -353,7 +344,7 @@ </imageobject> </mediaobject> </figure> - <para> This graphical editor allow you to perform drug/drop operations with the nodes of transform data to map the source data to target data. + <para>This graphical editor allows you to perform drag&drop operation with the nodes of transformed data to map the source data to target data. When you save the changes in the graphical editor the correct Smooks configuration file content will be generated. </para> </section> @@ -444,7 +435,7 @@ <listitem><para><emphasis>DOM</emphasis></para></listitem> </itemizedlist> </entry> - <entry>DOM</entry> + <entry>SAX</entry> </row> <row> @@ -453,7 +444,7 @@ Default serialization being turned on leads to locating StreamResult/DOMResult to the Result objects provided to the Smooks.filterSource method and to serialization all the events to that Result.</entry> - <entry>true</entry> + <entry>false</entry> </row> </tbody> @@ -520,5 +511,5 @@ </section> </section> - </section> + </chapter> Modified: trunk/smooks/docs/reference/en/modules/tasks.xml =================================================================== --- trunk/smooks/docs/reference/en/modules/tasks.xml 2010-03-09 18:24:28 UTC (rev 20714) +++ trunk/smooks/docs/reference/en/modules/tasks.xml 2010-03-09 18:55:57 UTC (rev 20715) @@ -9,7 +9,8 @@ </keywordset> </chapterinfo> <title>Tasks</title> - <para>This chapter describes the main tasks a user can be faced during Smooks tools usage.</para> + <para>This chapter describes the main tasks a user can be faced during Smooks tools usage. + Here we use the example that can be downloaded from <ulink url="http://sourceforge.net/projects/smooks/files/Smooks%20v1.2/Smooks%20v1.2/...">here</ulink> </para> <section id="config_file_wizzard"> <title>New Smooks Configuration File Creation</title> <para>Select the project where you want to create new Smooks Configuration File and right-click on it, @@ -26,7 +27,7 @@ </imageobject> </mediaobject> </figure> - <para>The first wizard page is a file path creation page. Select the <emphasis> + <para>The wizard page is a file path creation page. Select the <emphasis> <property>src</property> </emphasis> folder to be the files container, and input the name <emphasis><property>smooks-config.xml</property>.</emphasis> Click @@ -39,7 +40,7 @@ </imageobject> </mediaobject> </figure> - <para>The second wizard page allow you to select Smooks configuration file version. Select the appropriate one and click <emphasis><property>Finish</property></emphasis> to complete the wizard.</para> + </section> <section> <title>Input Task Configuring</title> @@ -66,7 +67,7 @@ <para> Once you've specified your reader configuration and sample data, you can see the input model rendered in a tree form in the <emphasis>Input model</emphasis> section. - On the picture below you can see the correct configuration of some XML input task. + On the picture below you can see the correct configuration of some XML input task where <emphasis><property>input-message.xml</property></emphasis> is set as an input data file. </para> <figure> <title>Input Task Configuring</title> @@ -114,7 +115,7 @@ </figure> <para>Another method of adding <emphasis>Java Mapping</emphasis> element to the canvas in the Processing Tasks section is to right click Input Task - element and select <emphasis>Java Mapping</emphasis> in the popup menu </para> + element and select <emphasis>Java Mapping</emphasis> in the popup menu. </para> <figure> <title>Java Mapping configuration</title> <mediaobject> @@ -136,8 +137,7 @@ </figure> <para> <emphasis>Java Bean Creation</emphasis> wizard appears. - Specify a unique identifier for the new class, the class path, - whether it's an array or not, and if it is a collection, also specify the collection class. + Specify a unique identifier for the new class, the class path. If the Java class is specified, you'll see a list of the properties in the box below. Click <emphasis>Finish</emphasis> when you're done. Now with the input and output models on the canvas, you can click and drag @@ -169,15 +169,94 @@ </mediaobject> </figure> <para> - Select "Apply Template" from the popup menu and it will appear to the right, connected to the task you created it from. Then select the "Apply Template" task. - Once you've defined your template model, you can click and drag from the various input elements to corresponding output elements in the template. Make sure to connect collection elements to corresponding collection elements + The <property>Message Type Selection</property> wizard will appear. + In our example we will transfer our data to csv output format,so you should select <emphasis><property>CSV</property></emphasis> and click <property>Next</property>.</para> + <figure> + <title>Message Type Selection</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process7a.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + On the next wizard page put the following string into the Fields,select Output fields Names and click <property>Finish</property>.</para> + <figure> + <title>CSV output message configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process7b.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + After these steps "Apply Template" task will appear to the right, connected to the task you created it from. + To continue the process of configuration you should click on it and find <emphasis>CSV Template</emphasis> + item with entered fields on the canvas.Now you can click and drag from various input elements to corresponding output elements + in the template. Make sure to connect collection elements to corresponding <emphasis>csv-record</emphasis> + In our example we transfer into CSV output only the elements of orderItems collection(see picture below) </para> + <figure> + <title>Relations between input and output models</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process7c.png"/> + </imageobject> + </mediaobject> + </figure> </section> <section> <title>Smooks Configuration testing using Smooks Run Configuration</title> <para>This option is intended to view the results of Smooks transforming procedure. - For more detailed information about this option please go <ulink url="http://community.jboss.org/wiki/UsingtheSmooksRunConfigurationtotestSmook...">here</ulink>.</para> + To do the testing you should select your <emphasis>Smooks Configuration file</emphasis> you want to transfer in the Project Navigator or open it in + the Smooks Configuration Editor and then select "Run As..." from the <emphasis><property>Run</property></emphasis> + toolbar button + or <emphasis><property>Run->Smooks Run Configuration</property></emphasis> option in the top menu bar. And Smooks Configuration file will be run automatically. + </para> + <figure> + <title>Smooks Configuration testing</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/process_page/process8.png"/> + </imageobject> + </mediaobject> + </figure> + <para>If any errors or warnings appear, they will pop up in a dialog. + The output of the test will appear in the Console view. + In our case the following streaming output will appear:</para> + <programlisting role="JAVA"><![CDATA[[Stream Templating Result ...] + |-- + |"productId","quantity","price" + |"111","2","8.9" + |"222","7","5.2" + |-- + +[Java Mapping Results...] + |-- + |> order (beanId = "order") + | > header (beanId = "header") + | > date = "2006-11-15 20:45:28.0 EET" + | > customerNumber = 123123L + | > customerName = "Joe" + | > orderItems (beanId = "orderItems") + | > example.model.OrderItem (beanId = "orderItem") + | > productId = 111L + | > quantity = 2I + | > price = 8.9D + | > example.model.OrderItem (beanId = "orderItem") + | > productId = 222L + | > quantity = 7I + | > price = 5.2D + |-- +]]></programlisting> + <para>If the test runs but doesn't generate any streaming output the Console output will be the following: + </para> + <programlisting role="JAVA"><![CDATA[ Nothing to Display: + - No Java Mappings. + - No Templates Applied.]]> + </programlisting> + </section> </chapter>

14 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r20714 - trunk/bpel/plugins/org.eclipse.bpel.ui/src/org/eclipse/bpel/ui/editparts.

by jbosstools-commits＠lists.jboss.org

Author: bbrodt Date: 2010-03-09 13:24:28 -0500 (Tue, 09 Mar 2010) New Revision: 20714 Modified: trunk/bpel/plugins/org.eclipse.bpel.ui/src/org/eclipse/bpel/ui/editparts/FlowEditPart.java Log: https://jira.jboss.org/jira/browse/JBIDE-6032 force auto layout at BPEL editor startup. Modified: trunk/bpel/plugins/org.eclipse.bpel.ui/src/org/eclipse/bpel/ui/editparts/FlowEditPart.java =================================================================== --- trunk/bpel/plugins/org.eclipse.bpel.ui/src/org/eclipse/bpel/ui/editparts/FlowEditPart.java 2010-03-09 18:02:57 UTC (rev 20713) +++ trunk/bpel/plugins/org.eclipse.bpel.ui/src/org/eclipse/bpel/ui/editparts/FlowEditPart.java 2010-03-09 18:24:28 UTC (rev 20714) @@ -235,6 +235,9 @@ IFigure child = ((GraphicalEditPart) childEditPart).getFigure(); getContentPane().add(child, getFigure().getLayoutManager().getConstraint(child), index); + // JBIDE-6032: force an auto layout at startup + if (getShowFreeformFlow() && getAutoLayout()) + doAutoLayout(false); } protected void setFlowEditPolicies() {

14 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r20713 - trunk/cdi/tests/org.jboss.tools.cdi.core.test/src/org/jboss/tools/cdi/core/test/tck.

by jbosstools-commits＠lists.jboss.org

Author: akazakov Date: 2010-03-09 13:02:57 -0500 (Tue, 09 Mar 2010) New Revision: 20713 Modified: trunk/cdi/tests/org.jboss.tools.cdi.core.test/src/org/jboss/tools/cdi/core/test/tck/BeanDefinitionTest.java Log: https://jira.jboss.org/jira/browse/JBIDE-5808 Modified: trunk/cdi/tests/org.jboss.tools.cdi.core.test/src/org/jboss/tools/cdi/core/test/tck/BeanDefinitionTest.java =================================================================== --- trunk/cdi/tests/org.jboss.tools.cdi.core.test/src/org/jboss/tools/cdi/core/test/tck/BeanDefinitionTest.java 2010-03-09 18:00:30 UTC (rev 20712) +++ trunk/cdi/tests/org.jboss.tools.cdi.core.test/src/org/jboss/tools/cdi/core/test/tck/BeanDefinitionTest.java 2010-03-09 18:02:57 UTC (rev 20713) @@ -113,6 +113,15 @@ assertTheOnlyBean("org.jboss.jsr299.tck.tests.definition.bean.Animal"); } + /** + * section 3.1.2 a) + * section 2.2 a) + * section 2.2.1 a) + * section 2.2.1 d) + * section 2.2.1 e) + * section 2.2 l) + * section 11.1 ba) + */ public void testBeanTypes() throws JavaModelException { Set<IBean> beans = getBeans("org.jboss.jsr299.tck.tests.definition.bean.Tarantula"); assertEquals("There should be the only bean in org.jboss.jsr299.tck.tests.definition.bean.Tarantula", 1, beans.size());

14 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r20712 - trunk/jsf/plugins/org.jboss.tools.jsf.text.ext.richfaces/src/org/jboss/tools/jsf/text/ext/richfaces/hyperlink.

by jbosstools-commits＠lists.jboss.org

Author: dazarov Date: 2010-03-09 13:00:30 -0500 (Tue, 09 Mar 2010) New Revision: 20712 Modified: trunk/jsf/plugins/org.jboss.tools.jsf.text.ext.richfaces/src/org/jboss/tools/jsf/text/ext/richfaces/hyperlink/RichfacesCSSClassHyperlinkPartitioner.java Log: https://jira.jboss.org/jira/browse/JBIDE-5986 Modified: trunk/jsf/plugins/org.jboss.tools.jsf.text.ext.richfaces/src/org/jboss/tools/jsf/text/ext/richfaces/hyperlink/RichfacesCSSClassHyperlinkPartitioner.java =================================================================== --- trunk/jsf/plugins/org.jboss.tools.jsf.text.ext.richfaces/src/org/jboss/tools/jsf/text/ext/richfaces/hyperlink/RichfacesCSSClassHyperlinkPartitioner.java 2010-03-09 18:00:25 UTC (rev 20711) +++ trunk/jsf/plugins/org.jboss.tools.jsf.text.ext.richfaces/src/org/jboss/tools/jsf/text/ext/richfaces/hyperlink/RichfacesCSSClassHyperlinkPartitioner.java 2010-03-09 18:00:30 UTC (rev 20712) @@ -22,13 +22,29 @@ */ public class RichfacesCSSClassHyperlinkPartitioner extends CSSClassHyperlinkPartitioner { public static final String RICHFACES_CSS_CLASS_PARTITION = "org.jboss.tools.common.text.ext.RICHFACES_CSS_CLASS"; //$NON-NLS-1$ - private static final String RICHFACES_CSS_CLASS_TOKEN = "/styleClass/"; //$NON-NLS-1$ + + private static final String[] tokens = new String[]{ + "/columnClasses/", + "/footerClass/", + "/headerClass/", + "/rowClasses/", + "/captionClass/", + "/captionStyle/", + "/styleClass/", + "/errorClass/", + "/fatalClass/", + "/infoClass/", + "/disabledClass/", + "/enabledClass/" + }; @Override public boolean recognize(IDocument document, IHyperlinkRegion region) { - if (region.getAxis() != null - && region.getAxis().endsWith(RICHFACES_CSS_CLASS_TOKEN)) - return true; + if (region.getAxis() != null){ + for(String token : tokens) + if(region.getAxis().endsWith(token)) + return true; + } return false; }

14 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits March 2010