You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Denis Weerasiri (JIRA)" <ji...@apache.org> on 2009/03/06 12:45:58 UTC
[jira] Updated: (ODE-373) MMC contains hardcoded paths; host, port
and context where the MMC expects Ode should be derived from the deployment
[ 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.