March 2012 - switchyard-issues - Jboss List Archives

[JBoss JIRA] (SWITCHYARD-712) BPEL invocation of missing service (404) currently throws exception

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-712: ------------------------------------- Summary: BPEL invocation of missing service (404) currently throws exception Key: SWITCHYARD-712 URL: https://issues.jboss.org/browse/SWITCHYARD-712 Project: SwitchYard Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 0.5 Issue found during investigation of SWITCHYARD-674 {noformat} 23:29:02,334 ERROR [org.switchyard.internal.DefaultHandlerChain] (pool-10-thread-1) org.switchyard.HandlerException was thrown by handler(provider): java.lang.Exception: java.lang.RuntimeException: org.apache.ode.bpel.iapi.ContextException: Failed to invoke external service --- Caused by java.lang.Exception: java.lang.RuntimeException: org.apache.ode.bpel.iapi.ContextException: Failed to invoke external service --- Caused by org.apache.ode.bpel.iapi.Scheduler$JobProcessorException: java.lang.RuntimeException: org.apache.ode.bpel.iapi.ContextException: Failed to invoke external service --- Caused by java.lang.RuntimeException: org.apache.ode.bpel.iapi.ContextException: Failed to invoke external service --- Caused by org.apache.ode.bpel.iapi.ContextException: Failed to invoke external service --- Caused by org.switchyard.exception.SwitchYardException: Cannot convert from 'org.switchyard.HandlerException' to 'org.w3c.dom.Node'. No registered Transformer available for transforming from 'java:org.switchyard.HandlerException' to 'java:org.w3c.dom.Node'. A Transformer must be registered. {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, 1 month

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-711) Add a forge command to create a reference in a bean service

by Mario Antollini (JIRA)

Mario Antollini created SWITCHYARD-711: ------------------------------------------ Summary: Add a forge command to create a reference in a bean service Key: SWITCHYARD-711 URL: https://issues.jboss.org/browse/SWITCHYARD-711 Project: SwitchYard Issue Type: Feature Request Components: tooling Reporter: Mario Antollini Fix For: 0.4 Add a new forge command (specific to bean service) which helps create a reference to another service. Should be something like this: bean-reference create —serviceName —referenceName -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-710) Allow direct storage of XML Nodes as Context properties from ContextMappers

by David Ward (JIRA)

David Ward created SWITCHYARD-710: ------------------------------------- Summary: Allow direct storage of XML Nodes as Context properties from ContextMappers Key: SWITCHYARD-710 URL: https://issues.jboss.org/browse/SWITCHYARD-710 Project: SwitchYard Issue Type: Enhancement Components: component-soap, core, docs Affects Versions: 0.3, 0.4 Reporter: David Ward Assignee: David Ward Fix For: 0.5 What started as a discussion regarding the behavior of SOAPContextMapper I believe should be a broader-scoped enhancement to ContextMappers in general. Right now, soap header elements are being deconstructed by using their name as the context property key, and their string value as the context property value. This does not take into consideration more complex use cases such as when an entire XML (sub-)tree needs to be stored for things like xml TX/security propagation, as required by SWITCHYARD-703. Thus a configuration property on <contextMapper/> should be added so that the entire Node can be carried along as-is. I do believe that the default behavior, however, should be kept as it is now, since for most cases I think just a simple value is sufficient. How is this a bigger issue than SOAPContextMappers? Well, we need to go through the other implementations to make sure values won't be assumed as simple Strings all the time. One thing I noticed right away is the HornetQContextMapper, which gets values out using source.getStringProperty instead of getObjectProperty. We need consistency across the ContextMappers. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-709) BPEL component closes the BPEL Engine when any deployment is removed

by Magesh Bojan (JIRA)

Magesh Bojan created SWITCHYARD-709: --------------------------------------- Summary: BPEL component closes the BPEL Engine when any deployment is removed Key: SWITCHYARD-709 URL: https://issues.jboss.org/browse/SWITCHYARD-709 Project: SwitchYard Issue Type: Bug Components: component-bpel Affects Versions: 0.4 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.4 When a deployment containing BPEL files is un-deployed the BPEL Engine is closed and the following error is thrown: {noformat} 19:27:50,437 ERROR [org.riftsaw.engine.internal.BPELEngineImpl] (pool-11-thread-1) Exception occured while invoking ODE: java.lang.NullPointerException at org.riftsaw.engine.internal.BPELEngineImpl.invoke(BPELEngineImpl.java:696) [engine-3.0.0.20120316-M2.jar:] at org.switchyard.component.bpel.riftsaw.RiftsawBPELExchangeHandler.handleMessage(RiftsawBPELExchangeHandler.java:236) [switchyard-component-bpel-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.internal.DefaultHandlerChain.handleMessage(DefaultHandlerChain.java:148) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.internal.DefaultHandlerChain.handle(DefaultHandlerChain.java:121) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.internal.LocalDispatcher.dispatch(LocalExchangeBus.java:72) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.internal.ExchangeImpl.sendInternal(ExchangeImpl.java:267) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.internal.ExchangeImpl.send(ExchangeImpl.java:184) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.component.soap.InboundHandler.invoke(InboundHandler.java:218) [switchyard-component-soap-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.component.soap.BaseWebService.invoke(BaseWebService.java:69) [switchyard-component-soap-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.component.soap.BaseWebService.invoke(BaseWebService.java:34) [switchyard-component-soap-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.6.0_30] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.6.0_30] at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.6.0_30] at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:173) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:89) at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:61) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:75) at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.6.0_30] at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.6.0_30] at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.6.0_30] at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) at org.apache.cxf.transport.http_jaxws_spi.JAXWSHttpSpiDestination.serviceRequest(JAXWSHttpSpiDestination.java:145) at org.apache.cxf.transport.http_jaxws_spi.JAXWSHttpSpiDestination.doService(JAXWSHttpSpiDestination.java:121) at org.apache.cxf.transport.http_jaxws_spi.HttpHandlerImpl.handle(HttpHandlerImpl.java:61) at org.jboss.wsf.stack.cxf.addons.transports.httpserver.HttpServerDestination$Handler.handle(HttpServerDestination.java:154) [jbossws-cxf-transports-httpserver-4.0.1.GA.jar:4.0.1.GA] 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:710) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_30] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_30] at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_30] {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, 1 month

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-708) Add JCA gateway

by Tomohisa igarashi (JIRA)

Tomohisa igarashi created SWITCHYARD-708: -------------------------------------------- Summary: Add JCA gateway Key: SWITCHYARD-708 URL: https://issues.jboss.org/browse/SWITCHYARD-708 Project: SwitchYard Issue Type: Feature Request Components: core Affects Versions: 0.5 Reporter: Tomohisa igarashi Assignee: Tomohisa igarashi Fix For: 0.5 Add an gateway implementation for JCA Message inflow -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-707) POM Build improvements for console

by Nick Cross (JIRA)

Nick Cross created SWITCHYARD-707: ------------------------------------- Summary: POM Build improvements for console Key: SWITCHYARD-707 URL: https://issues.jboss.org/browse/SWITCHYARD-707 Project: SwitchYard Issue Type: Task Reporter: Nick Cross Priority: Minor Fix For: 0.4 Compiling GWT permuations was crashing out on my machine - upping the JVM args from 512 to 1024 fixed it for me. Adding explicit versions for jbossas.console prevents issues if the version has been defined as a range. And finally during unpack of the source, exclude signing information to prevent clashes. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-706) Rules service should be called with message type declared in its interface

by Jachym Culka (JIRA)

Jachym Culka created SWITCHYARD-706: --------------------------------------- Summary: Rules service should be called with message type declared in its interface Key: SWITCHYARD-706 URL: https://issues.jboss.org/browse/SWITCHYARD-706 Project: SwitchYard Issue Type: Enhancement Components: component-rules Affects Versions: 0.4 Reporter: Jachym Culka Priority: Minor When calling a rules service, it doesn't matter what type is defined in drools interface, the argument is simply passed to drools engine without any transformation. I'd expect it to be converted into the type that is actually declared in its interface. To test this, you can simply change the type of the method argument of the drools interface in switchyard-quickstart-rules-interview to something else and the tests will still run sucessfully. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-705) Allow port configuration to be overloaded via system/test property

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-705: ------------------------------------- Summary: Allow port configuration to be overloaded via system/test property Key: SWITCHYARD-705 URL: https://issues.jboss.org/browse/SWITCHYARD-705 Project: SwitchYard Issue Type: Enhancement Components: test Reporter: Keith Babo Fix For: 0.5 Problem : you cannot run unit tests that bind to a port (e.g. 18001) at the same time an application is deployed to a running AS7 instance using the same port. This is incredibly annoying. Solution : support substitution of binding values via environment configuration and/or application configuration. The easy and quick solution piggy backs on the existing socket-binding support used for AS7 to allow a test case to be configured to use an alternate port during test runs. There should be a test API hook for this so you can call it in your test code and there should also be a way to inject it through a system property (e.g. mvn -D ). A more comprehensive solution looks at application properties as specified in SCA and ties all of this together using that. Like a binding URI could contain a property key and said key could resolve against different values for test execution and runtime execution. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-704) Report service metrics at operation-level

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-704: ------------------------------------- Summary: Report service metrics at operation-level Key: SWITCHYARD-704 URL: https://issues.jboss.org/browse/SWITCHYARD-704 Project: SwitchYard Issue Type: Enhancement Components: admin Affects Versions: 0.4 Reporter: Keith Babo Fix For: 0.5 We need to track service metrics down to the operation level. Right now, we just do it at service level. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-703) Propagate message headers between switchyard and riftsaw

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-703: ------------------------------------- Summary: Propagate message headers between switchyard and riftsaw Key: SWITCHYARD-703 URL: https://issues.jboss.org/browse/SWITCHYARD-703 Project: SwitchYard Issue Type: Feature Request Reporter: Gary Brown Currently only the message content is passed in and out of the bpel component. However for transaction and security purposes, it will be necessary for the header information to be passed between switchyard and riftsaw. -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues March 2012