January 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3017) jboss-esb.xml schema location fix

by Tom Eicher (JIRA)

jboss-esb.xml schema location fix --------------------------------- Key: JBESB-3017 URL: https://jira.jboss.org/jira/browse/JBESB-3017 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment, Documentation, Examples Affects Versions: 4.6, 4.5 Reporter: Tom Eicher 1. All jboss-esb.xml still point to http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... where nowadays it should be http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem... 2. shouldn't we use version 1.1.0 now ? 3. please include a xsi:schemaLocation xsi:schemaLocation="http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> Cheers, Tom. -- 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

14 years

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3082) Optional Parameter in XsltAction

by Fernando Ribeiro (JIRA)

Optional Parameter in XsltAction -------------------------------- Key: JBESB-3082 URL: https://jira.jboss.org/jira/browse/JBESB-3082 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Fernando Ribeiro The resultType parameter should really be optional, as described in the documentation. <action name="action1" class="org.jboss.soa.esb.actions.transformation.xslt.XsltAction"> <property name="templateFile" value="/xsl/Stylesheet1.xsl" /> </action> .. gives me an error saying resultType needs to be there. -- 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

14 years

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3081) Error in Documentation of XsltAction

by Fernando Ribeiro (JIRA)

Error in Documentation of XsltAction ------------------------------------ Key: JBESB-3081 URL: https://jira.jboss.org/jira/browse/JBESB-3081 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.7 Reporter: Fernando Ribeiro On page 98 of the Programmers Guide, it says "XslAction" instead of "XsltAction". -- 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

14 years

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3138) Usename token authentication does not work

by Jiri Pechanec (JIRA)

Usename token authentication does not work ------------------------------------------ Key: JBESB-3138 URL: https://jira.jboss.org/jira/browse/JBESB-3138 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Reporter: Jiri Pechanec Priority: Critical If security is enable on service and SOAP message with Username token is sent then server throws SecurityException 12:45:40,293 ERROR [ActionProcessingPipeline] SecurityService exception : org.jboss.soa.esb.services.security.SecurityServiceException: Service 'MyWSProducerService' has been configured for security but no AuthenticationRequest could be located in the Message Context. Cannot authenticate without an AuthenticationRequest. at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:527) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:419) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) -- 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

14 years

4
11
0 / 0

[JBoss JIRA] Created: (JBESB-2270) Provide an alternative for bean configured action

by Kevin Conner (JIRA)

Provide an alternative for bean configured action ------------------------------------------------- Key: JBESB-2270 URL: https://jira.jboss.org/jira/browse/JBESB-2270 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.x The bean configured action code has a number of deficiencies which include the following - instantiation of the action per message - no support for standard callbacks (including lifecycles) We should create an alternative which creates a single instance of the action, configures properties through reflection and also supports the standard callback methods. -- 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

14 years

2
3
0 / 0

[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

14 years

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

14 years

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

14 years

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3026) Remove DOCTYPE declarations from jboss-web files

by Kevin Conner (JIRA)

Remove DOCTYPE declarations from jboss-web files ------------------------------------------------ Key: JBESB-3026 URL: https://jira.jboss.org/jira/browse/JBESB-3026 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 This forces a network access which prevents offline CI runs from working and is unnecessary. -- 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

14 years

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

14 years

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2010