You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Andi Huber (JIRA)" <ji...@apache.org> on 2018/02/24 22:29:00 UTC

[jira] [Assigned] (ISIS-1880) New value type needed for internal URLs ?

     [ https://issues.apache.org/jira/browse/ISIS-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andi Huber reassigned ISIS-1880:
--------------------------------

    Assignee: Andi Huber

> New value type needed for internal URLs ?
> -----------------------------------------
>
>                 Key: ISIS-1880
>                 URL: https://issues.apache.org/jira/browse/ISIS-1880
>             Project: Isis
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>            Reporter: Andi Huber
>            Assignee: Andi Huber
>            Priority: Major
>             Fix For: 2.0.0-M1
>
>
> The framework in prototyping mode (when rendering domain objects) provides links to swagger and the restful api.
> However, this links do not work in general.
> Currently these links are contributed by actions that return java.net.URL value types. Which works fine if we want to link to external web-resources. But when linking to internal web-resources its almost impossible to derive the absolute URL a client actually sees.
> E.g. we have the relative path to swagger: '/swagger-ui/index.html' but it's impossible to derive the absolute path in general like 'http://some-server:someport:/...'. Not to mention that the servlet container hosting Isis could sit behind a http-reverse-proxy, or that we don't know if the protocol is http or https (SSL could be terminated somewhere else).
> And I believe, we should not even have to care!
> So I'd propose, we introduce a new value type similar to URL, but one that only represents relative paths within the web-app. 
> Feel free to comment, if I'm wrong our there is a better solution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)