synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Auke Schrijnen (JIRA)" <>
Subject [jira] [Updated] (SYNAPSE-896) Relative WSDL path not working in WAR deployment
Date Sun, 29 Jul 2012 12:28:33 GMT


Auke Schrijnen updated SYNAPSE-896:

    Attachment: 0001-SYNAPSE-896-Properly-use-SYNAPSE_HOME-when-resolving.patch

The attached patch fixes the current behavior.

There are still some issues:
- paths should be relative to the config directory (or config/resources)
- The method SynapseConfigUtils.getSynapseEnvironment is broken and the SynapseEnvironment
isn't available until the whole configuration is built
- The method WSDLEndpointFactory.createEndpoint uses the property RESOLVE_ROOT as base uri
when defining an inline WSDL definition, this doesn't make any sense (imports with relative
paths in an inline definition don't make sense)
> Relative WSDL path not working in WAR deployment
> ------------------------------------------------
>                 Key: SYNAPSE-896
>                 URL:
>             Project: Synapse
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: NIGHTLY
>            Reporter: Auke Schrijnen
>         Attachments: 0001-SYNAPSE-896-Properly-use-SYNAPSE_HOME-when-resolving.patch
> In a WAR deployment, a relative uri for the WSDL file is not working. Relative paths
are supposed to be relative to the Synapse home directory, but the SYNAPSE_HOME variable isn't
used correctly. All the samples using WSDLs (i.e. 56 and 150) are only working in a standalone
deployment because the current directory when starting Synapse is the Synapse home directory.
In a WAR deployment the current directory usually is the home directory of the application
> The ProxyService and WSDLEndpointFactory should respect the Synapse home directory to
fix the current behavior in a WAR deployment, although it makes much more sense to define
WSDL paths relative to the Synapse configuration directory (especially when using a multi-xml
configuration), or even relative to a resources directory within the configuration directory.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message