[ 
https://issues.apache.org/jira/browse/CXF-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543027
 ] 

Jeff Zhang commented on CXF-1199:
---------------------------------

Hi Dan,

I think that adding check resolver list code into ReflectionServiceFactoryBean  
is not correctly.
>From discussing with Sergey and Jervis, we agree only Service(null, qname) 
>make resolver work currently.

we need to add into simeple frontend client later. But adding into getWsdlURL 
method make code throw stackoverflowerror. Could you help me remove these code? 
and I would think more ReflectionServiceFactoryBean lifecycle later.

> new ServiceContractResolver that cxf can resolve wsdl file from extension 
> repository/storage
> --------------------------------------------------------------------------------------------
>
>                 Key: CXF-1199
>                 URL: https://issues.apache.org/jira/browse/CXF-1199
>             Project: CXF
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jeff Zhang
>            Assignee: Daniel Kulp
>         Attachments: hello_world_resolver.jar, resolve.patch
>
>
> currently, cxf support get wsdl URL from local file or internet location. we 
> can add ServiceContractResolver interface make cxf can get wsdl file from 
> extension repository/storage like zip files, UDDI repository, DB storage, 
> etc..
>  interface ServiceContractResolver {
>  URL getContractURL(QName);
>  }
> and bus extension to register and unregister resolvers into cxf bus:
>  interface ServiceContractResolverRegistry {  //cxf bus extension
>  URL getContractURL(QName);
>  void register(ServiceContractResolver);
>  void unregister(ServiceContractResolver);
>  bool isRegistered(ServiceContractResolver);
>  };

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to