You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "jimma (JIRA)" <ji...@apache.org> on 2007/07/24 08:37:31 UTC

[jira] Issue Comment Edited: (CXF-525) ClassNameAllocatorImpl might be missing class name collision checking for other types

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

jimma edited comment on CXF-525 at 7/23/07 11:37 PM:
-----------------------------------------------------

Bo, Is there a test case for this issue ? Currently ClassNameAllocatorImpl is only used to check the name collison for types class. (It  will be passed to jaxb and allocate types class name ) We use ClassCollector class to check other classes collision. 


 was:
Bo, Is there a test case for this issue ? Currently ClassNameAllocatorImpl is only used to check the name collison for types class. (It  will be pssed to jaxb and allocate types class name ) We use ClassCollector class to check other classes collision. 

> ClassNameAllocatorImpl might be missing class name collision checking for other types
> -------------------------------------------------------------------------------------
>
>                 Key: CXF-525
>                 URL: https://issues.apache.org/jira/browse/CXF-525
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.0-RC
>            Reporter: Bozhong Lin
>            Assignee: jimma
>             Fix For: 2.1
>
>
> ClassNameAllocatorImpl might be missing class name collision checking for other types, right now it only checks for SEI interface.

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