From: Edwin C. <com...@gm...> - 2010-02-25 09:33:43
|
Hi Poul, The WFS classes in 0.4 are stubs that did not really do anything and looking into the old WFSParams code I see that it is missing the constructor: public WFSParams(){ this(JSObject.createJSObject()); } You could try subclass WFSParams, for example as: public WFSParamsExt extends WFSParams { protected WFSParamsExt(JSObject jsObject) { super(jsObject); } public WFSParamsExt(){ this(JSObject.createJSObject()); } } Then you can pass a WFSParamsExt where WFSParams is expected, thanks to polymorphism :)... Another issue with doing WFS is that you will need a proxy (due to cross-domain restrictions on XMLHttpRequest requests). In GWT-OL there is no way to set OpenLayers.ProxyHost, so you will need to do that via JSNI and either get the Python proxy in OL examples up, or grab some proxy code from some place. Right now, I am fragmentarily working on a BasicWFS example for the showcase that uses WFSProtocol (which is minimally implemented in GWT-OL trunk) and a proxy bundled with GWT-OL. It is not finished, but maby it is good staring point if you check out the source from Mercurial. Greetings, Edwin Are you using GWT 2.0? Because On 25 February 2010 10:00, paweluz <pa...@tl...> wrote: > Hi! > > Sorry for writing to you directly but I really do not know what to do. I am using openlayers_gwt-0.4.jar and I have problem with WFSParams. It does not work for me at all... Here is my topic > > http://n2.nabble.com/WFS-GWT-WFSParams-problem-td4631183.html#a4631183 > > I have also written to gwt...@li... but my message does not appears on the forum. > > I hope you can help me... > > Regards, > Poul > |