To achieve something like this in your project I’d probably need to add 3 classes:
org.vaadin.vol.client.wrapppers.layers WebMapTileServiceLayer
org.vaadin.vol.client.ui VWebMapTileServiceLayer
org.vaadin.vol WebMapTileServiceLayer
Yes, I think you are on the right path. The first one is a “GWT java-javascript gateway” to access OL api. It also works without Vaadin at all. The last one is the server side class that you actually use in you Vaadin apps and the V prefixed class is the client side counterpart for it, whose purpose is to interpret messages from the server side to the OL.
Did you get the project properly imported into you IDE? Maven should configure it properly. Then you need to recompile the test app widgetset with mvn gwt:compile and launch the VolTestServer as normal java app (yes, the plain old main method).
BTW. What application are you using to create tile sets? Maybe I should look into that too some day.
import wasn’t a problem just pulled and ran mvn eclipse:eclipse.
Thanks for the explanations… how did you debug those javascript parts?
I’m afraid I can’t help you on the application. It’s a service hosted by the city of vienna. They offered a Capabilties.xml with those tilSets specified.
GWT “hosted mode” is a must have. Javascript debuggers also work surprisingly well even with GWT hosted mode. Especially with Webkit based browsers the performance is manageable. Vaadin has Util.browserDebugger() method that is handy to stop the execution at certain point. The test widgetset should GWT compile with “PRETTY” so stepping in js debugger should be somewhat readable.
[WARN]
Widget class org.vaadin.vol.client.ui.VWebMapTileServiceLayer was not found. The component org.vaadin.vol.WebMapTileServiceLayer will not be included in the widgetset.
Is it in the same package as other V-prefixed classes? GWT expect classes to be inside “client” package that sits next to the GWT module (.gwt.xml file).
It’s running allthough not with the array (wich seems to be unnecessary anyway). To date it’s probably only useable for RESTful encoding as you cannot define matrixId arrays.
Should I commit it anyway or wait until I had time to implement the missing functionality?
You could create a patch and attach it to an issue report in the google code project. I’ll then review the code and commit it. If it looks good I can give your google account some more powers so you can commit next changes directly.