You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Vijayaratha Vijayasingam (JIRA)" <ji...@apache.org> on 2011/03/31 12:46:05 UTC

[jira] [Created] (SYNAPSE-747) Provide a way to write custom implementations to resolve the wsdl and imported resources such as schemas.

Provide a way to write custom implementations to resolve the wsdl and imported resources such as schemas.
---------------------------------------------------------------------------------------------------------

                 Key: SYNAPSE-747
                 URL: https://issues.apache.org/jira/browse/SYNAPSE-747
             Project: Synapse
          Issue Type: Improvement
          Components: Core
    Affects Versions: NIGHTLY
            Reporter: Vijayaratha Vijayasingam
            Priority: Minor
             Fix For: FUTURE


Currently there is a standard way to resolve the wsdl imported resources(schema, ..) using  'CustomeWSDLLocator' and 'CustomXmlSchemaURIResolver'. Both  accept the "ResourceMap" instance which contains Relativelocation and the relevant Registrykeys.  Its bit annoying from the user perspective since he manually has to fill the ResourceMap each and every time when he creates a proxy service. Rather, if user allows to have his custom wsdl locator and the schema resolver would be great based on WSDLKey..

I have just wrote  two simple interfaces to map user defined implementations with the standard implementation and introduced two synapse properties
synapse.wsdl.resolver,synapse.schema.resolver
Please review and commit.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


[jira] [Resolved] (SYNAPSE-747) Provide a way to write custom implementations to resolve the wsdl and imported resources such as schemas.

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

Supun Kamburugamuva resolved SYNAPSE-747.
-----------------------------------------

    Resolution: Fixed

Applied the patch with minor modifications. Thanks Ratha for the contribution.

> Provide a way to write custom implementations to resolve the wsdl and imported resources such as schemas.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-747
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-747
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: NIGHTLY
>            Reporter: Vijayaratha Vijayasingam
>            Priority: Minor
>             Fix For: FUTURE
>
>         Attachments: UserDefinedResolverPatch.patch
>
>
> Currently there is a standard way to resolve the wsdl imported resources(schema, ..) using  'CustomeWSDLLocator' and 'CustomXmlSchemaURIResolver'. Both  accept the "ResourceMap" instance which contains Relativelocation and the relevant Registrykeys.  Its bit annoying from the user perspective since he manually has to fill the ResourceMap each and every time when he creates a proxy service. Rather, if user allows to have his custom wsdl locator and the schema resolver would be great based on WSDLKey..
> I have just wrote  two simple interfaces to map user defined implementations with the standard implementation and introduced two synapse properties
> synapse.wsdl.resolver,synapse.schema.resolver
> Please review and commit.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


[jira] [Updated] (SYNAPSE-747) Provide a way to write custom implementations to resolve the wsdl and imported resources such as schemas.

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

Vijayaratha Vijayasingam updated SYNAPSE-747:
---------------------------------------------

    Attachment: UserDefinedResolverPatch.patch

> Provide a way to write custom implementations to resolve the wsdl and imported resources such as schemas.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-747
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-747
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: NIGHTLY
>            Reporter: Vijayaratha Vijayasingam
>            Priority: Minor
>             Fix For: FUTURE
>
>         Attachments: UserDefinedResolverPatch.patch
>
>
> Currently there is a standard way to resolve the wsdl imported resources(schema, ..) using  'CustomeWSDLLocator' and 'CustomXmlSchemaURIResolver'. Both  accept the "ResourceMap" instance which contains Relativelocation and the relevant Registrykeys.  Its bit annoying from the user perspective since he manually has to fill the ResourceMap each and every time when he creates a proxy service. Rather, if user allows to have his custom wsdl locator and the schema resolver would be great based on WSDLKey..
> I have just wrote  two simple interfaces to map user defined implementations with the standard implementation and introduced two synapse properties
> synapse.wsdl.resolver,synapse.schema.resolver
> Please review and commit.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org