Bug 779656 - Expose complete SOAP message when exposing ESB as a WS
Summary: Expose complete SOAP message when exposing ESB as a WS
Keywords:
Status: CLOSED DUPLICATE of bug 2040112
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-31 14:31 UTC by Lennart Petersson
Modified: 2012-07-13 04:19 UTC (History)
1 user (show)

Fixed In Version:
Clone Of: SOA-2023
Environment:
Last Closed: 2010-04-01 13:35:56 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2023 0 None None None Never

Description Lennart Petersson 2010-03-31 14:31:54 UTC 
++ This bug is a clone of bug 779655 ++

Help Desk Ticket Reference: https://support.redhat.com/jbossnetwork/restricted/caseDetail.html?caseId=376239
project_key: SOA

We are deploying an ESB service and exposing it as a WS by the simple use of in/out/fault xsd on the service element. What is a pity is that we are not able to get hold of SOAP Header parameters from the incoming request in the action pipeline, and also not able to specify SOAP parameters for the response message.

This would be very good if it could be supported. Preferable via a service configuration - should SOAP parts be stripped away or not. Can really not see why this was not supported from the beginning since it should be a rather common scenario. The alternative approaches to expose ESB as a WS, works as a workaround, but they are to 'complicated'. Like this simple way better...

regards,

Lennart Petersson
Redpill Linpro
Comment 1 Lennart Petersson 2010-04-01 13:35:56 UTC 
https://jira.jboss.org/jira/browse/JBESB-3260
Note You need to log in before you can comment on or make changes to this bug.