[jira] [Closed] (CXF-7805) Transform feature outDropElements has no effect

["Colm O hEigeartaigh (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-7805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh closed CXF-7805.
------------------------------------

> Transform feature outDropElements has no effect
> -----------------------------------------------
>
>                 Key: CXF-7805
>                 URL: https://issues.apache.org/jira/browse/CXF-7805
>             Project: CXF
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 3.2.5
>         Environment: Java 8
> Tomcat 8.5
> Eclipse 4.3
> CXF 3.2.5
> Windows 7 Professional
>            Reporter: Michael Schäfer
>            Assignee: Colm O hEigeartaigh
>            Priority: Major
>              Labels: features, outDropElements, transform
>             Fix For: 3.2.6, 3.1.17
>
>         Attachments: cxfOutDropElements-2.zip, cxfOutDropElements.zip, eingangsdb-eks-2.0.jar
>
>
> We're running CXF 3.2.5 web services in Tomcat, java-first-approach.
> For compatibility with older clients, we'd like to remove some elements from the response using the transform feature. We'd prefer to do this via configuration, so the feature can be easily removed once all clients have upgraded.
> We put the configuration - jaxws:feature and beans - in WEB-INF/classes/CXF/beans.xml, referenced throug web.xml. Any other way - via cxf.xml, be it on classpath or referenced per JVM parameter - failed to find the bean defintion. Introducing errors in the bean definition leads to corresponding errors, so the bean is recognized, but the configuration has no effect on the outbound XML. We also tried addressing the elements with and without namespace, full paths, shallow and deep drop, and the XSLT feature, too, but to no avail.
> We suspect this might still be a configuration issue or some peculiar constellation we fail to recognize, but we are at out wit's end finding the real cause of it.
> Attached you find a Maven test project, stripped down to the one web service with the one method in question, and exported from Eclipse after running maven --clean. The pom contains all dependencies of the original project. There is no test case, we simply used SOAPUI which worked fine. The archive also contains the WSDL file copied from the source view of the browser.
> TIA,
> Michael



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)