Inputs for latlong bounding box in FeatureType config web page should have 4 fields
Description
In the FeatureType configuration page the latlong bounding box is one big field. I believe you are supposed to put in the bbox with comma delimited fields. This is confusing, as users have no idea what order to put them in, and I think there are a few different conventions (and even if there is one convention I personally never remember it). So it should have four fields, minx, miny, maxx, and maxy (not necessarily that order, maybe try to figure out what the ogc convention is). If we get [https://jira.codehaus.org/browse/GEOS-1" title="Generate LatLongBoundingBox dynamically" class="issue-link" data-issue-key="GEOS-1"><del>GEOS-1</del> working then the default values should be generated automatically. The user could then choose to just keep those (as most everyone will) or fill in his own.
In the FeatureType configuration page the latlong bounding box is one big field. I believe you are supposed to put in the bbox with comma delimited fields. This is confusing, as users have no idea what order to put them in, and I think there are a few different conventions (and even if there is one convention I personally never remember it). So it should have four fields, minx, miny, maxx, and maxy (not necessarily that order, maybe try to figure out what the ogc convention is). If we get [https://jira.codehaus.org/browse/GEOS-1" title="Generate LatLongBoundingBox dynamically" class="issue-link" data-issue-key="GEOS-1"><del>GEOS-1</del> working then the default values should be generated automatically. The user could then choose to just keep those (as most everyone will) or fill in his own.