juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex O'Ree (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] [Commented] (JUDDI-950) Improve JUDDI build by replacing hardcoded URLs
Date Sat, 07 Oct 2017 15:50:00 GMT

    [ https://issues.apache.org/jira/browse/JUDDI-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16195764#comment-16195764

Alex O'Ree commented on JUDDI-950:

in juddiv3.war's admin.jsp page, the localhost urls you see are html placeholders, not hard
coded url strings.

there is no admin jsp page in juddi-gui

> Improve JUDDI build by replacing hardcoded URLs
> -----------------------------------------------
>                 Key: JUDDI-950
>                 URL: https://issues.apache.org/jira/browse/JUDDI-950
>             Project: jUDDI
>          Issue Type: Improvement
>          Components: juddi-tomcat
>    Affects Versions: 3.3.2
>            Reporter: Matthieu Ghilain
> The two following URLs are hard coded at several places in resources:
> - http://localhost:8080/juddiv3
> - http://localhost:8443/juddiv3
> They can be be replaced by maven properties configured in the juddi-parent POM. This
would allow to easily build JUDDI to be deployed on another environment.
> It would also be even better to get those properties from the environment (passed as
JVM arguments to tomcat JVM).

This message was sent by Atlassian JIRA

View raw message