[
https://issues.apache.org/jira/browse/SYNAPSE-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598076#action_12598076
]
Andreas Veithen commented on SYNAPSE-311:
-----------------------------------------
There are still some issues:
- The way SynapseStartUpServlet overrides the init method(s) was incorrect,
causing NullPointerExceptions. I corrected this in the 1.2 branch.
- new File(synHome).exists() causes a NullPointerException if synHome is null.
The correct expression should be:
synHome == null || !new File(synHome).exists()
- resolve.root should not be mandatory.
- In my case I don't use the HTTPS NIO transport and I therefore don't have the
problem with paths inside axis2.xml. Also, processing an XML file as text file
can lead to unexpected results. This strategy is used in
SynapseCommodityServiceTest and caused the problem described in SYNAPSE-286. I
think we should better not include the axis2.xml hack in 1.2 and find a proper
solution for a later release.
> 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
>
> Attachments: synapse-311.patch
>
>
> 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]
