Create a separate common module/jar
-----------------------------------
Key: JBESB-666
URL: http://jira.jboss.com/jira/browse/JBESB-666
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Packaging
Affects Versions: 4.2 Milestone Release 2
Reporter: Mark Little
Assigned To: Mark Little
Priority: Optional
--
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
Mesage Action Guide on XStreamToObject does not match implementation
--------------------------------------------------------------------
Key: JBESB-1685
URL: http://jira.jboss.com/jira/browse/JBESB-1685
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.2.1
Reporter: Michael Martinsen
On page 14 of the document 'JBESB-MAG-10/31/07' the XStreamToObject is descibed to support aliases by:
<property name="aliases">
<alias name="alias1" value="com.acme.MyXXXClass1/>
</property>
This does not match the implementation which requires the string 'class' and not 'value'.
--
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
Mesage Action Guide on SOAPClient does not match implementation
---------------------------------------------------------------
Key: JBESB-1684
URL: http://jira.jboss.com/jira/browse/JBESB-1684
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.2.1
Reporter: Michael Martinsen
Starting at page 27 in the document 'JBESB-MAG-10/31/07' the SOAPClient action is described.
It says that one should specify the 'wsdl' and the 'operation' properties.
The SOAPClient code and Javadoc says different. The property 'operation' is no longer used and in stead 'SOAPAction' is used.
The quickstart 'webservice_consumer1' also has the 'operation' property - and also the 'SOAPAction' attribute.
--
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
Review Exceptions on the EPR types
----------------------------------
Key: JBESB-1386
URL: http://jira.jboss.com/jira/browse/JBESB-1386
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Rosetta, Transports
Affects Versions: 4.0
Reporter: Tom Fennelly
Fix For: 4.3
We're throwing exceptions on getter methods??? Example... throwing a URISyntaxException on JDBCEpr.getSQL()??? It's all over the place.
This might all fall back under a more general review of the whole API!
--
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
Comparision performance tests
-----------------------------
Key: JBESB-875
URL: http://jira.jboss.com/jira/browse/JBESB-875
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Transformation Service
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Tom Fennelly
Priority: Optional
Intern:
"Are there any performance tests in the release that someone could use to check Smooks versus XSLT? Does that even make sense?"
--
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
JBossRemotingGatewayListener not disconnecting properly on undeploy
--------------------------------------------------------------------
Key: JBESB-1378
URL: http://jira.jboss.com/jira/browse/JBESB-1378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.2.1
Reporter: Tom Fennelly
Fix For: 4.2.1 CP1
Looks as though the jbr-listener is not closing/stopping/disconnecting properly on the doStop 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
Create some wiki pages around SOA patterns for the ESB
------------------------------------------------------
Key: JBESB-777
URL: http://jira.jboss.com/jira/browse/JBESB-777
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Documentation
Reporter: Mark Little
Assigned To: Mark Little
Ones that don't rely on exposing individual objects on to the bus. Conform to recognised SOA patterns.
It'll be hard without all of the supporting tools, but it's still possible.
--
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
Refactor JMSRouter and NotifyJMS to use JmsConnectionPoolContainer
------------------------------------------------------------------
Key: JBESB-1425
URL: http://jira.jboss.com/jira/browse/JBESB-1425
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Fix For: 4.3
JMSRouter and NotifyJMS currently create their own JMS connections and sessions. This is done for every invokation which is not very efficient. Plus that there is code duplication here.
--
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
jUDDI using BRMS as repository
------------------------------
Key: JBESB-1486
URL: http://jira.jboss.com/jira/browse/JBESB-1486
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2.1
Reporter: Mark Little
Assigned To: Kurt Stam
Fix For: 5.0
--
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
Merge FP branch into trunk
--------------------------
Key: JBESB-1693
URL: http://jira.jboss.com/jira/browse/JBESB-1693
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Build and Release
Affects Versions: 4.2.1
Reporter: Kevin Conner
Assigned To: Kevin Conner
Priority: Blocker
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