May 2011 - switchyard-issues - Jboss List Archives

[JBoss JIRA] Created: (SWITCHYARD-238) AS7: org.jboss.as.ee.naming.NamespaceSelectorService has been removed in jboss-7.0.0.Beta4-SNAPSHOT

by Daniel Bevenius (JIRA)

AS7: org.jboss.as.ee.naming.NamespaceSelectorService has been removed in jboss-7.0.0.Beta4-SNAPSHOT --------------------------------------------------------------------------------------------------- Key: SWITCHYARD-238 URL: https://issues.jboss.org/browse/SWITCHYARD-238 Project: SwitchYard Issue Type: Task Components: deployment Reporter: Daniel Bevenius Priority: Minor I've been using building AS7 and using the lastest snapshot for testing and noticed this issue. Just creating this jira to give a hint to the issue incase anyone else runs into it. The "fix" to let me get around this can be found in the [branch|https://github.com/danbev/core/tree/as7-beta4]. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-237) Create a Transformer for Camel

by Daniel Bevenius (JIRA)

Create a Transformer for Camel ------------------------------ Key: SWITCHYARD-237 URL: https://issues.jboss.org/browse/SWITCHYARD-237 Project: SwitchYard Issue Type: Task Components: component-camel Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor The idea is to create a Switchyard transformer that delegates to Camel's TypeConverter mechanism. Please see the forum reference for more information about this task -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-236) config model InputStreams not always closed

by David Ward (JIRA)

config model InputStreams not always closed ------------------------------------------- Key: SWITCHYARD-236 URL: https://issues.jboss.org/browse/SWITCHYARD-236 Project: SwitchYard Issue Type: Bug Reporter: David Ward Assignee: David Ward Fix For: 0.1 There are places in the code where pulling input streams to build config models are not closing those streams. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-235) Allow the Message (and maybe Exchange) to be passed into Transformers

by Tom Fennelly (JIRA)

Allow the Message (and maybe Exchange) to be passed into Transformers --------------------------------------------------------------------- Key: SWITCHYARD-235 URL: https://issues.jboss.org/browse/SWITCHYARD-235 Project: SwitchYard Issue Type: Feature Request Components: transformation Reporter: Tom Fennelly Assignee: Tom Fennelly At the moment, the Transformer code assumes you are passing the Message payload to the Transformer instance. Makes sense to also be able to pass the whole Message instance (and maybe the Exchange). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-234) InOutOperation: make the constructors consistent and use 'operationName' instead of 'operationType'

by Daniel Bevenius (JIRA)

InOutOperation: make the constructors consistent and use 'operationName' instead of 'operationType' ---------------------------------------------------------------------------------------------------- Key: SWITCHYARD-234 URL: https://issues.jboss.org/browse/SWITCHYARD-234 Project: SwitchYard Issue Type: Task Components: core Reporter: Daniel Bevenius Priority: Minor The following constructors can be found in InOutOperation: {code:title=Bar.java|borderStyle=solid} public InOutOperation(String operationName) { this(operationName, null, null, null); } public InOutOperation(String operationType, QName inputType, QName outputType) { super(inputType, outputType, null); _operationName = operationType; } public InOutOperation(String operationType, QName inputType, QName outputType, QName faultType) { super(inputType, outputType, faultType); _operationName = operationType; } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-233) Add Java DSL support for Camel Component

by Keith Babo (JIRA)

Add Java DSL support for Camel Component ---------------------------------------- Key: SWITCHYARD-233 URL: https://issues.jboss.org/browse/SWITCHYARD-233 Project: SwitchYard Issue Type: Enhancement Reporter: Keith Babo Assignee: Keith Babo Fix For: 0.1 Allow Camel services to be defined via the Java DSL in addition to the currently supported XML configuration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-232) change quickstarts to follow convention

by David Ward (JIRA)

change quickstarts to follow convention --------------------------------------- Key: SWITCHYARD-232 URL: https://issues.jboss.org/browse/SWITCHYARD-232 Project: SwitchYard Issue Type: Task Components: quickstarts Affects Versions: M1 Reporter: David Ward Assignee: David Ward Priority: Minor Fix For: 0.1 1. Quickstarts should showcase a single feature. 2. Demos can showcase multiple features in combination. 3. Quickstarts should be named switchyard-quickstart-${NAME} 4. Demos should be in a subdirectory called "demos". 5. Demos should be named switchyard-quickstart-demo-${NAME}. 6. "m1app" should be renamed to switchyard-quickstart-demo-orders 7. "transform-smooks" should be renamed to switchyard-quickstart-transform-smooks -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-231) SmooksExceptions should be checked

by Michael Burman (JIRA)

SmooksExceptions should be checked ---------------------------------- Key: SWITCHYARD-231 URL: https://issues.jboss.org/browse/SWITCHYARD-231 Project: SwitchYard Issue Type: Enhancement Components: transformation Reporter: Michael Burman Executing Smooks might lead to throwing SmooksException in the process. If the environment is transacted, the action is always rollbacked and message returned to the previous phase. This is not correct behaviour often, since Smooks throws SmooksException for example in case of SAXParseException. That processed file is broken and will not work in the subsequent phases either. Writing any database log for example of happening is impossible since that would be rollbacked as well. All SmooksException should be checked whether they should be rollbacked or not (or just never rollback them, throw them as checked exceptions). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-230) Camel deployment fails in modular AS7

by Keith Babo (JIRA)

Camel deployment fails in modular AS7 ------------------------------------- Key: SWITCHYARD-230 URL: https://issues.jboss.org/browse/SWITCHYARD-230 Project: SwitchYard Issue Type: Bug Reporter: Keith Babo Assignee: Magesh Bojan Fix For: 0.1 Camel deployments fail with our modularized setup in AS7. App to reproduce attached. Stack trace below. I tried to add the obvious stuff (e.g. camel component dependency on "javax.xml.bind.api" and "com.sun.xml.bind") but that did not resolve the issue. 15:01:23,941 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."feedbackApp-1.0.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."feedbackApp-1.0.0-SNAPSHOT.jar".SwitchYardService: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1696) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24] Caused by: java.lang.ExceptionInInitializerError at org.switchyard.component.camel.config.model.v1.V1CamelModelMarshaller.read(V1CamelModelMarshaller.java:67) at org.switchyard.config.model.BaseModel.readModel(BaseModel.java:242) at org.switchyard.config.model.BaseModel.getFirstChildModelStartsWith(BaseModel.java:226) at org.switchyard.config.model.composite.v1.V1ComponentModel.getImplementation(V1ComponentModel.java:92) at org.switchyard.deploy.internal.Deployment.getActivator(Deployment.java:171) at org.switchyard.deploy.internal.Deployment.deployServices(Deployment.java:260) at org.switchyard.deploy.internal.Deployment.start(Deployment.java:119) at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:76) at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:68) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) ... 3 more Caused by: java.lang.RuntimeException: javax.xml.bind.JAXBException: Provider com.sun.xml.internal.bind.v2.ContextFactory not found - with linked exception: [java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory from [Module "deployment.feedbackApp-1.0.0-SNAPSHOT.jar:main" from Service Module Loader]] at org.switchyard.component.camel.config.model.v1.V1CamelImplementationModel.createJAXBInstance(V1CamelImplementationModel.java:76) at org.switchyard.component.camel.config.model.v1.V1CamelImplementationModel.<clinit>(V1CamelImplementationModel.java:41) ... 13 more Caused by: javax.xml.bind.JAXBException: Provider com.sun.xml.internal.bind.v2.ContextFactory not found - with linked exception: [java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory from [Module "deployment.feedbackApp-1.0.0-SNAPSHOT.jar:main" from Service Module Loader]] at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:146) [:1.6.0_24] at javax.xml.bind.ContextFinder.find(ContextFinder.java:289) [:1.6.0_24] at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:412) [:1.6.0_24] at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:375) [:1.6.0_24] at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:279) [:1.6.0_24] at org.switchyard.component.camel.config.model.v1.V1CamelImplementationModel.createJAXBInstance(V1CamelImplementationModel.java:74) ... 14 more Caused by: java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory from [Module "deployment.feedbackApp-1.0.0-SNAPSHOT.jar:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:184) [:1.0.0.Beta17] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:357) [:1.0.0.Beta17] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:306) [:1.0.0.Beta17] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:100) [:1.0.0.Beta17] at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:490) [:1.6.0_24] at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:112) [:1.6.0_24] ... 19 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-229) Global handler for observing messages inbound and outbound of ESB components/gateways

by Gary Brown (JIRA)

Global handler for observing messages inbound and outbound of ESB components/gateways ------------------------------------------------------------------------------------- Key: SWITCHYARD-229 URL: https://issues.jboss.org/browse/SWITCHYARD-229 Project: SwitchYard Issue Type: Feature Request Reporter: Gary Brown It would be useful to configure a global handler that can observe all messages in and out of all switchyard ESB services running within a container, rather than having to individually configure each service with the same handler prior to deployment. The specific usecase is to be able to monitor interactions between various technologies/components within a runtime environment, and compare these interactions against models representing the required business transaction flow. In terms of how this could be configured - a programmatic interface would be preferred, although not sure if this would be considered a security risk, allowing any component to listen in on the traffic between other components running in the server. The other option is a configuration file change to switchyard, which could only be done by an administrator, but not as straightforward. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues May 2011