Bug 780924 (SOA-3387) - WS-Addressing error message when SOAPAction != Action header is not intuitive
Summary: WS-Addressing error message when SOAPAction != Action header is not intuitive
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-3387
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: unspecified
Version: 5.2.0.ER3
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: 2011-09-19 14:00 UTC by Filip Nguyen
Modified: 2011-09-27 18:34 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-27 18:34:42 UTC
Type: Bug


Attachments (Terms of Use)


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

Description Filip Nguyen 2011-09-19 14:00:12 UTC
project_key: SOA

CXF installed. When user sends SOAP message to EBWS and  SOAPAction is not same as Action header then following message is generated: 
{code:title=Exception|borderStyle=solid}

13:55:14,137 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] Interceptor for {http://soa.jboss.org/CreditServices}CreditAgencyServiceService#{http://soa.jboss.org/CreditServices}CreditAgencyServiceOp has thrown exception, unwinding now
org.apache.cxf.binding.soap.SoapFault: Action http://soa.jboss.org/CreditServices/CreditAgencyServiceOpResp not supported
	at org.apache.cxf.ws.addressing.MAPAggregator.mediate(MAPAggregator.java:531)
	at org.apache.cxf.ws.addressing.MAPAggregator.handleMessage(MAPAggregator.java:188)
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
	at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
	at org.a
{code}

Comment 1 Anne-Louise Tangring 2011-09-27 18:34:42 UTC
Not a bug. this is the way cxf works.


Note You need to log in before you can comment on or make changes to this bug.