Hi thanks for the info, please see comments inline ?
On Mon, May 9, 2011 at 5:21 PM, cogitate <[email protected]> wrote: > thanks sergey for the explanation - i use the StaxTransformFeature > assymetrically as i illustrate below. > > in my scenario, the server is obviously pretending to be a soap service ( > i.e it has wsdls ) but the payload doesn't comply to the xsds w.r.t > namespaces. in fact , this is a third party vendor. > > what i do have is control over package-info.java ( in jaxb ) and with some > nifty removal and additions of default interceptors in the incoming message > i am able to marshal the message(s) back to jaxb objects. > > i must say, i have to use JAX-WS route since the 3rd party sends back SOAP > faults defined in the wsdl. > this is the need for my somewhat weird regex matching question ... > iow , i only have outTransformElements configured in my > StaxTransformFeature. > Is there any reason you are not using inTransformElements property ? > i guess, if we do have a regex feature, it'd be quite powerful - and i do > understand your concerns given how that can be abused :) > > hope my explanation makes some sense.. > > I think updating the feature to check wildcards will be starightforward, I'd appreciate though if you could explain a bit more what happening in the following two cases. Client makes an invocation and drops the output namespaces. What happens when: normal response is sent back ? exceptional response is sent back ? I'd just like to understand better how dropping namespaces using wildcards can help if you may need some explicit knowledge for response data be read, sorry if I'm a bit slow :-) Showing some sample in/out XML payloads can help :-) Thanks, Sergey > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/cxf-2-4-0-pattern-match-StaxTransformFeature-tp4381005p4382262.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Sergey Beryozkin Application Integration Division of Talend http://sberyozkin.blogspot.com
