This is the patch file, as requested.
I cann't quite get the formatting of two paragraphs correct. I need to bring them back to the left, they are:
"
From a Maven perspective, I have found working with WID Libraries and WID Modules packaged as Jar files to be the easiest.
Please refer to IBM developerWorks article IBM WebSphere Developer Technical Journal: Get started with WebSphere Integration Developer as a reference for the following examples.
This article creates a simple sample stock market service. It is implemented in two parts:
"
and
"
WID (6.0.2 at least) enforces that the source (and target) are set to the root dir of the project.
Under the covers, WID will create supporting projects as necessary. These are to be treated as generated artifacts and are generally not to be modified directly in any way. In this example, WID will generate a StockModuleApp (EAR) project, a StockModuleEJB (EJB) and if a Web Service is used or needed [not in this example] StockModuleWeb (Web) project. When outside the WID context, it is the job of ServiceDeploy to create these synthetic projects with the end point being an EAR file that can be deployed to Process Server.
Note: As Process Server sits on top of WebSphere Application Server, it is still perfectly capable of running normal J2EE EAR files.
"
If you can shift them to the left so that they line up with the primary text, then that would be great.
New Feature
Closed
Major
This is the patch file, as requested.
I cann't quite get the formatting of two paragraphs correct. I need to bring them back to the left, they are:
"
From a Maven perspective, I have found working with WID Libraries and WID Modules packaged as Jar files to be the easiest.
Please refer to IBM developerWorks article IBM WebSphere Developer Technical Journal: Get started with WebSphere Integration Developer as a reference for the following examples.
This article creates a simple sample stock market service. It is implemented in two parts:
"
and
"
WID (6.0.2 at least) enforces that the source (and target) are set to the root dir of the project.
Under the covers, WID will create supporting projects as necessary. These are to be treated as generated artifacts and are generally not to be modified directly in any way. In this example, WID will generate a StockModuleApp (EAR) project, a StockModuleEJB (EJB) and if a Web Service is used or needed [not in this example] StockModuleWeb (Web) project. When outside the WID context, it is the job of ServiceDeploy to create these synthetic projects with the end point being an EAR file that can be deployed to Process Server.
Note: As Process Server sits on top of WebSphere Application Server, it is still perfectly capable of running normal J2EE EAR files.
"
If you can shift them to the left so that they line up with the primary text, then that would be great.