Issue 29 in rave-in-context: Location of wookie server in wookie connector is not fully configurable

[rave-in-context....@codespot.com]

Status: Accepted
Owner: ----
Labels: Type-Defect Priority-High

New issue 29 by rgard...@opendirective.com: Location of wookie server in
wookie connector is not fully configurable
http://code.google.com/a/apache-extras.org/p/rave-in-context/issues/detail?id=29

In common/scripts/wookie_controller.js we create a WookieServerConnection
by calling "new WookiesServerConnection()" (no parameters). This means the
system defaults to localhost.

However, there is no mechanism for configuring this from a
local.build.properties file and so the only way to deply to a live server
is to edit the file directly.

[rave-in-context....@codespot.com]

Updates:
Labels: -Type-Defect -Priority-High Type-Enhancement Priority-Low

Comment #1 on issue 29 by rgard...@opendirective.com: Location of wookie

server in wookie connector is not fully configurable
http://code.google.com/a/apache-extras.org/p/rave-in-context/issues/detail?id=29

I've implemented a workaround for this. The location of the server is now a
property called "wookie.url"

In theory this can be set when calling the ant tasks to deploy the widget
with "-Dwookie.url=URL"