Quickstarts running standalone are running very slow
----------------------------------------------------
Key: JBESB-882
URL: http://jira.jboss.com/jira/browse/JBESB-882
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples, Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Tom Fennelly
Assigned To: Tom Fennelly
Fix For: 4.2
Burr suspects it's something to do with the new Scheduling code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Invalid events in bpm_orchestration1 and bpm_orchestration2 samples
-------------------------------------------------------------------
Key: JBESB-749
URL: http://jira.jboss.com/jira/browse/JBESB-749
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: BPM, Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Mark Little
Priority: Optional
The start nodes in both examples have attached actions on node-enter event. According to jBPM source code, this event is not supported on start node and thus not fired.
Recommended solution
Attach the action to node-leave event
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
bpm_orchestration2 QS message definitions need tidying up and fixing
--------------------------------------------------------------------
Key: JBESB-903
URL: http://jira.jboss.com/jira/browse/JBESB-903
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2
The naming is inconsistent and leads to errors in deployment (missing queues)
No dependencies on the queues have been configured.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Message does not implement equals()
-----------------------------------
Key: JBESB-862
URL: http://jira.jboss.com/jira/browse/JBESB-862
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Reporter: Kurt Stam
Assigned To: Mark Little
Fix For: 4.2.1
I need to compare two EsbMessage for equality. There is no such method.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
bpm_orchestration2 QS is missing script service1.groovy
-------------------------------------------------------
Key: JBESB-902
URL: http://jira.jboss.com/jira/browse/JBESB-902
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
bpm_orchestration1 QS contains invalid bpm mapping attributes
-------------------------------------------------------------
Key: JBESB-900
URL: http://jira.jboss.com/jira/browse/JBESB-900
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2
The configuration of the mapping from the ESB to jBPM is specified using incorrect attributes.
The mapping should be
<object-path esb="XX" bpm="YY" value="ZZ" />
but is
<object-path esb="XX" jbpm="YY" value="ZZ" />
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
bpm_orchestration1 QS contains duplicate action names
-----------------------------------------------------
Key: JBESB-899
URL: http://jira.jboss.com/jira/browse/JBESB-899
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2
org.jboss.soa.esb.ConfigurationException: Tried to register a duplicate action name. Service Starter_Service already contains an action named spy. Action names must be unique per service.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
scripting_groovy QS contains duplicate action names
---------------------------------------------------
Key: JBESB-898
URL: http://jira.jboss.com/jira/browse/JBESB-898
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2
org.jboss.soa.esb.ConfigurationException: Tried to register a duplicate action name. Service MoreActionService already contains an action named groovy. Action names must be unique per service.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Quickstarts still refer to ServiceInvoker.close()
-------------------------------------------------
Key: JBESB-896
URL: http://jira.jboss.com/jira/browse/JBESB-896
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2
The following quickstarts still contain a reference to ServiceInvoker.close(). This method has been removed from the codebase.
custom_action, exceptions_faults and scheduled_services.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
custom_action config references non existent exception metthod
--------------------------------------------------------------
Key: JBESB-897
URL: http://jira.jboss.com/jira/browse/JBESB-897
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2
Caused by: java.lang.NoSuchMethodException: org.jboss.soa.esb.samples.quickstart.customaction.CustomConfigAction.exceptionHandler(org.jboss.soa.esb.message.Message, java.lang.Throwable)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira