You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Alex O'Ree (JIRA)" <ju...@ws.apache.org> on 2015/12/05 14:38:11 UTC

[jira] [Commented] (JUDDI-950) Improve JUDDI build by replacing hardcoded URLs

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

Alex O'Ree commented on JUDDI-950:
----------------------------------

Where are they hard coded? As far as I know, they are only in example config files

> 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
(v6.3.4#6332)