synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (SYNAPSE-896) Relative WSDL path not working in WAR deployment
Date Thu, 08 Aug 2013 22:52:48 GMT


Hudson commented on SYNAPSE-896:

SUCCESS: Integrated in Synapse - Trunk #4701 (See [])
Resolving relative paths of WSDLs relative to SynapseHome. This is important in WAR deployments.
Patch applied from SYNAPSE-896 (hiranya: rev 1512065)
* /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/config/
* /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/config/xml/endpoints/
* /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/core/axis2/

> 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
>            Assignee: Hiranya Jayathilaka
>         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
For more information on JIRA, see:

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

View raw message