Just wanted to let you all know I figured out the problem, in case anyone
else wants to use Geowebcache with Map Builder. Apparently Map Builder
overrides Open Layers Max Resolution by default which causes the bizarre
behavior with Geowebcache. If you set the param back to it's default Open
Layers setting like this:
<MapPaneOL id="mainMapWidget">
<maxResolution>1.40625</maxResolution>
<htmlTagId>mainMapPane</htmlTagId>
<fixedSize>true</fixedSize>
</MapPaneOL>
Then it appears to work correctly. I'm not sure why 'auto' wouldn't work,
but it doesn't.
Ryan
On Fri, Apr 25, 2008 at 10:14 AM, Ryan Moquin <[EMAIL PROTECTED]>
wrote:
> One other question, in case they do work together, is if there are any
> examples anywhere of a working mapbuilder client with Geowebcache (we tried
> all the other tiling caches, but haven't had any luck getting them working
> at all)?
>
>
> On Thu, Apr 24, 2008 at 5:59 PM, Ryan Moquin <[EMAIL PROTECTED]>
> wrote:
>
> > BTW - It appears that mapbuilder can't even use the "States" layer that
> > geowebcache comes with out of the box... but openlayers has no problem with.
> >
> >
> > On Thu, Apr 24, 2008 at 5:02 PM, Ryan Moquin <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Has anyone tried mapbuilder with GeoWebCache? Using a very basic open
> > > layers (v. 2.6) html page, we can load a geoserver layer through
> > > geowebcache
> > > and have it display along with a gml file of features over top. When we
> > > take the same geowebcache url and plug it into mapbuilder, it goes
> > > COMPLETELY haywire. The actual tiled image scales and moves drastically
> > > differently than the gml features (using the same file that we used with
> > > the
> > > open layers client).
> > >
> > > Either way, the features and the layer, do not line up. And the
> > > relative positions between the gml points and layer changes, it's not
> > > consistent when zooming. The GML points are correctly positioned in
> > > mapbuilder though. It seems as though geowebcache will not work with
> > > mapbuilder. Has anyone tried this or confirmed this?
> > >
> > > I also tried out our geowebcache url in the latest "simple" example
> > > (from mapbuilder head), in place of the metacarta layer that is loaded
> > > (and
> > > tiled correctly). As soon as I replace that URL with our geowebcache URL,
> > > mapbuilder appears to randomly pull and load tiles. It's almost as if
> > > mapbuilder is requesting tiles in a completely different scheme (if that's
> > > even possible).
> > >
> > > If I request the same layer that geowebcache is loading, directly from
> > > geoserver into mapbuilder (with no geocache), then everything loads and
> > > works perfectly fine (except that it is horribly slow).
> > >
> > > I'm really hoping that maybe there is an extra configuration parameter
> > > that mapbuilder needs, but that wouldn't make sense, since it's using open
> > > layers underneath.
> > >
> >
> >
>
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Mapbuilder-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mapbuilder-users
