July 2011 - switchyard-issues - Jboss List Archives

[JBoss JIRA] Created: (SWITCHYARD-360) component-rules::RulesModelTest explicit assertion to linux path fails in windows

by Mario Antollini (JIRA)

component-rules::RulesModelTest explicit assertion to linux path fails in windows --------------------------------------------------------------------------------- Key: SWITCHYARD-360 URL: https://issues.jboss.org/browse/SWITCHYARD-360 Project: SwitchYard Issue Type: Bug Affects Versions: 0.2 Environment: Windows Reporter: Mario Antollini Priority: Minor Fix For: 0.2 This line (85) fails in windows: Assert.assertEquals("/tmp/foobar", ram.getFile().getAbsolutePath()); Project: componet-rules File: RulesModelTests::testReadComplete -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-359) Add Rules component + dependencies to AS 6 and 7 distributions

by David Ward (JIRA)

Add Rules component + dependencies to AS 6 and 7 distributions -------------------------------------------------------------- Key: SWITCHYARD-359 URL: https://issues.jboss.org/browse/SWITCHYARD-359 Project: SwitchYard Issue Type: Task Components: distribution Reporter: David Ward Assignee: Justin Wyer Fix For: 0.2 Need to add the component and dependencies to the AS distributions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-358) Create a HornetQ test MixIn

by Tom Fennelly (JIRA)

Create a HornetQ test MixIn --------------------------- Key: SWITCHYARD-358 URL: https://issues.jboss.org/browse/SWITCHYARD-358 Project: SwitchYard Issue Type: Feature Request Components: test Reporter: Tom Fennelly See CamelJMSTest for requirements. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-357) ServiceReference is currently bound to a concrete service registration

by Keith Babo (JIRA)

ServiceReference is currently bound to a concrete service registration ---------------------------------------------------------------------- Key: SWITCHYARD-357 URL: https://issues.jboss.org/browse/SWITCHYARD-357 Project: SwitchYard Issue Type: Feature Request Components: core Affects Versions: 0.2 Reporter: Keith Babo We support registering multiple instances of a service, but the ServiceReference that is injected into component Activator instances is tied to a specific service registration. We need to abstract this out so that a given service registration can go away and the logical service reference is still valid as long as an alternative service implementation still exists. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-356) Use of enum for ResourceType restricts extensibility

by Keith Babo (JIRA)

Use of enum for ResourceType restricts extensibility ---------------------------------------------------- Key: SWITCHYARD-356 URL: https://issues.jboss.org/browse/SWITCHYARD-356 Project: SwitchYard Issue Type: Bug Components: common, configuration Reporter: Keith Babo Assignee: David Ward Fix For: 0.2 Use of the ResourceType enum in the Resource config model restricts extensibility by requiring a change to core to support different resource types. For example, let's say I add a BPEL component and want to use the resource config model to point to a BPEL process definition. In order to make this work, I would also have to modify core to augment the enum to include a BPEL type. Making the type value a string should alleviate this problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-355) SOAP binding should support doclit as well as wrapped doclit

by Gary Brown (JIRA)

SOAP binding should support doclit as well as wrapped doclit ------------------------------------------------------------ Key: SWITCHYARD-355 URL: https://issues.jboss.org/browse/SWITCHYARD-355 Project: SwitchYard Issue Type: Feature Request Components: component-soap Affects Versions: 0.1 Reporter: Gary Brown Currently the SOAP binding expects the operation name as the immediate child node within the SOAP body. This is ok for wrapped doclit, but not doclit. To support doclit would need to derive the operation name based on the element type (found as the child node of the body). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-354) CamelActivator creates a DefaultCamelContext which might cause issues when deployed into an OSGI Container

by Daniel Bevenius (JIRA)

CamelActivator creates a DefaultCamelContext which might cause issues when deployed into an OSGI Container ---------------------------------------------------------------------------------------------------------- Key: SWITCHYARD-354 URL: https://issues.jboss.org/browse/SWITCHYARD-354 Project: SwitchYard Issue Type: Task Components: component-camel Reporter: Daniel Bevenius Currently we are creating a DefaultCamelContext in the constructor of CamelActivator. When running in an OSGI Container an OSGIDefaultCamelContext is used by Camel which provides access to resources via the BundleContext. We need to investigate how this will work with the PackageScanClassResolver and the Registry as well, which both have different implementations when running in an OSGI container. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-353) Look into adding fragment.xml file(s) to our jars to help Eclipse auto-load switchyard and sca schemas

by Tom Fennelly (JIRA)

Look into adding fragment.xml file(s) to our jars to help Eclipse auto-load switchyard and sca schemas ------------------------------------------------------------------------------------------------------ Key: SWITCHYARD-353 URL: https://issues.jboss.org/browse/SWITCHYARD-353 Project: SwitchYard Issue Type: Enhancement Components: configuration Reporter: Tom Fennelly Fix For: 0.2 Attachments: fragment.xml There's a way of contributing to the eclipse xsd catalog by adding a fragment.xml file to the root of a module. Not totally sure of Eclipse automatically picks this up, or f it needs to be dropped into the a special folder in the editor. Worth having a look at. I'll attach an example of a fragment.xml file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-352) switchyard-forge-soap-plugin package name should be soap instead of camel

by Mario Antollini (JIRA)

switchyard-forge-soap-plugin package name should be soap instead of camel ------------------------------------------------------------------------- Key: SWITCHYARD-352 URL: https://issues.jboss.org/browse/SWITCHYARD-352 Project: SwitchYard Issue Type: Enhancement Components: component-soap Affects Versions: 0.2 Reporter: Mario Antollini Priority: Minor Fix For: 0.2 components\tools\forge\soap should have "soap" package name instead of "camel" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-351) targetNamespace being lost by switchyard plugin (ConfigMojo) during final switchyard.xml generation

by David Ward (JIRA)

targetNamespace being lost by switchyard plugin (ConfigMojo) during final switchyard.xml generation --------------------------------------------------------------------------------------------------- Key: SWITCHYARD-351 URL: https://issues.jboss.org/browse/SWITCHYARD-351 Project: SwitchYard Issue Type: Bug Components: configuration Affects Versions: 0.1 Reporter: David Ward Assignee: David Ward Fix For: 0.2 Currently the merged configuration generator (ConfigMojo) does not seem to set the actual targetNamespace declared in the provided configuration. Say for e.g., <switchyard xmlns="urn:switchyard-config:switchyard:1.0" xmlns:swyd="urn:switchyard-config:switchyard:1.0" xmlns:trfm="urn:switchyard-config:transform:1.0" xmlns:bean="urn:switchyard-component-bean:config:1.0" xmlns:soap="urn:switchyard-component-soap:config:1.0" xmlns:sca="http://docs.oasis-open.org/ns/opencsa/sca/200912" targetNamespace="urn:switchyard-quickstart-demo:orders:0.1.0-SNAPSHOT" name="orders"> gets generated as <switchyard xmlns="urn:switchyard-config:switchyard:1.0"> <composite xmlns="http://docs.oasis-open.org/ns/opencsa/sca/200912" name="orders"> ... <component name="OrderService"> <service name="OrderService"> The targetNamespace is not included in switchyard Element. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues July 2011