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

Posted to issues@cxf.apache.org by "benson margulies (JIRA)" <ji...@apache.org> on 2007/09/19 00:27:43 UTC

[jira] Created: (CXF-1035) Two classes named AbstractDataBinding is too many

Two classes named AbstractDataBinding is too many
-------------------------------------------------

                 Key: CXF-1035
                 URL: https://issues.apache.org/jira/browse/CXF-1035
             Project: CXF
          Issue Type: Task
          Components: Aegis Databinding
    Affects Versions: 2.0.2
            Reporter: benson margulies
            Priority: Minor


In the process of introducing user control of namespace prefixes in Aegis, I ended up adding a new class named AbstractDataBinding and not removing the oddly located one that already existed.

Now that the dust has settled a bit, this issue calls for me to sort this out.


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

[jira] Resolved: (CXF-1035) Two classes named AbstractDataBinding is too many

Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.

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

Benson Margulies resolved CXF-1035.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1

Done.

> Two classes named AbstractDataBinding is too many
> -------------------------------------------------
>
>                 Key: CXF-1035
>                 URL: https://issues.apache.org/jira/browse/CXF-1035
>             Project: CXF
>          Issue Type: Task
>          Components: Aegis Databinding
>    Affects Versions: 2.0.2
>            Reporter: Benson Margulies
>            Priority: Minor
>             Fix For: 2.1
>
>
> In the process of introducing user control of namespace prefixes in Aegis, I ended up adding a new class named AbstractDataBinding and not removing the oddly located one that already existed.
> Now that the dust has settled a bit, this issue calls for me to sort this out.

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