November 2010 - jbosstools-commits

JBoss Tools SVN: r26878 - in trunk/jsf/tests: org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide and 1 other directories.

by jbosstools-commits＠lists.jboss.org

Author: mareshkau Date: 2010-11-24 09:44:28 -0500 (Wed, 24 Nov 2010) New Revision: 26878 Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.seam.test/src/org/jboss/tools/jsf/vpe/seam/test/JBIDE1484Test.java Removed: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE1484Test.java Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java trunk/jsf/tests/org.jboss.tools.jsf.vpe.seam.test/src/org/jboss/tools/jsf/vpe/seam/test/SeamAllTests.java Log: https://jira.jboss.org/browse/JBIDE-7704, moving seam test to right place Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2010-11-24 14:20:55 UTC (rev 26877) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2010-11-24 14:44:28 UTC (rev 26878) @@ -22,7 +22,6 @@ import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE1105Test; import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE1460Test; import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE1479Test; -import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE1484Test; import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE1494Test; import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE1615Test; import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE1720Test; @@ -163,7 +162,6 @@ suite.addTestSuite(JBIDE3441Test.class); suite.addTestSuite(JsfJbide1467Test.class); suite.addTestSuite(JsfJbide1501Test.class); - suite.addTestSuite(JBIDE1484Test.class); suite.addTestSuite(JsfJbide1568Test.class); suite.addTestSuite(JBIDE1615Test.class); suite.addTestSuite(JBIDE1479Test.class); Deleted: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE1484Test.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE1484Test.java 2010-11-24 14:20:55 UTC (rev 26877) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE1484Test.java 2010-11-24 14:44:28 UTC (rev 26878) @@ -1,92 +0,0 @@ -/******************************************************************************* - * Copyright (c) 2007 Red Hat, Inc. - * Distributed under license by Red Hat, Inc. All rights reserved. - * This program is made available under the terms of the - * Eclipse Public License v1.0 which accompanies this distribution, - * and is available at http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * Red Hat, Inc. - initial API and implementation - ******************************************************************************/ -package org.jboss.tools.jsf.vpe.jsf.test.jbide; - -import static org.jboss.tools.vpe.xulrunner.util.XPCOM.queryInterface; - -import java.util.ArrayList; -import java.util.List; - -import org.eclipse.core.resources.IFile; -import org.eclipse.ui.IEditorInput; -import org.eclipse.ui.part.FileEditorInput; -import org.jboss.tools.jsf.vpe.jsf.test.JsfAllTests; -import org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor; -import org.jboss.tools.vpe.editor.util.HTML; -import org.jboss.tools.vpe.ui.test.TestUtil; -import org.jboss.tools.vpe.ui.test.VpeTest; -import org.mozilla.interfaces.nsIDOMDocument; -import org.mozilla.interfaces.nsIDOMElement; -import org.mozilla.interfaces.nsIDOMNode; - -/** - * @author Max Areshkau - * - * junit for JBIDE-1484(http://jira.jboss.com/jira/browse/JBIDE-1484) - */ -public class JBIDE1484Test extends VpeTest { - - private static final String TEST_PAGE_NAME = "JBIDE/1484/JBIDE-1484.jsp"; //$NON-NLS-1$ - - public JBIDE1484Test(String name) { - - super(name); - } - - // test method for JBIDE 1484 - public void testJBIDE_1484() throws Throwable { - // wait - TestUtil.waitForJobs(); - // set exception - setException(null); - - // get test page path - IFile file = (IFile) TestUtil.getComponentPath(TEST_PAGE_NAME, - JsfAllTests.IMPORT_PROJECT_NAME); - - assertNotNull("Could not open specified file. componentPage = " + TEST_PAGE_NAME//$NON-NLS-1$ - + ";projectName = " + JsfAllTests.IMPORT_PROJECT_NAME, file);//$NON-NLS-1$ - - IEditorInput input = new FileEditorInput(file); - - assertNotNull("Editor input is null", input); //$NON-NLS-1$ - // open and get editor - JSPMultiPageEditor part = openEditor(input); - - // get dom document - nsIDOMDocument document = TestUtil.getVpeVisualDocument(part); - nsIDOMElement element = document.getDocumentElement(); - - // check that element is not null - assertNotNull(element); - - // get root node - nsIDOMNode node = queryInterface(element, nsIDOMNode.class); - - List<nsIDOMNode> elements = new ArrayList<nsIDOMNode>(); - - // find "input" elements - TestUtil.findElementsByName(node, elements, HTML.TAG_INPUT); - - assertEquals(3, elements.size()); - nsIDOMElement elementInput0 = queryInterface(elements.get(0), nsIDOMElement.class); - nsIDOMElement elementInput1 = queryInterface(elements.get(1), nsIDOMElement.class); - nsIDOMElement elementInput2 = queryInterface(elements.get(2), nsIDOMElement.class); - - assertEquals(" ", elementInput0.getAttribute("value")); //$NON-NLS-1$//$NON-NLS-2$ - assertEquals(" ", elementInput1.getAttribute("value")); //$NON-NLS-1$ //$NON-NLS-2$ - assertEquals("test", elementInput2.getAttribute("value")); //$NON-NLS-1$ //$NON-NLS-2$ - if (getException() != null) { - throw getException(); - } - } - -} Copied: trunk/jsf/tests/org.jboss.tools.jsf.vpe.seam.test/src/org/jboss/tools/jsf/vpe/seam/test/JBIDE1484Test.java (from rev 26876, trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE1484Test.java) =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.seam.test/src/org/jboss/tools/jsf/vpe/seam/test/JBIDE1484Test.java (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.seam.test/src/org/jboss/tools/jsf/vpe/seam/test/JBIDE1484Test.java 2010-11-24 14:44:28 UTC (rev 26878) @@ -0,0 +1,91 @@ +/******************************************************************************* + * Copyright (c) 2007 Red Hat, Inc. + * Distributed under license by Red Hat, Inc. All rights reserved. + * This program is made available under the terms of the + * Eclipse Public License v1.0 which accompanies this distribution, + * and is available at http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Red Hat, Inc. - initial API and implementation + ******************************************************************************/ +package org.jboss.tools.jsf.vpe.seam.test; + +import static org.jboss.tools.vpe.xulrunner.util.XPCOM.queryInterface; + +import java.util.ArrayList; +import java.util.List; + +import org.eclipse.core.resources.IFile; +import org.eclipse.ui.IEditorInput; +import org.eclipse.ui.part.FileEditorInput; +import org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor; +import org.jboss.tools.vpe.editor.util.HTML; +import org.jboss.tools.vpe.ui.test.TestUtil; +import org.jboss.tools.vpe.ui.test.VpeTest; +import org.mozilla.interfaces.nsIDOMDocument; +import org.mozilla.interfaces.nsIDOMElement; +import org.mozilla.interfaces.nsIDOMNode; + +/** + * @author Max Areshkau + * + * junit for JBIDE-1484(http://jira.jboss.com/jira/browse/JBIDE-1484) + */ +public class JBIDE1484Test extends VpeTest { + + private static final String TEST_PAGE_NAME = "JBIDE/1484/JBIDE-1484.jsp"; //$NON-NLS-1$ + + public JBIDE1484Test(String name) { + + super(name); + } + + // test method for JBIDE 1484 + public void testJBIDE_1484() throws Throwable { + // wait + TestUtil.waitForJobs(); + // set exception + setException(null); + + // get test page path + IFile file = (IFile) TestUtil.getComponentPath(TEST_PAGE_NAME, + SeamAllTests.IMPORT_PROJECT_NAME); + + assertNotNull("Could not open specified file. componentPage = " + TEST_PAGE_NAME//$NON-NLS-1$ + + ";projectName = " + SeamAllTests.IMPORT_PROJECT_NAME, file);//$NON-NLS-1$ + + IEditorInput input = new FileEditorInput(file); + + assertNotNull("Editor input is null", input); //$NON-NLS-1$ + // open and get editor + JSPMultiPageEditor part = openEditor(input); + + // get dom document + nsIDOMDocument document = TestUtil.getVpeVisualDocument(part); + nsIDOMElement element = document.getDocumentElement(); + + // check that element is not null + assertNotNull(element); + + // get root node + nsIDOMNode node = queryInterface(element, nsIDOMNode.class); + + List<nsIDOMNode> elements = new ArrayList<nsIDOMNode>(); + + // find "input" elements + TestUtil.findElementsByName(node, elements, HTML.TAG_INPUT); + + assertEquals(3, elements.size()); + nsIDOMElement elementInput0 = queryInterface(elements.get(0), nsIDOMElement.class); + nsIDOMElement elementInput1 = queryInterface(elements.get(1), nsIDOMElement.class); + nsIDOMElement elementInput2 = queryInterface(elements.get(2), nsIDOMElement.class); + + assertEquals(" ", elementInput0.getAttribute("value")); //$NON-NLS-1$//$NON-NLS-2$ + assertEquals(" ", elementInput1.getAttribute("value")); //$NON-NLS-1$ //$NON-NLS-2$ + assertEquals("test", elementInput2.getAttribute("value")); //$NON-NLS-1$ //$NON-NLS-2$ + if (getException() != null) { + throw getException(); + } + } + +} Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.seam.test/src/org/jboss/tools/jsf/vpe/seam/test/SeamAllTests.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.seam.test/src/org/jboss/tools/jsf/vpe/seam/test/SeamAllTests.java 2010-11-24 14:20:55 UTC (rev 26877) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.seam.test/src/org/jboss/tools/jsf/vpe/seam/test/SeamAllTests.java 2010-11-24 14:44:28 UTC (rev 26878) @@ -31,6 +31,7 @@ // $JUnit-BEGIN$ suite.addTestSuite(SeamComponentTest.class); suite.addTestSuite(SeamComponentContentTest.class); + suite.addTestSuite(JBIDE1484Test.class); // $JUnit-END$ return new VpeTestSetup(suite); }

13 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r26877 - trunk/common/plugins/org.jboss.tools.common.model/src/org/jboss/tools/common/model/loaders.

by jbosstools-commits＠lists.jboss.org

Author: scabanovich Date: 2010-11-24 09:20:55 -0500 (Wed, 24 Nov 2010) New Revision: 26877 Modified: trunk/common/plugins/org.jboss.tools.common.model/src/org/jboss/tools/common/model/loaders/XMLRecognizerContext.java Log: https://jira.jboss.org/browse/JBIDE-7728 Modified: trunk/common/plugins/org.jboss.tools.common.model/src/org/jboss/tools/common/model/loaders/XMLRecognizerContext.java =================================================================== --- trunk/common/plugins/org.jboss.tools.common.model/src/org/jboss/tools/common/model/loaders/XMLRecognizerContext.java 2010-11-24 12:06:15 UTC (rev 26876) +++ trunk/common/plugins/org.jboss.tools.common.model/src/org/jboss/tools/common/model/loaders/XMLRecognizerContext.java 2010-11-24 14:20:55 UTC (rev 26877) @@ -17,7 +17,7 @@ import javax.xml.parsers.DocumentBuilder; -import org.jboss.tools.common.model.util.SafeDocumentBuilderFactory; +import org.jboss.tools.common.xml.XMLUtilities; import org.w3c.dom.Document; import org.w3c.dom.DocumentType; import org.xml.sax.EntityResolver; @@ -90,7 +90,7 @@ return doctypes.get(docTypeString); } Reader xml = new StringReader(docTypeString + "<root></root>"); //$NON-NLS-1$ - DocumentBuilder db = SafeDocumentBuilderFactory.createDocumentBuilder(false); + DocumentBuilder db = XMLUtilities.createDocumentBuilder(false); if (db == null) return NULL_INFO;

13 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r26876 - in trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test: jbt and 1 other directories.

by jbosstools-commits＠lists.jboss.org

Author: jlukas(a)redhat.com Date: 2010-11-24 07:06:15 -0500 (Wed, 24 Nov 2010) New Revision: 26876 Modified: trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test/WSAllBotTests.java trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test/jbt/SampleWSTest.java trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test/wtp/WSTestBase.java Log: minor improvements Modified: trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test/WSAllBotTests.java =================================================================== --- trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test/WSAllBotTests.java 2010-11-24 11:27:52 UTC (rev 26875) +++ trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test/WSAllBotTests.java 2010-11-24 12:06:15 UTC (rev 26876) @@ -26,5 +26,4 @@ }) @RunWith(RequirementAwareSuite.class) public class WSAllBotTests { - } Modified: trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test/jbt/SampleWSTest.java =================================================================== --- trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test/jbt/SampleWSTest.java 2010-11-24 11:27:52 UTC (rev 26875) +++ trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test/jbt/SampleWSTest.java 2010-11-24 12:06:15 UTC (rev 26876) @@ -55,6 +55,16 @@ return "SampleSOAPWS"; } + @Override + protected String getWsPackage() { + return null; + } + + @Override + protected String getWsName() { + return null; + } + @Test public void testSampleSoapWS() { IFile dd = getDD(getWsProjectName()); @@ -181,16 +191,4 @@ } return ""; } - - @Override - protected String getWsPackage() { - // TODO Auto-generated method stub - return null; - } - - @Override - protected String getWsName() { - // TODO Auto-generated method stub - return null; - } } Modified: trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test/wtp/WSTestBase.java =================================================================== --- trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test/wtp/WSTestBase.java 2010-11-24 11:27:52 UTC (rev 26875) +++ trunk/ws/tests/org.jboss.tools.ws.ui.bot.test/src/org/jboss/tools/ws/ui/bot/test/wtp/WSTestBase.java 2010-11-24 12:06:15 UTC (rev 26876) @@ -256,11 +256,9 @@ assertEquals("Service was not sucessfully deployed, WSDL '" + wsdlURL + "' was not found", HttpURLConnection.HTTP_OK, connection.getResponseCode()); } catch (MalformedURLException e1) { - // TODO Auto-generated catch block - e1.printStackTrace(); + throw new RuntimeException(e1); } catch (IOException e) { - // TODO Auto-generated catch block - e.printStackTrace(); + throw new RuntimeException(e); } finally { if (connection != null) { connection.disconnect(); @@ -276,11 +274,9 @@ assertEquals("Project was not sucessfully undeployed, WSDL '" + wsdlURL + "' is still available", HttpURLConnection.HTTP_NOT_FOUND, connection.getResponseCode()); } catch (MalformedURLException e1) { - // TODO Auto-generated catch block - e1.printStackTrace(); + throw new RuntimeException(e1); } catch (IOException e) { - // TODO Auto-generated catch block - e.printStackTrace(); + throw new RuntimeException(e); } finally { if (connection != null) { connection.disconnect(); @@ -296,11 +292,9 @@ String rsp = readStream(is); assertContains(response, rsp); } catch (MalformedURLException e1) { - // TODO Auto-generated catch block - e1.printStackTrace(); + throw new RuntimeException(e1); } catch (IOException e) { - // TODO Auto-generated catch block - e.printStackTrace(); + throw new RuntimeException(e); } finally { if (is != null) { try {

13 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r26875 - trunk/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/helper.

by jbosstools-commits＠lists.jboss.org

Author: psrna Date: 2010-11-24 06:27:52 -0500 (Wed, 24 Nov 2010) New Revision: 26875 Modified: trunk/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/helper/DatabaseHelper.java Log: * teiid DBType Modified: trunk/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/helper/DatabaseHelper.java =================================================================== --- trunk/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/helper/DatabaseHelper.java 2010-11-24 10:43:54 UTC (rev 26874) +++ trunk/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/helper/DatabaseHelper.java 2010-11-24 11:27:52 UTC (rev 26875) @@ -184,7 +184,7 @@ * */ public enum DBType { - hsqldb18, db2_97, mssql2005, mssql2008, mysql50, mysql51, oracle10g, oracle11gR1, oracle11gR1RAC, oracle11gR2, oracle11gR2RAC, postgresql82, postgresql83, postgresql84, sybase15 + hsqldb18, db2_97, mssql2005, mssql2008, mysql50, mysql51, oracle10g, oracle11gR1, oracle11gR1RAC, oracle11gR2, oracle11gR2RAC, postgresql82, postgresql83, postgresql84, sybase15, teiid } /** @@ -229,6 +229,9 @@ case sybase15: ret = "org.eclipse.datatools.connectivity.db.sybase.ase.genericDriverTemplate_15"; break; + case teiid: + ret = "org.teiid.datatools.connectivity.driver.serverDriverTemplate"; + break; default: fail("Unknown db type"); break;

13 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r26874 - in trunk: jst/plugins/org.jboss.tools.jst.web/src/org/jboss/tools/jst/web/server and 2 other directories.

by jbosstools-commits＠lists.jboss.org

Author: rob.stryker(a)jboss.com Date: 2010-11-24 05:43:54 -0500 (Wed, 24 Nov 2010) New Revision: 26874 Modified: trunk/jst/plugins/org.jboss.tools.jst.web/src/org/jboss/tools/jst/web/context/RegisterServerContext.java trunk/jst/plugins/org.jboss.tools.jst.web/src/org/jboss/tools/jst/web/server/RegistrationHelper.java trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/DataSourceXmlDeployer.java trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/wizard/SeamProjectWizard.java Log: JBIDE-7701 - registering the ds-xml and the seam project must be chained to be properly executed in the right order. Modified: trunk/jst/plugins/org.jboss.tools.jst.web/src/org/jboss/tools/jst/web/context/RegisterServerContext.java =================================================================== --- trunk/jst/plugins/org.jboss.tools.jst.web/src/org/jboss/tools/jst/web/context/RegisterServerContext.java 2010-11-24 09:45:50 UTC (rev 26873) +++ trunk/jst/plugins/org.jboss.tools.jst.web/src/org/jboss/tools/jst/web/context/RegisterServerContext.java 2010-11-24 10:43:54 UTC (rev 26874) @@ -161,7 +161,7 @@ } @SuppressWarnings("restriction") - public String getErrorMessage() { + public String getErrorMessage() { if(runtimeName == null || runtimeName.length() == 0) return WebUIMessages.RUNTIME_IS_REQUIRED; if(runtime == null) return WebUIMessages.SPECIFIED_RUNTIME_DOESNOT_EXIST; Modified: trunk/jst/plugins/org.jboss.tools.jst.web/src/org/jboss/tools/jst/web/server/RegistrationHelper.java =================================================================== --- trunk/jst/plugins/org.jboss.tools.jst.web/src/org/jboss/tools/jst/web/server/RegistrationHelper.java 2010-11-24 09:45:50 UTC (rev 26873) +++ trunk/jst/plugins/org.jboss.tools.jst.web/src/org/jboss/tools/jst/web/server/RegistrationHelper.java 2010-11-24 10:43:54 UTC (rev 26874) @@ -204,10 +204,13 @@ } public static void runRegisterInServerJob(IProject p, IServer[] servers, String contextRoot) { - RegisterServerJob job = new RegisterServerJob(p, servers, contextRoot); - job.schedule(100); + getRegisterInServerJob(p, servers, contextRoot).schedule(100); } + public static RegisterServerJob getRegisterInServerJob(IProject p, IServer[] servers, String contextRoot) { + return new RegisterServerJob(p, servers, contextRoot); + } + // registerInJob private static class RegisterServerJob extends Job { Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/DataSourceXmlDeployer.java =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/DataSourceXmlDeployer.java 2010-11-24 09:45:50 UTC (rev 26873) +++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/DataSourceXmlDeployer.java 2010-11-24 10:43:54 UTC (rev 26874) @@ -10,8 +10,6 @@ ******************************************************************************/ package org.jboss.tools.seam.internal.core.project.facet; -import java.util.ArrayList; - import org.eclipse.core.resources.IProject; import org.eclipse.core.resources.ResourcesPlugin; import org.eclipse.core.runtime.CoreException; @@ -21,11 +19,10 @@ import org.eclipse.core.runtime.NullProgressMonitor; import org.eclipse.core.runtime.Path; import org.eclipse.core.runtime.Status; -import org.eclipse.core.runtime.jobs.Job; import org.eclipse.wst.server.core.IModule; import org.eclipse.wst.server.core.IServer; import org.eclipse.wst.server.core.IServerWorkingCopy; -import org.eclipse.wst.server.core.IServer.IOperationListener; +import org.eclipse.wst.server.core.internal.ChainedJob; import org.jboss.ide.eclipse.as.core.modules.SingleDeployableFactory; import org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior; import org.jboss.tools.seam.core.SeamCoreMessages; @@ -38,12 +35,12 @@ * @author eskimo * */ -public class DataSourceXmlDeployer extends Job { +public class DataSourceXmlDeployer extends ChainedJob { IProject project = null; IServer s = null; IPath deploy = null; public DataSourceXmlDeployer(IProject project, IServer s, IPath deploy) { - super(SeamCoreMessages.DATA_SOURCE_XML_DEPLOYER_DEPLOYING_DATASOURCE_TO_SERVER); + super(SeamCoreMessages.DATA_SOURCE_XML_DEPLOYER_DEPLOYING_DATASOURCE_TO_SERVER, s); this.project = project; // is must be user since ds.xml has the same behaviour for EAR // deployment. It should run after ear project created and imported into Modified: trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/wizard/SeamProjectWizard.java =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/wizard/SeamProjectWizard.java 2010-11-24 09:45:50 UTC (rev 26873) +++ trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/wizard/SeamProjectWizard.java 2010-11-24 10:43:54 UTC (rev 26874) @@ -28,9 +28,11 @@ import org.eclipse.core.runtime.CoreException; import org.eclipse.core.runtime.IPath; import org.eclipse.core.runtime.IProgressMonitor; +import org.eclipse.core.runtime.IStatus; import org.eclipse.core.runtime.NullProgressMonitor; import org.eclipse.core.runtime.Path; import org.eclipse.core.runtime.Preferences; +import org.eclipse.core.runtime.jobs.Job; import org.eclipse.jdt.core.IClasspathContainer; import org.eclipse.jdt.core.IClasspathEntry; import org.eclipse.jdt.core.IJavaProject; @@ -60,19 +62,20 @@ import org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper; import org.eclipse.wst.common.project.facet.core.FacetedProjectFramework; import org.eclipse.wst.common.project.facet.core.IFacetedProject; +import org.eclipse.wst.common.project.facet.core.IFacetedProject.Action; import org.eclipse.wst.common.project.facet.core.IFacetedProjectTemplate; import org.eclipse.wst.common.project.facet.core.IFacetedProjectWorkingCopy; import org.eclipse.wst.common.project.facet.core.IPreset; import org.eclipse.wst.common.project.facet.core.IProjectFacet; import org.eclipse.wst.common.project.facet.core.IProjectFacetVersion; import org.eclipse.wst.common.project.facet.core.ProjectFacetsManager; -import org.eclipse.wst.common.project.facet.core.IFacetedProject.Action; import org.eclipse.wst.common.project.facet.core.events.IFacetedProjectEvent; import org.eclipse.wst.common.project.facet.core.events.IFacetedProjectListener; import org.eclipse.wst.common.project.facet.core.runtime.IRuntime; import org.eclipse.wst.server.core.IServer; import org.eclipse.wst.server.core.IServerLifecycleListener; import org.eclipse.wst.server.core.ServerCore; +import org.eclipse.wst.server.core.internal.ChainedJob; import org.eclipse.wst.server.ui.ServerUIUtil; import org.jboss.ide.eclipse.as.core.server.internal.JBossServer; import org.jboss.tools.jst.web.server.RegistrationHelper; @@ -321,7 +324,6 @@ IFacetedProjectWorkingCopy fpwc = getFacetedProjectWorkingCopy(); IProjectFacet jpaFacet = ProjectFacetsManager.getProjectFacet("jpt.jpa"); IProjectFacetVersion pfv = fpwc.getProjectFacetVersion(jpaFacet); - if (isEAR && pfv != null){ //remove jpa facet from <project> // and add it to <project>-ejb with the same model @@ -420,15 +422,15 @@ } } - RegistrationHelper.runRegisterInServerJob(warProject, server); - IPath filePath = new Path("resources").append(warProject.getName() + "-ds.xml"); - + ChainedJob dsJob = null; if (deployAsEar) { - new DataSourceXmlDeployer(earProject, server, filePath).schedule(); + dsJob = new DataSourceXmlDeployer(earProject, server, filePath); } else { - new DataSourceXmlDeployer(warProject, server, filePath).schedule(); - } + dsJob = new DataSourceXmlDeployer(warProject, server, filePath); + } + dsJob.setNextJob(RegistrationHelper.getRegisterInServerJob(warProject, new IServer[]{server}, null)); + dsJob.schedule(); } }

13 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r26873 - in trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test: jbide and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: mareshkau Date: 2010-11-24 04:45:50 -0500 (Wed, 24 Nov 2010) New Revision: 26873 Removed: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/DocBookTemplatesTest.java Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java Log: https://jira.jboss.org/browse/JBIDE-7704, fixing junit tests fails. Removing docbook junit from jsf test, becouse its not right place.This test exist in docbook tests Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2010-11-24 09:45:05 UTC (rev 26872) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2010-11-24 09:45:50 UTC (rev 26873) @@ -16,7 +16,6 @@ import org.jboss.tools.jsf.vpe.jsf.test.jbide.ChangeMessageBundleTest_JBIDE5818; import org.jboss.tools.jsf.vpe.jsf.test.jbide.ContextMenuDoubleInsertionTest_JBIDE3888; import org.jboss.tools.jsf.vpe.jsf.test.jbide.DnD_JBIDE5042_JBIDE6229_Test; -import org.jboss.tools.jsf.vpe.jsf.test.jbide.DocBookTemplatesTest; import org.jboss.tools.jsf.vpe.jsf.test.jbide.EditFontFamilyTest_JBIDE5872; import org.jboss.tools.jsf.vpe.jsf.test.jbide.ExceptionInVPEComments_JBIDE5143; import org.jboss.tools.jsf.vpe.jsf.test.jbide.FacetProcessingTest; @@ -140,7 +139,6 @@ suite.addTestSuite(SourceDomUtilTest.class); suite.addTestSuite(XulRunnerVpeUtilsTest.class); suite.addTestSuite(JSF2ValidatorTest.class); - suite.addTestSuite(DocBookTemplatesTest.class); // suite.addTestSuite(DnD_JBIDE5042_JBIDE6229_Test.class); suite.addTestSuite(UnclosedELExpressionTest.class); suite.addTestSuite(TestContextPathResolution.class); Deleted: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/DocBookTemplatesTest.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/DocBookTemplatesTest.java 2010-11-24 09:45:05 UTC (rev 26872) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/DocBookTemplatesTest.java 2010-11-24 09:45:50 UTC (rev 26873) @@ -1,48 +0,0 @@ -/** - * - */ -package org.jboss.tools.jsf.vpe.jsf.test.jbide; - -import org.jboss.tools.jsf.vpe.jsf.test.JsfAllTests; -import org.jboss.tools.vpe.ui.test.ComponentContentTest; -import org.jboss.tools.vpe.ui.test.VpeTest; - -/** - * Junit test class for https://jira.jboss.org/browse/JBIDE-6600 - * @author mareshkau - * - */ -public class DocBookTemplatesTest extends ComponentContentTest{ - - private static String VPE_EDITOR_ID=VpeTest.EDITOR_ID; - - private static String DOC_BOOK_EDITOR_ID="org.jboss.tools.jst.jsp.jspeditor.DocBookEditor"; - - private String activeEditorID; - public DocBookTemplatesTest(String name) { - super(name); - } - - public void testCheckHtmlTitle() throws Throwable { - setActiveEditorID(VPE_EDITOR_ID); - performInvisibleTagTest("JBIDE/6600/jbide6600.html","title"); - } - - public void testCheckDocBookTitle() throws Throwable { - setActiveEditorID(DOC_BOOK_EDITOR_ID); - performContentTest("JBIDE/6600/jbide6600.xml"); - } - - @Override - protected String getTestProjectName() { - return JsfAllTests.IMPORT_PROJECT_NAME; - } - - private void setActiveEditorID(String editorID){ - this.activeEditorID = editorID; - } - - protected String getEditorID(){ - return this.activeEditorID; - } -}

13 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r26872 - trunk/bpel/docs/reference/en-US.

by jbosstools-commits＠lists.jboss.org

Author: Grid.Qian Date: 2010-11-24 04:45:05 -0500 (Wed, 24 Nov 2010) New Revision: 26872 Modified: trunk/bpel/docs/reference/en-US/master.xml Log: Update BPEL User Guide to make the build success https://jira.jboss.org/browse/TOOLSDOC-90 Modified: trunk/bpel/docs/reference/en-US/master.xml =================================================================== --- trunk/bpel/docs/reference/en-US/master.xml 2010-11-24 09:23:00 UTC (rev 26871) +++ trunk/bpel/docs/reference/en-US/master.xml 2010-11-24 09:45:05 UTC (rev 26872) @@ -1,56 +1,1106 @@ -<?xml version='1.0' encoding='UTF-8'?> -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN" -"http://www.docbook.org/xml/4.3/docbookx.dtd" - -[<!ENTITY overview SYSTEM "overview.xml"> -<!ENTITY install SYSTEM "install.xml"> -<!ENTITY detail SYSTEM "detail.xml"> -<!ENTITY deploy SYSTEM "deploy.xml"> -<!ENTITY reference SYSTEM "reference.xml"> -<!ENTITY summary SYSTEM "summary.xml"> -<!ENTITY tasks SYSTEM "tasks.xml"> -]> -<book> - <bookinfo> - <title>JBoss BPEL User Guide</title> - <corpauthor> - <inlinemediaobject> - <imageobject role="fo"> - <imagedata fileref="images/jbosstools_logo.png" format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata/> - </imageobject> - </inlinemediaobject> - </corpauthor> - <author> - <firstname>Denny</firstname> - <surname>Xu</surname> - <email>dxu(a)redhat.com</email> - </author> - <author> - <firstname>Grid</firstname> - <surname>Qian</surname> - <email>fqian(a)redhat.com</email> - </author> - <author> - <firstname>Bob</firstname> - <surname>Brodt</surname> - <email>bbrodt(a)redhat.com</email> - </author> - <copyright> - <year>2009</year> - <year>2010</year> - <holder>JBoss by Red Hat</holder> - </copyright> - <releaseinfo> Version: 1.0.0.trunk </releaseinfo> - <abstract> - <title/> - <para> - <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/bpel_ref_guide/pdf/B...">PDF version</ulink> - </para> - </abstract> - </bookinfo> - <toc/> -&overview;&install;&tasks;&reference;&summary;</book> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN" +"http://www.docbook.org/xml/4.3/docbookx.dtd"> +<book> + <bookinfo> + <title>JBoss BPEL User 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>Denny</firstname><surname>Xu</surname><email>dxu(a)redhat.com</email></author> + <author><firstname>Grid</firstname><surname>Qian</surname><email>fqian(a)redhat.com</email></author> + <author><firstname>Bob</firstname><surname>Brodt</surname><email>bbrodt(a)redhat.com</email></author> + <copyright> + <year>2009</year> + <year>2010</year> + <holder>JBoss by Red Hat</holder> + </copyright> + <releaseinfo> + Version: 1.0.0.trunk + </releaseinfo> + <abstract> + <title></title> + <para><ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/bpel_ref_guide/pdf/B...">PDF version</ulink></para> + </abstract> + </bookinfo> + <toc></toc> + +<chapter id="overview" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/bpel/docs/reference/en-US/modules/overview.xml"> + <title>JBoss BPEL project Overview</title> + + <para>JBoss BPEL project is a WS-BPEL 2.0 project that gives a way to create, edit, validate and deploy BPEL files to JBoss BPEL runtime. It is based on Eclipse + <ulink url="http://www.eclipse.org/bpel/">BPEL + project </ulink>. </para> + + <para>It improves the Eclipse BPEL project in the following way: </para> + <itemizedlist> + <listitem><para> Implements close integration with JBoss BPEL runtime. Adds a new project type for the deployment to JBoss BPEL runtime.</para></listitem> + <listitem><para> Supports two ways of deployment: one way is to deploy a bpel project directly to JBoss BPEL runtime. The other way is to deploy bpel files in JBoss ESB project to JBoss BPEL runtime. </para></listitem> + <listitem><para> Improves the BPEL validator and increases Eclipse BPEL editor's quality. </para></listitem> + </itemizedlist> + + <para> + <ulink url="http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html">WS-BPEL 2.0</ulink> + stands for Web Service Business Process Execution Language. Like EAI, BPEL is an XML-based language, + but BPEL is more specific and targeted. A programmer uses BPEL to join sometimes + disparate functions into an integrated process, resulting in a seamless use of the Internet to + conduct business transactions ranging from simple money exchanges to complex calculations and + asset reallocation. + </para> + + <section> + <title>Key Features of JBoss BPEL project</title> + <para>Let's start with looking through the table of the main features of JBoss BPEL editor project: </para> + + <table> + <title>Key Functionality for JBoss BPEL editor project</title> + <tgroup cols="2"> + <colspec align="left" colnum="1" colwidth="2*"></colspec> + <colspec colnum="2" colwidth="4*"></colspec> + <thead> + <row> + <entry>Feature</entry> + <entry>Benefit</entry> + </row> + </thead> + <tbody> + <row> + <entry><para>WS-BPEL 2.0 support</para></entry> + <entry><para>JBoss BPEL project supports the newest WS-BPEL 2.0 specifications. </para></entry> + </row> + <row> + <entry><para>Close integration with JBoss BPEL runtime</para></entry> + <entry><para>There are two ways to deploy BPEL files to JBoss BPEL runtime. + The user can deploy a BPEL project as a whole and can deploy BPEL files in + JBoss ESB project to JBoss BPEL runtime. </para></entry> + </row> + <row> + <entry><para>BPEL file editor</para></entry> + <entry><para>The user can use the editor separately to edit a BPEL file. </para></entry> + </row> + <row> + <entry><para>BPEL file validator</para></entry> + <entry><para>The validator can give the error messages about BPEL files to the user. </para></entry> + </row> + </tbody> + </tgroup> + </table> + </section> +</chapter> + +<chapter id="install" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/bpel/docs/reference/en-US/modules/install.xml"> + <title>Installation JBoss BPEL Tools</title> + <section id="installeclipse"> + <title>Installation JBoss BPEL editor</title> + <para>At first, you need Eclipse 3.6. You can get it from <ulink url="http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo...">Eclipse Web Site</ulink>. + </para> + <para>The JBoss BPEL editor is included into JBoss Tools. + You have some methods to install JBoss Tools. + See <ulink url="http://www.jboss.org/tools/download/installation.html">Installing JBoss Tools</ulink> for more information.</para> + <para>If you want to install only the JBoss BPEL editor, you can install it from <ulink url="http://jboss.org/tools/download/dev.html">JBoss Tools</ulink> page separately. + Please, note, that only JBoss Tools 3.1 or higher version includes JBoss BPEL editor. + </para> + </section> + <section id="installriftsaw"> + <title>Prerequisites</title> + <para>For installation and configuring BPEL engine into a JBossAS environment you will need the following: </para> + <itemizedlist> + <listitem><para>JBossAS (version 5.1.0.GA or higher), available from <ulink url="http://www.jboss.org/jbossas">http://www.jboss.org/jbossas</ulink>.</para></listitem> + <listitem><para>RiftSaw (version 2.1 or higher), available from <ulink url="http://www.jboss.org/riftsaw">http://www.jboss.org/riftsaw</ulink>.</para></listitem> + <listitem><para>Ant, available from <ulink url="http://ant.apache.org">here</ulink>.</para></listitem> + </itemizedlist> + </section> + <section id="installRuntime"> + <title>Installation JBoss BPEL Runtime</title> + <itemizedlist> + <listitem> + <para>Unpack the JBossAS installation archive into the required location.</para> + </listitem> + <listitem> + <para>Unpack the RiftSaw distribution into the location alongside the JBossAS installation:</para> + <itemizedlist> + <listitem> + <para>Edit the <property moreinfo="none">install/deployment.properties</property> file to update the JBossAS location settings.</para> + </listitem> + <listitem> + <para>From the <property moreinfo="none">install</property> folder, + run: <property moreinfo="none">ant deploy -Ddatabase=hsql</property> + to deploy RiftSaw to JBossAS. + </para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para>Then in the + <property moreinfo="none">${RiftSaw}/install</property> folder run the command: + <property moreinfo="none">ant deploy -Ddatabase=hsql -Dws.stack=native -Dws.version=3.2.2.GA</property> + It will help you to download the web service stack, and then upgrade it for JBoss AS. Anyway, you can do it step by step by following the guide from <ulink url="http://www.jboss.org/riftsaw/documentation">JBoss RiftSaw documents</ulink> or the README file in <property moreinfo="none">${RiftSaw}/install</property> + </para> + </listitem> + </itemizedlist> + + </section> +</chapter> + +<chapter id="tasks" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/bpel/docs/reference/en-US/modules/tasks.xml"> + <title>Tasks</title> + <section id="detail"> + <title>Creating and editing a BPEL project</title> + <para>In the chapter we describe the necessary steps to create a new BPEL project and edit the BPEL files. + You can get the source of the example from <property moreinfo="none"> + riftsaw/samples/quickstart/hello_world</property>. + Here and further in the guide we will create + a simple echo example, used to respond to a sent message with a + modified version of the request message being returned in a response. + First of all, you should create a BPEL project. + + </para> + <section id="createproject"> + <title>Creating a BPEL project</title> + <para>Create the project by selecting + <emphasis><property moreinfo="none">New > Project... > BPEL 2.0 > BPEL Project</property></emphasis> from the menu bar. + Then click the <property moreinfo="none">Next</property> button. + </para> + <figure float="0"> + <title>New BPEL Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>On this page of the <property moreinfo="none">New BPEL Project Wizard</property> enter a project name in the <property moreinfo="none">Project Name</property> + field,e.g enter <property moreinfo="none">HelloWorld</property>.</para> + + <figure float="0"> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>Click the <property moreinfo="none">Finish</property> button. + So you have created the BPEL project named <property moreinfo="none">HelloWorld</property>. + Its structure is like this: </para> + <figure float="0"> + <title>The BPEL Project structure</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="createprocess"> + <title>Creating a BPEL process</title> + <para>Now you should create a BPEL process. You can create it by selecting + <emphasis><property moreinfo="none">New > Others... > BPEL 2.0 > New BPEL Process File</property></emphasis>. + </para> + <figure float="0"> + <title>New BPEL Process File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>Click the <property moreinfo="none">Next</property> button. Enter the following information:</para> + <table> + + <title>Fields and values</title> + <tgroup cols="2"> + <colspec align="left" colnum="1" colwidth="2*"></colspec> + <colspec colnum="2" colwidth="4*"></colspec> + <thead> + <row> + <entry>Field</entry> + <entry>Value</entry> + + </row> + </thead> + <tbody> + <row> + <entry><para>BPEL Process Name</para></entry> + <entry><para>enter a process name. For example, <property moreinfo="none">HelloWorld</property>.</para></entry> + </row> + <row> + <entry><para>Namespace</para></entry> + <entry><para>enter or select a namespace for the BPEL process.</para></entry> + </row> + <row> + <entry><para>Template</para></entry> + <entry><para>Select the necessary template for the BPEL process. + When you select the template, you will see the information + about the template below on the page.In our case you should + select <property moreinfo="none">Synchronous BPEL Process</property>.</para></entry> + </row> + + </tbody> + </tgroup> + </table> + + <figure float="0"> + <title>New BPEL Process File Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Click the <property moreinfo="none">Next</property> button. On the second page, you can custom your wsdl service details. Enter the following information:</para> + <table> + + <title>Fields and values</title> + <tgroup cols="2"> + <colspec align="left" colnum="1" colwidth="2*"></colspec> + <colspec colnum="2" colwidth="4*"></colspec> + <thead> + <row> + <entry>Field</entry> + <entry>Value</entry> + + </row> + </thead> + <tbody> + <row> + <entry><para>Service Name</para></entry> + <entry><para>a wsdl service name for the BPEL process. The default is, <property moreinfo="none">HelloWorld</property>.</para></entry> + </row> + <row> + <entry><para>Port Name</para></entry> + <entry><para>a wsdl port name for the BPEL process. The default is, <property moreinfo="none">HelloWorldPort</property>.</para></entry> + </row> + <row> + <entry><para>Service Address</para></entry> + <entry><para>an address of the wsdl service for the BPEL process. The default is, <property moreinfo="none">http://localhost:8080/HelloWorld</property>.</para></entry> + </row> + <row> + <entry><para>Binding Protocol</para></entry> + <entry><para>the binding protocal that you use in the wsdl. You can choose SOAP or HTTP. The default is, <property moreinfo="none">SOAP</property>.</para></entry> + </row> + </tbody> + </tgroup> + </table> + + <figure float="0"> + <title>Create WSDL file for the BPEL Process wizardpage</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_2a.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Click the <property moreinfo="none">Next</property> button. On the third page, you can choose a folder for the process file from the projects in your workspace. If not choose, The default folder <property moreinfo="none">HelloWorld/bpelContent</property> is selected. + Click <property moreinfo="none">Finish</property>. + </para> + <note> + <para>All of your files that are used in your BPEL project must be under the <property moreinfo="none">bpelContent</property> folder of a BPEL project. Only in this case + these files can be deployed to JBoss server. + </para> + </note> + + <para>Up to now, you have got a simple BPEL process as on the screen below.</para> + <figure float="0"> + <title>A simple BPEL Process File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The next step, you can do is to edit the BPEL process file and then deploy it to JBoss server. </para> + </section> + <section id="editprocess"> + <title>Editing a BPEL process file</title> + <para>If the <emphasis><property moreinfo="none">Properties view</property></emphasis> and <emphasis><property moreinfo="none">Palette view</property></emphasis> are not opened, you can open the views by right-clicking the BPEL editor and selecting + <property moreinfo="none">Show in Properties</property>, <property moreinfo="none">Show Palette in Palette view</property>. Then you should have the view like this: + </para> + <figure float="0"> + <title>The BPEL editor view</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>In the <emphasis><property moreinfo="none">Palette view</property></emphasis>, you can drag a BPEL element to the BPEL editor and drop it in the place you want.</para> + <para>In the <emphasis><property moreinfo="none">Properties view</property></emphasis>, you can get the information about every element of the BPEL process. + In the BPEL editor select any element you want,and then + the element's properties will be shown in the Properties view.The table below describes the tabs of the Properties view: + </para> + <table> + + <title>Tabs of the Property view</title> + <tgroup cols="2"> + <colspec align="left" colnum="1" colwidth="2*"></colspec> + <colspec colnum="2" colwidth="4*"></colspec> + <thead> + <row> + <entry>Tab</entry> + <entry>Description</entry> + + </row> + </thead> + <tbody> + <row> + <entry><para>Description</para></entry> + <entry><para>Shows the descriptive information about the element,e.g. <property moreinfo="none">Name</property> of the element.</para></entry> + </row> + <row> + <entry><para>Details</para></entry> + <entry><para>Shows the detailed and important information about the element. + It is the most important section of an element. + Most of the properties of an element are set in this section.</para></entry> + </row> + <row> + <entry><para>Join Behavior</para></entry> + <entry><para>Shows the <property moreinfo="none">Join Failure</property> property of the element.</para></entry> + </row> + <row> + <entry><para>Documentation</para></entry> + <entry><para>Shows the <property moreinfo="none">documentation</property> sub-element of an element.</para></entry> + </row> + <row> + <entry><para>Other</para></entry> + <entry><para>Every BPEL element has its own sections: Correlation section, Message Exchange section, and so on. We will + introduce them while using them.</para></entry> + </row> + </tbody> + </tgroup> + </table> + <para>In order to see how a simple BPEL process works in action, you should do some steps as below: </para> + <itemizedlist> + <listitem> + <para>Modify two variables of the process:</para> + <itemizedlist> + <listitem><para>Click on the details tab of the input variable, + select <property moreinfo="none">Browse...</property>. + Then choose <property moreinfo="none">string</property> primitive from the list.</para> + <figure float="0"> + <title>Edit variable in <property moreinfo="none">process</property> file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpel_task_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Select <property moreinfo="none">xsd</property> as a namespace in the popup menu.</para> + </listitem> + </itemizedlist> + + </listitem> + <listitem> + <para>Add an <property moreinfo="none">Assign</property> element between the <property moreinfo="none">receiveInput</property> element and <property moreinfo="none">replyOutput</property> element.</para> + </listitem> + <listitem> + <para>Click the <property moreinfo="none">Assign</property> element in the BPEL editor in order to get the properties information of it in the Properties view. + </para> + </listitem> + <listitem> + <para>Set its name in the <property moreinfo="none">Description</property> tab as <property moreinfo="none">assignHelloMesg</property>.</para> + <para>In the <property moreinfo="none">Details</property> section of Properties view, + you should click the <property moreinfo="none">New</property> button to add a <property moreinfo="none">copy</property> sub-element to the element. + Assign "Variable to Variable"(input:string to output). At this time, an "<property moreinfo="none">initializer</property>" popup dialog appears. Click on the <property moreinfo="none">Yes</property> button in the dialog. + </para> + <figure float="0"> + <title>Add <property moreinfo="none">Assign</property> to the process</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpel_task_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>Then you should click <property moreinfo="none">New</property> once more and select Expression to Variable (assign <code>concat($input,' World')</code>) to <property moreinfo="none">result:string</property>.</para> + <figure float="0"> + <title>Add <property moreinfo="none">Expression assign</property> to the process</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpel_task_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + </section> + + <section id="wsdl"> + <title>Adding Service to WSDL file</title> + <para></para> + <para>The HelloWorldArtifacts.wsdl has been added a service when you create a BPEL process file. You have a default service in this WSDL file. But if you want to add a service by yourself, you can follow the steps as below: </para> + <itemizedlist> + <listitem> + <para>Open the file "<property moreinfo="none">HelloWorldArtifacts.wsdl</property>" in the "<property moreinfo="none">HelloWorld</property>" project by double-clicking the file. Right-click the WSDL editor and select + <property moreinfo="none">Add Service</property>. A new service should appear in the editor. Name it <property moreinfo="none">HelloWorldProcessService</property>. It has the Port + named <property moreinfo="none">NewPort</property>. Select it, right-click on it and rename it to <property moreinfo="none">HelloWorldProcessPort</property> in the Properties + view. + </para> + <figure float="0"> + <title>Add <property moreinfo="none">Service</property> to the WSDL file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Right-click somewhere in the whitespace of the WSDL editor and select + <property moreinfo="none">Add Binding</property>. A new Binding component will appear in the editor. Name it <property moreinfo="none">HelloWorldSOAPBinding</property>. Select it, in the + General tab of the Properties view and select <property moreinfo="none">HelloWorld</property> as a port type in the <property moreinfo="none">PortType</property>. Then click on the + <property moreinfo="none">Generate Binding Content...</property> button to open the <property moreinfo="none">Binding Wizard</property>. In the wizard, select <property moreinfo="none">SOAP </property> + as the <property moreinfo="none">Protocol</property>. Finally, click the <property moreinfo="none">Finish</property> button to close the wizard. + </para> + <figure float="0"> + <title>Add a <property moreinfo="none">Binding</property> to the WSDL file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Click the <property moreinfo="none">HelloWorldProcessPort</property> property in the General section of the Properties view, select <property moreinfo="none">HelloWorldSOAPBinding</property> in + the <property moreinfo="none">Binding</property> combobox. In the <property moreinfo="none">Address</property> field input <ulink url="http://localhost:8080/bpel/processes/HelloWorld?wsdl">http://localhost:8080/bpel/processes/HelloWorld?wsdl</ulink>. + </para> + <figure float="0"> + <title>Add the <property moreinfo="none">HelloWorldSOAPBinding</property> to the <property moreinfo="none">HelloWorldProcessPort</property></title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem><para>You should also change some service part configurations. + To do this,click part element in the WSDL editor, + then put the following data in the Properties view. + </para> + <figure float="0"> + <title>Configuration of service part</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + + <para>Now you have finished creating a simple BPEL process. As a next step, you can deploy the BPEL project to JBoss BPEL Runtime.</para> + + </section> + + </section> + <section id="deploy"> + <title>Deploy a JBoss BPEL project to JBoss BPEL Runtime</title> + <section id="createdeploy"> + <title>Creating a deploy.xml file</title> + <para>If you want to deploy a BPEL project to JBoss BPEL Runtime, you should create a deploy.xml file. + JBoss tools can help you to create it: + </para> + <itemizedlist> + <listitem> + <para>Create the deploy.xml by selecting + <emphasis><property moreinfo="none">New > Other... > BPEL 2.0 > Apache ODE Deployment Descriptor</property></emphasis>. Click the <property moreinfo="none">Next</property> button. + </para> + <figure float="0"> + <title>New BPEL Deploy file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>On the next wizard page you should enter the following information:</para> + <para><emphasis><property moreinfo="none">BPEL Project</property></emphasis>: Click the <property moreinfo="none">Browse...</property> button to select the BPEL project in your workspace which you want to deploy to the runtime. + Please note, that you should select the <property moreinfo="none">bpelContent</property> folder in your new BPEL project as a value of <property moreinfo="none">BPEL Project</property> field because the deploy.xml should be created in this place. + </para> + <para><emphasis><property moreinfo="none">File name</property></emphasis>: The default value is deploy.xml. Please, don't change it.</para> + <para>Click on <property moreinfo="none">Finish</property> button to close the wizard and a new deploy.xml file will be created.</para> + <figure float="0"> + <title>New BPEL Deploy file Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Double-click the deploy.xml file to open it in ODE Descriptor Deployment Editor. + In the <property moreinfo="none">Inbound Interfaces</property> section, click the + <property moreinfo="none">Associated Port</property> column and select <property moreinfo="none">HelloWorldProcessPort</property> + in the dropdown box.The <property moreinfo="none">Related Service</property> and <property moreinfo="none">Binding Used</property> + columns should be automatically filled in. Save the <emphasis><property moreinfo="none">deploy.xml</property></emphasis>. + </para> + <figure float="0"> + <title>deploy.xml file editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + </section> + <section id="createruntime"> + <title>Creating JBoss BPEL Server</title> + <para>Suppose you have installed the <property moreinfo="none">JBoss BPEL Runtime-RiftSaw</property> as it was described <link linkend="installRuntime">before</link>, now you can create a server for JBoss BPEL runtime.</para> + <itemizedlist> + <listitem> + <para>Open the <property moreinfo="none">Servers</property> view by selecting + <emphasis><property moreinfo="none">Windows > Show View > Other... > Server > Servers</property></emphasis>. + </para> + </listitem> + <listitem> + <para>Right-click the Servers view and select + <emphasis><property moreinfo="none">New > Server</property></emphasis> to open the New Server Wizard: + </para> + <figure float="0"> + <title>New Server Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Select <property moreinfo="none">JBoss AS 5.1 </property>as a server type. </para> + <note> + <para>Please note, that only JBoss As 5.1 or higher version supports BPEL.</para> + </note> + </listitem> + <listitem> + + <para>Click the <property moreinfo="none">Next</property> button. On the next page, you should input your <emphasis><property moreinfo="none">JBoss As</property></emphasis> location. Then click the <property moreinfo="none">Next</property> button and + you will get the page like this: + </para> + <figure float="0"> + <title>Add resource to the server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Select <property moreinfo="none">HelloWorld</property>, then click the <property moreinfo="none">Add </property> button to add the project to the server. + Then click on the <property moreinfo="none">Finish</property> button. + </para> + <para>Start the server by right-clicking on the server and selecting the <property moreinfo="none">Start</property> item. </para> + + <figure float="0"> + <title>The started server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_6.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>If some aspects of server creation is not clear, please, read <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/as/html_single/index...">JBoss Server Manager Reference Guide</ulink> for more details.</para> + </listitem> + <listitem> + <para>You can enter the link <ulink url="http://localhost:8080/bpel-console/app.html">http://localhost:8080/bpel-console/app.html</ulink> to the browser to get the deployed processes.</para> + <figure float="0"> + <title>The BPEL console</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_7.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <para>If there's anything we didn't cover or you can't figure out, please feel free to visit our <ulink + url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201" + >JBoss Tools Users Forum</ulink> to ask questions. + There we are also waiting for your suggestions and comments.</para> </section> + </section> +</chapter> + +  + +<chapter id="reference" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/bpel/docs/reference/en-US/modules/reference.xml"> + <?dbhtml filename="reference.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>BPEL</keyword> + <keyword>JBT</keyword> + </keywordset> + </chapterinfo> + <title>Reference</title> + <para>This chapter includes detailed reference information about all BPEL tools wizards and editors.</para> + <section> + <title>Wizards</title> + <section> + <title>New BPEL project Wizard</title> + <para>This wizard helps to create new BPEL project.It is available with clicking + <property moreinfo="none">File->New->Other->BPEL project</property> in the menu bar.</para> + <figure float="0"> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>It consists of only one page:</para> + <itemizedlist> + <listitem><para>On the page you can adjust the name of the project and the directory where it will be created.</para> + <para>If "<property moreinfo="none">Use default</property>" option is checked the output directory will be the workspace, + othervise the user should specify it by himself using <property moreinfo="none">Browse</property> button.</para> + <figure float="0"> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + </section> + <section> + <title>Apache ODE Deployment Descriptor Wizard</title> + <para>Using this wizard user can create ODE deployment descriptor (deploy.xml) and place it in the temporary directory.It is available with clicking + <property moreinfo="none">File->New->Other->Apache ODE Deployment Descriptor Wizard</property> in the menu bar.</para> + <figure float="0"> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>On the page you can adjust the name of the deployment descriptor and + the directory where it will be created.Note,that you should use <property moreinfo="none"> + /PROJECT_NAME/bpelContent</property> directory as an output one.</para> + + </section> + <section> + <title>New BPEL Process file Wizard</title> + <para>Using <property moreinfo="none">New BPEL Process file Wizard</property> + user can create BPEL process file and WSDL file if it is necessary. + The wizard includes several pages:</para> + <itemizedlist> + <listitem><para>The first page has the following options to set:</para> + <table> + <title>New BPEL Process file Wizard. First Page Options.</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>Name</entry> + <entry>Enter the process name.</entry> + <entry>no default value</entry> + </row> + + + <row> + <entry>Namespace</entry> + <entry>Enter the namespace url here</entry> + <entry>no default value</entry> + </row> + + <row> + <entry>Template</entry> + <entry>Select one of the provided templates: + <itemizedlist> + <listitem><para><emphasis>Asynchronous BPEL Process</emphasis> - + generates the basis of orchestration logic: receive and reply activities + are included into the process;client WSDL is generated, + service is defined in the <property moreinfo="none">parentlink</property> of the process. + The caller is notified asynchronously when the process completes. + </para></listitem> + <listitem><para><emphasis>Empty BPEL Process</emphasis> - list of services participating in this BPEL process together + with the one of messages used within the process is empty.There are no any orchestration logic.</para></listitem> + <listitem><para><emphasis>Synchronous BPEL Process</emphasis> - + similar to Asynchronous BPEL Process template except the fact that here + the caller is notified synchronously when the process completes.</para></listitem> + </itemizedlist></entry> + <entry>Asynchronous BPEL Process</entry> + </row> + <row> + <entry>Abstract Process</entry> + <entry>Specifies the created process as an abstract one -partially + specified processes that are not intended to be executed.</entry> + <entry>unchecked</entry> + </row> + </tbody> + </tgroup> + </table> + <figure float="0"> + <title>New BPEL Process file Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + </listitem> + + <listitem><para>The second page has the following options to set:</para> + <table> + <title>New BPEL Process file Wizard. Second Page Options.</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>Service Name</entry> + <entry>Enter a wsdl service name for the BPEL process.</entry> + <entry>The process name</entry> + </row> + + <row> + <entry>Port Name</entry> + <entry>Enter a wsdl port name for the BPEL process.</entry> + <entry>The process name + 'Port' </entry> + </row> + + <row> + <entry>Service Address</entry> + <entry>Enter an address of the wsdl service for the BPEL process.</entry> + <entry>http://localhost:8080/ + process name </entry> + </row> + + <row> + <entry>Binding Protocol</entry> + <entry>Choose the binding protocal that you use in the wsdl: SOAP or HTTP </entry> + <entry>SOAP </entry> + </row> + </tbody> + </tgroup> + </table> + <figure float="0"> + <title>New BPEL Process file Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_3a.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + </listitem> + + + + <listitem><para>On the third page the user should select the BPEL project + and folder where the process file will be created:</para> + <figure float="0"> + <title>New BPEL Process file Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <note> + <para>Process files that are used in the BPEL project must be under the <property moreinfo="none">bpelContent</property> folder. Only in this case + these files can be deployed to JBoss server. + </para> + </note> + </section> + </section> + <section> + <title>Editors</title> + <section> + <title>Business Process Editor</title> + <para>Business Process Editor is intended to facilitate the process of changing and + adding new logic to BPEL process file.You can open <emphasis>.bpel</emphasis> + in this editor by right click the file in the project explorer and selecting + <property moreinfo="none">Open With...->Business Process Editor</property> + </para> + <figure float="0"> + <title>Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The editor consists of two tabs:<property moreinfo="none">Design</property> tab and <property moreinfo="none">Source</property> tab.</para> + <section> + <title>Design tab</title> + <para>Design tab is the main part of Business Process Editor.It consists of 3 parts:</para> + <itemizedlist> + <listitem><para>Visual Pane:</para> + <figure float="0"> + <title>Visual Pane of Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_6.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The Visual Pane graphically displays the order in which the activities are executed.</para> + </listitem> + <listitem><para>Palette:</para> + <figure float="0"> + <title>Palette of Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_7.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The <property moreinfo="none">Palette</property> represents different elements of the BPEL activities + organized into functional categories. + Using it the user can easily add new elements to the sequence activity. + To do this,he should just click the required element and then drug + and drop it to the place on the Visual Pane where it should be added.</para> + </listitem> + <listitem><para>Behavior Components View:</para> + <figure float="0"> + <title>Behavior Components View of Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_8.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>Execution behavior components are grouped into the <property moreinfo="none"> + Behavior Components View</property>. + The view is also fully syncronized with Properties view where you can customize all + the properties of the component.</para> + <figure float="0"> + <title>Process Structure View of Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_9.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>To add an element to some component group click plus(<inlinemediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_10.png"></imagedata> + </imageobject> + </inlinemediaobject>) icon, + for its deleting you should click the element and + use its <property moreinfo="none">Delete</property> option in the popup menu.</para> + </listitem> + + </itemizedlist> + + + </section> + <section> + <title>Source tab</title> + <para>Source tab can be used for editing BPEL process file directly. + The validation of file structure is also available. + </para> + <figure float="0"> + <title>Validation error in Source tab</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_11.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>If the user wants to disable/unable validation he can do it by following + <property moreinfo="none">Window->Preferences->Validation</property>.</para> + <figure float="0"> + <title>Validation configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_12.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </section> + </section> + <section> + <title>ODE Deployment Descriptor Editor</title> + <para>To deploy your process in Ode you need to create a + simple deployment descriptor with basic information and + <property moreinfo="none">ODE Deployment Descriptor Editor</property> facilitates the process of descriptor configuration. + You can see how the descriptor file,opened in the editor looks like on the picture below: + </para> + <figure float="0"> + <title>ODE Deployment Descriptor Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_13.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The table below describes the configuration options of the + ODE Deployment Descriptor Editor:</para> + <table> + <title>ODE Deployment Descriptor Editor.Options.</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>Section</entry> + <entry>Options</entry> + <entry>Description</entry> + </row> + </thead> + <tbody> + <row> + <entry morerows="1" valign="middle"><para> + General</para></entry> + + <entry>This process is</entry> + <entry>Select one of the provided options: + <itemizedlist> + <listitem> + <para><emphasis>activated</emphasis> + </para> + </listitem> + <listitem> + <para><emphasis>deactivated</emphasis></para> + </listitem> + <listitem> + <para><emphasis>retired</emphasis> + </para> + </listitem> + </itemizedlist></entry> + + </row> + <row><entry>Run this process in memory</entry> + <entry>for performance purposes, + you can define the process as being + executed only in-memory.</entry> + </row> + + <row> + <entry>Inbound Interfaces(Services)</entry> + <entry>Associated Port</entry> + <entry>Click Associated Port and the dropdown list with all available port names will appear. + Select the one you need ,other fields will be filled automatically. + This action configure the services + provided by the process and + bind each service to an endpoint + </entry> + + </row> + + <row> + <entry>Outbound Interfaces(Invokes)</entry> + <entry>Associated Port</entry> + <entry>Click Associated Port and the dropdown list with all available port names will appear. + Select the one you need, other fields will be filled automatically. + This action configure the services + invoked by the process</entry> + </row> + <row> + <entry>Process-level Monitoring Events</entry> + <entry> <itemizedlist> + <listitem><para> + <emphasis>None</emphasis> + </para></listitem> + <listitem> + <para> + <emphasis>All</emphasis> + </para> + </listitem> + <listitem> + <para> + <emphasis>Selected</emphasis>: + </para> + <itemizedlist> + <listitem><para>Instance life cycle</para></listitem> + <listitem><para>Activity life cycle</para></listitem> + <listitem><para>Data handling</para></listitem> + <listitem><para>Scope handling</para></listitem> + <listitem><para>Correlation</para></listitem> + + </itemizedlist> + + </listitem> + </itemizedlist> + </entry> + <entry>Using ODE's deployment descriptor, it's also + possible to make events generation to + filtrate which ones get created. + All option just duplicates the default behaviour, + when nothing is specified in the deployment.</entry> + </row> + <row> + <entry>Scope-level Monitoring Events</entry> + <entry>Scope</entry> + <entry>This section makes it possible to + define filtering for each scope of your process. + </entry> + </row> + </tbody> + </tgroup> + </table> + </section> + + </section> + + +</chapter> + + + +<chapter xml:base="file:///home/vchukhutsina/repos/ochik_jboss/bpel/docs/reference/en-US/modules/summary.xml"> + <?dbhtml filename="summary.html"?> + <title>Summary</title> + <para>In conclusion, with this document you know all the capabilities of BPEL Tools + and could easily start with them. + The chapters above walked you through the steps on how to create and configure BPEL process and + deployment descriptor files. + 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> + + </section> +</chapter> + +</book>

13 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r26871 - in trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui: editor and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: rob.stryker(a)jboss.com Date: 2010-11-24 04:23:00 -0500 (Wed, 24 Nov 2010) New Revision: 26871 Modified: trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/Messages.java trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/Messages.properties trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/editor/DeploymentModuleOptionCompositeAssistant.java trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/editor/ModuleDeploymentPage.java Log: JBIDE-7287 trunk Modified: trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/Messages.java =================================================================== --- trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/Messages.java 2010-11-24 09:16:21 UTC (rev 26870) +++ trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/Messages.java 2010-11-24 09:23:00 UTC (rev 26871) @@ -202,6 +202,7 @@ public static String EditorCPD_RestoreDefault; public static String EditorNoRuntimeSelected; public static String EditorLocalDeployment; + public static String EditorRefreshViewer; public static String ExploreUtils_Action_Text; Modified: trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/Messages.properties =================================================================== --- trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/Messages.properties 2010-11-24 09:16:21 UTC (rev 26870) +++ trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/Messages.properties 2010-11-24 09:23:00 UTC (rev 26871) @@ -2,7 +2,7 @@ serverName=Server Name copy=Copy... delete=Delete... -directory=Directory: +directory=Directory\: wf_BaseNameVersionReplacement=_VERSION_ wf_NameLabel=Name wf_HomeDirLabel=Home Directory @@ -28,7 +28,7 @@ JBossRuntimeWizardFragment_DeleteConfigConfirmation=Are you sure you want to delete this folder? This cannot be undone. JBossRuntimeWizardFragment_DeleteConfigTitle=Delete Configuration? JBossRuntimeWizardFragment_MustSelectValidConfig=User must select a valid configuration -JBossRuntimeWizardFragment_OutputFolderExists=The output folder already exists: +JBossRuntimeWizardFragment_OutputFolderExists=The output folder already exists\: swf_Title=Create a new JBoss Server swf_RuntimeInformation=Runtime Information swf_Explanation=A JBoss Server manages starting and stopping instances of JBoss. \nIt manages command line arguments and keeps track of which modules have been deployed. @@ -42,7 +42,7 @@ swf_NameInUse=Server name already in use swf_DeployEditorHeading=Default Settings swf_DeploymentDescriptionLabel=Set the default publish settings for your deployments.\nSettings can be overridden per-module in the table below. -swf_DeploymentDescription=This section sets the default deploy folders for your deployments. To ensure safe and fast file copies, the temporary deploy folder should be on the same file-system as the main deploy folder.\n\nCustomizations can be made in the table below on a per-module basis. Blank (uncustomized) modules will continue to use the default values. Customized paths may be absolute or relative to the server's root directory (eg: server/default/deploy/custom/folder).\n\nChanges should *not* be made to this page while the server is running. +swf_DeploymentDescription=This section sets the default deploy folders for your deployments. To ensure safe and fast file copies, the temporary deploy folder should be on the same file-system as the main deploy folder.\n\nCustomizations can be made in the table below on a per-module basis. Blank (uncustomized) modules will continue to use the default values. Customized paths may be absolute or relative to the server's root directory (eg\: server/default/deploy/custom/folder).\n\nChanges should *not* be made to this page while the server is running. swf_DeployDirectory=Deploy Directory swf_TempDeployDirectory=Temporary Deploy Directory swf_CloneConfiguration=Copy this configuration into workspace metadata @@ -117,11 +117,11 @@ XPathActionProvider_RemoveCategoryQuestion=Remove Category? XPathAttribute=Attribute Name\: XPathDialogs_BlankCategoryError=Category must not be blank -XPathDialogs_CategoryLabel=Category: +XPathDialogs_CategoryLabel=Category\: XPathDialogs_NoElementsMatched=No XML elements matched your search. XPathDialogs_PreviewButton=Preview XPathDialogs_SelectServer=Please Select a Server -XPathDialogs_ServerLabel=Server: +XPathDialogs_ServerLabel=Server\: XPathDialogs_XPathDescriptionLabel=An XPath is a way to find a specific XML element inside an xml file. This dialog will help you create one. XPathTreeContentProvider_JobName=Loading XPaths XPathTreeLabelProvider_LoadingLabel=Loading... @@ -177,6 +177,7 @@ EditorCPD_RestoreDefault=Restore Default EditorNoRuntimeSelected=No Runtime Selected. Please select a runtime and refresh your deployment options. EditorLocalDeployment=Local Deployment +EditorRefreshViewer=Refresh Table ExploreUtils_Action_Text=Explore ExploreUtils_Description=Explore deploy directory Modified: trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/editor/DeploymentModuleOptionCompositeAssistant.java =================================================================== --- trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/editor/DeploymentModuleOptionCompositeAssistant.java 2010-11-24 09:16:21 UTC (rev 26870) +++ trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/editor/DeploymentModuleOptionCompositeAssistant.java 2010-11-24 09:23:00 UTC (rev 26871) @@ -12,7 +12,6 @@ import java.beans.PropertyChangeEvent; import java.beans.PropertyChangeListener; -import java.io.ByteArrayOutputStream; import java.io.File; import java.util.HashMap; @@ -43,13 +42,17 @@ import org.eclipse.swt.widgets.Control; import org.eclipse.swt.widgets.DirectoryDialog; import org.eclipse.swt.widgets.Label; +import org.eclipse.swt.widgets.Link; import org.eclipse.swt.widgets.Shell; import org.eclipse.swt.widgets.Text; import org.eclipse.swt.widgets.TreeColumn; import org.eclipse.swt.widgets.TreeItem; import org.eclipse.ui.forms.IFormColors; +import org.eclipse.ui.forms.events.HyperlinkEvent; +import org.eclipse.ui.forms.events.IHyperlinkListener; import org.eclipse.ui.forms.widgets.ExpandableComposite; import org.eclipse.ui.forms.widgets.FormToolkit; +import org.eclipse.ui.forms.widgets.Hyperlink; import org.eclipse.ui.forms.widgets.Section; import org.eclipse.wst.server.core.IModule; import org.eclipse.wst.server.core.IRuntime; @@ -67,7 +70,6 @@ import org.jboss.ide.eclipse.as.core.server.internal.ServerAttributeHelper; import org.jboss.ide.eclipse.as.core.util.DeploymentPreferenceLoader.DeploymentModulePrefs; import org.jboss.ide.eclipse.as.core.util.DeploymentPreferenceLoader.DeploymentPreferences; -import org.jboss.ide.eclipse.as.core.util.DeploymentPreferenceLoader; import org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants; import org.jboss.ide.eclipse.as.core.util.ServerConverter; import org.jboss.ide.eclipse.as.ui.Messages; @@ -615,12 +617,6 @@ publishLocColumn.setWidth(200); publishTempLocColumn.setWidth(200); - FormData treeData = new FormData(); - treeData.top = new FormAttachment(0, 5); - treeData.bottom = new FormAttachment(100, -5); - treeData.left = new FormAttachment(0, 5); - treeData.right = new FormAttachment(100, -5); - viewer.getTree().setLayoutData(treeData); viewer.setContentProvider(new ModulePageContentProvider()); viewer.setLabelProvider(new ModulePageLabelProvider()); @@ -633,10 +629,36 @@ new TextCellEditor(viewer.getTree()) }; viewer.setCellModifier(new LocalDeploymentCellModifier()); viewer.setCellEditors(editors); + + Link link = new Link(root, SWT.DEFAULT); + link.setText("<a>" + Messages.EditorRefreshViewer + "</a>"); + link.addSelectionListener(new SelectionListener() { + public void widgetSelected(SelectionEvent e) { + refreshViewer(); + } + public void widgetDefaultSelected(SelectionEvent e) { + } + }); + FormData linkData = new FormData(); + linkData.bottom = new FormAttachment(100,-5); + linkData.left = new FormAttachment(0, 5); + link.setLayoutData(linkData); + + FormData treeData = new FormData(); + treeData.top = new FormAttachment(0, 5); + treeData.bottom = new FormAttachment(link, -5); + treeData.left = new FormAttachment(0, 5); + treeData.right = new FormAttachment(100, -5); + viewer.getTree().setLayoutData(treeData); return root; } + private void refreshViewer() { + page.refreshPossibleModules(); + viewer.setInput(""); // irrelevent + } + private class LocalDeploymentCellModifier implements ICellModifier { public boolean canModify(Object element, String property) { if( property == COLUMN_NAME) Modified: trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/editor/ModuleDeploymentPage.java =================================================================== --- trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/editor/ModuleDeploymentPage.java 2010-11-24 09:16:21 UTC (rev 26870) +++ trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/editor/ModuleDeploymentPage.java 2010-11-24 09:23:00 UTC (rev 26871) @@ -79,6 +79,17 @@ public void init(IEditorSite site, IEditorInput input) { super.init(site, input); + refreshPossibleModules(); + if (input instanceof IServerEditorPartInput) { + IServerEditorPartInput sepi = (IServerEditorPartInput) input; + server = sepi.getServer(); + commandManager = ((ServerEditorPartInput) sepi).getServerCommandManager(); + readOnly = sepi.isServerReadOnly(); + } + helper = new ServerAttributeHelper(server.getOriginal(), server); + } + + public void refreshPossibleModules() { ArrayList<IModule> possibleChildren = new ArrayList<IModule>(); IModule[] modules2 = org.eclipse.wst.server.core.ServerUtil.getModules(server.getServerType().getRuntimeType().getModuleTypes()); if (modules2 != null) { @@ -91,20 +102,13 @@ } } this.possibleModules = possibleChildren; - if (input instanceof IServerEditorPartInput) { - IServerEditorPartInput sepi = (IServerEditorPartInput) input; - server = sepi.getServer(); - commandManager = ((ServerEditorPartInput) sepi).getServerCommandManager(); - readOnly = sepi.isServerReadOnly(); - } - helper = new ServerAttributeHelper(server.getOriginal(), server); - } public void createPartControl(Composite parent) { preferences = DeploymentPreferenceLoader.loadPreferencesFromServer(server.getOriginal()); ScrolledForm innerContent = createPageStructure(parent); addDeploymentLocationControls(innerContent.getBody(), null); + innerContent.reflow(true); }

13 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r26870 - trunk/drools/tests/org.jboss.tools.drools.ui.bot.test.

by jbosstools-commits＠lists.jboss.org

Author: vpakan(a)redhat.com Date: 2010-11-24 04:16:21 -0500 (Wed, 24 Nov 2010) New Revision: 26870 Modified: trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/pom.xml Log: Disable SWTBot test running. Change packaging to eclipse-plugin. Modified: trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/pom.xml =================================================================== --- trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/pom.xml 2010-11-24 08:59:38 UTC (rev 26869) +++ trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/pom.xml 2010-11-24 09:16:21 UTC (rev 26870) @@ -10,7 +10,7 @@ <groupId>org.jboss.tools.drools</groupId> <artifactId>org.jboss.tools.drools.ui.bot.test</artifactId> <version>1.0.0-SNAPSHOT</version> - <packaging>eclipse-test-plugin</packaging> + <packaging>eclipse-plugin</packaging> <build> <plugins> <plugin>

13 years, 10 months

1
0
0 / 0

JBoss Tools SVN: r26869 - trunk/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext.

by jbosstools-commits＠lists.jboss.org

Author: vpakan(a)redhat.com Date: 2010-11-24 03:59:38 -0500 (Wed, 24 Nov 2010) New Revision: 26869 Modified: trunk/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/SWTEclipseExt.java Log: Check Perspective existence correctly. Modified: trunk/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/SWTEclipseExt.java =================================================================== --- trunk/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/SWTEclipseExt.java 2010-11-24 08:37:08 UTC (rev 26868) +++ trunk/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/SWTEclipseExt.java 2010-11-24 08:59:38 UTC (rev 26869) @@ -201,13 +201,16 @@ SWTBotMenu menu2 = menu1.menu(IDELabel.Menu.OPEN_PERSPECTIVE); bot.sleep(Timing.time1S()); menu2.menu(IDELabel.Menu.OTHER).click(); - bot.sleep(Timing.time1S()); - try { - bot.table().select(perspectiveLabel); - } catch (WidgetNotFoundException e) { - log.warn("WARN - Perspecive with label " + perspectiveLabel + " not found, try + (default)"); - bot.table().select(perspectiveLabel + (" (default)")); + bot.sleep(Timing.time1S()); + SWTBotTable table = bot.table(); + if (isItemInTableColumn(table, perspectiveLabel, 0)){ + table.select(perspectiveLabel); } + else{ + log.warn("WARN - Perspecive with label '" + perspectiveLabel + "' was not found, trying label '" + + perspectiveLabel + " (default)'"); + table.select(perspectiveLabel + (" (default)")); + } bot.sleep(Timing.time1S()); // Another approach SWTBotShell openPerpectiveShell = bot.shell("Open Perspective"); @@ -398,7 +401,7 @@ */ public void assertSameContent(String pluginId, String projectName, String... path) { - File file = util.getResourceFile(pluginId, path); + File file = SWTUtilExt.getResourceFile(pluginId, path); String resourceContent = SWTTestExt.util.readTextFile(file); openAsText(projectName, path); @@ -439,7 +442,7 @@ SWTBotEclipseEditor editor; editor = bot.editorByTitle(path[path.length - 1]).toTextEditor(); editor.selectRange(0, 0, editor.getLineCount()); - File file = util.getResourceFile(pluginId, path); + File file = SWTUtilExt.getResourceFile(pluginId, path); String content = util.readTextFile(file); editor.setText(content); if (save) @@ -457,7 +460,7 @@ String pluginId, String... path) { SWTBotEclipseEditor edit = editor.toTextEditor(); edit.selectRange(0, 0, edit.getText().length()); - File file = util.getResourceFile(pluginId, path); + File file = SWTUtilExt.getResourceFile(pluginId, path); String content = util.readTextFile(file); edit.setText(content); if (save)

13 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits November 2010