August 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3639) Quickstarts fail to compile or deploy depending on existence of /server/default directory

by Tom Cunningham (JIRA)

Quickstarts fail to compile or deploy depending on existence of /server/default directory ----------------------------------------------------------------------------------------- Key: JBESB-3639 URL: https://issues.jboss.org/browse/JBESB-3639 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 When one tries to deploy (ant deploy) any quickstart the QS/conf/base-build.xml among other thins checks for existence of /server/default directory... if the directory doesn't exist, the ant execution fails. If anyone removes or renames (that is presumable) the default profile he would not be able to run the quickstarts ant at all... To reproduce: 1) unzip SOA-P 2) move/rename ${SOA-P}/jboss-as/server/default to ${SOA-P}/jboss-as/server/<anything-else> 3) from ${SOA-P}/jboss-as/samles/quickstarts/helloworld run 'ant deploy': $ ant deploy Buildfile: build.xml BUILD FAILED /SOA-P/jboss-as/samples/quickstarts/helloworld/build.xml:9: The following error occurred while executing this line: /SOA-P/jboss-as/samples/quickstarts/conf/base-build.xml:57: Cannot determine build hierarchy Total time: 0 seconds -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3659) Investigate conflicting JAR versions in SOA-P

by Tom Cunningham (JIRA)

Investigate conflicting JAR versions in SOA-P --------------------------------------------- Key: JBESB-3659 URL: https://issues.jboss.org/browse/JBESB-3659 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Investigate whether we can change versions of the following JARs : esb.deployer/lib/commons-codec-1.3.jar /client/commons-codec-1.4.jar jbpm.esb/commons-fileupload.jar (version 1.1.1) jbpm.esb/gpd-deployer.war/WEB-INF/lib/commons-fileupload-1.2.1.jar esb.deployer/lib/commons-io-1.3.jar jbpm.esb/gpd-deployer.war/WEB-INF/lib/commons-io-1.4.jar esb.deployer/lib/stringtemplate-3.0.jar jbrules.esb/stringtemplate-3.2.1.jar -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3628) business_ruleservice_stateful QS doesn't work as expected

by Tom Cunningham (JIRA)

business_ruleservice_stateful QS doesn't work as expected --------------------------------------------------------- Key: JBESB-3628 URL: https://issues.jboss.org/browse/JBESB-3628 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 After the second message is sent, business_ruleservice_stateful QS should set the discount on the second order to 10 %. Instead, the following is seen in server.log, stating that the discount is actually 0 %. 2010-10-19 13:12:56,924 INFO [STDOUT] (pool-37-thread-1) set discount of 0.0 on order 2 for customer user1 2010-10-19 13:12:56,924 INFO [STDOUT] (pool-37-thread-1) set discount of 0.0 on order 1 for customer user1 2010-10-19 13:12:56,924 INFO [STDOUT] (pool-37-thread-1) Customer user1 now has a shopping total of 129.84 2010-10-19 13:12:56,925 INFO [STDOUT] (pool-37-thread-1) set discount of 0.0 on order 2 for customer user1 2010-10-19 13:12:56,925 INFO [STDOUT] (pool-37-thread-1) Customer user1 now has a shopping total of 129.84 The time the third message is sent, the discount is actually set to 10 %, with this in the server.log: 2010-10-19 13:37:19,701 INFO [STDOUT] (pool-28-thread-1) set discount of 0.0 on order 3 for customer user1 2010-10-19 13:37:19,701 INFO [STDOUT] (pool-28-thread-1) set discount of 0.0 on order 2 for customer user1 2010-10-19 13:37:19,701 INFO [STDOUT] (pool-28-thread-1) set discount of 0.0 on order 1 for customer user1 2010-10-19 13:37:19,702 INFO [STDOUT] (pool-28-thread-1) Customer user1 now has a shopping total of 194.76 2010-10-19 13:37:19,702 INFO [STDOUT] (pool-28-thread-1) set discount of 10.0 on order 3 for customer user1 2010-10-19 13:37:19,702 INFO [STDOUT] (pool-28-thread-1) set discount of 10.0 on order 3 for customer user1 2010-10-19 13:37:19,702 INFO [STDOUT] (pool-28-thread-1) Customer user1 now has a shopping total of 194.76 2010-10-19 13:37:19,702 INFO [STDOUT] (pool-28-thread-1) Customer user1 now has a shopping total of 194.76 It seems as if a different Customer instance is picked when the rules are fired the second time - the instance that still has the discount set to 0 %. This would suggest some faulty behavior wrt. classloading, perhaps even SOA-2419. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3646) Apply patch from SOA-3221, create GSS-SOA-3222 branch

by Tom Cunningham (JIRA)

Apply patch from SOA-3221, create GSS-SOA-3222 branch ----------------------------------------------------- Key: JBESB-3646 URL: https://issues.jboss.org/browse/JBESB-3646 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.4 CP2 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 CP5 Create a branch of JBESB_4_4_GA_CP5_CR2 and apply the patch from SOA-3221 for byte[] handling. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3656) Remove extraneous pom.xml from soapui-client

by Tom Cunningham (JIRA)

Remove extraneous pom.xml from soapui-client -------------------------------------------- Key: JBESB-3656 URL: https://issues.jboss.org/browse/JBESB-3656 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Remove extraneous pom.xml from soapui-client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3655) Patch POSTHttpMethodFactory for 4.3CP02

by Tom Cunningham (JIRA)

Patch POSTHttpMethodFactory for 4.3CP02 --------------------------------------- Key: JBESB-3655 URL: https://issues.jboss.org/browse/JBESB-3655 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 CP3 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 CP4 Make POSTHttpMethodFactory accept byte []. See attached SOA bugs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3654) Wise SOAPClient SOAPFaultException lost

by Tom Cunningham (JIRA)

Wise SOAPClient SOAPFaultException lost --------------------------------------- Key: JBESB-3654 URL: https://issues.jboss.org/browse/JBESB-3654 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.9 CP1 Reporter: Tom Cunningham Fix For: 4.9 CP2 Wise will allow expected exceptions to be returned as an InvocationResult but will trap anything it does not recognise and throw it back to the invoker as an exception. This terminates the pipeline and the remainder of the pipeline is prevented from processing the valid SOAP response because wise is turning it into an exception, thereby treating it in a different manner from the exceptions that are defined within the WSDL (and expected). It is still visible through the exception processing but shouldn't be, it should be treated in the same manner as other SOAP faults. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2011