The legend panel seems to have fatal issues when a new OpenLayers.Layer.WMS's
LAYERS value is 0 as in 'zero'.
Take the stock legendpanel.html as an example.
Instead of the default Tasmania layer which looks like this:
new OpenLayers.Layer.WMS(
"Tasmania",
"http://demo.opengeo.org/geoserver/wms?";,
{layers: 'topp:tasmania_state_boundaries', format: 'image/png',
transparent: true},
{singleTile: true}),
. . . simply swap out the proper LAYERS value for a '0' which ends up looking
like this:
new OpenLayers.Layer.WMS(
"Tasmania",
"http://demo.opengeo.org/geoserver/wms?";,
{layers: '0', format: 'image/png', transparent: true},
{singleTile: true}),
Upon refreshing the page, you'll see an immediate GeoExt.js error. I don't
expect an image to show up since the '0' name is made up, but I don't expect
the .js error.
This is an issue because my app is supporting dynamic inclusion of remote
WMS-es via getcaps parsing. In one case, lucky me, a layer is named '0'.
Charlton Galvarino
1 (803) 233-6205 : voice
1 (803) 223-9579 : fax
[email protected]<mailto:[email protected]>
P.O. Box 50960
Columbia, SC 29250
_______________________________________________
Users mailing list
[email protected]
http://www.geoext.org/cgi-bin/mailman/listinfo/users
