March 2012 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3769) ContentBasedWiretap fails to route message to original recipiet if no match is found for message

by Jason Shepherd (JIRA)

Jason Shepherd created JBESB-3769: ------------------------------------- Summary: ContentBasedWiretap fails to route message to original recipiet if no match is found for message Key: JBESB-3769 URL: https://issues.jboss.org/browse/JBESB-3769 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.7 Environment: JBoss Enterprise SOA-P 5.0.1 Reporter: Jason Shepherd Priority: Minor See the attach fun_cbr.src.zip. I added an action after the ContentRouterWiretap. I found that this action is called when we get a match for the ContentBasedWiretap, but in the case that you send a message that does not match, the action Println is not executed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
3
0 / 0

[JBoss JIRA] (JBESB-3755) Add a JAXB Binding file to a Wise Soap Client

by Jason Shepherd (JIRA)

Jason Shepherd created JBESB-3755: ------------------------------------- Summary: Add a JAXB Binding file to a Wise Soap Client Key: JBESB-3755 URL: https://issues.jboss.org/browse/JBESB-3755 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.10 Environment: SOA-P 5.1.2 ESB 4.10 Reporter: Jason Shepherd Currently the Wise SOAP Client doesn't have a way to pass a binding file when parsing the WSDL. This would be very useful, as it would allow the customization of the marshalled WSDL. For example, the generated classes could be force to Serializable. Add a property for the jaxb-binding.xml file to use for the parsing of the WSDL. Eg: <action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.wise.SOAPClient"> <property name="wsdl" value="http://127.0.0.1:8080/Quickstart_webservice_consumer_wise4/HelloWorldWS?wsdl" /> <property name="bindingFile" value="jaxb-binding.xml"/> </action> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
8
0 / 0

[JBoss JIRA] (JBESB-3768) Race condition in sql-provider

by Dave Siracusa (JIRA)

Dave Siracusa created JBESB-3768: ------------------------------------ Summary: Race condition in sql-provider Key: JBESB-3768 URL: https://issues.jboss.org/browse/JBESB-3768 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.8 Environment: Windows 7, RHEL Linux 64bit Reporter: Dave Siracusa Appears to be a bug in SqlTableGatewayListener.java. Method changeStatus uses the insert-timestamp-column to insure it alone updated the row. The value it puts in the string is based on now.toString() (i.e: Wed Mar 28 15:57:10 EDT 2012) I believe this level of granularity will lead lead to race conditions when running on multiple threads, nodes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
2
0 / 0

[JBoss JIRA] (JBESB-3766) Add test for WISE SOAPClient with wrapped services

by Magesh Bojan (JIRA)

Magesh Bojan created JBESB-3766: ----------------------------------- Summary: Add test for WISE SOAPClient with wrapped services Key: JBESB-3766 URL: https://issues.jboss.org/browse/JBESB-3766 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.10 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 4.11 Test for JBESB-3727. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] (JBESB-3762) Add ivy.xml for jbrules

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3762: ------------------------------------- Summary: Add ivy.xml for jbrules Key: JBESB-3762 URL: https://issues.jboss.org/browse/JBESB-3762 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Add a ivy.xml for jbrules. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
2
0 / 0

[JBoss JIRA] (JBESB-3765) Please make WISE client properties available for variable substitutions

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3765: ------------------------------------- Summary: Please make WISE client properties available for variable substitutions Key: JBESB-3765 URL: https://issues.jboss.org/browse/JBESB-3765 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 The Wise SOAPClient currently uses a properties file to specify configuration values like a working directory. These are not subject to property substitution like everything we have in our XML configuration files. Please move the properties into XML configuration (perhaps in the Action configuration in jboss-esb.xml) so our customers will have a consistent substitution mechanism. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
4
0 / 0

[JBoss JIRA] (JBESB-3764) Investigate failure of BusinessRulesProcessorUnitTest

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3764: ------------------------------------- Summary: Investigate failure of BusinessRulesProcessorUnitTest Key: JBESB-3764 URL: https://issues.jboss.org/browse/JBESB-3764 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.11 Reporter: Tom Cunningham Fix For: 4.12 Investigate the sporadic failure of the BusinessRulesProcessorUnitTest test. On some systems, this test fails repeatedly, on others it does not, and on others it fails sporadically. Adding the following patch from Magesh to temporarily get the test to run again, please uncomment the line specified below when testing the BusinessRulesProcessorUnitTest Index: product/services/jbrules/src/test/java/org/jboss/soa/esb/actions/BusinessRulesProcessorUnitTest.java =================================================================== --- product/services/jbrules/src/test/java/org/jboss/soa/esb/actions/BusinessRulesProcessorUnitTest.java (revision 37925) +++ product/services/jbrules/src/test/java/org/jboss/soa/esb/actions/BusinessRulesProcessorUnitTest.java (working copy) @@ -266,7 +266,7 @@ runCEP(processor, message, "Joe", "vote5", "Joe", "vote5") ; // dispose the session after this call - message.getProperties().setProperty( DISPOSE.getName(), Boolean.TRUE ); + //message.getProperties().setProperty( DISPOSE.getName(), Boolean.TRUE ); runCEP(processor, message, "Jane", "vote6", "Jane", "vote6") ; } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3756) Hibernate/juddi error upon deployment in JBoss AS 6.1.0.Final

by Daniel Bevenius (JIRA)

Daniel Bevenius created JBESB-3756: -------------------------------------- Summary: Hibernate/juddi error upon deployment in JBoss AS 6.1.0.Final Key: JBESB-3756 URL: https://issues.jboss.org/browse/JBESB-3756 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.10 Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Optional Fix For: 4.11 Upon start up of JBoss ESB 4.10 on JBoss AS 6.1.0.Final the following error is logged in the console: {code} 08:57:58,495 INFO [Configuration] Reading mappings from resource : META-INF/esb-juddi-orm.xml 08:57:58,513 ERROR [ErrorLogger] Error parsing XML (5) : cvc-complex-type.3.1: Value '1.0' of attribute 'version' of element 'entity-mappings' is not valid with respect to the corresponding attribute use. Attribute 'version' has a fixed value of '2.0'. {code} The mapping error is really just a warning that hibernate could not parse the mapping file with JPA 2.0, but hibernate will fallback to 1.0 and things will work as expected. Details can be found [here|http://lists.jboss.org/pipermail/hibernate-dev/2011-May/006483.html] A possible solution for this is to have a different esb-juddi-orm.xml for as6 which will be used when installing to AS 6.1.0.Final. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
2
0 / 0

[JBoss JIRA] (JBESB-3760) Deploying JBoss ESB to JBoss AS 6.1.0.Final fails from source distribution

by Daniel Bevenius (JIRA)

Daniel Bevenius created JBESB-3760: -------------------------------------- Summary: Deploying JBoss ESB to JBoss AS 6.1.0.Final fails from source distribution Key: JBESB-3760 URL: https://issues.jboss.org/browse/JBESB-3760 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Reporter: Daniel Bevenius Assignee: Daniel Bevenius When running 'ant deploy' from the install directory the following error occurs: {noformat} internal.deploy.jbossas6: [copy] Copying 1 file to /Users/danbev/work/jboss/as/bundles/jboss-6.1.0.Final/server/default/deployers/esb.deployer/META-INF [copy] Copying 1 file to /Users/danbev/work/jboss/as/bundles/jboss-6.1.0.Final/server/default/deployers/esb.deployer/lib [copy] Copying 1 file to /Users/danbev/work/jboss/as/bundles/jboss-6.1.0.Final/server/default/deploy/jbpm.esb BUILD FAILED /Users/danbev/work/jboss/esb/trunk/product/install/build.xml:511: Warning: Could not find file /Users/danbev/work/jboss/esb/trunk/product/build/jbossesb/install/as6-extras/jbpm/jbpm-identity-config.jar to copy. {noformat} There is only one jar in the directory build/jbossesb/install/as6-extras/jbpm/ which is jbpm-identity-3.2.7.jar so perhaps this is just a left over from a previous task. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] (JBESB-3727) WISE SOAPClient fails to work with WRAPPED services

by Magesh Bojan (JIRA)

Magesh Bojan created JBESB-3727: ----------------------------------- Summary: WISE SOAPClient fails to work with WRAPPED services Key: JBESB-3727 URL: https://issues.jboss.org/browse/JBESB-3727 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.10 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 4.10 CP1 Using WRAPPED services not all parameters are mapped to the SOAP request envelope. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2012