January 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2295) Duplicate schema types in wsdl generated by EBWS

by Taro Yasuma (JIRA)

Duplicate schema types in wsdl generated by EBWS ------------------------------------------------ Key: JBESB-2295 URL: https://jira.jboss.org/jira/browse/JBESB-2295 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.4 CP1 Reporter: Taro Yasuma See SOA-1137. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2298) Programmers_Guide.pdf StaticWiretap description is confusing

by Jeff Yu (JIRA)

Programmers_Guide.pdf StaticWiretap description is confusing ------------------------------------------------------------ Key: JBESB-2298 URL: https://jira.jboss.org/jira/browse/JBESB-2298 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 Reporter: Jeff Yu Priority: Minor Fix For: 4.5 Copied this from Burr's concern: --------------------- This section: StaticWiretap Static message wiretapping action. The StaticWiretap differs from the StaticRouter in that the StaticWiretap "listens in" on the action chain and allows the message to continue in the chain to subsequent actions, while the StaticRouter action only pushes the message to destinations that are defined in its route-to chain. ------------- I believe StaticWiretap differs from StaticRouter in that the wiretap allows the actions below it to be executed while the router terminates the action chain at the point it is used. The router should therefore be the last action in the chain. Review org.jboss.soa.esb.actions.StaticRouter (extends StaticWiretap): public Message process(Message message) throws ActionProcessingException { super.process(message) ; return null ; } Where return null terminates the action chain. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2297) contradictory statements about gateway EPRs in Programmers Guide

by Jeff Yu (JIRA)

contradictory statements about gateway EPRs in Programmers Guide ---------------------------------------------------------------- Key: JBESB-2297 URL: https://jira.jboss.org/jira/browse/JBESB-2297 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 Reporter: Jeff Yu Fix For: 4.5 The following two statements from the Programmers Guide Chapter 9 - Services, page 67 - Also, note that since a gateway is not an endpoints, it does not have an Endpoint Reference (EPR) persisted in the registry. Chapter 4 - Building and using Services, page 38 - It is possible that multiple EPRs may be present in the Registry with the same Service Name/Category and that some of these EPRs may not be ESB-aware, e.g., Gateways. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2291) No port number in HOST header in outgoing request

by Taro Yasuma (JIRA)

No port number in HOST header in outgoing request ------------------------------------------------- Key: JBESB-2291 URL: https://jira.jboss.org/jira/browse/JBESB-2291 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Taro Yasuma A outgoing request with using SOAPClient action results Host header without port number. HOW TO REPRODUCE: You can see this issue by running a simple example. 1. configure httpclient and httpclient.wire.content category as DEBUG in jboss-log4j.xml to make output of HTTP headers: For example) <category name="org.apache.commons.httpclient"> <priority value="DEBUG"/> </category> <category name="httpclient.wire.content"> <priority value="DEBUG"/> 2. run samples/quickstarts/webservice_consumer1. For example) $ant deploy $ant runtest 3. Find debug output of the Host header in the server log. For example) 2009-01-19 13:28:40,191 DEBUG [org.apache.commons.httpclient.HttpConnection] Open connection to 127.0.0.1:8080 2009-01-19 13:28:40,194 DEBUG [httpclient.wire.header] >> "GET /Quickstart_webservice_consumer1/HelloWorldWS?wsdl HTTP/1.1[\r][\n]" 2009-01-19 13:28:40,259 DEBUG [httpclient.wire.header] >> "User-Agent: Jakarta Commons-HttpClient/3.0.1[\r][\n]" 2009-01-19 13:28:40,259 DEBUG [httpclient.wire.header] >> "Host: 127.0.0.1[\r][\n]" 2009-01-19 13:28:40,259 DEBUG [httpclient.wire.header] >> "[\r][\n]" (snip) -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2293) Incorporate embedded JOPR 1.1.0.GA into esb-console

by Tom Cunningham (JIRA)

Incorporate embedded JOPR 1.1.0.GA into esb-console --------------------------------------------------- Key: JBESB-2293 URL: https://jira.jboss.org/jira/browse/JBESB-2293 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.5 Incorporate the embedded JOPR 1.1.0.GA into esb-console. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2294) Make sure services collect "total number of byte"

by Tom Cunningham (JIRA)

Make sure services collect "total number of byte" ------------------------------------------------- Key: JBESB-2294 URL: https://jira.jboss.org/jira/browse/JBESB-2294 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.5 Placeholder bug for SOA-785 -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2188) Wrong ReplyTo after message delivery failure

by Kevin Conner (JIRA)

Wrong ReplyTo after message delivery failure -------------------------------------------- Key: JBESB-2188 URL: https://jira.jboss.org/jira/browse/JBESB-2188 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Environment: 4 node JBoss ESB 4.4 cluster, clustered JBM 1.4.0 SP3, replicated MySQL 5.0 Reporter: Joakim Sandström Assignee: Kevin Conner Fix For: 4.2.1 CP4, 4.5, 4.4 CP2 ServiceInvoker does not reset ReplyTO when message delivery fails, which causes the next EPR (for the same service) to get the wrong ReplyTO address Steps to reproduce: Node1: 10.5.0.229 Node2: 10.5.0.230 1. uddi contains all cluster node EPR's 2. kill the node (10.5.0.230) behind the first EPR for a service in uddi 3. invoke the service 4. ServiceInvoker sends a mesage to jms://10.5.0.230:1100/queue/myserviceEsbChannel, which failes because the node is down 4.1 ReplyTo is jms://10.5.0.230:1100/queue/myserviceEsbChannel_reply 5. ServiceInvoker sends a message to the next EPR jms://10.5.0.229:1100/queue/myserviceEsbChannel, which succeeds 5.1 ReplyTo IS STILL jms://10.5.0.230:1100/queue/myserviceEsbChannel_reply 6. Message gets delivered successfully, but the reply fails First EPR, message sent to node2, reply to node2: deliver message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://10.5.0.230:1100/queue/myserviceEsbChannel/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.5.0.230:1100/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory :ClusteredConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://10.5.0.230:1100/queue/myserviceEsbChannel_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.5.0.230:1100/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ClusteredConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : jbossESBresponseUUID='de1ddfaf-6d45-4d03-b9ab-97b72244457c'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]] to Service [mycategory:myservice]. Second EPR, message sent to node1, reply to is still node2: deliver message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://10.5.0.229:1100/queue/myserviceEsbChannel/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.5.0.229:1100/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory :ClusteredConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://10.5.0.230:1100/queue/myserviceEsbChannel_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.5.0.230:1100/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ClusteredConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : jbossESBresponseUUID='de1ddfaf-6d45-4d03-b9ab-97b72244457c'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]] to Service [mycategory:myservice]. -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2228) Replies/faults generated from within jBPM should initialise the relatesTo

by Kevin Conner (JIRA)

Replies/faults generated from within jBPM should initialise the relatesTo ------------------------------------------------------------------------- Key: JBESB-2228 URL: https://jira.jboss.org/jira/browse/JBESB-2228 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP1, 4.4 Reporter: Kevin Conner Fix For: 4.5, 4.4 CP2 It should be based on the messageId used when the jBPM process is created. -- 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, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2177) Create a proper mechanism for handling schema evolutions

by Kevin Conner (JIRA)

Create a proper mechanism for handling schema evolutions -------------------------------------------------------- Key: JBESB-2177 URL: https://jira.jboss.org/jira/browse/JBESB-2177 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 Reporter: Kevin Conner Priority: Blocker Fix For: 4.5 We need to create a proper mechanism for handling different schema mechanisms. The current schema has evolved through a number of revisions without updating the version, this is generally a bad practice. We should base the 1.0.1 version of the schema on the SOA 4.3 GA version with any subsequent changes requiring an update to the version/namespace. -- 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, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-2292) Increment jbossesb-server version to 4.5.GA

by Daniel Bevenius (JIRA)

Increment jbossesb-server version to 4.5.GA ------------------------------------------- Key: JBESB-2292 URL: https://jira.jboss.org/jira/browse/JBESB-2292 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Assignee: Daniel Bevenius 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, 3 months

1
1
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