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

Asankha C. Perera resolved SYNAPSE-311.
---------------------------------------

    Resolution: Fixed

Fixed.. 

        Synapse currently only supports the extracted WAR deployment model. 
Thus you need
        to extract the synapse.war to a directory, and then configure your 
servlet engine to
        deploy it off the file system.

        At a minimum, the synapse.home parameter must be specified, as the full 
and
        absolute path to the extracted synapse.war file. You must also edit the 
axis2.xml
        inside the WEB-INF/conf directory, and specify full absolute paths to 
all https
        keystores (e.g. replace "lib/identity.jks" etc..) You may also have to 
change the
        default http port (8080) to something else, if it conflict with the 
servlet engine port

i.e. bottom line, is that you still have to edit web.xml and axis2.xml :)..

> Deployment of synapse.war fails on JBoss due to wrong paths specified in the 
> axis2.xml and web.xml files
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-311
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-311
>             Project: Synapse
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: 1.2-QA-B2
>         Environment: JBoss 4.2.2GA, JDK 1.5.0_14, Ubuntu 7.10
>            Reporter: Evanthika Amarasiri
>            Assignee: Asankha C. Perera
>            Priority: Blocker
>             Fix For: 1.2-QA-B3
>
>
> The paths specified in the web.xml and axis2.xml are invalid.
> In the web.xml the paths specified for the synapse.xml, axis2.repo, 
> axis2.xml, resolve.root are wrong.
> In the conf/axis2.xml the paths specified for identity.jks and trust.jks are 
> wrong.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to