[Geoserver-devel] What is happening?

Morning everyone - I am wondering what is happening in the GeoServer development world:

Here is what I kind of think is going on:
1) A new GeoServer 1.2.0 release candidate (rc2 or rc3?) focused on bug fixes is in flight this week
2) An update of the geotools2 jars
- from the fid_mm - I kind of think this has happened? (Needed today to test Brent's Postgis server crash bug)
- from geotools trunk after fid_exp has been merged? (I need this to fix the bounding box button)
3) I have a demo for the 29th on making a new validation plug-in (so I will make some documentation)
4) geotools ext/view has a start of a task/operation api
- to allow for geoserver work from RobA
- contains improved Filter construction
- development will begin in earnest on 1 geotools 2.1 branch after everyone gets back from OGC meeting
5) Chris will focus on documentation for the final 1.2.0 release - I would like to see the community help by making use of the wiki.
6) Paul will be starting a WFS comparison project/report

Am I missing anything?
Jody

Here is what I kind of think is going on:
1) A new GeoServer 1.2.0 release candidate (rc2 or rc3?) focused on bug
fixes is in flight this week

Yes. My week's been a little more disorganized than I'd have liked, but
I'm working all day and tonight.

2) An update of the geotools2 jars
- from the fid_mm - I kind of think this has happened? (Needed today to
test Brent's Postgis server crash bug)

Yes, this kind of happened. For some reason I can't get the new code that
Andrea wrote for PostgisDataStoreFactory to work right with geoserver,
namely the canProcess function, but if I revert to the old way of doing
things everything works fine. I can commit the fixed jar to geoserver,
but I don't want to commit the code to fid-mm.

- from geotools trunk after fid_exp has been merged? (I need this to fix
the bounding box button)

Yes. I'm hoping Andrea gets it in tonight, since if I don't get the
release out saturday we're going to have to wait another week, as I'm
pretty booked next week.

3) I have a demo for the 29th on making a new validation plug-in (so I
will make some documentation)
4) geotools ext/view has a start of a task/operation api
- to allow for geoserver work from RobA
- contains improved Filter construction
- development will begin in earnest on 1 geotools 2.1 branch after
everyone gets back from OGC meeting
5) Chris will focus on documentation for the final 1.2.0 release - I
would like to see the community help by making use of the wiki.
6) Paul will be starting a WFS comparison project/report

Am I missing anything?

I believe you've got it all.

Chris

Alle 20:05, giovedì 17 giugno 2004, Chris Holmes ha scritto:

> Here is what I kind of think is going on:
> 1) A new GeoServer 1.2.0 release candidate (rc2 or rc3?) focused on bug
> fixes is in flight this week

Yes. My week's been a little more disorganized than I'd have liked, but
I'm working all day and tonight.

> 2) An update of the geotools2 jars
> - from the fid_mm - I kind of think this has happened? (Needed today to
> test Brent's Postgis server crash bug)

Yes, this kind of happened. For some reason I can't get the new code that
Andrea wrote for PostgisDataStoreFactory to work right with geoserver,
namely the canProcess function, but if I revert to the old way of doing
things everything works fine. I can commit the fixed jar to geoserver,
but I don't want to commit the code to fid-mm.

This is bad, since I've merged fid-mm onto the trunk this morning (hey, no-one
is looking at the cvs-commit mailing list :wink: )
What are the problems? That's probably something not covered by a test.
Also, you should use the newest postgres jdbc driver,

> - from geotools trunk after fid_exp has been merged? (I need this to fix
> the bounding box button)

Done :slight_smile:

Best regards
Andrea Aime

Jody Garnett wrote:

6) Paul will be starting a WFS comparison project/report

Am I missing anything?

6.1) ArcSDE testing environment - it does look like Paul's Mapserver contact may be able to supply geotools/geoserver with an ArcSDE to develop against. It would be great if we could follow up on this one. I don't really know much about what we need at this stage.

> > Here is what I kind of think is going on:
> > 1) A new GeoServer 1.2.0 release candidate (rc2 or rc3?) focused on bug
> > fixes is in flight this week
>
> Yes. My week's been a little more disorganized than I'd have liked, but
> I'm working all day and tonight.
>
> > 2) An update of the geotools2 jars
> > - from the fid_mm - I kind of think this has happened? (Needed today to
> > test Brent's Postgis server crash bug)
>
> Yes, this kind of happened. For some reason I can't get the new code that
> Andrea wrote for PostgisDataStoreFactory to work right with geoserver,
> namely the canProcess function, but if I revert to the old way of doing
> things everything works fine. I can commit the fixed jar to geoserver,
> but I don't want to commit the code to fid-mm.

This is bad, since I've merged fid-mm onto the trunk this morning (hey, no-one
is looking at the cvs-commit mailing list :wink: )

Oh nice. I'm on the digest and I don't think it's come up yet.

What are the problems? That's probably something not covered by a test.
Also, you should use the newest postgres jdbc driver,

Yeah, I'm on the newest postgres driver. I'll try to get a bug report in
later today, but it may be a problem with how geoserver requests stuff.
I doubt I can even replicate it outside of GeoServer, as I can't figure
out how the two requests that geoserver makes to the DataStore finder are
different. I'm in a rush so I may put out geoserver with my slightly
changed version and revisit later. It should be done your new way, and
it's a weird little problem, because geoserver seems to get it to work the
first time but not the second.

> > - from geotools trunk after fid_exp has been merged? (I need this to fix
> > the bounding box button)

Done :slight_smile:

Excellent.

Chris

Best regards
Andrea Aime

--

Chris Holmes wrote:

Here is what I kind of think is going on:
1) A new GeoServer 1.2.0 release candidate (rc2 or rc3?) focused on bug
fixes is in flight this week
       

Yes. My week's been a little more disorganized than I'd have liked, but
I'm working all day and tonight.
     

Are we working on rc2 or rc3 this week - I have lost track.

2) An update of the geotools2 jars
- from the fid_mm - I kind of think this has happened? (Needed today to
test Brent's Postgis server crash bug)
       

One thing I had to do on the GeoServer MM branch was update to vecmath 1.3 - I only see 1.2 commited to the GeoServer repository at this time. Am I missing something? Or will this change only be required when you update to geotools trunk?

IM is down so I will be sending more email for a bit.
Jody

Chris Holmes wrote:

2) An update of the geotools2 jars
- from the fid_mm - I kind of think this has happened? (Needed today to test Brent's Postgis server crash bug)
   

Yes, this kind of happened. For some reason I can't get the new code that Andrea wrote for PostgisDataStoreFactory to work right with geoserver, namely the canProcess function, but if I revert to the old way of doing things everything works fine. I can commit the fixed jar to geoserver, but I don't want to commit the code to fid-mm.

I just tried a check out of GeoServer head and cannot get useBasic to run against Tomcat 5. My first thought was that the zip input stream problem would be based on chris commiting a jar file with the wrong bin/ascii property - but everthing looks okay...

Anyone have any ideas?

Jody

Log of Tomcat 5 not working:

INFO: Installing web application at context path /geoserver from URL file:C:/java/Tomcat5/webapps/geoserver
17-Jun-2004 12:38:30 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Error installing
java.lang.IllegalArgumentException
    at java.util.zip.ZipInputStream.getUTF8String(ZipInputStream.java:298)
    at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:237)
    at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:73)
    at java.util.jar.JarInputStream.<init>(JarInputStream.java:58)
    at java.util.jar.JarInputStream.<init>(JarInputStream.java:43)
    at org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionValidator.java:420)
    at org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:248)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4133)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:866)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:850)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:638)
    at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:320)
    at org.apache.catalina.core.StandardHost.install(StandardHost.java:875)
    at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:476)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1008)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:394)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1134)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:832)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1126)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:521)
    at org.apache.catalina.core.StandardService.start(StandardService.java:519)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:2345)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:594)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398)
17-Jun-2004 12:38:30 PM org.apache.catalina.startup.HostConfig deployWARs
SEVERE: Exception while expanding web application archive geoserver.war
java.io.IOException: java.lang.IllegalArgumentException
    at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:326)
    at org.apache.catalina.core.StandardHost.install(StandardHost.java:875)
    at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:476)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1008)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:394)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1134)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:832)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1126)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:521)
    at org.apache.catalina.core.StandardService.start(StandardService.java:519)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:2345)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:594)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398)

>>>>Here is what I kind of think is going on:
>>>>1) A new GeoServer 1.2.0 release candidate (rc2 or rc3?) focused on bug
>>>>fixes is in flight this week
>>>>
>>>>
>>>Yes. My week's been a little more disorganized than I'd have liked, but
>>>I'm working all day and tonight.
>>>
>>>
Are we working on rc2 or rc3 this week - I have lost track.

rc2

>>>>2) An update of the geotools2 jars
>>>>- from the fid_mm - I kind of think this has happened? (Needed today to
>>>>test Brent's Postgis server crash bug)
>>>>
>>>>
One thing I had to do on the GeoServer MM branch was update to vecmath
1.3 - I only see 1.2 commited to the GeoServer repository at this time.
Am I missing something? Or will this change only be required when you
update to geotools trunk?

It's probably needed now - I haven't tested wms stuff yet. Go ahead and
update if you'd like.

>>2) An update of the geotools2 jars
>>- from the fid_mm - I kind of think this has happened? (Needed today to
>>test Brent's Postgis server crash bug)
>>
>>
>Yes, this kind of happened. For some reason I can't get the new code that
>Andrea wrote for PostgisDataStoreFactory to work right with geoserver,
>namely the canProcess function, but if I revert to the old way of doing
>things everything works fine. I can commit the fixed jar to geoserver,
>but I don't want to commit the code to fid-mm.
>
>
I just tried a check out of GeoServer head and cannot get useBasic to
run against Tomcat 5. My first thought was that the zip input stream
problem would be based on chris commiting a jar file with the wrong
bin/ascii property - but everthing looks okay...

Anyone have any ideas?

No, you're right, I hate myself. If I even just once remember to add with
kb I will be so happy. geoapi-SNAPSHOT seemed to be needed, just
recommitted with with kb.

C

Jody

Log of Tomcat 5 not working:

> INFO: Installing web application at context path /geoserver from URL
> file:C:/java/Tomcat5/webapps/geoserver
> 17-Jun-2004 12:38:30 PM org.apache.catalina.core.StandardHostDeployer
> install
> INFO: Error installing
> java.lang.IllegalArgumentException
> at java.util.zip.ZipInputStream.getUTF8String(ZipInputStream.java:298)
> at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:237)
> at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:73)
> at java.util.jar.JarInputStream.<init>(JarInputStream.java:58)
> at java.util.jar.JarInputStream.<init>(JarInputStream.java:43)
> at
> org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionValidator.java:420)
> at
> org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:248)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4133)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:866)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:850)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:638)
> at
> org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:320)
> at
> org.apache.catalina.core.StandardHost.install(StandardHost.java:875)
> at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:657)
> at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:476)
> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1008)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:394)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1134)
> at org.apache.catalina.core.StandardHost.start(StandardHost.java:832)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1126)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:521)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:519)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:2345)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:594)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398)
> 17-Jun-2004 12:38:30 PM org.apache.catalina.startup.HostConfig deployWARs
> SEVERE: Exception while expanding web application archive geoserver.war
> java.io.IOException: java.lang.IllegalArgumentException
> at
> org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:326)
> at
> org.apache.catalina.core.StandardHost.install(StandardHost.java:875)
> at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:657)
> at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:476)
> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1008)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:394)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1134)
> at org.apache.catalina.core.StandardHost.start(StandardHost.java:832)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1126)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:521)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:519)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:2345)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:594)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398)

--

Chris Holmes wrote:

I just tried a check out of GeoServer head and cannot get useBasic to run against Tomcat 5. My first thought was that the zip input stream problem would be based on chris commiting a jar file with the wrong bin/ascii property - but everthing looks okay...

Anyone have any ideas?
   

No, you're right, I hate myself. If I even just once remember to add with kb I will be so happy. geoapi-SNAPSHOT seemed to be needed, just recommitted with with kb.

Easy buddy -

I tried to say above that "Everything looks okay" - the jars were jars (if not I would not have been able to build). We got something else going wrong here -

Wash rinse repeat "anyone have any ideas"?

Jody

>>I just tried a check out of GeoServer head and cannot get useBasic to
>>run against Tomcat 5. My first thought was that the zip input stream
>>problem would be based on chris commiting a jar file with the wrong
>>bin/ascii property - but everthing looks okay...
>>
>>Anyone have any ideas?
>>
>>
>No, you're right, I hate myself. If I even just once remember to add with
>kb I will be so happy. geoapi-SNAPSHOT seemed to be needed, just
>recommitted with with kb.
>
>
Easy buddy -

I tried to say above that "Everything looks okay" - the jars were jars
(if not I would not have been able to build). We got something else
going wrong here -

Wash rinse repeat "anyone have any ideas"?

What's the error that you're getting? I did definitely commit
geoapi-SNAPSHOT wrong, so you may try checking out again.

And give me a few seconds, I'm going to put the jars from head (with one
little modification for postgis) up on geoserver cvs.