On 10/03/2010 14:57, Adrien Futschik wrote:
Hy !
I have now successfully installed wookie on tomcat 6.0.23 and Mysql 5.0.77.
I am trying to debug widget execution or at least be sure to get more
error messages in the logs.
I'm curious as to why you would want to configure a complete environment
in order to run a development version of Wookie.
There is nothing wrong with doing this, but it is a great deal harder
than simply running Wookie in standalone mode. understanding the
benefits you see in having a Tomcat + MySQL setup would help us in
future design decisions.
Ross
I have a rss feed reader that doesn't seems to get any data.
Wookie is behind a proxy server. I was wondering what I had to configure
to make it work.
I have modified the widgetserver.properties file like this :
widget.proxy.scheme=
widget.proxy.hostname=PROXY-HOST
widget.proxy.port=PROXY-PORT
## default is to use the Wookie whitelist proxy
widget.proxy.path=/wookie/proxy
## comment out the line above, and uncomment this to use the Shindig
open proxy instead
# widget.proxy.path=/gadgets/proxy
widget.proxy.username=PROXY-USER
widget.proxy.password=PROXY-PASSWORD
widget.proxy.usentlmauthentication=false
Is there something else to do for my widget to be able to pass-through
the proxy ? What kind of log can I enable ?
I have modified the log4j.properties file like this :
## log level for the this project - change this to "info" to kill the
debug messages
log4j.logger.org.apache.wookie=debug, widgety
log4j.logger.org.directwebremoting.impl.DefaultCreatorManager=debug, widgety
Regards,
Adrien
