You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Jens Schumann (JIRA)" <ji...@apache.org> on 2006/09/03 01:41:22 UTC
[jira] Created: (AXIS2-1105) HardCoded Context Root in
ConfigurationContext
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
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1105) HardCoded Context Root in
ConfigurationContext
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1105?page=comments#action_12432309 ]
Davanum Srinivas commented on AXIS2-1105:
-----------------------------------------
Jens,
could u plz help with a patch?
thx,
dims
> 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
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-1105) HardCoded Context Root in
ConfigurationContext
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1105?page=all ]
Davanum Srinivas resolved AXIS2-1105.
-------------------------------------
Resolution: Fixed
please check latest svn.
thx,
dims
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1105) HardCoded Context Root in
ConfigurationContext
Posted by "Jens Schumann (JIRA)" <ji...@apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-1105) HardCoded Context Root in
ConfigurationContext
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1105?page=all ]
Davanum Srinivas reassigned AXIS2-1105:
---------------------------------------
Assignee: Eran Chinthaka
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org