[
https://issues.apache.org/jira/browse/CXF-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CXF-3277.
-------------------------------
Resolution: Fixed
commit fix
http://svn.apache.org/viewvc?rev=1063157&view=rev for trunk
http://svn.apache.org/viewvc?rev=1063171&view=rev for 2.3 branch
> soap headers can't be carried back when exception happen
> --------------------------------------------------------
>
> Key: CXF-3277
> URL: https://issues.apache.org/jira/browse/CXF-3277
> Project: CXF
> Issue Type: Bug
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 2.4, 2.3.3
>
> Attachments: CXF-3277-test.patch
>
>
> for example we have a methoh like
> {code}
> public BareDocumentResponse testDocLitFault(String in) throws
> BadRecordLitFault {
> System.out.println("Executing testDocLitFault sayHi\n");
> List<Header> headers = new ArrayList<Header>();
> Header header = null;
> try {
> header = new Header(new QName("http://test";, "test"),
> new String("test"), new
> JAXBDataBinding(String.class));
> } catch (JAXBException e) {
> e.printStackTrace();
> }
> headers.add(header);
> context.getMessageContext().put(Header.HEADER_LIST, headers);
> throw new BadRecordLitFault("int fault", 5);
> }
> {code}
> we explicitly put some headers for response message, it works in normal
> response, but doesn't work when throw Fault/Exception
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
