That said, may be XSLTJaxabProvider can actually support String and wrap
it internally into Document or something else that JAXB will understand,
I'll think about it
Cheers, Sergey
On 04/08/13 22:27, Sergey Beryozkin wrote:
Yes, you need to do a non JAXB XSLT provider if XSLT XML input is
represented as String.
Injecting JAX-RS UriInfo context inside that provider will help the
actual path and query parameters
Cheers, Sergey
On 03/08/13 04:45, Dev1 wrote:
Usecase:
url example -
http://localhost:port:myserviceMthd/domainNameXYZ/userIDAbc?client=ppp
From the above url,I need to get the path and query values and
pass them to
the xslt that
addes the path and query values to a XML string. So the XSLT output -
<?xml version="1.0" encoding="UTF-8"?>
<domainName>domainNameXYZ</domainName>
I need to make use of that xml in the application logic.
All this needs to be done at the webservice Impl class
Since I am not doing any thing with result of the method, I did not
make it
as JAXBElement.
Instead, I made the method paramater domain as @XMLElement but nothing
happens.
MyWSImpl:
@XmlElement String dmn;
public class MyWSServiceImpl implements MyWSService{
@GET
@Path("/myserviceMthd/{domain}/{userId}")
@Produces("text/xml")
@WebMethod
public String myserviceMthd(@PathParam("domain") String domain,
@PathParam("userId") String userId
{
dmn = domain;
}
How to get hold of the injected xsltJaxbprovider and execute it with url
values (so that I can get the output of the xslt as a XML string)?
Instead do you want me to use a custom provider which does NOT use
XSLTJaxb
databinding?
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-Web-client-test-with-mock-URL-tp5731684p5731921.html
Sent from the cxf-user mailing list archive at Nabble.com.
