ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tammo van Lessen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (ODE-373) MMC contains hardcoded paths; host, port and context where the MMC expects Ode should be derived from the deployment
Date Fri, 06 Mar 2009 12:25:56 GMT

     [ 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.


Mime
View raw message