Well... i've given up for today... uDig and Geoserver WFS just aren't
getting along! Rendering works fine, but thematic styling only works
partially (on a WFS layer, Change Style...> Theme > click a pallette).
Geoserver spits out lots of this:
java.lang.RuntimeException: Error reading Feature
arcsde module IP check
--
Key: GEOT-837
URL: http://jira.codehaus.org/browse/GEOT-837
Project: GeoTools
Type: Task
Components: arcsde
Reporter: Gabriel Roldán
Assigned to: Gabriel Roldán
Priority: Critical
Fix For: 2.3.M0
per
Chris Holmes wrote:
Hrm, just realized I never sent this. Not sure if a decision was
made, but there are still a couple comments of note.
Like the idea of scaling back geotools to "what is trusted".
I think we can have separate dependencies for test code in maven 2, so
perhaps the XML chicken
Hrm, just realized I never sent this. Not sure if a decision was made,
but there are still a couple comments of note.
-
Yeah, test cases are the big annoyance, the reason for the circular
depenancies that lead to the module merge in the first place. Mostly
default core relying on xml readers
Adrian Custer wrote:
So how's that for starters?
Great! To answer your question the "Repository" is used for cross
DataStore operations (like "unlock").
This is different from catalog which actually allows you to bring all
the geotools resources together (Grid, Data, and Services).
I usu
Adrian Custer wrote:
Hey everyone,
As preparation for drawing up architectural diagrams of geotools for the
pleasure of users like myself, I've been parsing the source code
distribution of 2.2.RC2. Some questions arise because there are only
three directories which lump together several packages
Hey everyone,
As preparation for drawing up architectural diagrams of geotools for the
pleasure of users like myself, I've been parsing the source code
distribution of 2.2.RC2. Some questions arise because there are only
three directories which lump together several packages: api (all of
which are
Chris Holmes wrote:
To make this work right we'd either need FeatureSources to have a
transaction field (that would be used just for the hints), or else
make setTransaction() in FeatureSource.
Either way I feel like using Transaction hints to do rendering stuff
is stretching the design a slig
GeoTools2 module build report 20060420
gt2:referencing cleaned, compiled
---
release is 2.1.x
---
---
Using Tomcat but need to do more? Need to supp
