cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-5216) WSDL definition cache issue for web service client when WSDL in service war changed
Date Tue, 20 Aug 2013 07:22:53 GMT

     [ https://issues.apache.org/jira/browse/CXF-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Freeman Fang resolved CXF-5216.
-------------------------------

    Resolution: Not A Problem
    
> WSDL definition cache issue for web service client when WSDL in service war changed
> -----------------------------------------------------------------------------------
>
>                 Key: CXF-5216
>                 URL: https://issues.apache.org/jira/browse/CXF-5216
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.6.2
>            Reporter: Bin Zhu
>            Assignee: Freeman Fang
>         Attachments: CXF-5216-2.patch, CXF-5216.patch
>
>
> In current design, the WSDL definition will be cached in case the the same wsdl will
be queried later.(WSDLManagerImpl.getDefinition)
> e.g.
>     public Definition getDefinition(String url) throws WSDLException {
>         synchronized (definitionsMap) {
>             if (definitionsMap.containsKey(url)) {
>                 return definitionsMap.get(url);
>             }
>         }
>         return loadDefinition(url);
>     }
> The cache mechanism indeed improves the performance in most scenarios. But if the WSDL
file in service provider app changed, the client will not get the correct WSDL definition
even using retrieves the wsdl from server dynamically (http://hostname:portname/xxx?wsdl),unless
restarting the client app.
> It would be more reasonable to introduce a client property to allow user to disable the
definition cache so that they can choose if they get WSDL definition from cache or the URL
dynamically for their scenarios. Any thoughts? Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message