June 2011 - switchyard-issues - Jboss List Archives

[JBoss JIRA] Created: (SWITCHYARD-329) Add BPM annotations to mark methods as process action triggers

by David Ward (JIRA)

Add BPM annotations to mark methods as process action triggers -------------------------------------------------------------- Key: SWITCHYARD-329 URL: https://issues.jboss.org/browse/SWITCHYARD-329 Project: SwitchYard Issue Type: Enhancement Components: component-bpm Reporter: David Ward Assignee: David Ward Fix For: 0.2 Per the discussion in the Forum Reference (see jira link), adding @StartProcess, @SignalEvent and @AbortProcess method-level annotations would allow the developer to declaratively designate which service invocations will result in what type of process action to trigger. Additionally, the @BPM class-level annotation should change to @Process to maintain consistency in naming, and all 4 annotations should move to a new org.switchyard.component.bpm.annotation(s?) package. -- 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

[JBoss JIRA] Created: (SWITCHYARD-328) bump distribution version to 0.2

by Keith Babo (JIRA)

bump distribution version to 0.2 -------------------------------- Key: SWITCHYARD-328 URL: https://issues.jboss.org/browse/SWITCHYARD-328 Project: SwitchYard Issue Type: Task Components: distribution Reporter: Keith Babo Assignee: Keith Babo Fix For: 0.2 The distro versions are currently set to 0.1: switchyard-as7-0.1 switchyard-as6-0.1 -- 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

[JBoss JIRA] Created: (SWITCHYARD-327) Create a Forge plugin for the BPM component

by David Ward (JIRA)

Create a Forge plugin for the BPM component ------------------------------------------- Key: SWITCHYARD-327 URL: https://issues.jboss.org/browse/SWITCHYARD-327 Project: SwitchYard Issue Type: Feature Request Components: component-bpm, tooling Reporter: David Ward Assignee: Keith Babo Fix For: 0.2 We need to add a switchyard-forge-bpm-plugin, similar to our existing bean, soap, camel and clojure ones. The information that can be prompted for matches the properties of the models found in org.switchyard.component.bpm.config.model. <component name="defaults to ${ServiceInterfaceName}"> <service name="defaults to ${ServiceInterfaceName}"> <interface.java interface="${ServiceInterfaceClass}"/> </service> <implementation.bpm processDefinition="file://, http://, https://, or classpath path, defaults to META-INF/${ServiceInterfaceName}.bpmn", processDefinitionType="a ProcessResourceType, defaults to BPMN2", processId="id of the process in the processDefinition, defaults to ${ServiceInterfaceName}", messageContentName="name of the jBPM process instance variable holding the SwitchYard message content, defaults to ProcessConstants.MESSAGE_CONTENT_NAME_VAR"> <processResource location="file://, http://, https://, or classpath path, required", type="a ProcessResourceType, required"/> (0..*) <taskHandler class="the class name, duh!", name="defaults to taskHandlerImpl.getName()"/> (0..*) </implementation.bpm> </component> An example switchyard.xml config with the above completed can be seen here: http://community.jboss.org/wiki/SwitchYardBPMComponent -- 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

[JBoss JIRA] Created: (SWITCHYARD-326) Camel JMS Route throws NullPointerException when the route is stopped.

by Daniel Bevenius (JIRA)

Camel JMS Route throws NullPointerException when the route is stopped. ---------------------------------------------------------------------- Key: SWITCHYARD-326 URL: https://issues.jboss.org/browse/SWITCHYARD-326 Project: SwitchYard Issue Type: Bug Components: component-camel Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 0.2 The following NullPointerException can be seen in the logs when A Camel JMS route is stopped: {noformat} 8:04:19,257 INFO [impl.DefaultShutdownStrategy] Route: SimpleCamelService-[jms://TestQueue?connectionFactory=#ConnectionFactory] suspended and shutdown deferred, was consuming from: Endpoint[jms://TestQueue?connectionFactory=%23ConnectionFactory] 08:04:19,258 WARN [impl.DefaultShutdownStrategy] Error occurred while shutting down route: Consumer[jms://TestQueue?connectionFactory=%23ConnectionFactory]. This exception will be ignored. java.lang.NullPointerException at org.apache.camel.component.jms.JmsConsumer.doStop(JmsConsumer.java:130) at org.apache.camel.impl.ServiceSupport.stop(ServiceSupport.java:98) at org.apache.camel.impl.ServiceSupport.stop(ServiceSupport.java:122) at org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:108) at org.apache.camel.impl.DefaultShutdownStrategy.shutdownNow(DefaultShutdownStrategy.java:248) at org.apache.camel.impl.DefaultShutdownStrategy$ShutdownTask.run(DefaultShutdownStrategy.java:475) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) 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:680) 08:04:19,258 INFO [impl.DefaultShutdownStrategy] Route: SimpleCamelService-[jms://TestQueue?connectionFactory=#ConnectionFactory] shutdown complete. 08:04:19,259 INFO [impl.DefaultShutdownStrategy] Graceful shutdown of 1 routes completed in 0 seconds {noformat} By stepping through this it seems like Camel is trying to stop the route twice, once which is triggered by SwitchYard's InboundHandler and a second time by Camel. The second call is what is producing this NPE. -- 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

[JBoss JIRA] Created: (SWITCHYARD-325) Allow developer-defined correlationId to refer to BPM processes in addition to processInstanceId

by David Ward (JIRA)

Allow developer-defined correlationId to refer to BPM processes in addition to processInstanceId ------------------------------------------------------------------------------------------------ Key: SWITCHYARD-325 URL: https://issues.jboss.org/browse/SWITCHYARD-325 Project: SwitchYard Issue Type: Feature Request Components: component-bpm Reporter: David Ward Assignee: David Ward Fix For: 0.2 Currently, a processInstanceId variable is required to be passed back-and-forth with the DroolsBPMExchangeHandler so that we know which process instance should be interacted with (signaling and aborting, for example). It would be useful for a developer to be able to specify their own correlation id (perhaps a pre-existing application-specific one) instead of having to use the process instance id that we key off of internally. -- 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

[JBoss JIRA] Created: (SWITCHYARD-324) Auto-start processes if processActionType header is unspecified

by David Ward (JIRA)

Auto-start processes if processActionType header is unspecified --------------------------------------------------------------- Key: SWITCHYARD-324 URL: https://issues.jboss.org/browse/SWITCHYARD-324 Project: SwitchYard Issue Type: Feature Request Components: component-bpm Reporter: David Ward Assignee: David Ward Fix For: 0.2 Inside DroolsBpmExchangeHandler ( http://goo.gl/i0LML ), a processActionType context property is required for any work to be done. Changing this behavior to assume a default processActionType of startProcess would be desirable. -- 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

[JBoss JIRA] Created: (SWITCHYARD-323) Add BPMMixin to switchyard-test

by David Ward (JIRA)

Add BPMMixin to switchyard-test ------------------------------- Key: SWITCHYARD-323 URL: https://issues.jboss.org/browse/SWITCHYARD-323 Project: SwitchYard Issue Type: Enhancement Components: component-bpm Reporter: David Ward Assignee: David Ward Fix For: 0.2 A lot of work is done in HelpDeskTests ( http://goo.gl/3Qc9S ) just to start and stop the human task server, as well as automatically complete human tasks. Introducing a BPMMixin (alongside the HTTPMixin and CDIMixin) to do this work will alleviate the test author from having to write that code him/herself. -- 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

[JBoss JIRA] Created: (SWITCHYARD-322) Support service name on @Service annotation

by Keith Babo (JIRA)

Support service name on @Service annotation ------------------------------------------- Key: SWITCHYARD-322 URL: https://issues.jboss.org/browse/SWITCHYARD-322 Project: SwitchYard Issue Type: Enhancement Components: component-bean Affects Versions: 0.2 Reporter: Keith Babo Fix For: 0.2 We need to allow service name to be specified as an optional element of the @Service annotation. See forum discussion for more info. -- 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

[JBoss JIRA] Created: (SWITCHYARD-321) Deployment class Activation Lists will continually grow through multiple stop/start cycles

by Tom Fennelly (JIRA)

Deployment class Activation Lists will continually grow through multiple stop/start cycles ------------------------------------------------------------------------------------------ Key: SWITCHYARD-321 URL: https://issues.jboss.org/browse/SWITCHYARD-321 Project: SwitchYard Issue Type: Bug Components: core Reporter: Tom Fennelly Priority: Minor Fix For: 0.2 Deployment.start() adds Activation instances to a number of different Lists. Stop calls stop on these Activation instances, but does not remove them from the underlying List. Follow this by another call to Deployment.start() (restart) and we add more Activation instances. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-320) Improve sorting logic of fallback transformers where multiple unrelated transformers are resolved for a given type

by Tom Fennelly (JIRA)

Improve sorting logic of fallback transformers where multiple unrelated transformers are resolved for a given type ------------------------------------------------------------------------------------------------------------------ Key: SWITCHYARD-320 URL: https://issues.jboss.org/browse/SWITCHYARD-320 Project: SwitchYard Issue Type: Enhancement Components: transformation Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.2 At the moment, if unrelated fallback transformers are discovered (un-assignable types), the user gets an error and they need to manually add an explicit transformer to resolve. With Camel in the mix and all of its converters, the likelihood of hitting this situation goes up a lot and becomes a PITA. We can improve the sorting so as to take into account how far in the inheritance tree the incompatible types are from the target type, weighting in favor the type that is closer. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues June 2011