February 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2322) ESB Administrator Guide refers to jbossesb-listener.xml and jbossesb-gateway.xml

by Stelios Koussouris (JIRA)

ESB Administrator Guide refers to jbossesb-listener.xml and jbossesb-gateway.xml -------------------------------------------------------------------------------- Key: JBESB-2322 URL: https://jira.jboss.org/jira/browse/JBESB-2322 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.3 Reporter: Stelios Koussouris Priority: Trivial Administration Guide" pg. 1 "How can I configure them? You can configure JMSListeners and JMSGateways to listen to a Queue or Topic by specifying the following parameters in their configuration (jbossesb-listener.xml and jbossesb-gateway.xml): • jndi-URL • jndi-context-factory • jndi-pkg-prefix • connection-factory • destination-type • destination-name" Do jbossesb-listener.xml and jbossesb-gateway.xml still exist or are they part of the jboss-esb.xml? ie. obsolete now? I believe they might be internally used but not needed to be configured by the users -- 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

17 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2196) max-pool=size typo in jbossesb-properties.xml

by Joakim Sandström (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

17 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2193) POSTHttpMethodFactory dosn't support Encoding

by Jurij (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

17 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2096) Programmers Guide: Include Environment.EXCEPTION_ON_DELIVERY_FAILURE

by Burr Sutter (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

17 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2195) Services Guide: Replace concept image in docs for content routing

by Darrin Mison (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/docs http://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

17 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2372) SOA Software Integration Document corrections

by Scott Dawson (JIRA)

SOA Software Integration Document corrections --------------------------------------------- Key: JBESB-2372 URL: https://jira.jboss.org/jira/browse/JBESB-2372 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 CP2 Reporter: Scott Dawson Some corrections and clarifications are needed in the SOA Software integration document (SOASoftwareIntegration.odt). 1) In step 4 'Change the workflow...', the 'After' section of XML doesn't match the text description. The 'After' XML should look like this, so that the function element and the step attribute are correct: <action id="1" name="@create"> <results> <unconditional-result old-status="Created" status="Draft" step="100" owner="${caller}"/> </results> <post-functions> <function type="publish" /> </post-functions> </action> 2) In step 3, instead of: Hit modify on "Guest" under "Role Memberships it should say: Click "Manage Role" for "Guest" under "Role Memberships" and instead of: Go to the top level registry node in Workbench on the right hand side of the screen it is clearer to say: Click on the top level registry node in Workbench (in the Organization Tree) 3) Add some information about versions of the ESB and SOA Software: a. Service Manager 5.2 must have updates 2.0 and 2.1 applied along with the associated database scripts b. For JBoss ESB 4.4.GA, the Scout jar must be updated to scout-1.0rc2.aop.jar c. Also in ESB 4.4.GA, the following change is necessary (but fixed in later versions, see JBESB-2072): In Service Manager, click on "Configure" tab, "Registry" sub tab, and "tModels" sub sub tab. Add a tModel with org.jboss.soa.esb.:category as the name and decription (note: the dot followed by a colon is correct). Select "Category Group Scheme" as the tModel type. Leave the other fields blank and click Apply. -- 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

17 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2399) InVM RequestResponse replies not being handled properly by DefaultJmsReplyToEpr

by Kevin Conner (JIRA)

InVM RequestResponse replies not being handled properly by DefaultJmsReplyToEpr ------------------------------------------------------------------------------- Key: JBESB-2399 URL: https://jira.jboss.org/jira/browse/JBESB-2399 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.5 -- 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

17 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2398) InVM RequestResponse replies not being handled properly by DefaultJmsReplyToEpr

by Tom Fennelly (JIRA)

InVM RequestResponse replies not being handled properly by DefaultJmsReplyToEpr ------------------------------------------------------------------------------- Key: JBESB-2398 URL: https://jira.jboss.org/jira/browse/JBESB-2398 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.5 -- 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

17 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2383) JmsConnectionPoolContainer ignores additional jndi-prefixes

by Kevin Conner (JIRA)

JmsConnectionPoolContainer ignores additional jndi-prefixes ----------------------------------------------------------- Key: JBESB-2383 URL: https://jira.jboss.org/jira/browse/JBESB-2383 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.5 -- 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

17 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2402) message when running business_ruleservice_ruleAgent QS

by Mark Little (JIRA)

message when running business_ruleservice_ruleAgent QS ------------------------------------------------------ Key: JBESB-2402 URL: https://jira.jboss.org/jira/browse/JBESB-2402 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 Reporter: Jaroslaw Kijanowski Assignee: Daniel Bevenius Fix For: 4.6 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

17 years, 2 months

2
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2009