You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "hwavelet (JIRA)" <ji...@apache.org> on 2008/05/21 05:58:55 UTC

[jira] Created: (CXF-1599) URIResolver can't be replaced eazy

URIResolver can't be replaced eazy
----------------------------------

                 Key: CXF-1599
                 URL: https://issues.apache.org/jira/browse/CXF-1599
             Project: CXF
          Issue Type: New Feature
    Affects Versions: 2.1.1
            Reporter: hwavelet
             Fix For: 2.1.1


If we need a new policy to load wsdl/xsd files (something like load from a specified directory all split the wsdl/xsd files into separate modules each of them has desiginated classloader....), cxf can't handle it very well. the cause is that many of the cxf code use code fragement like this "new org.apache.cxf.resource.ExtendedURIResolver()", i think it needs to refactor as an interface and as a bus extension, so it can be replaced by the user to meet their requirements, so if we need that will do like that:

ExtendURIResolver resolver = bus.getExtension(ExtendURIResolver.class)

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


[jira] Assigned: (CXF-1599) URIResolver can't be replaced eazy

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang reassigned CXF-1599:
---------------------------------

    Assignee: Willem Jiang

> URIResolver can't be replaced eazy
> ----------------------------------
>
>                 Key: CXF-1599
>                 URL: https://issues.apache.org/jira/browse/CXF-1599
>             Project: CXF
>          Issue Type: New Feature
>    Affects Versions: 2.1.1
>            Reporter: hwavelet
>            Assignee: Willem Jiang
>             Fix For: 2.1.4
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> If we need a new policy to load wsdl/xsd files (something like load from a specified directory all split the wsdl/xsd files into separate modules each of them has desiginated classloader....), cxf can't handle it very well. the cause is that many of the cxf code use code fragement like this "new org.apache.cxf.resource.ExtendedURIResolver()", i think it needs to refactor as an interface and as a bus extension, so it can be replaced by the user to meet their requirements, so if we need that will do like that:
> ExtendURIResolver resolver = bus.getExtension(ExtendURIResolver.class)

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


[jira] Updated: (CXF-1599) URIResolver can't be replaced eazy

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang updated CXF-1599:
------------------------------

    Fix Version/s:     (was: 2.1.3)
                   2.1.4

> URIResolver can't be replaced eazy
> ----------------------------------
>
>                 Key: CXF-1599
>                 URL: https://issues.apache.org/jira/browse/CXF-1599
>             Project: CXF
>          Issue Type: New Feature
>    Affects Versions: 2.1.1
>            Reporter: hwavelet
>             Fix For: 2.1.4
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> If we need a new policy to load wsdl/xsd files (something like load from a specified directory all split the wsdl/xsd files into separate modules each of them has desiginated classloader....), cxf can't handle it very well. the cause is that many of the cxf code use code fragement like this "new org.apache.cxf.resource.ExtendedURIResolver()", i think it needs to refactor as an interface and as a bus extension, so it can be replaced by the user to meet their requirements, so if we need that will do like that:
> ExtendURIResolver resolver = bus.getExtension(ExtendURIResolver.class)

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


[jira] Resolved: (CXF-1599) URIResolver can't be replaced eazy

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang resolved CXF-1599.
-------------------------------

    Resolution: Won't Fix

> URIResolver can't be replaced eazy
> ----------------------------------
>
>                 Key: CXF-1599
>                 URL: https://issues.apache.org/jira/browse/CXF-1599
>             Project: CXF
>          Issue Type: New Feature
>    Affects Versions: 2.1.1
>            Reporter: hwavelet
>            Assignee: Willem Jiang
>             Fix For: 2.1.4
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> If we need a new policy to load wsdl/xsd files (something like load from a specified directory all split the wsdl/xsd files into separate modules each of them has desiginated classloader....), cxf can't handle it very well. the cause is that many of the cxf code use code fragement like this "new org.apache.cxf.resource.ExtendedURIResolver()", i think it needs to refactor as an interface and as a bus extension, so it can be replaced by the user to meet their requirements, so if we need that will do like that:
> ExtendURIResolver resolver = bus.getExtension(ExtendURIResolver.class)

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


[jira] Commented: (CXF-1599) URIResolver can't be replaced eazy

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643737#action_12643737 ] 

Willem Jiang commented on CXF-1599:
-----------------------------------

I just went through the codes which call the "new org.apache.cxf.resource.ExtendedURIResolver()", 
most of they don't have reference of the bus instance, so I don't want to change them to relay on any bus instance.

After reading the ExtendedURIResolver, I don't think it is necessary to add some extension for loading the resource for a designated classloader in ExtendURIResolver. 
I think you can implement your costumer  ResourceManager to meet with your requirement.




> URIResolver can't be replaced eazy
> ----------------------------------
>
>                 Key: CXF-1599
>                 URL: https://issues.apache.org/jira/browse/CXF-1599
>             Project: CXF
>          Issue Type: New Feature
>    Affects Versions: 2.1.1
>            Reporter: hwavelet
>            Assignee: Willem Jiang
>             Fix For: 2.1.4
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> If we need a new policy to load wsdl/xsd files (something like load from a specified directory all split the wsdl/xsd files into separate modules each of them has desiginated classloader....), cxf can't handle it very well. the cause is that many of the cxf code use code fragement like this "new org.apache.cxf.resource.ExtendedURIResolver()", i think it needs to refactor as an interface and as a bus extension, so it can be replaced by the user to meet their requirements, so if we need that will do like that:
> ExtendURIResolver resolver = bus.getExtension(ExtendURIResolver.class)

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