forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cyriaque Dupoirieux (JIRA)" <>
Subject [jira] Assigned: (FOR-962) Wrong port used in ForrestBar if none standard forrest port used
Date Wed, 28 Mar 2007 13:31:25 GMT


Cyriaque Dupoirieux reassigned FOR-962:

    Assignee:     (was: Cyriaque Dupoirieux)

I have just added an Option window to be able to specifiy the host (default is localhost)
and the port (default is 8888) of "Forrest run" and saved - if needed - in the user preferences.
The solution is more robust - cf. the old javascript function isLocalUrl() where the host
and port were hard coded...
Ross has thought of a solution much more simple based on a Regexp of the current Url to find
the host and port.
My dilemma was that some installations (mine for instance) have several web server running
at the same time (I always have an apache for Oracle on port 8080...) So I wanted a solution
flexible and independant.
I don't know what to say, but now, the forrest bar has an Option window ready for future features
and it may be a good thing ;-)

> Wrong port used in ForrestBar if none standard forrest port used
> ----------------------------------------------------------------
>                 Key: FOR-962
>                 URL:
>             Project: Forrest
>          Issue Type: Bug
>          Components: Dispatcher (aka views), Tool: Forrestbar
>    Affects Versions: 0.8-dev
>            Reporter: Ross Gardler
>            Priority: Minor
> If Forrest is run on a port other than 8888, the forrestbar fails to pick this up from
the request URI.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message