Hmm...I think you figured out the issue on the udig list, but I'll
answer here for completeness.
I'm pretty sure that I compiled against the "real" jars, and that your
issue is due to compiling against the "dummy" jars and then inserting
the "real" jars in at runtime. Apparently this switch-er
HI Saul,
Did you compile the gt2 arcsde jar against the "real" jars or the
dummy jar? I have tried a zillion different permutations now but I
realize that I compiled against the dummy jar.
Jesse
On 7-Dec-06, at 3:14 PM, Saul Farber wrote:
> I updated and everything built to 2.2.3-SNAPSHOT l
I updated and everything built to 2.2.3-SNAPSHOT like a charm.
Thanks Gabriel!
--saul
Gabriel Roldán wrote:
> fixed the poms in 2.2.x land,
> you should just update and get it building ok.
>
> bug me if not.
>
> regards,
>
> gabriel
--
fixed the poms in 2.2.x land,
you should just update and get it building ok.
bug me if not.
regards,
gabriel
On Thursday 07 December 2006 23:27, Saul Farber wrote:
> Jesse,
>
> Sorry this took me so long!
>
> I'm trying with the latest build of 2.2.x (2.2.3-SNAPSHOT + some kind of
> weirdness in
Jesse,
Sorry this took me so long!
I'm trying with the latest build of 2.2.x (2.2.3-SNAPSHOT + some kind of
weirdness in the maven repo right now involving lots of downloaded 2.2.2
jars) and geoserver-1.4.x.
First try:
using jars from maven.geotools.fr
(http://maven.geotools.fr/repository/com
Jesse,
I'll build with the latest 2.2.x jars and see if I have the same
problem, but it definitely looks like a problem with your jsde jars. Do
you have all three of them in your webapps/lib directory and can you
confirm the version (and maybe an sha1 checksum to see if I have the
same ones?)
I'm using ArcSDE built from 2.2.x, 2.2.3-SNAPSHOT to be exact.
Does this stack trace mean anything. Maybe I have the wrong jsde-sdk
jar? I believe I have the 9.0 jar. What verison should I use?
Caused by: java.lang.NoSuchFieldError: SE_OPTIMIZE
at
org.geotools.data.arcsde.ArcSDEQuery.cre
