September 2011 - switchyard-issues

[JBoss JIRA] Created: (SWITCHYARD-452) Upgrade to JBoss AS 7.0.1

by Keith Babo (JIRA)

Upgrade to JBoss AS 7.0.1 ------------------------- Key: SWITCHYARD-452 URL: https://issues.jboss.org/browse/SWITCHYARD-452 Project: SwitchYard Issue Type: Task Components: distribution Reporter: Keith Babo Fix For: 0.3 Upgrade version of AS7 used in our distro. Note the issue mentioned in this thread: http://community.jboss.org/thread/172223 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-451) Tooling should allow for cases where switchyard.xml in resources folders may be invalid

by Rob Cernich (JIRA)

Tooling should allow for cases where switchyard.xml in resources folders may be invalid --------------------------------------------------------------------------------------- Key: SWITCHYARD-451 URL: https://issues.jboss.org/browse/SWITCHYARD-451 Project: SwitchYard Issue Type: Bug Components: tooling Reporter: Rob Cernich Assignee: Rob Cernich The switchyard.xml file maintained by the user may be incomplete as portions may be contributed through code (e.g. annotations in a Java file). The externally contributed portions are merged with the user's portion to create the final switchyard.xml that gets bundled with the application. Because of this, the user's file may not be valid XML per the SwitchYard schema. The tooling should accommodate this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-450) Add wizard for creating SwitchYard projects in Eclipse

by Rob Cernich (JIRA)

Add wizard for creating SwitchYard projects in Eclipse ------------------------------------------------------ Key: SWITCHYARD-450 URL: https://issues.jboss.org/browse/SWITCHYARD-450 Project: SwitchYard Issue Type: Sub-task Components: tooling Reporter: Rob Cernich Assignee: Rob Cernich Fix For: 0.3 Add wizard for creating SwitchYard projects in Eclipse. The wizard should provide functionality similar to the existing Forge and Maven plugins. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-449) SwitchYard Eclipse Tooling

by Rob Cernich (JIRA)

SwitchYard Eclipse Tooling -------------------------- Key: SWITCHYARD-449 URL: https://issues.jboss.org/browse/SWITCHYARD-449 Project: SwitchYard Issue Type: Feature Request Components: tooling Reporter: Rob Cernich Assignee: Rob Cernich Fix For: 0.3 Top level issue organizing Eclipse tooling features. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-448) Incorrect message type used in SwitchYard producer when composite-level interface is specified

by Keith Babo (JIRA)

Incorrect message type used in SwitchYard producer when composite-level interface is specified ---------------------------------------------------------------------------------------------- Key: SWITCHYARD-448 URL: https://issues.jboss.org/browse/SWITCHYARD-448 Project: SwitchYard Issue Type: Bug Components: component-camel Affects Versions: 0.2 Reporter: Keith Babo Fix For: 0.3 The Camel component is not using the appropriate message type from the service reference in SwitchYardProducer if a composite-level interface is supplied. For example, take something like this: <service name="CarIntake" promote="CarIntake"> <interface.java interface="org.switchyard.workshop.lab2.FileIntake"/> <binding.camel xmlns="urn:switchyard-component-camel:config:1.0" configURI="file:///tmp/input"/> </service> When the producer code creates a SwitchYard exchange, it should be using the message types declared in FileIntake.java. It shouldn't be using the Java type here - just use the result of ServiceOperation.getInputType() from the ServiceInterface. What's happening now is that the producer is taking the class name from the Camel message body and setting that as the type. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-447) XSLT transformer improvements

by Keith Babo (JIRA)

XSLT transformer improvements ----------------------------- Key: SWITCHYARD-447 URL: https://issues.jboss.org/browse/SWITCHYARD-447 Project: SwitchYard Issue Type: Enhancement Components: transformation Reporter: Keith Babo Fix For: 0.3 A few things related to the XSLT transformer need to be updated for 0.3: 1) There is no transform-xslt quickstart 2) We need to look at the support for XSLT in JBoss ESB 4.x and make sure we support that level of functionality 3) If there are any additional features that would be interesting to implement around XSLT -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-446) SOAPGatewayTest fails with java.net.ConnectException: Connection refused: connect

by Magesh Bojan (JIRA)

SOAPGatewayTest fails with java.net.ConnectException: Connection refused: connect --------------------------------------------------------------------------------- Key: SWITCHYARD-446 URL: https://issues.jboss.org/browse/SWITCHYARD-446 Project: SwitchYard Issue Type: Task Components: component-soap Affects Versions: 0.2 Environment: Some high end dual core Intel systems running 32 bit OS. Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.3 When executing tests under JUnit, SOAPGatewayTest fails with message java.net.ConnectException: Connection refused: connect. This is very intermittent and often not reproducible under the same conditions. There seem to be an issue when running under JUnit that at shutdown, the port isn't completely released. When the next service is published up on that same port, it goes into a strange state. Turning off inbound.stop resolves this issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-445) Add the ability to disable bindings for a unit test

by Keith Babo (JIRA)

Add the ability to disable bindings for a unit test --------------------------------------------------- Key: SWITCHYARD-445 URL: https://issues.jboss.org/browse/SWITCHYARD-445 Project: SwitchYard Issue Type: Enhancement Components: test Reporter: Keith Babo Fix For: 0.3 When you pass a config to the test kit, everything in the config is activated on deploy. This sucks when testing out an implementation that happens to include a binding in it's config. Add the ability to disable bindings inside the test framework. This will obviously have to percolate down into the deployer implementation in some way. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-444) Dependency on components/tests module currently pulls in many unnecessary dependencies

by Gary Brown (JIRA)

Dependency on components/tests module currently pulls in many unnecessary dependencies -------------------------------------------------------------------------------------- Key: SWITCHYARD-444 URL: https://issues.jboss.org/browse/SWITCHYARD-444 Project: SwitchYard Issue Type: Task Affects Versions: 0.3 Reporter: Gary Brown While working on the bpel component I noticed that the module was inheriting many unnecessary dependencies. These dependencies are due to the tests module referencing other components. So for example, my bpel module was seeing dependencies on jbpm/drools, etc. However the bpel component needs to have a dependency on the tests component for the switchyard test kit. Two possible solutions, the component specific tests should be co-located with the component they are testing, or alternatively split the tests module into the 'test infrastructure' and 'tests'. Probably the easiest change would be the later, so components could just be dependent upon the test infra. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-443) camel-core pom should not specify groupId but instead inherit it from parent

by Daniel Bevenius (JIRA)

camel-core pom should not specify groupId but instead inherit it from parent ---------------------------------------------------------------------------- Key: SWITCHYARD-443 URL: https://issues.jboss.org/browse/SWITCHYARD-443 Project: SwitchYard Issue Type: Task Components: component-camel Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Trivial Fix For: 0.3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues September 2011