Revisit the trailblazer
-----------------------
Key: JBESB-1732
URL: http://jira.jboss.com/jira/browse/JBESB-1732
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.3
Reporter: Kevin Conner
Fix For: 4.4
We need to revisit the trailblazer, providing a more comprehensive example of what is available using the ESB.
As things stand, some of the quickstarts involve more functionality.
--
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
max-pool=size typo in jbossesb-properties.xml
---------------------------------------------
Key: JBESB-2196
URL: https://jira.jboss.org/jira/browse/JBESB-2196
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Reporter: Joakim Sandström
Shouldn't max-pool=size be max-pool-size? Although I didn't find any place in the code where it's used!
<properties name="connection">
<property name="min-pool-size" value="5"/>
<property name="max-pool=size" value="10"/>
Every jbossesb-properties.xml, template and sample has this typo.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
POSTHttpMethodFactory dosn't support Encoding
---------------------------------------------
Key: JBESB-2193
URL: https://jira.jboss.org/jira/browse/JBESB-2193
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.4
Environment: Debian, Linux 64
Reporter: Jurij
POSTHttpMethodFactory call constructor of StringRequestEntity with one parameter. This is on apache side ist depricated! Use the contructor with three parameters, this should be set in Action config as parameteers. If not use default encoding.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Programmers Guide: Include Environment.EXCEPTION_ON_DELIVERY_FAILURE
--------------------------------------------------------------------
Key: JBESB-2096
URL: https://jira.jboss.org/jira/browse/JBESB-2096
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.4
Reporter: Burr Sutter
Priority: Minor
Include information on Environment.EXCEPTION_ON_DELIVERY_FAILURE when describing ServiceInvoker and deliverySync(), in addition, this area should describe how to deal with timeouts overall as well as the 3 possible exceptions thrown by ServiceInvoker:
MessageDeliverException
RegistryException
FaultMessageException
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Services Guide: Replace concept image in docs for content routing
-----------------------------------------------------------------
Key: JBESB-2195
URL: https://jira.jboss.org/jira/browse/JBESB-2195
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.4
Reporter: Darrin Mison
This image, while still being referred to, is missing from the ESB4.4 Services Guide, Chapter 6 - What is Content-Based Routing
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/docshttp://www.jboss.org/jbossesb/docs/4.4.GA/manuals/html/ServicesGuide.html
This replacement image is from the SOA 4.2.CP03 Platform Services Guide. It illustrates the basic content routing concepts.
Replacement of the preceding text describing it:
"The diagram below illustrates a very basic example of the Content-based Routing Architecture. The
client sends a message to Service A. Service A forwards the message to Router which, based
on the content of the message, forwards the message to either Service B or Service C."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
convert quickstart readme.txt to readme.html to allow for links & images
------------------------------------------------------------------------
Key: JBESB-520
URL: http://jira.jboss.com/jira/browse/JBESB-520
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Jason Lenhart
Priority: Minor
Fix For: 4.2 Milestone Release 2
The main readme.txt should be converted to HTML, provide a brief description of each individual quickstart and actually link to that quickstart's readme.html.
readme.html's might also include an image describing the architecture as well.
--
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
ERROR message when running business_ruleservice_ruleAgent QS
------------------------------------------------------------
Key: JBESB-2050
URL: https://jira.jboss.org/jira/browse/JBESB-2050
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.4
Reporter: Jaroslaw Kijanowski
project jira for SOA-800
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
ESBConfig GUI needs additional configuration options
----------------------------------------------------
Key: JBESB-1546
URL: http://jira.jboss.com/jira/browse/JBESB-1546
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.2.1
Environment: JDK 1.5.0_14
Windows XP MCE
Reporter: Antonio Souza
The "JBR Provider" must be added to the list of available providers in ESBConfig Flash GUI.
Additionally, when adding 'Actions', it should have a field of MEP type (one-way, request-response).
This 2 items must be addressed in the next releases of the ESBConfig GUI.
--
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
SQL Listener should deal with rows
----------------------------------
Key: JBESB-591
URL: http://jira.jboss.com/jira/browse/JBESB-591
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Tom Cunningham
Assigned To: Mark Little
Talked to Burr and Kurt today about the SQL poller quickstart and the SQL listener with regards to the hibernate listener. Burr thinks that the SQL listener should be dealing with the entire row as a message, rather than just a column. This would probably demand changes in both Listener and 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
Upgrade the Smooks console to use the newer config model
--------------------------------------------------------
Key: JBESB-629
URL: http://jira.jboss.com/jira/browse/JBESB-629
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Tooling, Transformation Service
Affects Versions: 4.2 Milestone Release 2
Reporter: Tom Fennelly
Assigned To: Tom Fennelly
It's currently using the Smooks v0.8 DTD based model. Upgrade it to use the newer v0.9 XSD based model. v0.9 is backward compatible with the v0.8 config model, but it throws out warnings (not exceptions) to the console.
--
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