On 10 Mar 2010, at 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 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=falseIs there something else to do for my widget to be able to pass- through the proxy ?
OK, a widget needs to do two things to get outside requests.1. Define an access request in its config.xml file, which can be a wildcard, e.g.
<access origin="*"/>If you deploy your widget by dropping it into the deploy folder, this request will be granted with an access policy - you'll see a log/ console message like:
access policy granted for MyWidget to access * 2. "Proxify" all URLs it intends to request. E.g. var url = "http://my.feed.com/1.rss";; url = widget.proxify(url); jquery.get(url, function);These requests will then go through the server-side proxy and avoid same-origin restrictions.
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 messageslog4j.logger.org.apache.wookie=debug, widgetylog4j.logger.org.directwebremoting.impl.DefaultCreatorManager=debug, widgety
if you enable debug level logging on org.apache.wookie.proxy.ProxyClient this will log all requests that get proxied.
Regards, Adrien
smime.p7s
Description: S/MIME cryptographic signature
