Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of monish.unni@gmail.com)
Date: Mon, 9 May 2011 09:21:14 -0700 (PDT)
From: cogitate <monish.unni@gmail.com>
To: users@cxf.apache.org
Message-ID: <1304958074746-4382262.post@n5.nabble.com>
In-Reply-To: <BANLkTinNuypXyTB11Jz0ifLfs5tNT2O-_A@mail.gmail.com>
References: <1304911151802-4381005.post@n5.nabble.com>
 <BANLkTinNuypXyTB11Jz0ifLfs5tNT2O-_A@mail.gmail.com>
Subject: Re: cxf-2.4.0 pattern match StaxTransformFeature?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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. 

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..


--
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.