June 2011 - switchyard-issues - Jboss List Archives

[JBoss JIRA] Created: (SWITCHYARD-269) AS7 config stylesheet adds multiple switchyard entries when run repeatedly

by Keith Babo (JIRA)

AS7 config stylesheet adds multiple switchyard entries when run repeatedly -------------------------------------------------------------------------- Key: SWITCHYARD-269 URL: https://issues.jboss.org/browse/SWITCHYARD-269 Project: SwitchYard Issue Type: Bug Components: build Reporter: Keith Babo Tom and I noticed that performing the following in the release/jboss-as7 module produces duplicate switchyard config: > mvn clean install > mvn deploy The problem is that the AS7 config stylesheet simply adds configuration, so each time it runs another set of switchyard config is added. Might be better to go with a velocity template or we need to tweak the sytlesheet to overwrite existing config instead of adding to it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-268) Publish AS6 deployer build to Nexus

by Keith Babo (JIRA)

Publish AS6 deployer build to Nexus ----------------------------------- Key: SWITCHYARD-268 URL: https://issues.jboss.org/browse/SWITCHYARD-268 Project: SwitchYard Issue Type: Task Components: build Affects Versions: 0.1 Reporter: Keith Babo Fix For: 0.1 Skipping the maven deploy of AS6 deployer causes problems for a clean (i.e. no local SwitchYard artifacts) release build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-267) Bean component is setting payload type as an array in client proxy

by Keith Babo (JIRA)

Bean component is setting payload type as an array in client proxy ------------------------------------------------------------------ Key: SWITCHYARD-267 URL: https://issues.jboss.org/browse/SWITCHYARD-267 Project: SwitchYard Issue Type: Bug Components: component-bean Reporter: Keith Babo Assignee: Tom Fennelly Fix For: 0.1 ClientProxyBean is setting the message content to Object[] args. IIRC, we are not allowing multiple arg invocations. In any case, we should at least add a conditional that checks for an array length of 1 to set the actual object as the message content. Something like this: {noformat} if (args.length == 1) { exchangeIn.send(exchangeIn.createMessage().setContent(args[0])); } else { exchangeIn.send(exchangeIn.createMessage().setContent(args)); } {noformat} Note that there are two instances of this in ClientProxyBean.invoke() (one for in-out and one for in-only). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-266) ExchangeImpl is swallowing exception info for unhandled faults

by Keith Babo (JIRA)

ExchangeImpl is swallowing exception info for unhandled faults -------------------------------------------------------------- Key: SWITCHYARD-266 URL: https://issues.jboss.org/browse/SWITCHYARD-266 Project: SwitchYard Issue Type: Bug Components: core Affects Versions: 0.1 Reporter: Keith Babo The following code in ExchangeImpl results in the fault details getting swallowed since DefaultMessage.toString() will not print the content of the message: {noformat} // if a fault was thrown by the handler chain and there's no reply chain // we need to log. // TODO : stick this in a central fault/error queue if (ExchangeState.FAULT.equals(_state) && _replyChain == null) { _log.warn("Fault generated during exchange without a handler: " + _message); return; } {noformat} Here's what it looks like in the log: {noformat} 22:49:52,382 ERROR [org.switchyard.internal.DefaultHandlerChain] (Camel (camel-8) thread #6 - file:///tmp/input) org.switchyard.component.bean.BeanComponentException: Invocation of operation 'sayHello' on bean component 'org.example.test1.TestServiceBean' failed with exception. See attached cause. 22:49:52,384 WARN [org.switchyard.internal.ExchangeImpl] (Camel (camel-8) thread #6 - file:///tmp/input) Fault generated during exchange without a handler: org.switchyard.internal.DefaultMessage@64fe7a67 {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-265) Bean component throws NPE when service reference in unavailable

by Keith Babo (JIRA)

Bean component throws NPE when service reference in unavailable ---------------------------------------------------------------- Key: SWITCHYARD-265 URL: https://issues.jboss.org/browse/SWITCHYARD-265 Project: SwitchYard Issue Type: Bug Components: component-bean Affects Versions: 0.1 Reporter: Keith Babo Say you have something like this in your Bean class: {noformat} @Inject @Reference private MyService myService; {noformat} If "MyService" is not available when the Bean component's activator is kicked then we get this: 22:46:19,809 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."test1-1.0.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."test1-1.0.0-SNAPSHOT.jar".SwitchYardService: java.lang.NullPointerException at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:75) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) 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.NullPointerException at org.switchyard.component.bean.deploy.BeanComponentActivator.start(BeanComponentActivator.java:106) at org.switchyard.deploy.internal.Activation.start(Deployment.java:371) at org.switchyard.deploy.internal.Deployment.deployReferences(Deployment.java:297) at org.switchyard.deploy.internal.Deployment.start(Deployment.java:121) at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:76) at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:68) ... 4 more Might be nicer to just throw a deployment exception indicating that the target service could not be located. Maybe this should even be part of the deployer validation ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-264) Fill holes in forge tooling

by Keith Babo (JIRA)

Fill holes in forge tooling --------------------------- Key: SWITCHYARD-264 URL: https://issues.jboss.org/browse/SWITCHYARD-264 Project: SwitchYard Issue Type: Enhancement Components: configuration, tooling Reporter: Keith Babo Fix For: 0.1 Missing the following functionality: - View service and reference bindings - View service and reference interfaces - Promote references - Bind references All of the above can be handled with a few commands. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-263) Add configuration support for Camel Timer component

by Mario Antollini (JIRA)

Add configuration support for Camel Timer component --------------------------------------------------- Key: SWITCHYARD-263 URL: https://issues.jboss.org/browse/SWITCHYARD-263 Project: SwitchYard Issue Type: Task Components: component-camel Reporter: Mario Antollini Fix For: 0.2 Add configuration support for Camel Timer Component http://camel.apache.org/timer.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-262) Add configuration support for Camel's Bean component

by Mario Antollini (JIRA)

Add configuration support for Camel's Bean component ---------------------------------------------------- Key: SWITCHYARD-262 URL: https://issues.jboss.org/browse/SWITCHYARD-262 Project: SwitchYard Issue Type: Task Components: component-camel Reporter: Mario Antollini Fix For: 0.2 Add configuration support for Camel Bean Component. http://camel.apache.org/bean.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-261) SwitchYardDeploymentProcessor should only add a dependency on the Weld BeanManagerService if WeldDeploymentMetadata has been attached to the DeploymentUnit

by Tom Fennelly (JIRA)

SwitchYardDeploymentProcessor should only add a dependency on the Weld BeanManagerService if WeldDeploymentMetadata has been attached to the DeploymentUnit ------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: SWITCHYARD-261 URL: https://issues.jboss.org/browse/SWITCHYARD-261 Project: SwitchYard Issue Type: Bug Components: deployment Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.1 Otherwise we get a failed deployment for SwitchYard apps that are not using CDI Beans. It fails because SwitchYardDeploymentProcessor marks the deployment as having a dependency on the Weld BeanManagerService, when it doesn't really have a dependency on it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-260) pom parent path fixes

by Tom Fennelly (JIRA)

pom parent path fixes ---------------------- Key: SWITCHYARD-260 URL: https://issues.jboss.org/browse/SWITCHYARD-260 Project: SwitchYard Issue Type: Bug Components: build Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.1 A number of the component and quickstart poms do not contain a relative path to their parent pom. This causes the build to break on a clean system because these poms reference the ${project.parent.version} variable, resolution of which appears to require direct access to the parent pom. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues June 2011