August 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2574) OGNLUtils.assertIsCollection fails

by jarkko Lietolahti (JIRA)

OGNLUtils.assertIsCollection fails ---------------------------------- Key: JBESB-2574 URL: https://jira.jboss.org/jira/browse/JBESB-2574 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: jarkko Lietolahti The method private static boolean assertIsCollection(Element element) { if(element.getAttributeNS(JBOSSESB_SOAP_NS, IS_COLLECTION_ATTRIB).equals("true")) { // It's already been attributed... no need to check for the soapui comment... return true; } Comment firstComment = (Comment) YADOMUtil.getFirstChildByType(element, Node.COMMENT_NODE); // TODO: Get Ole (soapUI) to add an attribute to the collection element - better than looking for this comment. if(firstComment != null && firstComment.getTextContent().indexOf("1 or more repetitions") != -1) { return true; } return false; } Especially row; Comment firstComment = (Comment) YADOMUtil.getFirstChildByType(element, Node.COMMENT_NODE); is causing a grief. Given an WSDL like below; <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" > <soapenv:Header/> <soapenv:Body> <QueryRequest> <username>?</username> <password>?</password> <Customer id="?" telcoid="?"> </Customer>  <productIds>?</productIds> <isLookup>?</isLookup> <maxWaitTime>?</maxWaitTime> </QueryRequest> </soapenv:Body> </soapenv:Envelope> OGNLUtils creates ognlExpression QueryRequest[0] for all the elements below QueryRequest. E.g. ognl for username, password etc is "QueryRequest[0]" when in reality it should be QueryRequest.username , QueryRequest.password etc.. This is caused by the array element LATER in the WSDL; -- 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

13 years, 11 months

4
9
0 / 0

[JBoss JIRA] Created: (JBESB-1171) Remove usages org.jboss.soa.esb.listeners.message.MockMessageComposer and replace with BasicMessageComposer

by Tom Fennelly (JIRA)

Remove usages org.jboss.soa.esb.listeners.message.MockMessageComposer and replace with BasicMessageComposer ----------------------------------------------------------------------------------------------------------- Key: JBESB-1171 URL: http://jira.jboss.com/jira/browse/JBESB-1171 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 IR1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 Not doing anything extra -- 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

13 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2489) JMS bus with topic cannot be used in jms-jca-provider

by Martin Vecera (JIRA)

JMS bus with topic cannot be used in jms-jca-provider ----------------------------------------------------- Key: JBESB-2489 URL: https://jira.jboss.org/jira/browse/JBESB-2489 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP2 Reporter: Martin Vecera JMS bus based on a topic cannot be used within jms-jca-provider. On deployment the following exception occurs: 009-03-25 09:46:45,904 WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@3efbb1d8(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)6333934d destination=queue/pt_qs_nojbm_notifier_topictest_gw isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=1 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) java.lang.ClassCastException: Object at 'queue/pt_qs_nojbm_notifier_topictest_gw' in context {java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, hostKey=localhost:1100, jnp.partitionName=DefaultPartition, jnp.discoveryTimeout=5000, jnp.discoveryGroup=230.0.0.4, jnp.disableDiscovery=false, java.naming.provider.url=localhost:1100, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces, jnp.maxRetries=1, jnp.discoveryPort=1102, jnp.discoveryTTL=16} is not an instance of [class=javax.jms.Topic classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Destination classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2}}] object class is [class=org.jboss.jms.destination.JBossQueue classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Queue classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2}}] at org.jboss.util.naming.Util.checkObject(Util.java:329) at org.jboss.util.naming.Util.lookup(Util.java:216) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:409) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:316) at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:635) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756) at java.lang.Thread.run(Thread.java:595) Then on usage: 2009-03-25 09:46:55,926 INFO [org.jboss.resource.adapter.jms.inflow.JmsActivation] Attempting to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@3efbb1d8(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)6333934d destination=queue/pt_qs_nojbm_notifier_topictest_gw isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=1 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) 2009-03-25 09:46:55,931 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@3efbb1d8(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)6333934d destination=queue/pt_qs_nojbm_notifier_topictest_gw isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=1 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) java.lang.ClassCastException: Object at 'queue/pt_qs_nojbm_notifier_topictest_gw' in context {java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, hostKey=localhost:1100, jnp.partitionName=DefaultPartition, jnp.discoveryTimeout=5000, jnp.discoveryGroup=230.0.0.4, jnp.disableDiscovery=false, java.naming.provider.url=localhost:1100, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces, jnp.maxRetries=1, jnp.discoveryPort=1102, jnp.discoveryTTL=16} is not an instance of [class=javax.jms.Topic classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Destination classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2}}] object class is [class=org.jboss.jms.destination.JBossQueue classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Queue classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2}}] at org.jboss.util.naming.Util.checkObject(Util.java:329) at org.jboss.util.naming.Util.lookup(Util.java:216) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:409) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:316) at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:259) at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:639) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756) at java.lang.Thread.run(Thread.java:595) -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2554) HttpRouter stores http headers of request in body instead of headers from http response

by Jurgen Van Bouchaute (JIRA)

HttpRouter stores http headers of request in body instead of headers from http response ---------------------------------------------------------------------------------------- Key: JBESB-2554 URL: https://jira.jboss.org/jira/browse/JBESB-2554 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.5 Environment: Windows Vista Ultimate, Sun JRE 1.6.10, JBOSS ESB 4.5-GA Reporter: Jurgen Van Bouchaute Priority: Minor org.jboss.soa.esb.actions.routing.http.HttpRouter using http method "POST" stores HTTP headers from the request in the Message body instead of headers from the response : private void attachResponseDetails(Message message, HttpMethodBase method, int responseCode) { HttpResponse response = new HttpResponse(responseCode); response.setEncoding(method.getResponseCharSet()); response.setLength(method.getResponseContentLength()); >>>>> Header[] responseHeaders = method.getRequestHeaders(); <<<<<<< for(Header responseHeader : responseHeaders) { response.addHeader(new HttpHeader(responseHeader.getName(), responseHeader.getValue())); } message.getBody().add(HttpResponse.RESPONSE_KEY, response); } -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-800) Provide in the documentation the links of the existing wiki pages for the quickstart samples.

by angel asencio (JIRA)

Provide in the documentation the links of the existing wiki pages for the quickstart samples. --------------------------------------------------------------------------------------------- Key: JBESB-800 URL: http://jira.jboss.com/jira/browse/JBESB-800 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: angel asencio Assigned To: Mark Little Priority: Minor To list any existing wiki quickstart sample link under the corresponding quickstart sample listed in the GettingStarted Guide and the readme.txt of that quickstart sample. For examples: There exist a wiki for the Hello World quickstart: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossESBHelloworld This should be listed under the listing of helloworld in the Getting Started Guide and in the readme.txt of the helloworld quickstart sample. -- 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

13 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-801) Wiki pages should be create for all JBoss ESB Quickstarts.

by angel asencio (JIRA)

Wiki pages should be create for all JBoss ESB Quickstarts. ---------------------------------------------------------- Key: JBESB-801 URL: http://jira.jboss.com/jira/browse/JBESB-801 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: angel asencio Assigned To: Mark Little Priority: Minor Wiiki pages should be provided like the ones created for the quickstart samples helloworld and simple_cbr that ease the understanding of these concepts. In addition it can provide navigation links to dependent concepts or concepts that the quickstart sample depends on. -- 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

13 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1912) There are two HttpRouter actions in codebase

by Jiri Pechanec (JIRA)

There are two HttpRouter actions in codebase -------------------------------------------- Key: JBESB-1912 URL: https://jira.jboss.org/jira/browse/JBESB-1912 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Jiri Pechanec Fix For: 4.4 CP1 There is org.jboss.soa.esb.actions.routing.HttpRouter action. This action does not support standard router features and should be removed. -- 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

13 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2748) Statistics in JBossESB console contains null values

by Jiri Pechanec (JIRA)

Statistics in JBossESB console contains null values --------------------------------------------------- Key: JBESB-2748 URL: https://jira.jboss.org/jira/browse/JBESB-2748 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management, Tooling Affects Versions: 4.4 CP3 Environment: SOA-P 4.3 CP02 ER3 - plain all config Reporter: Jiri Pechanec Whenever the statisccs are collected and recorded the management console displays two values - one with real data and second with null value 07-16 13:35:29 0 07-16 13:35:29 null It is enough just to start server and hit Collect statistics button in 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

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2800) SOAPClient does not allow specification of content type in the http header

by Pavel Drozd (JIRA)

SOAPClient does not allow specification of content type in the http header -------------------------------------------------------------------------- Key: JBESB-2800 URL: https://jira.jboss.org/jira/browse/JBESB-2800 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.3 Reporter: Pavel Drozd SOAPClient does not allow communication in SOAP 1.2 with Axis Webservice. Axis requires (in SOAP1.2) specific content type in the http header (application/soap+xml). The SOAPClient does not allow to change this and allways fills the content type by the string "text/xml", which is specific for SOAP1.1. -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2798) QS: transfrorm_XML2XML_simple - org.jboss.soa.esb.testutils.JMSUtil class missing

by Boris Belovic (JIRA)

QS: transfrorm_XML2XML_simple - org.jboss.soa.esb.testutils.JMSUtil class missing --------------------------------------------------------------------------------- Key: JBESB-2798 URL: https://jira.jboss.org/jira/browse/JBESB-2798 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 Reporter: Boris Belovic In build.xml ( on line 22) in transform_XML2XML_simple quickstart is notifyUpdate target which depends on org.jboss.soa.esb.testutils.JMSUtil class. This target fails because this class is no more part of ESB, other targets work fine for this quickstart. Target with missing class: <target name="notifyUpdate" depends="compile" description="Send a notification message to the JMS Topic"> <echo>Sending transformation update notification for transform "simple-transform" to deployed ESB.</echo> <java fork="yes" classname="org.jboss.soa.esb.testutils.JMSUtil" failonerror="true" classpathref="exec-classpath"> <arg value="topic/org.jboss.soa.esb.transformation.Update"/> <arg value="topic"/> <arg value="simple-transform"/> </java> </target> and the exception which this target throws: Caused by: java.lang.ClassNotFoundException: org.jboss.soa.esb.testutils.JMSUtil [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:200) [java] at java.security.AccessController.doPrivileged(Native Method) [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:307) [java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:252) [java] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) [java] Could not find the main class: org.jboss.soa.esb.testutils.JMSUtil. Program will exit. -- 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

13 years, 11 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2009