You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2008/09/18 10:11:44 UTC
[jira] Created: (ODE-373) Host, port and context where the MMC
expects Ode should be derived from the deployment
Host, port and context where the MMC expects Ode should be derived from the deployment
--------------------------------------------------------------------------------------
Key: ODE-373
URL: https://issues.apache.org/jira/browse/ODE-373
Project: ODE
Issue Type: Bug
Components: Management Console
Reporter: Tammo van Lessen
Fix For: 1.3
Host, port and context are currently hard coded. This leads to the effect that the MMC stops working when ODE is deployed in a different context name than "ode" or tomcat has setup for a different port. In addition, hard-coded paths cause some troubles when the console shall be accessed from other machines due to some XSS protections in browsers.
I think the best way to fix this is to use relative URLs as this should solve all the problems stated above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-373) MMC contains hardcoded paths; host, port
and context where the MMC expects Ode should be derived from the deployment
Posted by "Denis Weerasiri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Weerasiri updated ODE-373:
--------------------------------
Attachment: ODE-373.patch
Hardcoded Host, port and context were removed and Management Console JavaScripts were updated based on the Management API schema.
> MMC contains hardcoded paths; host, port and context where the MMC expects Ode should be derived from the deployment
> --------------------------------------------------------------------------------------------------------------------
>
> Key: ODE-373
> URL: https://issues.apache.org/jira/browse/ODE-373
> Project: ODE
> Issue Type: Bug
> Components: Management Console
> Reporter: Tammo van Lessen
> Priority: Critical
> Fix For: 1.3, 2.0
>
> Attachments: ODE-373.patch
>
>
> Host, port and context are currently hard coded. This leads to the effect that the MMC stops working when ODE is deployed in a different context name than "ode" or tomcat has setup for a different port. In addition, hard-coded paths cause some troubles when the console shall be accessed from other machines due to some XSS protections in browsers.
> I think the best way to fix this is to use relative URLs as this should solve all the problems stated above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-373) Host, port and context where the MMC
expects Ode should be derived from the deployment
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou updated ODE-373:
------------------------------
Fix Version/s: (was: 1.3)
2.0
> Host, port and context where the MMC expects Ode should be derived from the deployment
> --------------------------------------------------------------------------------------
>
> Key: ODE-373
> URL: https://issues.apache.org/jira/browse/ODE-373
> Project: ODE
> Issue Type: Bug
> Components: Management Console
> Reporter: Tammo van Lessen
> Fix For: 2.0
>
>
> Host, port and context are currently hard coded. This leads to the effect that the MMC stops working when ODE is deployed in a different context name than "ode" or tomcat has setup for a different port. In addition, hard-coded paths cause some troubles when the console shall be accessed from other machines due to some XSS protections in browsers.
> I think the best way to fix this is to use relative URLs as this should solve all the problems stated above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-373) MMC contains hardcoded paths; host, port
and context where the MMC expects Ode should be derived from the deployment
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen resolved ODE-373.
----------------------------------
Resolution: Fixed
Assignee: Tammo van Lessen
Thanks for the patch. Applied to both trunk and 1.x branch.
> MMC contains hardcoded paths; host, port and context where the MMC expects Ode should be derived from the deployment
> --------------------------------------------------------------------------------------------------------------------
>
> Key: ODE-373
> URL: https://issues.apache.org/jira/browse/ODE-373
> Project: ODE
> Issue Type: Bug
> Components: Management Console
> Reporter: Tammo van Lessen
> Assignee: Tammo van Lessen
> Priority: Critical
> Fix For: 1.3, 2.0
>
> Attachments: ODE-373.patch
>
>
> Host, port and context are currently hard coded. This leads to the effect that the MMC stops working when ODE is deployed in a different context name than "ode" or tomcat has setup for a different port. In addition, hard-coded paths cause some troubles when the console shall be accessed from other machines due to some XSS protections in browsers.
> I think the best way to fix this is to use relative URLs as this should solve all the problems stated above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-373) MMC contains hardcoded paths; host, port
and context where the MMC expects Ode should be derived from the deployment
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated ODE-373:
---------------------------------
Priority: Critical (was: Major)
Fix Version/s: 1.3
Summary: MMC contains hardcoded paths; host, port and context where the MMC expects Ode should be derived from the deployment (was: Host, port and context where the MMC expects Ode should be derived from the deployment)
MMC is also part of 1.3 and the bug is somehow critical because it expects some resources at http://localhost:8080/ode which is not necessarily the right assumption.
> MMC contains hardcoded paths; host, port and context where the MMC expects Ode should be derived from the deployment
> --------------------------------------------------------------------------------------------------------------------
>
> Key: ODE-373
> URL: https://issues.apache.org/jira/browse/ODE-373
> Project: ODE
> Issue Type: Bug
> Components: Management Console
> Reporter: Tammo van Lessen
> Priority: Critical
> Fix For: 1.3, 2.0
>
>
> Host, port and context are currently hard coded. This leads to the effect that the MMC stops working when ODE is deployed in a different context name than "ode" or tomcat has setup for a different port. In addition, hard-coded paths cause some troubles when the console shall be accessed from other machines due to some XSS protections in browsers.
> I think the best way to fix this is to use relative URLs as this should solve all the problems stated above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.