30 character limit of tablenames in Oracle
------------------------------------------
Key: JBESB-1342
URL: http://jira.jboss.com/jira/browse/JBESB-1342
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transformation Service
Reporter: Kurt Stam
Fix For: 4.2.1 CP1
The JBossESB console needs transformationresourceparameter and transformationresourceparameterspec tables, whos names are too long (tablename length limited into 30 characters in Oracle).
--
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
Update build to support JDK6
----------------------------
Key: JBESB-1674
URL: http://jira.jboss.com/jira/browse/JBESB-1674
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.2.1 CP2, 4.2.1
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2.1 CP3, 4.3
We need to look at running our codebase on JDK6 as well as JDK5. As a first step we need to modify the build to allow the use of JDK6 and create hudson runs to verify.
--
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
Improved Spring integration
---------------------------
Key: JBESB-1660
URL: http://jira.jboss.com/jira/browse/JBESB-1660
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Deployment
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
Make an Eclipse plugin for ESB configuration editor
----------------------------------------------------
Key: JBESB-1365
URL: http://jira.jboss.com/jira/browse/JBESB-1365
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Tooling
Affects Versions: 4.2.1
Reporter: Mark Little
Assigned To: Daniel Bevenius
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
Allow Registry registrations to include a flag to indicate whether the endpoint is message aware/unaware.
---------------------------------------------------------------------------------------------------------
Key: JBESB-498
URL: http://jira.jboss.com/jira/browse/JBESB-498
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2 Milestone Release 1
Reporter: Tom Fennelly
Assigned To: Mark Little
Fix For: 4.2 Milestone Release 2
This will also mean adding query capability against this.
This requirement could be generalised to simply allow registrations to be decorated with attributes, and have these same attributes returned in the lookups.
--
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
Webservice QS CI tests need debugging
-------------------------------------
Key: JBESB-1470
URL: http://jira.jboss.com/jira/browse/JBESB-1470
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Testing
Affects Versions: 4.2.1
Reporter: Tom Cunningham
Assigned To: Tom Cunningham
Fix For: 4.3
The webservice* QS CI tests are excluded currently because they do not find a record after their wait period when run within the test harness. When run individually under the "ant internal-one-test" target, these tests all work fine.
--
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
Need a "tracer bullet" monitoring function
------------------------------------------
Key: JBESB-1676
URL: http://jira.jboss.com/jira/browse/JBESB-1676
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tooling
Affects Versions: 4.2.1 CP2
Reporter: Tom Cunningham
Need a "tracer bullet" monitoring function which can trace a message through the ESB.
--
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
org.jboss.soa.esb.actions.scripting.GroovyActionProcessor doesn't throw an ActionProcessingException if the Process(Message)-method fails
-----------------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-1689
URL: http://jira.jboss.com/jira/browse/JBESB-1689
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.2.1
Reporter: Morten Damm Jensen
The Process(Message)-method in org.jboss.soa.esb.actions.scripting.GroovyActionProcessor is surrounded with a try-catch, and if an Exception is caught is is just logged and then the Message is returned.
Instead of returning the Message it should throw an ActionProcessingException!
If not, it is impossible for the surrounding environment to take action on this error, and it will assume that the processing was successful.
--
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
SOAPClient process method should guard against ClassCastExceptions on the payload
---------------------------------------------------------------------------------
Key: JBESB-1645
URL: http://jira.jboss.com/jira/browse/JBESB-1645
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.2.1 CP2, 4.2.1 CP1
Reporter: Tom Fennelly
It's currently just doing a cast to a Map, but not guarding against something else being there.
--
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
Controlled shutdown
-------------------
Key: JBESB-522
URL: http://jira.jboss.com/jira/browse/JBESB-522
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Kevin Conner
Assigned To: Mark Little
Fix For: 5.0 Milestone Release 1
During a controlled shutdown, the ESB should prevent any further message inflow but allow all messages being processed/delivered to finish.
--
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