January 2012 - switchyard-issues - Jboss List Archives

[JBoss JIRA] (SWITCHYARD-635) Provide implementation-agnostic way for users' applications to control BPM tasks

by David Ward (JIRA)

David Ward created SWITCHYARD-635: ------------------------------------- Summary: Provide implementation-agnostic way for users' applications to control BPM tasks Key: SWITCHYARD-635 URL: https://issues.jboss.org/browse/SWITCHYARD-635 Project: SwitchYard Issue Type: Enhancement Components: component-bpm, quickstarts Affects Versions: 0.3 Reporter: David Ward Assignee: David Ward Fix For: 0.4 The API will not be bound to jBPM, however the only implementation we will provide now is jBPM. The API should provide querying, claiming, starting, completing and aborting of tasks. Additionally, this ability should be demonstrable in a quickstart. -- 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-634) Camel endpoint for reference binding is not destroyed after application undeployment

by Robert Balent (JIRA)

Robert Balent created SWITCHYARD-634: ---------------------------------------- Summary: Camel endpoint for reference binding is not destroyed after application undeployment Key: SWITCHYARD-634 URL: https://issues.jboss.org/browse/SWITCHYARD-634 Project: SwitchYard Issue Type: Bug Components: core Affects Versions: 0.3 Reporter: Robert Balent Fix For: 0.4 Attachments: reference_binding_server.log, switchyard.xml I've created simple application with camel file:// binding input, one bean injecting XML route, XML route and file:// reference binding output. The problem is that when application is undeployed the reference binding stays still active and is not destroyed. In log you can see: * Creating endpoint uri=\[file:///home/rbalent/temp/sw-input], path=[/home/rbalent/temp/sw-input], parameters=[{}] and when file is consumed * Creating endpoint uri=\[file:///home/rbalent/temp/sw-output], path=[/home/rbalent/temp/sw-output], parameters=[{}] But in undeployment process there is not even mention about the second endpoint. It stays still active. Of course file: endpoint can't consume any message but when I've tried it with camel-irc component it stays connected to irc server after application undeployment. My switchyard.xml and full AS7 server.log with notes when application deployment and undeployment started is attached. -- 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-633) simple_correlation quickstart for BPEL component.

by Jeff Yu (JIRA)

Jeff Yu created SWITCHYARD-633: ---------------------------------- Summary: simple_correlation quickstart for BPEL component. Key: SWITCHYARD-633 URL: https://issues.jboss.org/browse/SWITCHYARD-633 Project: SwitchYard Issue Type: Task Components: quickstarts Affects Versions: 0.3 Reporter: Jeff Yu Fix For: 0.4 Migrated the simple_correlation example into SwitchYard 04. (RiftSaw 3) -- 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-632) CDI references are not injected if the service is not contained in the project or is not referenced by another service

by Rob Cernich (JIRA)

Rob Cernich created SWITCHYARD-632: -------------------------------------- Summary: CDI references are not injected if the service is not contained in the project or is not referenced by another service Key: SWITCHYARD-632 URL: https://issues.jboss.org/browse/SWITCHYARD-632 Project: SwitchYard Issue Type: Bug Components: component-bean, deployment Reporter: Rob Cernich Assignee: Rob Cernich This prohibits services from being referenced by non-SwitchYard code. Any @Reference within a project should cause a component to be generated within the switchyard.xml file which defines the reference. In addition to the above, a test case should be added to ensure the reference is resolved even when no other CDI services exist. For example: 1. Create a Camel or Rule service. 2. Create a Java class that references the service. 3. Verify that the reference is injected correctly. -- 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-631) Integrate SwitchYard console into AS7 console

by Rob Cernich (JIRA)

Rob Cernich created SWITCHYARD-631: -------------------------------------- Summary: Integrate SwitchYard console into AS7 console Key: SWITCHYARD-631 URL: https://issues.jboss.org/browse/SWITCHYARD-631 Project: SwitchYard Issue Type: Enhancement Components: console, distribution Reporter: Rob Cernich Assignee: Rob Cernich Fix For: 0.4 Move SwitchYard console functionality into the AS7 console. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-630) Application ClassLoader should be passed via deployer

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-630: ------------------------------------- Summary: Application ClassLoader should be passed via deployer Key: SWITCHYARD-630 URL: https://issues.jboss.org/browse/SWITCHYARD-630 Project: SwitchYard Issue Type: Enhancement Components: component-camel, component-hornetq, component-soap, deployment Reporter: Keith Babo Fix For: 0.4 Several gateways are doing something like this to set the class loader for incoming messages: ClassLoader origCL = Thread.currentThread().getContextClassLoader(); try { Thread.currentThread().setContextClassLoader(anotherCL); } finally { Thread.currentThread().setContextClassLoader(origCL); } We should create a standard slot for the application loader and pass that in through init in the component's activator (or something equivalent). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-629) Switchyard Application simulation support

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-629: ------------------------------------- Summary: Switchyard Application simulation support Key: SWITCHYARD-629 URL: https://issues.jboss.org/browse/SWITCHYARD-629 Project: SwitchYard Issue Type: Feature Request Reporter: Gary Brown Would like to simulate switchyard applications from within Savara, using a scenario (i.e. sequence diagram) with example messages. The tooling will primarily be used from within Eclipse, although can also be used outside this environment. To support enhancements and additions to switchyard, would prefer to point the Eclipse environment at an external installation of switchyard - i.e. so the user is not dependent upon a single version of switchyard bundled with the Eclipse plugins. Reason for mentioning this, is that selective classpath (to not include bindings) is not going to be easy with this approach, as it would require the user to configure their environment with knowledge of which jars to select. The aim would be to have a component that I could initialise with a switchyard.xml, with any relevant classes/resources being in the classpath. Reason for specifying the location of the switchyard.xml, rather than just picking up from classpath, is that the simulator may be simulating more than one switchyard application at the same time (i.e. different apps playing different participants within a choreography - simulating the end to end business transaction). The only difference from normal initialisation is that the bindings should not be initialised, and instead would interact with this simulation component, so inbound messages would be provided by the simulation container, and messages sent by the switchyard application would be received/handled by the simulation container. Each component instance should be a separate switchyard environment, to avoid conflicts with other components running different switchyard apps, and should support a 'close' method to tidyup its environment - i.e. its possible a session may be terminated mid way, if the scenario represents just a partial transaction. It would also be useful to be able to determine that a session was still active, to know further messages are expected. For simplicity the component could provide a synchronous invoke method, that takes the message and an optional name that can be used to specify the source binding (where multiple have been defined), but if not specified and only a single source binding, then the message should be routed as if it came from that source binding. If no name is defined, and multiple possible bindings exist, then an exception should be thrown. A callback interface should be provided that will be invoked to handle external service invocations (i.e. that would normally be routed via a reference binding). This interface should offer one-way and request/response variations, and supply the outbound message and the target binding name. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-628) WS-Security support

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-628: ------------------------------------- Summary: WS-Security support Key: SWITCHYARD-628 URL: https://issues.jboss.org/browse/SWITCHYARD-628 Project: SwitchYard Issue Type: Feature Request Reporter: Gary Brown Riftsaw (BPEL engine) version 2, when deployed to JBossAS 5/6 uses jbossws to provide web service support, and leverages its WS-Security capabilities to provide secure services. Now that Riftsaw is embedded as the BPEL component in Switchyard, just wondering how secure web services would be provided? Will WS-Security be supported? -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-627) SOAP binding RPC style support

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-627: ------------------------------------- Summary: SOAP binding RPC style support Key: SWITCHYARD-627 URL: https://issues.jboss.org/browse/SWITCHYARD-627 Project: SwitchYard Issue Type: Feature Request Reporter: Gary Brown Currently the SOAP binding supports doclit style. However the RPC style is also popular and may be used to define the wsdl contract (in a contract driven methodology) or used by external services being consumed. Therefore ideally the SOAP binding should also support this style. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-626) Make sure to use correct TCCL when acceessing a CDI bean

by Tomohisa igarashi (JIRA)

Tomohisa igarashi created SWITCHYARD-626: -------------------------------------------- Summary: Make sure to use correct TCCL when acceessing a CDI bean Key: SWITCHYARD-626 URL: https://issues.jboss.org/browse/SWITCHYARD-626 Project: SwitchYard Issue Type: Bug Components: component-bean Affects Versions: 0.4 Reporter: Tomohisa igarashi You will see following error when you access a CDI bean from hornetq-binding service. According to https://issues.jboss.org/browse/AS7-2496 , the thread context class loader should be a one that is used to load that CDI bean. hornetq-binding service is invoked as a HornetQ client thread so the context class loader come from HornetQ. That should be switched when accessing a CDI bean. {quote} java.lang.IllegalStateException: Singleton not set for ModuleClassLoader for Module "org.hornetq:main" from local module loader @36d1c778 (roots: /opt/switchyard-as7-0.4/modules) {quote} -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues January 2012