July 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2604) Document registry interceptors

by Aaron Pestel (JIRA)

Document registry interceptors ------------------------------ Key: JBESB-2604 URL: https://jira.jboss.org/jira/browse/JBESB-2604 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Environment: SOA-P 4.3 SP1 Reporter: Aaron Pestel Priority: Minor This is a request to document the two known registry interceptors: org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor and org.jboss.internal.soa.esb.services.registry.CachingRegistryInterceptor The InVMRegistryInterceptor is listed in the services guide, section 2.1 and 3.2: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP01/html-single/... In section 2.1, it shows an extract of the registry portion of the jbossesb-properties.xml - which includes InVMRegistryInterceptor, and then goes on to describe each property, but neglects to describe the org.jboss.soa.esb.registry.interceptors property where InVMRegistryInterceptor is set. I am requesting a description in section 2.1 of the org.jboss.soa.esb.registry.interceptors property to include: 1.) format for adding 1 or many interceptors (using ", ") 2.) description of two currently available interceptors (InVMRegistryInterceptor and CachingRegistryInterceptor) 3.) description of when it would make sense or not make sense to use these two interceptors Thanks! -- 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

15 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-2442) Scout creates a new AuthToken for every invocation through BusinessQuery/BusinessLifecycle Managers

by Kevin Conner (JIRA)

Scout creates a new AuthToken for every invocation through BusinessQuery/BusinessLifecycle Managers --------------------------------------------------------------------------------------------------- Key: JBESB-2442 URL: https://jira.jboss.org/jira/browse/JBESB-2442 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The consequence of this is that the jUDDI authentication table keeps growing quickly. -- 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

15 years, 9 months

3
14
0 / 0

[JBoss JIRA] Created: (JBESB-2110) Move LogicalEPRUnitTest away from files

by Kevin Conner (JIRA)

Move LogicalEPRUnitTest away from files --------------------------------------- Key: JBESB-2110 URL: https://jira.jboss.org/jira/browse/JBESB-2110 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.4 Reporter: Kevin Conner The test relies on the existence of a file for output, leading to an obvious race between creating/reading. We should change this test to pass the messages via an MBean as in the other tests. -- 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

15 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-1715) Add support for annotated actions

by Kevin Conner (JIRA)

Add support for annotated actions --------------------------------- Key: JBESB-1715 URL: http://jira.jboss.com/jira/browse/JBESB-1715 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.4 -- 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

15 years, 9 months

4
10
0 / 0

[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

15 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2556) Character corruption using SOAPClient (SOAPUI)

by Theodore S (JIRA)

Character corruption using SOAPClient (SOAPUI) ---------------------------------------------- Key: JBESB-2556 URL: https://jira.jboss.org/jira/browse/JBESB-2556 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.5 Environment: any Reporter: Theodore S When using SOAPUI using International characters can lead to character corruption. How to reproduce: Send chinese characters in the WS request to a webservice endpoint using the SOAPUI integration in JBossESB. Fix: In class org.jboss.soa.esb.actions.soap.SOAPClient change line 462: post.setRequestEntity(new StringRequestEntity(request)); to StringRequestEntity requestEntity = new StringRequestEntity(request,"text/xml","UTF-8"); post.setRequestEntity(requestEntity); -- 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

15 years, 10 months

3
3
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

15 years, 11 months

5
21
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

15 years, 11 months

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

15 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

15 years, 11 months

3
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2009