August 2011 - switchyard-issues - Jboss List Archives

[JBoss JIRA] Created: (SWITCHYARD-425) BeanSwitchYardScanner is not able to scan a project if the path contains a plus sign

by Mario Antollini (JIRA)

BeanSwitchYardScanner is not able to scan a project if the path contains a plus sign ------------------------------------------------------------------------------------ Key: SWITCHYARD-425 URL: https://issues.jboss.org/browse/SWITCHYARD-425 Project: SwitchYard Issue Type: Bug Components: component-bean Affects Versions: 0.2 Environment: Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500) Java version: 1.6.0_24, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x", version: "10.6.7", arch: "x86_64", family: "mac" Reporter: Mario Antollini Priority: Minor When a project is located inside a path that contains a + sign, the BeanSwitchYardScanner fails. This can be as a quite unusual matter but in fact in my computer all the tests are run in a temp directory automatically generated which contains some + signs. -- 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-424) Reference binding for SOAP fails with NPE

by Keith Babo (JIRA)

Reference binding for SOAP fails with NPE ----------------------------------------- Key: SWITCHYARD-424 URL: https://issues.jboss.org/browse/SWITCHYARD-424 Project: SwitchYard Issue Type: Bug Components: component-soap Reporter: Keith Babo Assignee: Magesh Bojan Fix For: 0.2 Attachments: soapcamel.zip Deploy the attached application to AS7 and you'll get an NPE in soap component's OutboundHandler. Looks like this is coming from inside JAX-WS, but not sure why. I have attached a sample app to reproduce. 14:37:14,079 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC00001: Failed to start service jboss.deployment.unit."soapcamel.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."soapcamel.jar".SwitchYardService: java.lang.NullPointerException 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(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:680) [:1.6.0_26] Caused by: java.lang.NullPointerException at org.apache.cxf.jaxws.ServiceImpl.getJaxwsEndpoint(ServiceImpl.java:258) at org.apache.cxf.jaxws.ServiceImpl.createDispatch(ServiceImpl.java:618) at javax.xml.ws.Service.createDispatch(Service.java:368) [:1.6.0_26] at org.switchyard.component.soap.OutboundHandler.start(OutboundHandler.java:119) at org.switchyard.component.soap.deploy.SOAPActivator.start(SOAPActivator.java:100) at org.switchyard.deploy.internal.Activation.start(Deployment.java:477) at org.switchyard.deploy.internal.Deployment.deployReferenceBindings(Deployment.java:236) at org.switchyard.deploy.internal.Deployment.doStart(Deployment.java:118) 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 -- 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-423) merged config is not schema valid

by Keith Babo (JIRA)

merged config is not schema valid --------------------------------- Key: SWITCHYARD-423 URL: https://issues.jboss.org/browse/SWITCHYARD-423 Project: SwitchYard Issue Type: Bug Components: configuration Reporter: Keith Babo Assignee: David Ward Fix For: 0.2 errantepiphany: let's say I have an auto-generated config from a Camel Java DSL route that produces the following config: <composite xmlns="http://docs.oasis-open.org/ns/opencsa/sca/200912" name="soapcamel" targetNamespace="urn:switchyard:application:soapcamel"> <service name="MyTest" promote="MyTest"> <binding.soap xmlns="urn:switchyard-component-soap:config:1.0"> <wsdl>wsdl/Test.wsdl</wsdl> <serverPort>18000</serverPort> </binding.soap> </service> <component name="MyTestBuilder"> <implementation.camel xmlns="urn:switchyard-component-camel:config:1.0"> <java class="org.soapcamel.MyTestBuilder"/> </implementation.camel> <service name="MyTest"> <interface.java interface="org.soapcamel.MyTest"/> </service> </component> </composite> errantepiphany: but I want to add a reference to that generated config 1:15 lanceball is now known as lancelunch 1:15 kcbabo errantepiphany: the user's switchyard.xml just looks like this at first: <composite xmlns="http://docs.oasis-open.org/ns/opencsa/sca/200912" name="soapcamel" targetNamespace="urn:switchyard:application:soapcamel"> <service name="MyTest" promote="MyTest"> <binding.soap xmlns="urn:switchyard-component-soap:config:1.0"> <wsdl>wsdl/Test.wsdl</wsdl> <serverPort>18000</serverPort> </binding.soap> </service> </composite> errantepiphany: so I add this: <component name="MyTestBuilder"> <reference name="AnotherEndpoint"/> </component> 1:16 jgraham_ left the room (quit: Remote host closed the connection). 1:16 kcbabo errantepiphany: the merged config picks up the reference correctly, along with the other stufff errantepiphany: so that's all good errantepiphany: but the merged config is not schema valid 1:17 errantepiphany kcbabo: what does the merged config look like? 1:17 kcbabo <component name="MyTestBuilder"> <reference name="AnotherEndpoint"/> <implementation.camel xmlns="urn:switchyard-component-camel:config:1.0"> <java class="org.soapcamel.MyTestBuilder"/> </implementation.camel> <service name="MyTest"> <interface.java interface="org.soapcamel.MyTest"/> </service> </component> 1:17 errantepiphany: so reference is in the wrong spot -- 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-422) SOAP Forge facet is missing dependency on SwitchYard facet

by Keith Babo (JIRA)

SOAP Forge facet is missing dependency on SwitchYard facet ---------------------------------------------------------- Key: SWITCHYARD-422 URL: https://issues.jboss.org/browse/SWITCHYARD-422 Project: SwitchYard Issue Type: Bug Components: component-soap, tooling Affects Versions: 0.2 Reporter: Keith Babo Assignee: Tomohisa igarashi Fix For: 0.2 SOAPFacet is missing a dependency on SwitchYardFacet, which creates problems if you try and install the switchyard.soap facet in forge without installing the switchyard facet first. The SOAPFacet definition should look like this: {noformat} @Alias("switchyard.soap") @RequiresFacet({ DependencyFacet.class, PackagingFacet.class, SwitchYardFacet.class}) @RequiresPackagingType(PackagingType.JAR) public class SOAPFacet extends AbstractFacet { {noformat} -- 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-421) Generalized mechanism for context property handling

by Keith Babo (JIRA)

Generalized mechanism for context property handling --------------------------------------------------- Key: SWITCHYARD-421 URL: https://issues.jboss.org/browse/SWITCHYARD-421 Project: SwitchYard Issue Type: Feature Request Components: core Reporter: Keith Babo Fix For: 0.3 We need a consistent strategy and generalized mechanism for handling how component properties are mapped into context properties. Components need a way to map metadata (e.g. SOAP Headers from the SOAP component, File properties from Camel File gateway, etc.) into and out of context properties. For example, you should be able to get or set a SOAP header by manipulating a given context property at Scope.MESSAGE. In addition to the above, we need a way to customize how context properties are mapped. So the default strategy might be to copy all SOAP headers into a context property called soap.headers as a DOM tree. But this default composition strategy could be customized to pick certain headers out and set those under a given context property name. -- 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-420) Add a web service proxy quickstart

by Keith Babo (JIRA)

Add a web service proxy quickstart ---------------------------------- Key: SWITCHYARD-420 URL: https://issues.jboss.org/browse/SWITCHYARD-420 Project: SwitchYard Issue Type: Feature Request Components: quickstarts Reporter: Keith Babo Fix For: 0.3 Add a quickstart demonstrating web service proxying capabilities. This would most likely involve: - Camel route service which terminates with a switchyard:// reference - SOAP binding for camel route service - SOAP binding for the switchyard: reference in the route You will probably hit a few issues, with the following areas requiring fixes before the quickstart will work: 1) SOAP headers need to travel as context properties. The 2) Context properties need to flow into and out of Camel routes in a predictable manner 3) HTTP/S propagation -- 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-419) Separate API dependencies from component runtimes

by Keith Babo (JIRA)

Separate API dependencies from component runtimes ------------------------------------------------- Key: SWITCHYARD-419 URL: https://issues.jboss.org/browse/SWITCHYARD-419 Project: SwitchYard Issue Type: Feature Request Components: core, tooling Reporter: Keith Babo Fix For: 0.3 We need a clean way to separate out public interfaces of components from their runtime at a maven dependency level. At present, depending on a component drags in a ton of other maven dependencies, which is a total bummer. -- 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-418) Add testcase for quickstart/bpm-service deploying on AS7

by Tomohisa igarashi (JIRA)

Add testcase for quickstart/bpm-service deploying on AS7 -------------------------------------------------------- Key: SWITCHYARD-418 URL: https://issues.jboss.org/browse/SWITCHYARD-418 Project: SwitchYard Issue Type: Sub-task Components: quickstarts, test Affects Versions: 0.2 Reporter: Tomohisa igarashi Priority: Minor Fix For: 0.2 -- 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-417) Deployment error on AS7 when deploying more than one quickstart

by Rob Cernich (JIRA)

Deployment error on AS7 when deploying more than one quickstart --------------------------------------------------------------- Key: SWITCHYARD-417 URL: https://issues.jboss.org/browse/SWITCHYARD-417 Project: SwitchYard Issue Type: Bug Components: deployment Affects Versions: 0.2 Reporter: Rob Cernich Deploying all quickstarts on an AS7 SwitchYard build results in a failure, with no quickstarts being deployed. If the JAXB example is removed, deployment will succeed for all the other quickstarts. The JAXB quickstart can only be deployed by itself. It can be deployed before or after other quickstarts are deployed. The following is the stack trace produced during deployment: 07:45:59,951 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."switchyard-quickstart-transform-jaxb-0.2.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-quickstart-transform-jaxb-0.2.0-SNAPSHOT.jar".SwitchYardService: javax.xml.ws.WebServiceException: java.lang.RuntimeException: java.net.BindException: Address already in use 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(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:662) [:1.6.0_24] Caused by: javax.xml.ws.WebServiceException: java.lang.RuntimeException: java.net.BindException: Address already in use 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:478) 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 at org.jboss.wsf.stack.cxf.addons.transports.httpserver.HttpServerEngine.addHandler(HttpServerEngine.java:97) at org.jboss.wsf.stack.cxf.addons.transports.httpserver.HttpServerDestination.activate(HttpServerDestination.java:124) 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 at sun.nio.ch.ServerSocketChannelImpl.listen(Native Method) [:1.6.0_24] at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:127) [:1.6.0_24] at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [:1.6.0_24] 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:92) ... 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

[JBoss JIRA] Created: (SWITCHYARD-416) Add SwitchYard AS7 OpenShift Express distribution

by Magesh Bojan (JIRA)

Add SwitchYard AS7 OpenShift Express distribution ------------------------------------------------- Key: SWITCHYARD-416 URL: https://issues.jboss.org/browse/SWITCHYARD-416 Project: SwitchYard Issue Type: Feature Request Components: distribution Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.2 Create a release build that builds SwitchYard-As7 for OpenShift Express. This configuration will be identical to the one hosted in OpenShift Express and can be used for local testing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues August 2011