I should have noted that you definitely do have to make some modifications to the web.xml. Perhaps these are the other modifications David mentions?
Jeff On Thu, Mar 15, 2012 at 1:13 PM, Jeffrey Johnson <[email protected]> wrote: > David, > > Can you describe these "other modifications". I've never run into > trouble doing it this way, and just saying its not a good idea to do > it this way is just not a good enough reason for me not to continue > doing it. > > On Thu, Mar 15, 2012 at 1:07 PM, David Winslow <[email protected]> wrote: >> I don't recommend just dropping the geonode-geoserver-ext JAR into a >> standard GeoServer installation. The WAR file that we distribute has some >> modifications beyond just adding the geoserver-geonode-ext JAR. WIthout >> them, it is non-deterministic whether or not the GeoNode integration with >> the GeoServer security system actually takes effect. (Actually, it used to >> be non-deterministic but I think now it just doesn't work.) > > I did this as recently as monday, and it certainly did work, and in > fact, I carefully tested that the GeoNode based security most > certainly was working. > >> The GeoNode WAR is built from GeoServer nightly jars and has all bugfixes >> that have gone into GeoServer 2.1.3. I also put together a branch to bring >> GeoNode up to the GeoServer 2.2 >> series: https://github.com/dwins/geonode/tree/geoserver-2.2 Please try one >> of those instead of trying to "geonode-ize" a regular GeoServer. > > Is there a reason that this geoserver-2.2 branch hasnt been submitted > as a pull request and pulled onto master yet? Seems like it makes > sense for us to get GeoNode up to speed with current GeoServer > development sooner rather than later. > > Jeff > >> -- >> David Winslow >> OpenGeo - http://opengeo.org/ >> >> On Thu, Mar 15, 2012 at 3:57 PM, Jeffrey Johnson <[email protected]> >> wrote: >>> >>> I've had good luck building geoserver straight from a trunk checkout >>> and after deploying the war, just adding the geoserver-geonode-ext.jar >>> into the WEB-INF/lib directory and restarting the servlet container. >>> In fact, I did it specifically to work with cascaded layers. >>> >>> Matthew, have you checked out my remote_services branch? >>> https://github.com/jj0hns0n/geonode/tree/remote_services It is the >>> first set of steps toward supporting cascaded layers directly in >>> GeoNode. I would love to have some other collaborators on that branch. >>> >>> Jeff >>> >>> On Thu, Mar 15, 2012 at 12:40 PM, Matthew Hanson >>> <[email protected]> wrote: >>> > How difficult is it to upgrade the GeoServer that GeoNode uses? >>> > >>> > I'm trying to add a cascaded WMS from the National Atlas, but any that >>> > I try to add GeoServer coughs out a >>> > "Connection test failed: Error while parsing XML." >>> > with error in the log of: >>> > >>> > ERROR [xml.sax] - Bounding Box element contains no CRS/SRS attribute >>> > >>> > org.geotools.data.wms.xml.WMSComplexTypes$_BoundingBoxType.getValue(WMSComplexTypes.java:3062) >>> > >>> > >>> > On both my development (using jetty), and production (using tomcat6) >>> > versions. I see that GeoServer 2.1.3 includes various bug fixes and >>> > thought it would be worth trying that version. >>> > >>> > >>> > Matt Hanson >> >>
