Lifecycle Unit Test does not work
---------------------------------
Key: JBESB-1663
URL: http://jira.jboss.com/jira/browse/JBESB-1663
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP2
Reporter: Mark Little
Assigned To: Kevin Conner
Priority: Minor
Fix For: 4.3
// assertEquals(LifecycleResourceManager.DEFAULT_IDENTITY, first.getDestroyId()) ;
--
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
Add an expected output portion to jms_transacted QS
---------------------------------------------------
Key: JBESB-1664
URL: http://jira.jboss.com/jira/browse/JBESB-1664
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Tom Cunningham
Assigned To: Tom Cunningham
Fix For: 4.2.1 CP3
Add an "expected output" portion to the jms_transacted QS.
--
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
jms_secured quickstart does not work in the SOA platform
--------------------------------------------------------
Key: JBESB-1639
URL: http://jira.jboss.com/jira/browse/JBESB-1639
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2.1 CP2
Reporter: Kevin Conner
Fix For: 4.2.1 CP3
This quickstart attempts to modify the messaging security policy by updating the property files under conf, but the SOA platform defines a messaging policy to retrieve this information from a database.
The required credentials are therefore not found when running the quickstart.
--
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
The JbpmService MBean is missing a dependency
---------------------------------------------
Key: JBESB-1635
URL: http://jira.jboss.com/jira/browse/JBESB-1635
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.2.1, 4.2.1 CP2
Reporter: Kevin Conner
Fix For: 4.2.1 CP3, 4.3
--
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
MBean dependencies specify the datasource but not the initialiser
-----------------------------------------------------------------
Key: JBESB-1636
URL: http://jira.jboss.com/jira/browse/JBESB-1636
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.2.1, 4.2.1 CP2
Reporter: Kevin Conner
Fix For: 4.2.1 CP3, 4.3
The result of this dependency is that there is a race between the user of the datasource and the configuration of the tables.
--
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
Support authentication on outgoing JMS (i.e. JMSRouter)
-------------------------------------------------------
Key: JBESB-1627
URL: http://jira.jboss.com/jira/browse/JBESB-1627
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: David Smiley
JMSRouter doesn't support authenticating to JMS, and it should. This should be easy to add.
Note: related to JBESB-1404
--
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
Remove JNDI default configuration from quickstart jboss-esb.xml files
---------------------------------------------------------------------
Key: JBESB-1595
URL: http://jira.jboss.com/jira/browse/JBESB-1595
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Fix For: 4.2.1 CP2
Specifying the default JNDI configuration in the quickstart jboss-esb.xml files is unnecessary and prevents deployment if the server has been bound with a different configuration.
We should remove these configurations from the quickstarts and update the readme files.
--
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 quickstarts should use only JMS transports and they should be configured to participate in transactions
-----------------------------------------------------------------------------------------------------------
Key: JBESB-1508
URL: http://jira.jboss.com/jira/browse/JBESB-1508
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2.1
Environment: soa-4.2.0.CR1.zip standalone-soa-4.2.0.CR1.zip
Reporter: Jiri Pechanec
Assigned To: Kevin Conner
Fix For: 4.2.1 CP1
It is good practice to show customer how the BPM should be used correctly - to avoid problems with message duplicates, callback responses coming before process is committed etc.
--
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
Document best practices
-----------------------
Key: JBESB-1662
URL: http://jira.jboss.com/jira/browse/JBESB-1662
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Configuration, Deployment, Documentation
Affects Versions: 4.2.1 CP2
Reporter: Mark Little
Fix For: 4.3
--
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