Excellent! Geo-information system, largely thanks to your advice is almost ready! Thank you so much for helping in the process of working on it!
There remains little question - i set the width as you indicated, but the result is the same:
I’d guess the parent component isn’t providing any room for the component so it falls back to the default size. You should probably use setWidth(“100%”) also for the component that contains your map widget (and all its possible parents).
I don’t really know OpenLayers, but the map is cut here at the 180 longitude, so this should not be related with the map size.
You might need to set some flag for OpenLayers to enable support for map features that cross the 180 longitude - probably there is such a setting.
It might also be that your data source does not support features crossing the 180 longitude, or might need some special settings for that there.
So, I did all this - ordered width to 100% for the map and the whole hierarchy of nesting, but the result is not affected, longitude 180 map is still cut off.
As Henri noticed, your clipping occurs on dateline. I think the wrapper currently has no Java api for the OpenLayers dateline setting. You should add an issue of that to the google code host page about that. It should be pretty straightforward to implement once it is on the “roadmap”.