[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-308) Instructions for deploying quickstart bpel_esb_helloworld to SOA-P 5.3.1 do not work

Instructions for deploying quickstart bpel_esb_helloworld to SOA-P 5.3.1 do not work ------------------------------------------------------------------------------------ Key: TOOLSDOC-308 URL: https://issues.jboss.org/browse/TOOLSDOC-308 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public(Everyone can see) Components: Getting Started Guide Reporter: Nick Boldt Assignee: Michelle Murray Attachments: jbds6-soap531-bpel-esb-helloworld-cannot-deploy.png Trying to work though this: https://access.redhat.com/site/documentation//en-US/JBoss_Enterprise_SOA_... Problems: 1. {quote} (In this example, we are going to import an existing project from the SOA_ROOT/jboss-as/samples/quickstart/bpel_esb_helloworld directory). {quote} In SOA-P 5.3.1, the folder is called quickstarts (plural), not quickstart. 2. Because there is no .project file in that folder, JBDS cannot import it as it does not know what type of project it is. If I add a .project file, which may or may not be correct: {code} <?xml version="1.0" encoding="UTF-8"?> <projectDescription> <name>bpel_esb_helloworld</name> <comment></comment> <projects> </projects> <buildSpec> <buildCommand> <name>org.eclipse.wst.common.project.facet.core.builder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.eclipse.wst.validation.validationbuilder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.eclipse.bpel.validator.builder</name> <arguments> <dictionary> <key>debug</key> <value>false</value> </dictionary> </arguments> </buildCommand> </buildSpec> <natures> <nature>org.eclipse.jem.workbench.JavaEMFNature</nature> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature> <nature>org.eclipse.wst.common.project.facet.core.nature</nature> </natures> </projectDescription> {code} I can then import the project. 3. {quote}Once the server has been started, right-click on the server entry again, and select Add and Remove->bpel_esb_helloworld.{quote} Unfortunately, the project is not available to be deployed. !jbds6-soap531-bpel-esb-helloworld-cannot-deploy.png! 4. {quote}Test the deployed BPEL process by using the Ant script provided with the quick start sample. Right-click on the project root folder's build.xml file and select Run As->Ant Build. {quote} So I did that, and it built the project. THEN I noticed the "Note" below, which says to select the menu item with "..." instead. Why not just tell people to select *Run As->Ant Build...* instead of *Run As->Ant Build* ? 5. In step 15, obviously, the console throws errors because I was unable to deploy the project to the server. --- So this is partly a documentation problem. But worse, the sample project lacks a .project file and therefore cannot be imported; chances are my .project file was incomplete (missing the correct builders/natures) and therefore it cannot be deployed to the server either, even with my hackaround. Note that I used JBDS 7.0.0.Alpha2, but the same problem occurs for JBDS 6.0.1 and JBDS 5.0.2 w/ SOA-P 5.3.1.