September 2013 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3950) SOAPClient generates empty objects for not-required fields

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3950: ------------------------------------- Summary: SOAPClient generates empty objects for not-required fields Key: JBESB-3950 URL: https://issues.jboss.org/browse/JBESB-3950 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.11 CP3 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP3 >From Musharraf Hussein : I have a case [1] where customer is having a problem with the way "SOAPClient" generates SOAP messages to invoke the backend WebServices. Actually it is observed that if a complex type of message (element in SOAP message) contains a 'null' then 'SOAPClient' sends an empty element (as well as an empty child element). According to the customer this shouldn't happen and ESB should rather omit the entire parent-child elements altogether, as it is causing them an NPE in their code. This is how executing their test case (attached) look like. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3948) Add option in JBoss ESB Editor to disable an ESB action

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBESB-3948?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick updated JBESB-3948: ------------------------------------- Affects Version/s: 4.x > Add option in JBoss ESB Editor to disable an ESB action > ------------------------------------------------------- > > Key: JBESB-3948 > URL: https://issues.jboss.org/browse/JBESB-3948 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.x > Environment: JBDS 2.0.0.GA > Reporter: Joao Viragine > Assignee: Brian Fitzpatrick > Priority: Optional > > It would be great if we could disable an specific action in ESB. > E.g. > <action class="org.jboss.soa.esb.actions.SystemPrintln" name="Println" enabled="false"> > <property name="message" value="JBoss ESB Rulez"/> > </action> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3948) Add option in JBoss ESB Editor to disable an ESB action

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBESB-3948?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick updated JBESB-3948: ------------------------------------- Component/s: Tooling > Add option in JBoss ESB Editor to disable an ESB action > ------------------------------------------------------- > > Key: JBESB-3948 > URL: https://issues.jboss.org/browse/JBESB-3948 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Environment: JBDS 2.0.0.GA > Reporter: Joao Viragine > Assignee: Brian Fitzpatrick > Priority: Optional > > It would be great if we could disable an specific action in ESB. > E.g. > <action class="org.jboss.soa.esb.actions.SystemPrintln" name="Println" enabled="false"> > <property name="message" value="JBoss ESB Rulez"/> > </action> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3949) Feature request - to support editing JBossESB/SOA-P deployment.xml and jbm-queue-service.xml files

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBESB-3949?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick commented on JBESB-3949: ------------------------------------------ moved to JBESB so we can look at this down the line. > Feature request - to support editing JBossESB/SOA-P deployment.xml and jbm-queue-service.xml files > -------------------------------------------------------------------------------------------------- > > Key: JBESB-3949 > URL: https://issues.jboss.org/browse/JBESB-3949 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > See: JBIDE-6932 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3949) Feature request - to support editing JBossESB/SOA-P deployment.xml and jbm-queue-service.xml files

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBESB-3949?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick moved JBIDE-10114 to JBESB-3949: -------------------------------------------------- Project: JBoss ESB (was: Tools (JBoss Tools)) Key: JBESB-3949 (was: JBIDE-10114) Workflow: jira (was: GIT Pull Request workflow ) Affects Version/s: (was: 3.3.0.M1) Component/s: Tooling (was: esb) Security: Public Fix Version/s: (was: LATER) Rank (Obsolete): (was: 21300000000) > Feature request - to support editing JBossESB/SOA-P deployment.xml and jbm-queue-service.xml files > -------------------------------------------------------------------------------------------------- > > Key: JBESB-3949 > URL: https://issues.jboss.org/browse/JBESB-3949 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > See: JBIDE-6932 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3948) Add option in JBoss ESB Editor to disable an ESB action

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBESB-3948?page=com.atlassian.jira.plugin... ] Paul Leacu moved JBIDE-4160 to JBESB-3948: ------------------------------------------ Project: JBoss ESB (was: Tools (JBoss Tools)) Key: JBESB-3948 (was: JBIDE-4160) Workflow: jira (was: GIT Pull Request workflow ) Affects Version/s: (was: 3.0.0.GA) Component/s: (was: esb) Security: Public Fix Version/s: (was: LATER) Rank (Obsolete): (was: 8950000000) > Add option in JBoss ESB Editor to disable an ESB action > ------------------------------------------------------- > > Key: JBESB-3948 > URL: https://issues.jboss.org/browse/JBESB-3948 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: JBDS 2.0.0.GA > Reporter: Joao Viragine > Assignee: Brian Fitzpatrick > Priority: Optional > > It would be great if we could disable an specific action in ESB. > E.g. > <action class="org.jboss.soa.esb.actions.SystemPrintln" name="Println" enabled="false"> > <property name="message" value="JBoss ESB Rulez"/> > </action> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3946) SOA-P 5.3.1 needs to support SOAP 1.2 Authentication

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3946?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3946. --------------------------------- > SOA-P 5.3.1 needs to support SOAP 1.2 Authentication > ---------------------------------------------------- > > Key: JBESB-3946 > URL: https://issues.jboss.org/browse/JBESB-3946 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP3 > > > From case : > We want to use SOAP 1.2 with JBoss ESB, but some of the classes are not compatible implemented. > In "SoapExtractionUtil" hard coded QNames are used! > Code snippet: > public static boolean isStartOfHeader(final XMLEvent event) > { > return event.isStartElement() && ((StartElement)event).getName().equals(SOAP_HEADER_QNAME); > } > When this is used by the "UsernameTokenExtractor", in the method "extractSecurityInfo" and the security is no longer useable when using SOAP 1.2!!! > Code snippet: > public AuthenticationRequest extractSecurityInfo(final String soap) > throws ExtractionException { > if (soap == null || !soap.startsWith("<")) > return null; > XMLEventReader xmlReader = null; > User user = null; > Set<Object> credentials = new HashSet<Object>(); > try { > xmlReader = XML_INPUT_FACTORY > .createXMLEventReader(new StringReader(soap)); > while (xmlReader.hasNext()) { > XMLEvent xmlEvent = xmlReader.nextEvent(); > if (isStartOfHeader(xmlEvent)) { > We need to support "SOAP 1.2" to communicate with customers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3946) SOA-P 5.3.1 needs to support SOAP 1.2 Authentication

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3946?page=com.atlassian.jira.plugin... ] Tom Cunningham resolved JBESB-3946. ----------------------------------- Assignee: Tom Cunningham Resolution: Done > SOA-P 5.3.1 needs to support SOAP 1.2 Authentication > ---------------------------------------------------- > > Key: JBESB-3946 > URL: https://issues.jboss.org/browse/JBESB-3946 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP3 > > > From case : > We want to use SOAP 1.2 with JBoss ESB, but some of the classes are not compatible implemented. > In "SoapExtractionUtil" hard coded QNames are used! > Code snippet: > public static boolean isStartOfHeader(final XMLEvent event) > { > return event.isStartElement() && ((StartElement)event).getName().equals(SOAP_HEADER_QNAME); > } > When this is used by the "UsernameTokenExtractor", in the method "extractSecurityInfo" and the security is no longer useable when using SOAP 1.2!!! > Code snippet: > public AuthenticationRequest extractSecurityInfo(final String soap) > throws ExtractionException { > if (soap == null || !soap.startsWith("<")) > return null; > XMLEventReader xmlReader = null; > User user = null; > Set<Object> credentials = new HashSet<Object>(); > try { > xmlReader = XML_INPUT_FACTORY > .createXMLEventReader(new StringReader(soap)); > while (xmlReader.hasNext()) { > XMLEvent xmlEvent = xmlReader.nextEvent(); > if (isStartOfHeader(xmlEvent)) { > We need to support "SOAP 1.2" to communicate with customers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2013