[
https://issues.apache.org/jira/browse/JUDDI-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Cunningham resolved JUDDI-174.
----------------------------------
Resolution: Fixed
Update the URLs in uddi-client/src/test/resource/uddi.properties to go to port
8880.
Also, changed the process so that we copy in a server.xml with 8880 set the the
http port into the tomcat bundle. Cargo says that it is possible to set a
<cargo.servlet.port> but there apparently is a bug with this feature where it
doesn't work if you are using an "existing" tomcat setup, like we need to (we
want to reuse the juddi-tomcat artifact that we have just produced).
> Switch cargo to different port
> ------------------------------
>
> Key: JUDDI-174
> URL: https://issues.apache.org/jira/browse/JUDDI-174
> Project: jUDDI
> Issue Type: Task
> Affects Versions: 3.0alpha
> Reporter: Kurt T Stam
> Assignee: Tom Cunningham
> Fix For: 3.0alpha
>
>
> The uddi-client module uses cargo, which brings up tomcat on port 8080, on
> the buildmachine port 8080 is taken, can we switch it to a different port
> (maybe 8880?)
> Please also update urls in the uddi-client/src/test/resource/uddi.properties,
> when changing over.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
