Hello! I think I was not enough clear. There are a huge, complex wsdl (a standard), and I dont like to create the whole object structure, just to use some fields form the request:
request (wsdl1) -> xslt -> service (wsdl2) -> xslt -> response (wsdl1) so In my service will be use a simple object with some attributes, maybe a simple wsdl description, or even better, if I dont need to create a wsdl (code first server) and the next step will be: request#1 (wsdl1) -> xslt -> service (wsdl2) -> logic -> client (wsdl2) -> xslt -> request#2 (wsdl1) response#1 (wsdl1) <- xslt <- service(wsdl2) <- logic <- client (wsdl2) <- xslt <- response#2 (wsdl1) I think its not a big task if I find the right point to do the XSLT transform both direction... Csaba On 2018.04.05. 11:27, Colm O hEigeartaigh wrote: > I added a test recently for a JAX-WS service using the XSLTFeature here: > > https://github.com/apache/cxf/commit/80e7e9720a77196ed6f996c46f7cff648a77628b > > Colm. > > On Thu, Apr 5, 2018 at 6:30 AM, Tóth Csaba <ig...@domen.hu> wrote: > >> Hello! >> >> I'd like to develope a service, what can handle a big, complex request, >> but I need only a part of this request, so I think I try do a XSLT on >> the body first, and than give the new XML to deseriasabling. >> I have two question: >> - is there some example/tutorial to do a XSLT for the incomming/outgoing >> xml body? (i think i can do with interceptor) >> - is there some example/tutorial to create a code first service? I'd >> like to write the object first in java, and than create a service to it. >> >> Thanx >> >> Csaba >> >> >
