December 2011 - switchyard-issues

[JBoss JIRA] (SWITCHYARD-593) SY Eclipse tools cannot create test classes using Eclipse 3.6

by Rob Cernich (Created) (JIRA)

SY Eclipse tools cannot create test classes using Eclipse 3.6 ------------------------------------------------------------- Key: SWITCHYARD-593 URL: https://issues.jboss.org/browse/SWITCHYARD-593 Project: SwitchYard Issue Type: Bug Affects Versions: 0.3 Reporter: Rob Cernich Fix For: 0.4 The test file is blank and there is an exception in the Eclipse log. This is caused by the AST language level used to create the source parser, used to add the methods. The level used is only supported in Eclipse 3.7.1. The typical error in the Eclipse log: eclipse.buildId=M20110210-1200 java.version=1.6.0_27 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product Error Mon Dec 19 09:44:16 MST 2011 Error creating bean service class. java.lang.IllegalArgumentException at org.eclipse.jdt.core.dom.ASTParser.<init>(ASTParser.java:222) at org.eclipse.jdt.core.dom.ASTParser.newParser(ASTParser.java:125) at org.eclipse.jdt.internal.corext.refactoring.util.RefactoringASTParser.<init>(RefactoringASTParser.java:40) at org.switchyard.tools.ui.wizards.NewServiceTestClassWizardPage.resolveServiceType(NewServiceTestClassWizardPage.java:298) at org.switchyard.tools.ui.wizards.NewServiceTestClassWizardPage.createTypeMembers(NewServiceTestClassWizardPage.java:262) at org.eclipse.jdt.ui.wizards.NewTypeWizardPage.createType(NewTypeWizardPage.java:2068) at org.switchyard.tools.ui.operations.CreateBeanServiceOperation.execute(CreateBeanServiceOperation.java:88) at org.switchyard.tools.ui.operations.AbstractSwitchYardProjectOperation.run(AbstractSwitchYardProjectOperation.java:100) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1957) at org.switchyard.tools.ui.wizards.NewBeanServiceWizard$1.run(NewBeanServiceWizard.java:91) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-592) Generated BPM definition should contain variable definitions for in and out message

by Keith Babo (Created) (JIRA)

Generated BPM definition should contain variable definitions for in and out message ----------------------------------------------------------------------------------- Key: SWITCHYARD-592 URL: https://issues.jboss.org/browse/SWITCHYARD-592 Project: SwitchYard Issue Type: Enhancement Components: tooling Affects Versions: 0.3 Reporter: Keith Babo Fix For: 0.4 The default message names (messageContentIn, messageContentOut) should be set as process variables in generated BPMN 2 definitions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-591) BPM service node missing InputMessageVariable, OutputMessageVariable

by Murray Todd Williams (Created) (JIRA)

BPM service node missing InputMessageVariable, OutputMessageVariable -------------------------------------------------------------------- Key: SWITCHYARD-591 URL: https://issues.jboss.org/browse/SWITCHYARD-591 Project: SwitchYard Issue Type: Bug Components: component-bpm Affects Versions: 0.3 Reporter: Murray Todd Williams Attachments: bpmn2.png When designing a process in the BPMN2 editor, the SwitchYard Service node lacks InputMessageVariable and OutputMessageVariable properties. Automatic bindings do not appear to happen, so service nodes get called with null messages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-590) messageComposer setting ignored on Camel composite service bindings

by Rob Cernich (Created) (JIRA)

messageComposer setting ignored on Camel composite service bindings ------------------------------------------------------------------- Key: SWITCHYARD-590 URL: https://issues.jboss.org/browse/SWITCHYARD-590 Project: SwitchYard Issue Type: Bug Components: component-camel Affects Versions: 0.3 Reporter: Rob Cernich Not sure if this is a bug, an enhancement, or user error, but... The Camel configuration schema allows one to specify a message composer as part of the binding configuration. When applied to a composite service, the composer is not used. Specifically, I am trying to use Camel Quartz to invoke a service and I need to setup the message that gets passed to the service (in this case, simply setting the fire time in the message body). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-589) Forge plugin "bpm-service create" command breaks switchyard.xml schema

by Murray Todd Williams (Created) (JIRA)

Forge plugin "bpm-service create" command breaks switchyard.xml schema ---------------------------------------------------------------------- Key: SWITCHYARD-589 URL: https://issues.jboss.org/browse/SWITCHYARD-589 Project: SwitchYard Issue Type: Bug Components: tooling Affects Versions: 0.3 Environment: Eclipse with JBoss Tools 3.3 Reporter: Murray Todd Williams Forge execution of "bpm-service create --serviceName Foo" modifies the switchyard.xml file in a way that violates the schema. (<service> and <implementation> tags are reversed) Eclipse will show an XML validation error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-588) Quickstart "Rules Interview Agent" RulesInterviewTest hangs, looking for schema

by Murray Todd Williams (Created) (JIRA)

Quickstart "Rules Interview Agent" RulesInterviewTest hangs, looking for schema ------------------------------------------------------------------------------- Key: SWITCHYARD-588 URL: https://issues.jboss.org/browse/SWITCHYARD-588 Project: SwitchYard Issue Type: Bug Components: quickstarts Affects Versions: 0.3 Reporter: Murray Todd Williams In the SwitchYard 0.3.0 source's quickstart directory, if I do a basic "mvn install" at the top level, the system stops at the "Rules Interview Agent" module during the unit test—specifically the org.switchyard.quickstarts.rules.interview.RulesInterviewTest test. The test doesn't actually fail, but the system hangs for about _eight minutes_ before showing the following messages: {noformat} ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.switchyard.quickstarts.rules.interview.RulesInterviewTest (null: 1, 283): schema_reference.4: Failed to read schema document 'http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-api/src/...', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. (null: 1, 283): cvc-elt.1: Cannot find the declaration of element 'change-set'. (null: 1, 288): schema_reference.4: Failed to read schema document 'http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-api/src/...', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. (null: 1, 471): schema_reference.4: Failed to read schema document 'http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-api/src/...', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. ********** David is a valid applicant. ********** Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 455.781 sec {noformat} Looks like the system is missing an XML schema catalog file and the XML validator is hanging. (My computer is behind a corporate proxy, so this might not show up on computers with straight access to the Internet.) Not a show-stopper, but worth noting.... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-587) Default to current version for Forge-generated applications

by Keith Babo (Created) (JIRA)

Default to current version for Forge-generated applications ----------------------------------------------------------- Key: SWITCHYARD-587 URL: https://issues.jboss.org/browse/SWITCHYARD-587 Project: SwitchYard Issue Type: Enhancement Components: tooling Affects Versions: 0.3 Reporter: Keith Babo Fix For: 0.4 When installing the SwitchYard facet, you are faced with a question of which version to choose like this: {code} [foo] foo $ project install-facet switchyard Please select a version to install: 1 - [org.switchyard:switchyard-api:::0.1.0-M1] 2 - [org.switchyard:switchyard-api:::0.1.0-SNAPSHOT] 3 - [org.switchyard:switchyard-api:::0.1.0] 4 - [org.switchyard:switchyard-api:::0.2.0-SNAPSHOT] 5 - [org.switchyard:switchyard-api:::0.2.0] 6 - [org.switchyard:switchyard-api:::0.3.0-SNAPSHOT] 7 - [org.switchyard:switchyard-api:::0.3.0.CR1] 8 - [org.switchyard:switchyard-api:::0.3.0.Final] 9 - [org.switchyard:switchyard-api:::0.4.0-SNAPSHOT] ? Choose an option by typing the number of the selection: {code} It's unlikely that users will want to choose a different version than the tooling they are using, so we should default to that and allow them to opt out with a y/n question. If they answer no to the default, then pop up a choice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-586) Service and Reference promotions naming issue

by Magesh Bojan (Created) (JIRA)

Service and Reference promotions naming issue --------------------------------------------- Key: SWITCHYARD-586 URL: https://issues.jboss.org/browse/SWITCHYARD-586 Project: SwitchYard Issue Type: Bug Components: component-camel, configuration Reporter: Magesh Bojan When we change the name of the promotions to anything other than what is given in promote the Camel component is unable to setup the route properly. Say for example this: <sca:service name="PromotedService" promote="PromoteMeService"> ... </sca:service> and this: <sca:reference name="PromotedReference" promote="PromoteMeReference"> ... </sca:reference> when referenced in Camel route as: <spring:to uri="switchyard://PromotedService"/> or <spring:to uri="switchyard://PromotedReference"/> or <spring:to uri="switchyard://PromoteMeService"/> or <spring:to uri="switchyard://PromoteMeReference"/> always throws error Caused by: org.switchyard.exception.SwitchYardException: Could find the service reference for 'PromoteMeService' which is referenced in To[switchyard://PromoteMeService?namespace=urn%3Aswitchyard-quickstart%3Atest%3A1.0] at org.switchyard.component.camel.deploy.CamelActivator.handleImplementation(CamelActivator.java:190) at org.switchyard.component.camel.deploy.CamelActivator.init(CamelActivator.java:115) at org.switchyard.deploy.internal.Deployment.deployServices(Deployment.java:323) at org.switchyard.deploy.internal.Deployment.doStart(Deployment.java:131) at org.switchyard.deploy.internal.AbstractDeployment.start(AbstractDeployment.java:191) at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:105) at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:86) ... 5 more Caused by: org.switchyard.exception.SwitchYardException: Could find the service reference for 'PromoteMeService' which is referenced in To[switchyard://PromoteMeService?namespace=urn%3Aswitchyard-quickstart%3Atest%3A1.0] at org.switchyard.component.camel.deploy.CamelActivator.checkSwitchYardReferencedServiceExist(CamelActivator.java:211) at org.switchyard.component.camel.deploy.CamelActivator.handleImplementation(CamelActivator.java:181) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-585) Refactor poms so there is a single dependencyManagement and version property section

by Nick Cross (Created) (JIRA)

Refactor poms so there is a single dependencyManagement and version property section ------------------------------------------------------------------------------------ Key: SWITCHYARD-585 URL: https://issues.jboss.org/browse/SWITCHYARD-585 Project: SwitchYard Issue Type: Task Reporter: Nick Cross A lot of the modules have their own dependencyManagement section and version properties. It would make it simpler for long term maintenance if all the information was refactored into the parent pom. This would allow use of VBOMs. The multiple versions also lead to situations where the modules are using 3 different versions of e.g. hornetq, arquillian etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-584) Ensure that the release tests do end-to-end testing and not just deployment

by Tom Cunningham (Created) (JIRA)

Ensure that the release tests do end-to-end testing and not just deployment --------------------------------------------------------------------------- Key: SWITCHYARD-584 URL: https://issues.jboss.org/browse/SWITCHYARD-584 Project: SwitchYard Issue Type: Task Components: test Affects Versions: 0.4 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 0.4 >From Keith's email : We should also make sure that all of the release tests actually test end-to-end and not just deployment. If you look in the release/jboss-as7/tests project, the violators have test methods that look like this: @Test public void testDeployment() { Assert.assertNotNull("Dummy not null", ""); } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues December 2011