[ http://issues.apache.org/jira/browse/AXIS2-1105?page=comments#action_12432342 ] Jens Schumann commented on AXIS2-1105: --------------------------------------
Due to the current implementation an easy fix seems to be impossible. Right now an instance of ConfigurationContext is created within HttpServlet#init(ServletConfig config), which does not allow access to the name of the context root nor servlet path. Within an Servlet you have access to both through HttpServletRequest only. I could provide a workaround, which I personally would like to avoid. So here is my question: Why do we need both Context Root and ServiceContextRoot in ConfigurationContext? I couldn't find a straight forward answer. Is it because of the ongoing spring integration? > HardCoded Context Root in ConfigurationContext > ---------------------------------------------- > > Key: AXIS2-1105 > URL: http://issues.apache.org/jira/browse/AXIS2-1105 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: core > Reporter: Jens Schumann > Assigned To: Eran Chinthaka > Priority: Blocker > > Current Axis2 Snapshot uses a hard coded contextroot in ConfigurationContext, > which may be overridden in axis2.xml. This is rather convienient for using > Axis outside axis2.war or in enviroments, where the target context root may > be changed during deployment. > Please revert this behaviour and go back to > 1. Context root auto detection (use a fallback if it's impossible to locate. > I don't know why that shouldn't work) > 2. Ensure that there is no need to specify both contextRoot and > serviceContextPath to alter the contextRoot. Currenly serviceContextPath is > not altered if serviceContextPath is changed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
