September 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1946) Soapclient ognl soapenc:array support

by Joakim Sandström (JIRA)

Soapclient ognl soapenc:array support ------------------------------------- Key: JBESB-1946 URL: https://jira.jboss.org/jira/browse/JBESB-1946 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Joakim Sandström The current ognl implementation doesn't handle the following response correctly. Only the last findBySomethingReturn item is returned. i.e. <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <ns1:findBySomethingResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://mydomain"> <findBySomethingReturn soapenc:arrayType="ns2:customer[2]" xsi:type="soapenc:Array" xmlns:ns2="urn:sys" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"> <findBySomethingReturn xsi:type="ns2:customer"> <id xsi:type="xsd:int">1</id> <name xsi:type="xsd:string">one</name> </findBySomethingReturn> <findBySomethingReturn xsi:type="ns2:customer"> <id xsi:type="xsd:int">2</id> <name xsi:type="xsd:string">two</name> </findBySomethingReturn> </findBySomethingReturn> </ns1:findBySomethingResponse> </soapenv:Body> </soapenv:Envelope> -- 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, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1553) SOAPClient action remappes objects with null strings to empty strings

by Jiri Pechanec (JIRA)

SOAPClient action remappes objects with null strings to empty strings --------------------------------------------------------------------- Key: JBESB-1553 URL: http://jira.jboss.com/jira/browse/JBESB-1553 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Assigned To: Kevin Conner Fix For: 4.2.1 CP2 Use webservice_consumer2 quickstart and use the attached files - contains enhanced equals and toString defintions. Make sure that option1 is used. The object with following contents is sent to processing to ivoke web service id = 101 lineItems = [Line Item ID= 1 Price=10.0 Ship To=aname, Line Item ID= 2 Price=20.0 Ship To=aname2] shipTo = null But in the web service processing method the contents is id = 101 lineItems = [Line Item ID= 1 Price=10.0 Ship To=aname, Line Item ID= 2 Price=20.0 Ship To=aname2] shipTo = The difference is in shipTo property which was set tu null on the input but comes to web service as empty string. -- 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, 10 months

5
21
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-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-2075) PreparedStatement Factory for debugging

by Mark Little (JIRA)

PreparedStatement Factory for debugging --------------------------------------- Key: JBESB-2075 URL: https://jira.jboss.org/jira/browse/JBESB-2075 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Testing Affects Versions: 4.4 Reporter: Mark Little Consider reworking JDBC transport code to use a PreparedStatement factory pattern that can return a debug-enabled instance for improved traceability. I've got an implementation from JBossTS and I think Kevin has one too. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBESB-2067) Revisit DataFilerScheduler and address scheduler

by Kevin Conner (JIRA)

Revisit DataFilerScheduler and address scheduler ------------------------------------------------ Key: JBESB-2067 URL: https://jira.jboss.org/jira/browse/JBESB-2067 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Reporter: Kevin Conner It is currently setup to use the default quartz scheduler. -- 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-2035) Spring Security as part of service definition.

by Chris Harris (JIRA)

Spring Security as part of service definition. ----------------------------------------------- Key: JBESB-2035 URL: https://jira.jboss.org/jira/browse/JBESB-2035 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP3 Reporter: Chris Harris A customer would like clean integration with Spring Security. It would be nice to be able to define the security constrains as part of the service definition. -- 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-1897) ClassCastException while Drools is getting shadow object

by Martin Vecera (JIRA)

ClassCastException while Drools is getting shadow object -------------------------------------------------------- Key: JBESB-1897 URL: https://jira.jboss.org/jira/browse/JBESB-1897 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.3 Environment: Drools 4.0.2 and 4.0.7 (tried with both), mvel 1.2.24 and 1.3.1 (tried with both), QS bpm_orchestration4 Reporter: Martin Vecera Reproducible 100% = Basic plot = bpm_orchestration4 has the following message flow (it is little bit simplified but covers important parts): starter service -> jBPM process that calls -> intake service with Drools action -> back to jBPM process -> task assigned to an user -> jBPM process calls -> discount service with another Drools action (*) (*) Shows the part where problem arises (inside Drools action): 2008-08-04 08:42:16,210 WARN [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: InVMEpr [ PortReferenc org.drools.RuntimeDroolsException: Error creating shadow fact for object: 2, Wed Nov 15 19:45:28 GMT+01:00 2006, 0, 59.97, 64.92, 4.95, at org.drools.reteoo.Rete$ClassObjectTypeConf.getShadow(Rete.java:636) at org.drools.reteoo.Rete.assertObject(Rete.java:164) at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:192) at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:911) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:883) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:684) at org.jboss.internal.soa.esb.services.routing.cbr.JBossRulesRouter.route(JBossRulesRouter.java:169) at org.jboss.soa.esb.actions.BusinessRulesProcessor.process(BusinessRulesProcessor.java:58) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.ClassCastException: org.jboss.soa.esb.store.OrderHeader at org.jboss.soa.esb.store.OrderHeaderShadowProxy.setShadowedObject(Unknown Source) at org.drools.reteoo.Rete$ClassObjectTypeConf.getShadow(Rete.java:634) ... 13 more The same exception is thrown for both Drools/mvel versions. You have to execute the QS at least TWICE to get the exception (for the first time it works well)! Steps to reproduce: 1. get ESB 4.3.0GA binaries, start it 2. execute samples/quickstarts/bpm_orchestration4 (ant deploy, deployProcess, startProcess) 3. click "Save and Close" on every task that appears in jBPM console 4. the first time the QS finishes without problems so run ant startProcess once more 5. click "Save and Close" on the first task in jBPM console, you won't get the second task assigned since the exception is thrown This QS (from version 4.3.0.GA) works fine with ESB server from trunk (08/04/2008). When I skipped the return from the intake service to jBPM process and put static router from intake service directly to discount service (skipping appropriate process nodes as well), the problem didn't show up. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2008