January 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2180) change jca-gateway transacted attribute to be of type boolean.

by Daniel Bevenius (JIRA)

change jca-gateway transacted attribute to be of type boolean. -------------------------------------------------------------- Key: JBESB-2180 URL: https://jira.jboss.org/jira/browse/JBESB-2180 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Reporter: Daniel Bevenius Priority: Minor Fix For: 4.5 When testing JBDS 2.0 I noticed that the jca-gateway's transacted attribute is of type string and not of the boolean type. This will make that field a text field in the eclipse ESB editor and would be nice if it could be simple dropdown with a true or false option. -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-2213) Create SchemaValidationAction

by Daniel Bevenius (JIRA)

Create SchemaValidationAction ----------------------------- Key: JBESB-2213 URL: https://jira.jboss.org/jira/browse/JBESB-2213 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples, Rosetta Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.5 Create an Action that can validate against a specified schema. Create a quickstart to demonstrate it. -- 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

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1881) DataFiler errors on trunk

by Tom Cunningham (JIRA)

DataFiler errors on trunk ------------------------- Key: JBESB-1881 URL: https://jira.jboss.org/jira/browse/JBESB-1881 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Reporter: Tom Cunningham Assignee: Tom Cunningham Burr sees the following on trunk: 17:00:03,296 ERROR [DataFiler] ERROR - found type of java.lang.Integer for actio n bytes failed 17:00:03,298 ERROR [DataFiler] ERROR - found type of java.lang.Integer for actio n bytes processed 17:00:03,304 ERROR [DataFiler] ERROR - found type of java.lang.Integer for overa ll bytes processed 17:00:03,307 ERROR [DataFiler] ERROR - found type of java.lang.Integer for overa ll bytes failed 17:00:03,373 ERROR [DataFiler] ERROR - found type of java.lang.Integer for testS tore bytes failed 17:00:03,375 ERROR [DataFiler] ERROR - found type of java.lang.Integer for setup Key bytes failed -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1923) Need a barrier-service.xml with embedded-console

by Tom Cunningham (JIRA)

Need a barrier-service.xml with embedded-console ------------------------------------------------ Key: JBESB-1923 URL: https://jira.jboss.org/jira/browse/JBESB-1923 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 CP1 JBMANCON-355 explains that a barrier-service.xml is necessary for embedded-console.war to start up after all .esb deployments so that the .esb deployments are discovered. We'd need to add this in to our build. -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1813) Add support for property injection in jboss-esb.xml

by Naveen Malik (JIRA)

Add support for property injection in jboss-esb.xml --------------------------------------------------- Key: JBESB-1813 URL: http://jira.jboss.com/jira/browse/JBESB-1813 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.2.1 Reporter: Naveen Malik This came about from a discussion on the port defined for a HTTP listener. As it is today, the value must be hard coded in the jboss-esb.xml file, which is part of the esb archive. This makes it hard to configure when moving between environments without changing that file and rebuilding the archive. We would like to move this type of configuration into external properties. I propose using system properties and the ModulePropertyManager provided by JBoss ESB, adding a new module named "action". I will provide a patch for this feature today or tomorrow. -- 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

17 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-1732) Revisit the trailblazer

by Kevin Conner (JIRA)

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

17 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2321) ESB Getting Started Guide Needs Reviewing

by Stelios Koussouris (JIRA)

ESB Getting Started Guide Needs Reviewing ----------------------------------------- Key: JBESB-2321 URL: https://jira.jboss.org/jira/browse/JBESB-2321 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.3 Reporter: Stelios Koussouris Priority: Trivial The following problems were identified in the Getting Started Guide and were checked/verified by SEG Section 3.3 "SOA_GetStarted_Guide" Issue1. It says that before any messages are sent the "FirstService:SimpleJMSService" s registered with the Registry Service. Where does it get the "FirstService:SimpleJMSService" the service is defined with attributes category="FirstServiceESB" and name="SimpleListener" is this a typo? Also, when it says it is registered with the Registry Service where/how does that happen & get configured? Answer 1. Typo, it should have been FirstServiceESB:SimpleListener --> category:name Issue2. In the example the JMS client is sending the message "queue/quickstart_helloworld_Request_gw" and not "queue/quickstart_helloworld_Request". Is this a typo or something I am missing? Similarly, where is the JMS Gateway Listener listening to as the above is confusing matters. Answer 2. Typo: the build.xml in helloworld says "sends a JMS message to --> queue/quickstart_helloworld_Request_gw" Issue3. The "JMS Gateway Listener uses the registry to lookup the Endpoint Reference (EPR) or "FirstService:SimpleJMSService" Service" could you please explain how this is done again? And then it finds that "his works out to be JMS Queue "queue/quickstart_helloworld_Request_gw""... more confusion how it has worked that out and why now it is this queue. Answer 3. Typo again. the document-er has confused between gateways and non-gateways. A gateway is suffixed with _gw for convenience. -- 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-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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2009