You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Colm O hEigeartaigh (Jira)" <ji...@apache.org> on 2026/10/19 08:48:00 UTC

[jira] [Resolved] (CXF-8277) WSDLManagerImpl.removeDefinition doesn't work as expected

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

Colm O hEigeartaigh resolved CXF-8277.
--------------------------------------
    Resolution: Duplicate

> WSDLManagerImpl.removeDefinition doesn't work as expected
> ---------------------------------------------------------
>
>                 Key: CXF-8277
>                 URL: https://issues.apache.org/jira/browse/CXF-8277
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 3.3.2
>         Environment: OpenJDK 12
> Apache CXF 3.3.2
>            Reporter: Ranjit Vadakkan
>            Priority: Major
>         Attachments: Screen Shot 2020-05-05 at 12.32.35 PM.png
>
>
> Identical to CXF-5407
> If I simply make the call to WSDLManagerImpl.removeDefinition to remove a cached WSDL entry, the entry remains. Please see the attachment for a debugger screenshot. Changes in the WSDL are not reflected in the JAXB model.
> But if I make a second call WSDLManagerImpl.getDefinitions after WSDLManagerImpl.removeDefinition that simply gets the map of cached entries, something triggers the memory model that causes that cache to clear the entry I previously tried to remove via WSDLManagerImpl.removeDefinition. In this case, changes in the WSDL are correctly reflected in the JAXB model.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)