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

Posted to issues@cxf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2011/02/16 14:00:57 UTC

[jira] Assigned: (CXF-3340) wsdl2java caches the input wsdl file or result so there is no differnce in the output when called a second time from the same process and with the same wsdl file path

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

Freeman Fang reassigned CXF-3340:
---------------------------------

    Assignee: Freeman Fang

> wsdl2java caches the input wsdl file or result so there is no differnce in the output when called a second time from the same process and with the same wsdl file path
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-3340
>                 URL: https://issues.apache.org/jira/browse/CXF-3340
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.3.1
>         Environment: Linux
>            Reporter: Kjell Winblad
>            Assignee: Freeman Fang
>            Priority: Critical
>         Attachments: cxfcachebug.tar.gz
>
>
> When the public class WSDL2Java is used two times from the same process and with the same path to the wsdl file, the generated files are the same both times even if the content of the file at the wsdl file path has changed so it should result in different output. It seems like CXF is caching the content of the WSDL somewhere and just reads from the cache the second time WSDL2Java is called. If the path is different from all paths that have previously been used with WSDL2Java the file is correctly read from disk. A maven project that can be used to reproduce the behavior will be attached to this bug.
> This is critical for us since our application can call WSDL2Java many times during it's life time and we don't want files to be cached somewhere between the calls so that our application leaks memory and so we get unexpected results. If we just knew how to clear all caches between the calls then that would be a good enough workaround for us. This problem did not exist in CXF version 2.0.6.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira