February 2012 - switchyard-issues

[JBoss JIRA] (SWITCHYARD-644) Fix release jar file names

by Nick Cross (JIRA)

Nick Cross created SWITCHYARD-644: ------------------------------------- Summary: Fix release jar file names Key: SWITCHYARD-644 URL: https://issues.jboss.org/browse/SWITCHYARD-644 Project: SwitchYard Issue Type: Task Reporter: Nick Cross Fix For: 0.4 Due to POM changes fusesource/jaxen are being incorrectly packaged e.g. ./jboss-as7/standalone/dist/target/switchyard-as7-0.4/modules/org/jaxen/main/jaxen-${version.jaxen}.jar ./jboss-as7/standalone/dist/target/jboss-switchyard/jboss-as-7.1.0.CR1b/modules/org/fusesource/commonman/main/commons-management-${version.fusesource.commonman}.jar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-643) Upgrade Junit to use AS7 version.

by Nick Cross (JIRA)

Nick Cross created SWITCHYARD-643: ------------------------------------- Summary: Upgrade Junit to use AS7 version. Key: SWITCHYARD-643 URL: https://issues.jboss.org/browse/SWITCHYARD-643 Project: SwitchYard Issue Type: Task Reporter: Nick Cross Fix For: 0.4 Junit is currently using 4.8.1. AS7 BOM provides 4.10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-642) Enable some quickstart execution tests that is disabled because of JBWS-3424

by Tomohisa igarashi (JIRA)

Tomohisa igarashi created SWITCHYARD-642: -------------------------------------------- Summary: Enable some quickstart execution tests that is disabled because of JBWS-3424 Key: SWITCHYARD-642 URL: https://issues.jboss.org/browse/SWITCHYARD-642 Project: SwitchYard Issue Type: Task Components: distribution, quickstarts, test Reporter: Tomohisa igarashi Fix For: 0.5 Once a AS7 includes the fix for JBWS-3424 is released, we need to enable some quickstart tests on release build: * CamelServiceQuickstartTest * RulesInterviewAgentQuickstartTest * RulesInterviewQuickstartTest * HornetqReferenceBindingQuickstartTest -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-641) NPE in Weld during startup

by Rob Cernich (JIRA)

Rob Cernich created SWITCHYARD-641: -------------------------------------- Summary: NPE in Weld during startup Key: SWITCHYARD-641 URL: https://issues.jboss.org/browse/SWITCHYARD-641 Project: SwitchYard Issue Type: Bug Reporter: Rob Cernich The following happens about half the time I start the server. The following quickstarts are deployed: demo/orders, bean-service, transform-jaxb, transform-json. (Note, this may be environmental as I installed SY using a local installer build, which had configuration issues that needed to be cleaned up manually.) 13:35:02,950 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."switchyard-quickstart-transform-jaxb-0.4.0-SNAPSHOT.jar".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-quickstart-transform-jaxb-0.4.0-SNAPSHOT.jar".WeldService: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: Exception 0 : java.lang.NullPointerException at org.jboss.weld.manager.BeanManagerImpl.getMostSpecializedBean(BeanManagerImpl.java:931) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:605) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:228) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:207) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46) at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:46) at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:322) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:80) at org.jboss.as.weld.services.WeldService.start(WeldService.java:89) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) at org.jboss.as.weld.services.WeldService.start(WeldService.java:96) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_30] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_30] at java.lang.Thread.run(Thread.java:662) [:1.6.0_30] Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: Exception 0 : java.lang.NullPointerException at org.jboss.weld.manager.BeanManagerImpl.getMostSpecializedBean(BeanManagerImpl.java:931) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:605) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:228) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:207) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46) at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:46) at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:322) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:80) at org.jboss.as.weld.services.WeldService.start(WeldService.java:89) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:48) at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:46) at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:322) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:80) at org.jboss.as.weld.services.WeldService.start(WeldService.java:89) ... 5 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-640) Create web app demo that showcases switchyard bpm task api

by David Ward (JIRA)

David Ward created SWITCHYARD-640: ------------------------------------- Summary: Create web app demo that showcases switchyard bpm task api Key: SWITCHYARD-640 URL: https://issues.jboss.org/browse/SWITCHYARD-640 Project: SwitchYard Issue Type: Task Components: component-bpm, quickstarts Affects Versions: 0.3 Reporter: David Ward Assignee: David Ward Fix For: 0.4 A simple jsp/jsf app should be sufficient. It just needs to use the api introduced in SWITCHYARD-635. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-639) NPE thrown when transformer class not on classpath.

by Marek Baluch (JIRA)

Marek Baluch created SWITCHYARD-639: --------------------------------------- Summary: NPE thrown when transformer class not on classpath. Key: SWITCHYARD-639 URL: https://issues.jboss.org/browse/SWITCHYARD-639 Project: SwitchYard Issue Type: Bug Components: transformation Affects Versions: 0.3 Reporter: Marek Baluch When a transformer class is defined and is not on classpath then a NPE is thrown. IMO this should be handled with an error message. e.g. {code} <transforms> <transform.java xmlns="urn:switchyard-config:transform:1.0" class="org.missing.clazz.Transformers" from="{urn:switchyard-quickstart:bean-service:1.0}helloRequest" to="java:java.lang.String"/> </transforms> {code} {noformat} 10:15:53,491 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."bean-service-0.3.0.Final.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."bean-service-0.3.0.Final.jar".SwitchYardService: org.switchyard.exception.SwitchYardException: Error constructing Transformer instance for class 'org.jboss.cdi.defconf.Transformers'. at ... (legt out) Caused by: java.lang.NullPointerException at org.switchyard.transform.TransformerUtil.isTransformer(TransformerUtil.java:217) at org.switchyard.transform.TransformerUtil.newTransformers(TransformerUtil.java:112) at org.switchyard.transform.TransformerUtil.newTransformers(TransformerUtil.java:71) ... 11 more {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-638) WSDLUtil is unable to handle WSDL message definitions with type attribute.

by Marek Baluch (JIRA)

Marek Baluch created SWITCHYARD-638: --------------------------------------- Summary: WSDLUtil is unable to handle WSDL message definitions with type attribute. Key: SWITCHYARD-638 URL: https://issues.jboss.org/browse/SWITCHYARD-638 Project: SwitchYard Issue Type: Bug Components: component-soap Affects Versions: 0.3 Reporter: Marek Baluch If I have the following message definition: {code} <wsdl:message name="GreetingTarget_Message"> <wsdl:part name="ToWhom" type="xsd:string"/> </wsdl:message> {code} then WSDLUtil throws an NPE with the following stack-trace: {noformat} To has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault at org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:155) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.createFault(AbstractJAXWSMethodInvoker.java:86) [cxf-rt-frontend-jaxws-2.4.1.jar:2.4.1] at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:121) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:61) [cxf-rt-frontend-jaxws-2.4.1.jar:2.4.1] at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:75) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58) [cxf-rt-core-2.4.1.jar:2.4.1] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_16] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_16] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_16] at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263) [cxf-api-2.4.1.jar:2.4.1] at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:118) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.transport.http_jaxws_spi.JAXWSHttpSpiDestination.serviceRequest(JAXWSHttpSpiDestination.java:147) [cxf-rt-frontend-jaxws-2.4.1.jar:2.4.1] at org.apache.cxf.transport.http_jaxws_spi.JAXWSHttpSpiDestination.doService(JAXWSHttpSpiDestination.java:123) [cxf-rt-frontend-jaxws-2.4.1.jar:2.4.1] at org.apache.cxf.transport.http_jaxws_spi.HttpHandlerImpl.handle(HttpHandlerImpl.java:61) [cxf-rt-frontend-jaxws-2.4.1.jar:2.4.1] at org.jboss.wsf.stack.cxf.addons.transports.httpserver.HttpServerDestination$Handler.handle(HttpServerDestination.java:154) [jbossws-cxf-transports-httpserver-4.0.0.Beta3.jar:4.0.0.Beta3] at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:80) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:689) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:661) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_16] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_16] at java.lang.Thread.run(Thread.java:619) [:1.6.0_16] Caused by: java.lang.NullPointerException at org.switchyard.component.soap.util.WSDLUtil.getOperation(WSDLUtil.java:237) [switchyard-component-soap-0.3.0.Final.jar:0.3.0.Final] at org.switchyard.component.soap.InboundHandler.invoke(InboundHandler.java:187) [switchyard-component-soap-0.3.0.Final.jar:0.3.0.Final] at org.switchyard.component.soap.BaseWebService.invoke(BaseWebService.java:69) [switchyard-component-soap-0.3.0.Final.jar:0.3.0.Final] at org.switchyard.component.soap.BaseWebService.invoke(BaseWebService.java:34) [switchyard-component-soap-0.3.0.Final.jar:0.3.0.Final] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_16] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_16] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_16] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_16] at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:173) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:89) [cxf-rt-core-2.4.1.jar:2.4.1] ... 23 more {noformat} The reason for this is that it attempts to get the localPart from an elementName instead of typeName. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-637) Add a capability to connect to remote HornetQ server on HornetQMixIn

by Tomohisa igarashi (JIRA)

Tomohisa igarashi created SWITCHYARD-637: -------------------------------------------- Summary: Add a capability to connect to remote HornetQ server on HornetQMixIn Key: SWITCHYARD-637 URL: https://issues.jboss.org/browse/SWITCHYARD-637 Project: SwitchYard Issue Type: Enhancement Components: test Affects Versions: 0.4 Reporter: Tomohisa igarashi Fix For: 0.4 Currently HornetQMixIn uses EmbeddedJMS server, but connecting to existing remote HornetQ server is also needed to test actual deployment on AS7, that should be tested in release build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-636) Adding BPEL console needed libraries into SwitchYard BPEL component.

by Jeff Yu (JIRA)

Jeff Yu created SWITCHYARD-636: ---------------------------------- Summary: Adding BPEL console needed libraries into SwitchYard BPEL component. Key: SWITCHYARD-636 URL: https://issues.jboss.org/browse/SWITCHYARD-636 Project: SwitchYard Issue Type: Feature Request Components: component-bpel Affects Versions: 0.3 Reporter: Jeff Yu Fix For: 0.4 Need to add about 5 jars that required by BPEL console, also two modules (one is the batik, the other one is jettison) in the external modules. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa 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 February 2012