You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Jiang Ning <ni...@iona.com> on 2006/10/11 06:09:34 UTC
something about porting Axis2 performance test case
Hi
When I porting Axis2 performance test , I found some interesting things
when I compare Axis2 with CXF.
1. Getting the wsdl from the endpoint published url.
Axis2 support for querying service's WSDL (using ?wsdl), schema (using
?xsd) and policies (using ?policy).
Current CXF only support servlet to get the wsdl from published url+?wsdl.
IMO CXF should catch up with Axis2.
2. Supporting of JAXWS
When we use the same wsdl as Axis2 to generate the artifacts, I found
Axis tools can't tell wrapped and bare message according to JAXWS
specification but the CXF's tools support it.
But CXF run time don't support the wrapped and bare message in the same
interface because of there are different interceptor chains will be
involved in this use case.
IMO CXF need to looking into it and find a way to solve it.
Willem.
Re: something about porting Axis2 performance test case
Posted by Jiang Ning <ni...@iona.com>.
Jiang Ning wrote:
> Hi
>
> When I porting Axis2 performance test , I found some interesting
> things when I compare Axis2 with CXF.
>
> 1. Getting the wsdl from the endpoint published url.
> Axis2 support for querying service's WSDL (using ?wsdl), schema (using
> ?xsd) and policies (using ?policy).
> Current CXF only support servlet to get the wsdl from published
> url+?wsdl.
> IMO CXF should catch up with Axis2.
Sorry, my mistake for the ?wsdl. I also did a quick test of CXF sample
and look into the code, the ?wsdl option support to get the wsdl file,
Please see
trunk/rt/transports/http/src/main/java/org/apache/cxf/transport/http/JettyHTTPDestination.java
if ("GET".equals(req.getMethod()) &&
req.getURI().toString().toLowerCase().endsWith("?wsdl")) {
try {
resp.addField("Content-Type", "text/xml");
OutputStream os = resp.getOutputStream();
WSDLWriter wsdlWriter =
WSDLFactory.newInstance().newWSDLWriter();
Definition def = new
ServiceWSDLBuilder(endpointInfo.getService()).build();
wsdlWriter.writeWSDL(def, os);
resp.getOutputStream().flush();
resp.commit();
req.setHandled(true);
return;
} catch (Exception ex) {
ex.printStackTrace();
}
}
>
> 2. Supporting of JAXWS
> When we use the same wsdl as Axis2 to generate the artifacts, I found
> Axis tools can't tell wrapped and bare message according to JAXWS
> specification but the CXF's tools support it.
> But CXF run time don't support the wrapped and bare message in the
> same interface because of there are different interceptor chains will
> be involved in this use case.
> IMO CXF need to looking into it and find a way to solve it.
>
> Willem.
>
>
>
--
Willem Jiang
Software Engineer
IONA Asia Pacific Software Development Center
2/F, Unit A, Information Center
Zhongguancun Software Park Haidian District,
Beijing, P.R.China (100094)
Tel: +86-10-82825151 - 523
Fax: +86-10-82825210
Email: ning.jiang@iona.com