September 2011 - switchyard-issues

[JBoss JIRA] Created: (SWITCHYARD-442) SwitchYard application projects contain Maven errors with m2eclipse

by Keith Babo (JIRA)

SwitchYard application projects contain Maven errors with m2eclipse ------------------------------------------------------------------- Key: SWITCHYARD-442 URL: https://issues.jboss.org/browse/SWITCHYARD-442 Project: SwitchYard Issue Type: Bug Components: tooling Reporter: Keith Babo Assignee: Rob Cernich Fix For: 0.3 Create a new application using the forge tooling and install the switchyard facet. Then open the app in Eclipse and notice how there are m2eclipse validation errors. Looks like we need to provide some sort of extension to m2eclipse to get it to recognize our custom plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-441) Add remaining JBoss ESB Rules functionality to the Rules Component

by David Ward (JIRA)

Add remaining JBoss ESB Rules functionality to the Rules Component ------------------------------------------------------------------ Key: SWITCHYARD-441 URL: https://issues.jboss.org/browse/SWITCHYARD-441 Project: SwitchYard Issue Type: Feature Request Components: component-rules, configuration, quickstarts, tooling Affects Versions: 0.2 Reporter: David Ward Assignee: David Ward Fix For: 0.3 Right now the functionality of the implementation.rules component is: - Based on Drools 5.2.0.Final - Stateless execution - Stateful execution respecting "continue" & "dispose" properties - Audit logging (console, file, threaded_file; file name; interval) - Annotation-based config (although it's clunky in 0.2; see SWITCHYARD-428) - Forge plugin/facet support. Functionality which is lacking, but currently in JBoss ESB 4.9 is: - Complex Event Processing (CEP) - KnowledgeAgent / Guvnor integration - Content Based Routing (CBR) These things should be added to SwitchYard. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-440) Missing slf4j dependency in application silently fails during bean discovery

by Keith Babo (JIRA)

Missing slf4j dependency in application silently fails during bean discovery ---------------------------------------------------------------------------- Key: SWITCHYARD-440 URL: https://issues.jboss.org/browse/SWITCHYARD-440 Project: SwitchYard Issue Type: Bug Components: component-bean Affects Versions: 0.2 Reporter: Keith Babo Fix For: 0.3 Adding sl4fj to the bean-service quickstarts results in a deployment error, but only due to the bean service not being found. An earlier failure must occur which causes the bean not to be discovered, but there's no evidence of this in the console or log. Need to investigate to see if we are missing this in our CDI Extension or if this is purely a Weld/CDI issue in AS7. Check the forum thread for more info and an app to reproduce. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-439) SOAP gateway should return SOAP Fault even if fault message content is not SOAP Fault Body

by Tomohisa igarashi (JIRA)

SOAP gateway should return SOAP Fault even if fault message content is not SOAP Fault Body ------------------------------------------------------------------------------------------ Key: SWITCHYARD-439 URL: https://issues.jboss.org/browse/SWITCHYARD-439 Project: SwitchYard Issue Type: Sub-task Components: component-soap Affects Versions: 0.3 Reporter: Tomohisa igarashi Fix For: 0.3 When sendFault() is called on component, SOAP Gateway should return SOAP Fault even if the content of fault message which is transfered by sendFault() is not the body of SOAP Fault. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-438) getting all ResourceTypes by extension ignores extension inheritance

by David Ward (JIRA)

getting all ResourceTypes by extension ignores extension inheritance -------------------------------------------------------------------- Key: SWITCHYARD-438 URL: https://issues.jboss.org/browse/SWITCHYARD-438 Project: SwitchYard Issue Type: Bug Components: common Reporter: David Ward Assignee: David Ward Priority: Minor Fix For: 0.3 The includeInherited parameter of the +forExtension(String,boolean):ResourceType[] method is not being propagated into the call to the +getExtensions(boolean):Set<String> method. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-437) SOAP binding not returning a SOAP fault

by Gary Brown (JIRA)

SOAP binding not returning a SOAP fault --------------------------------------- Key: SWITCHYARD-437 URL: https://issues.jboss.org/browse/SWITCHYARD-437 Project: SwitchYard Issue Type: Bug Affects Versions: 0.3 Reporter: Gary Brown Currently working on a BPEL component for switchyard. When this component returns a fault, using the Exchange.sendFault(), with the content being returned as a DOM element, the SOAP binding component is returning it as a normal SOAP message. One of the issues here is how the fault code will be transferred. One possibility is to support a fault being passed between components as a SOAPFault? although other content types would need to be handled. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-436) SOAP gateway deployment error during startup on AS7

by Magesh Bojan (JIRA)

SOAP gateway deployment error during startup on AS7 --------------------------------------------------- Key: SWITCHYARD-436 URL: https://issues.jboss.org/browse/SWITCHYARD-436 Project: SwitchYard Issue Type: Bug Components: component-soap Affects Versions: 0.2 Environment: AS7 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.3 When multiple deployments are present using the same port, say 18001, but different context paths the following error is thrown and all deployment fails: (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."switchyard-quickstart-demo-orders-0.2.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-quickstart-demo-orders-0.2.0-SNAPSHOT.jar".SwitchYardService: javax.xml.ws.WebServiceException: java.lang.RuntimeException: java.net.BindException: Address already in use: bind at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:90) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [:1.6.0_26] at java.lang.Thread.run(Unknown Source) [:1.6.0_26] Caused by: javax.xml.ws.WebServiceException: java.lang.RuntimeException: java.net.BindException: Address already in use: bind at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:350) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:239) at org.jboss.wsf.stack.cxf.client.ProviderImpl$DelegateEndpointImpl.publish(ProviderImpl.java:300) at org.switchyard.component.soap.InboundHandler.start(InboundHandler.java:158) at org.switchyard.component.soap.deploy.SOAPActivator.start(SOAPActivator.java:92) at org.switchyard.deploy.internal.Activation.start(Deployment.java:481) at org.switchyard.deploy.internal.Deployment.deployServiceBindings(Deployment.java:380) at org.switchyard.deploy.internal.Deployment.doStart(Deployment.java:122) at org.switchyard.deploy.internal.AbstractDeployment.start(AbstractDeployment.java:168) at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:99) at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:83) ... 5 more Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind at org.jboss.wsf.stack.cxf.addons.transports.httpserver.HttpServerEngine.addHandler(HttpServerEngine.java:103) at org.jboss.wsf.stack.cxf.addons.transports.httpserver.HttpServerDestination.activate(HttpServerDestination.java:128) at org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:48) at org.apache.cxf.binding.AbstractBaseBindingFactory.addListener(AbstractBaseBindingFactory.java:97) at org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:836) at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127) at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:341) ... 15 more Caused by: java.net.BindException: Address already in use: bind at sun.nio.ch.Net.bind(Native Method) [:1.6.0_26] at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source) [:1.6.0_26] at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) [:1.6.0_26] at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:112) at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:47) at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:37) at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:126) at org.jboss.wsf.stack.cxf.addons.transports.httpserver.HttpServerEngine.addHandler(HttpServerEngine.java:94) ... 21 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues September 2011