It's finally up and out. Please check it out, and post any bugs you find in Jira. To test the new UI just point yourself to http://localhost:8080/geoserver/ . We have not yet compiled the JSPs, and yes we do intend to do this for the version 1.2 release. All other known issues are in the Readme or online in Jira.
David
README.txt (4.34 KB)
David Zwiers wrote:
It's finally up and out. Please check it out, and post any bugs you find in Jira. To test the new UI just point yourself to http://localhost:8080/geoserver/ . We have not yet compiled the JSPs, and yes we do intend to do this for the version 1.2 release. All other known issues are in the Readme or online in Jira.
Please make use of the tar file that Chris Holmes has uploaded (12 megs) vs the origional 51 meg zip file (geotools2 snuck in).
Jody
Would like to thank Chris for finding our release bugs so far, and helping to fix tham all. A smaller version is now availiable 
David
David Zwiers wrote:
David Zwiers wrote:
Would like to thank Chris for finding our release bugs so far, and helping to fix tham all. A smaller version is now availiable
David
Oh good it is my Turn Now:
Excludes needed:
-geoserver1.2alpha.tar file (now we know why it is bigger)
-.project file
-.classpath file
README.txt
- consider a readme.html with links?
- do we need both?
- need to replace link to http://localhost:8081/geoserver/Welcome.do
(internal tomcat starts on port 8081)
- need installation quick start here
doc/user/*.html
- we will need up date these files
- looks like the place for a user's guide with screen snapshots
startup.bat- I would like the zip and and run startup.bat
- (GEOSERVER_HOME is a bad idea bin/startup.bat could figure this out)
- startup does not, it keeps control of the shell when called from the command line
- requirement to run from GEOSERVER_HOME & set the variable is a bit much
- cannot call startup.bat from explorer (and never will be able to given above restriction
- need a pretty shortcut/icon
- 8081 is not the "usual" port - try for port 80 in a release
Build/War (from Windows Perspective)
- Why do I have to download ant?
- And build the war?
- Isn't a war supposed to be included in the distribution? (we could skip the ant requirement then)
- unit tests are annoying before building war (although could be reassuring I suppose)
- we need to move the external directory stuff up to the top for our users to edit
conf
- some extra datastores seem to have been added
- refractions hydra is used as example 
Internal TOmcat - test-clean:
- only copies the servlets over
Internal Tomcat- test:
- Also copies WEB-INF?
- starts up the webserver with exceptions
[java] ContextConfig: Missing default web.xml, using application web.xml only
[java] ContextConfig: Added certificates -> request attribute Valve
[java] FreefsLog: init
[java] action: init
[java] StandardContext: Servlet threw load() exception
[java] javax.servlet.ServletException: Servlet.init() for servlet action threw exception
(It seems that none of the struts config or jsp files make it into the internal web server)
External Resin 3.4
- Starts up with some config errors:
[15:58:12.968] Application[http://localhost:8080/geoserver\] starting
[15:58:12.984] FreefsLog: init
[15:58:13.312] action: init
[15:58:16.546] loading catalog configuration
[15:58:19.171] FeatureTypeInfo local.postgis:::geom_test could not be used - DataStore local.postgis is not defined!
[15:58:19.203] FeatureTypeInfo bc_shapefile:::bc_roads ignored - Style 'null' not found!
[15:58:19.781] unknown filter [ogc:Not: null]
[15:58:19.859] Application[http://localhost:8080] starting
[16:00:22.625] WFSGetCapabilities: init
[16:00:22.625] Looking for configured service responses' stratagy
[16:00:22.625] Looking for configured service stratagy SPEED
[16:00:22.625] Using service stratagy class org.vfny.geoserver.servlets.SpeedStratagy
[16:00:22.796] Service handled
(The Style 'null' was not expected !)
- JSP and STRUTS work okay
External Resin 2.1.9
- has finest detail on! Lots of docs...
- Actually FINEST in on all the time It must be Resin 3.4 which is ignoring service.xml
- after changing service.xml file to INFO:
[2004-01-21 16:10:22.250] initializing application http://localhost:8080/geoserver
15 [INFO] org.vfny.geoserver.global.xml.XMLConfigReader - loading catalog configuration
1593 [SEVERE] org.vfny.geoserver.global.Data - FeatureTypeInfo local.postgis:::geom_test could not be used - DataStore
local.postgis is not defined!
1625 [SEVERE] org.vfny.geoserver.global.Data - FeatureTypeInfo bc_shapefile:::bc_roads ignored - Style 'null' not found!
1922 [WARNING] org.geotools.filter.FilterDOMParser - unknown filter [Element [Name ogc:{http://www.opengis.net/ogc\}Not]]
[2004-01-21 16:10:26.281] initializing application http://localhost:8080/
[2004-01-21 16:10:26.281] initializing application http://localhost:8080/java_tut
[2004-01-21 16:10:26.281] initializing application http://localhost:8080/examples/basic
[2004-01-21 16:10:26.281] initializing application http://localhost:8080/examples/tags
[2004-01-21 16:10:26.281] initializing application http://localhost:8080/examples/tictactoe
[2004-01-21 16:10:26.281] initializing application http://localhost:8080/examples/navigation
[2004-01-21 16:10:26.281] initializing application http://localhost:8080/examples/xsl
[2004-01-21 16:10:26.281] initializing application http://localhost:8080/examples/templates
[2004-01-21 16:10:26.281] initializing application http://localhost:8080/examples/login
- JSP and STRUTS work okay
External Tomcat 4.1 (default port 8080)
- also makes use of FINEST
- after changing service.xml file to INFO:
Jan 21, 2004 4:20:30 PM org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
Jan 21, 2004 4:20:30 PM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
Jan 21, 2004 4:20:31 PM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
Jan 21, 2004 4:20:31 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.24-LE-jdk14
31 [INFO] org.vfny.geoserver.global.xml.XMLConfigReader - loading catalog configuration
1359 [SEVERE] org.vfny.geoserver.global.Data - FeatureTypeInfo local.postgis:::geom_test could not be used - DataStore
local.postgis is not defined!
1390 [SEVERE] org.vfny.geoserver.global.Data - FeatureTypeInfo bc_shapefile:::bc_roads ignored - Style 'null' not found!
1625 [WARNING] org.geotools.filter.FilterDOMParser - unknown filter [ogc:Not: null]
Jan 21, 2004 4:20:39 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
Jan 21, 2004 4:20:39 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
Jan 21, 2004 4:20:39 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/110 config=C:\java\jakarta-tomcat\bin\..\conf\jk2.properties
- JSP and STRUTS work okay
README.txt
- consider a readme.html with links?
I personally like a little text file at least telling me what is up with
the release, that I can open with emacs or textpad or whatever. I think
the readme should just be a few quick notes, things that are new in the
release, what it's about, what's changed ect. and then it should point to
where the real installation notes are. Perhaps we should rename
README.txt to RELEASE_NOTES.txt
- need installation quick start here
Yes, would be good to have that in a text file at the top level. And
perhaps as html as well, in the real user docs.
doc/user/*.html
- we will need up date these files
- looks like the place for a user's guide with screen snapshots
Yes. I think it might be nice to keep around the how to with the files
for a bit though.
startup.bat- I would like the zip and and run startup.bat
- (GEOSERVER_HOME is a bad idea bin/startup.bat could figure this out)
- startup does not, it keeps control of the shell when called from the
command line
- requirement to run from GEOSERVER_HOME & set the variable is a bit much
- cannot call startup.bat from explorer (and never will be able to given
above restriction
- need a pretty shortcut/icon
- 8081 is not the "usual" port - try for port 80 in a release
I think my ideal would be something like an install shield, which would
set the variables, and during install would allow the user to choose an
alternate port. The problem with 80 is that it won't work if people are
running a normal webserver.
Build/War (from Windows Perspective)
- Why do I have to download ant?
- And build the war?
- Isn't a war supposed to be included in the distribution? (we could
skip the ant requirement then)
We should move to ant not being required for sure. That wasn't really
possibly before the web config tool. War file in the distribution could
be the way to go.
- unit tests are annoying before building war (although could be
reassuring I suppose)
Yes that is annoying. Perhaps we should turn them off.
- we need to move the external directory stuff up to the top for our
users to edit
You mean in the build.xml file? That's a good idea.
conf
- some extra datastores seem to have been added
- refractions hydra is used as example
Yes, I'd say we should go back to the one I used for 1.1.0 - it gives
samples for all four supported datastores.
Internal TOmcat - test-clean:
- only copies the servlets over
Yes, I don't think anyone's done any work on getting it working. I'd put
this as essential for the beta release. As an extension to the 'why do I
need ant?' there is also 'why do I need a servlet container', and the
answer to that should be 'you don't, just use the built in one'. And they
should be able to start it right up, at least with a bat file.
Ok, that's all from me for now. I have to set up new computer and
environments, but early next week I'll probably send an email similar to
Jody's, with every little thing I want to see done for 1.2beta and 1.2.0
(which I'm really excited about, this new stuff is taking GeoServer to a
whole new level, great work guys).
Chris
