cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <>
Subject Re: [jira] Created: (CXF-446) Allow JAX-WS implementation bean not to implement the service endpoint interface
Date Tue, 06 Mar 2007 07:48:22 GMT
Hi Jarek,

I am sorry I can't apply all you patch.
I found these two test failed in both Linux and Windows box after I 
applied you patch.
I looked these issue and tried to fix it.  I caught the  message 
request  and  response between  the  client  and server.
I found the  request and response message's target namespace is not 
matched, so the two tests failed.

Current CXF's code first approach is implemented by simple front end's 
ReflectionServiceFactoryBean. It work for turning the POJO style Java 
code to service model.
It does not consume the Jaxws annotation and take the response message 
target namespace as the operation namespace 
And the  response message target namespace actually should be 

To fix this issue, we need to implement creation of service module from 
class which is annotated with the Jaxws annotation without WSDL location.
So I will fill a JIRA task for it, if there is no other objection.



Jarek Gawor (JIRA) wrote:

>Allow JAX-WS implementation bean not to implement the service endpoint interface
>                 Key: CXF-446
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>            Reporter: Jarek Gawor
>         Attachments: CXF-446.patch
>JAX-WS services (as per spec) are not required to implement the service endpoint interface.
Right now, if the service does not implement the SEI, a "object is not an instance of" error
is returned on an invocation. The attached patch enables the services not to implement the
SEI and contains test for such cases.
>This patch also contains updated test cases for CXF-444.

View raw message