August 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3425) Upgrade Drools to 5.1.0.FINAL

by David Ward (JIRA)

Upgrade Drools to 5.1.0.FINAL ----------------------------- Key: JBESB-3425 URL: https://jira.jboss.org/browse/JBESB-3425 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.8 Reporter: David Ward Assignee: David Ward Fix For: 4.9 trunk is currently at Drools 5.1.0.CR1. 5.1.0.FINAL has been released. We should retest everything, and if there are no code changes, and all the junit tests and quickstarts still work, we should upgrade before 4.9 releases. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3423) Make Drools naming/version consistent in Release Notes and Getting Started Guide

by David Ward (JIRA)

Make Drools naming/version consistent in Release Notes and Getting Started Guide -------------------------------------------------------------------------------- Key: JBESB-3423 URL: https://jira.jboss.org/browse/JBESB-3423 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Documentation Reporter: David Ward Assignee: David Ward The Programmer's Guide and Services Guides were already fixed as part of JBESB-3411 and JBESB-3408, respectively. The Release Notes and Getting Started Guide also need to be consistent. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3408) Merge Drools doc changes to ServicesGuide over to docbook docs

by Tom Cunningham (JIRA)

Merge Drools doc changes to ServicesGuide over to docbook docs -------------------------------------------------------------- Key: JBESB-3408 URL: https://jira.jboss.org/browse/JBESB-3408 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assignee: David Ward Fix For: 4.9 Merge the changes in this checkin from the ODT over to docbook docs. [tcunning@localhost docs]$ svn log ServicesGuide.odt | more ------------------------------------------------------------------------ r34210 | dward | 2010-07-26 16:58:33 -0400 (Mon, 26 Jul 2010) | 2 lines Changes required to resolve JBESB-3360, JBESB-2883, JBESB-2882, JBESB-2831 and J BESB-2830. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-3411) Merge Drools doc changes to ProgrammersGuide over to docbook docs

by Tom Cunningham (JIRA)

Merge Drools doc changes to ProgrammersGuide over to docbook docs ----------------------------------------------------------------- Key: JBESB-3411 URL: https://jira.jboss.org/browse/JBESB-3411 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.9 Reporter: Tom Cunningham Assignee: David Ward Fix For: 4.9 Merge Drools changes to Programmer's Guide in this checkin from ODT over to docbook files : ------------------------------------------------------------------------ r34210 | dward | 2010-07-26 16:58:33 -0400 (Mon, 26 Jul 2010) | 2 lines Changes required to resolve JBESB-3360, JBESB-2883, JBESB-2882, JBESB-2831 and J BESB-2830. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-3422) Update the load_generator quickstart to work with hornetq

by Tom Fennelly (JIRA)

Update the load_generator quickstart to work with hornetq --------------------------------------------------------- Key: JBESB-3422 URL: https://jira.jboss.org/browse/JBESB-3422 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.9 The load.xml file contains refs to the JMS mbeans, with the JBM/JBMQ objectnames... which don't work for hornetq. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3421) Update the jms_secured quickstart to work with hornetq

by Tom Fennelly (JIRA)

Update the jms_secured quickstart to work with hornetq ------------------------------------------------------ Key: JBESB-3421 URL: https://jira.jboss.org/browse/JBESB-3421 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.9 Requires a diff deployment to jbm/jbmq + instructions for user mods to some central (not in the quickstart) config files - hornetq-roles.properties, hornetq-users.properties and hornetq-configuration.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3401) Update documentation about CXF support

by Magesh Kumar B (JIRA)

Update documentation about CXF support -------------------------------------- Key: JBESB-3401 URL: https://jira.jboss.org/browse/JBESB-3401 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.8 Reporter: Magesh Kumar B Assignee: Magesh Kumar B Priority: Minor Fix For: 4.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3418) shorthand internal:// URI format causes problems

by David Ward (JIRA)

shorthand internal:// URI format causes problems ------------------------------------------------ Key: JBESB-3418 URL: https://jira.jboss.org/browse/JBESB-3418 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Web Services Reporter: David Ward Priority: Blocker Fix For: 4.9 Before doing JBESB-3410 and JBESB-3400, I believe we need to re-visit why we changed the internal:// URI format for the SOAPProxy wsdl configuration property. Originally, a wsdl property would look like this: <property name="wsdl" value="internal://jboss.ws:context=Quickstart_webservice_proxy_basic_ws,endpoint=HelloWorldWS"/> The value after the "internal://" sheme is the full mbean name of that web service. This was done because "HelloWorldWS" is not specific enough. Two different applications could be deployed that each call their web service "HelloWorldWS". The full mbean name was chosen because it is fully unique in the system - per deployment as well as web service short-hand name. In trunk (for 4.9), as part of the work for JBESB-3372, the internal:// URI syntax was shortend to just the short-hand name of the web service. I have discovered that this does, in fact, cause problems. What I did was dupicate the webservice_proxy_basic quickstart to webservice_proxy_test. Inside it, I besides changing the deployment name, I went through and changed everywhere I saw "hello" with "goodbye". However, I LEFT THE SHORTHAND name of "HelloWorldWS" the same. On deployment, this is what I saw: 15:36:23,222 INFO [DefaultEndpointRegistry] register: jboss.ws:context=Quickstart_webservice_proxy_test_ws,endpoint=HelloWorldWS 15:36:23,227 INFO [TomcatDeployer] deploy, ctxPath=/Quickstart_webservice_proxy_test_ws, warUrl=.../tmp/deploy/tmp5058294535306107812Quickstart_webservice_proxy_test_ws-exp.war/ 15:36:23,439 INFO [WSDLFilePublisher] WSDL published to: file:/home/dward/repos/jbossesb/trunk/product/build/jbossesb-server-4.9/server/default/data/wsdl/Quickstart_webservice_proxy_test_ws.war/HelloWorldWSService1656390998107952897.wsdl 15:36:23,465 INFO [JBoss4ESBDeployer] create esb service, Quickstart_webservice_proxy_test.esb 15:36:23,499 INFO [JBoss4ESBDeployment] Deploying 'Quickstart_webservice_proxy_test.war' 15:36:23,506 INFO [TomcatDeployer] deploy, ctxPath=/Quickstart_webservice_proxy_test, warUrl=.../tmp/deploy/tmp6427004333585839758Quickstart_webservice_proxy_test-exp.war/ 15:36:23,693 INFO [SOAPProxy] mapped soapaction [""] to binding [{http://webservice_proxy_test/goodbyeworld}HelloWorldBinding] 15:36:23,693 INFO [SOAPProxy] mapped operation [{http://webservice_proxy_test/goodbyeworld}sayGoodbye] to binding [{http://webservice_proxy_test/goodbyeworld}HelloWorldBinding] 15:36:23,693 INFO [SOAPProxy] mapped binding [{http://webservice_proxy_test/goodbyeworld}HelloWorldBinding] to transport [org.jboss.soa.esb.actions.soap.proxy.HttpSOAPProxyTransport] with endpoint address: [http://127.0.0.1:8080/Quickstart_webservice_proxy_test_ws/HelloWorldWS] 15:36:38,743 INFO [DefaultEndpointRegistry] register: jboss.ws:context=Quickstart_webservice_proxy_basic_ws,endpoint=HelloWorldWS 15:36:38,748 INFO [TomcatDeployer] deploy, ctxPath=/Quickstart_webservice_proxy_basic_ws, warUrl=.../tmp/deploy/tmp5564876594631336257Quickstart_webservice_proxy_basic_ws-exp.war/ 15:36:38,945 INFO [WSDLFilePublisher] WSDL published to: file:/home/dward/repos/jbossesb/trunk/product/build/jbossesb-server-4.9/server/default/data/wsdl/Quickstart_webservice_proxy_basic_ws.war/HelloWorldWSService4562073185226278059.wsdl 15:36:38,967 INFO [JBoss4ESBDeployer] create esb service, Quickstart_webservice_proxy_basic.esb 15:36:39,002 INFO [JBoss4ESBDeployment] Deploying 'Quickstart_webservice_proxy_basic.war' 15:36:39,012 INFO [TomcatDeployer] deploy, ctxPath=/Quickstart_webservice_proxy_basic, warUrl=.../tmp/deploy/tmp6238185939414067851Quickstart_webservice_proxy_basic-exp.war/ 15:36:39,227 INFO [SOAPProxy] mapped soapaction [""] to binding [{http://webservice_proxy_test/goodbyeworld}HelloWorldBinding] 15:36:39,228 INFO [SOAPProxy] mapped operation [{http://webservice_proxy_test/goodbyeworld}sayGoodbye] to binding [{http://webservice_proxy_test/goodbyeworld}HelloWorldBinding] 15:36:39,228 INFO [SOAPProxy] mapped binding [{http://webservice_proxy_test/goodbyeworld}HelloWorldBinding] to transport [org.jboss.soa.esb.actions.soap.proxy.HttpSOAPProxyTransport] with endpoint address: [http://127.0.0.1:8080/Quickstart_webservice_proxy_test_ws/HelloWorldWS] If you read the log lines, you will see that the mapping for BOTH deployments is using the "goodbye"-based contract. I believe this is because "HelloWorldWS" is not unique enough. The deployment name has to be in the internal:// URI as well as the shorthand webservice name. For the same reason, the proxy contracts found in http://localhost:8080/contract/ are also both the same (so one of them is wrong). Additionally, and this is just my opinion, changing the format of the internal:// wsdl URI means that all our customers and users who use the original format have to know to change it to the new format. Even if the new format worked (which it doesn't), if the reason for this was only cosmetic, I believe that's not a good enough reason to cause pain for all the customers and users. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-3400) Document SOAPProxy internal:// url format change

by Magesh Kumar B (JIRA)

Document SOAPProxy internal:// url format change ------------------------------------------------ Key: JBESB-3400 URL: https://jira.jboss.org/browse/JBESB-3400 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.8 Reporter: Magesh Kumar B Assignee: Magesh Kumar B Priority: Minor Fix For: 4.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3416) LifecycleResourceManager disassociateDeployment method accesses identities map outside of lock.

by Kevin Conner (JIRA)

LifecycleResourceManager disassociateDeployment method accesses identities map outside of lock. ----------------------------------------------------------------------------------------------- Key: JBESB-3416 URL: https://jira.jboss.org/browse/JBESB-3416 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.8 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2010