Hello,
It seems that the ArcSDE plugin does not manage the ESRI versioning mechanism.
When a geodatabase is registered as versioned, no transaction can be done,
throwing an IOException without any message.
Is there a plan to support versioning, or has there ever been a request for it ?
At a fi
View results here ->
http://geo.openplans.org:9090/buildresults/geotools?log=log20060829130748Lbuild.1
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated tec
So it is time to work with others, the geotools project has ported the
uDig IResolve API (for catalog), and completed it as an implementation
of the "extensible interface pattern". What does this mean? It means
that you will be able to supply a factory that can make new adapters for
existing IS
Note as maintain of module/api Justin did talk to me first, I apologize
for not emailing the list. Here is what the changes look like
> C:\java\geotools\trunk\module\api>svn up
> Usrc\org\geotools\data\Query.java
> Usrc\org\geotools\data\FIDSQuery.java
> Usrc\org\geotools\data\ALLQ
Hi all,
There are a few classes sitting on FM that I require on trunk as part of
the xml work. The first is an implementation of
org.opengis.feature.type.Name, which is essentially the same as QName.
The second is an implementation of org.opengis.feature.Schema, which
basically maps a bunch of na
I have not had time to make a 2.3 release, perhaps those working on WCS
can give it a go. I would like to see a release around next week for
those attending the conference to point people at.
Jody
> It saddens me that i did all the deprecation of the filter interfaces
> last year and we still hav
It saddens me that i did all the deprecation of the filter interfaces
last year and we still haven't had a release out of it. Well SortBy
already extends geoapi SortBy and is deprecated. So after we get 2.3 out
we can kill it. With a single module ( MemoryDataStore ) using it
shouldn't be a huge im
Sorry guys,
I will committ the fix this evening (Italy time) when I get back home.
Simone.
On 8/29/06, Justin Deoliveira <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> It has been a full day with the build down. Simone do you have a time
> line for your fix? If not near future can I ask that we take
Hi guys,
It has been a full day with the build down. Simone do you have a time
line for your fix? If not near future can I ask that we take imagemosaic
out of the build?
-Justin
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> plugin/imagemosaic does not compile for me. Can anyone else conf
Can you point me to the wiki page you already have going. The one with
guidelines and stuff like that.
Jody Garnett wrote:
> Right I forgot, can you place this on a wiki page please (others really
> need to know, otherwise we will
> never get a project to drive this).
>
> Cheers,
> Jody
>> Hi Jod
Right I forgot, can you place this on a wiki page please (others really
need to know, otherwise we will
never get a project to drive this).
Cheers,
Jody
> Hi Jody,
>
> I apologize, without a project driving this it gets put on the back
> burner. Your plan looks good, the only modification I would
Vitali Diatchkov wrote:
> Achtung!:)
>
> The question is about transactions in geotools JDBC API.
>
> ShapefileDataStore and ShapefileRenderer are working against transaction
> state in memory. Modified/added/removed features are kept in transaction
> state in memory until we commit to rewrite shap
Hi Jody,
I apologize, without a project driving this it gets put on the back
burner. Your plan looks good, the only modification I would make is part
of goal 3. Instead of swapping to SimpleFeature, we swap to an extension
of SimpleFeature that looks exactly the same as the current feature.
Same t
Achtung!:)
The question is about transactions in geotools JDBC API.
ShapefileDataStore and ShapefileRenderer are working against transaction
state in memory. Modified/added/removed features are kept in transaction
state in memory until we commit to rewrite shapefile or rollback
modifications.
W
Vitali Diatchkov wrote:
> I have a question here. I don't follow the process of GT 2.3 development and
> latest changes, but does it mean that specifying FeatureFactory for
> particular DataStore, the last one starts to use factory to produce features
> by its readers/writers ?
>
> That is what I t
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:geotools-devel-
> [EMAIL PROTECTED] On Behalf Of Jody Garnett
> Sent: Tuesday, August 29, 2006 2:50 PM
> To: GeoTools Devel List
> Subject: [Geotools-devel] FM Plan needed
>
> Justin we need your plan :-)
>
> It is getting hard to p
1: SQLBuilder and sorting
2: Backward Compatibility vs Clover
rgould: 1) SQLBuilder and sorting: jdeolive
jdeolive: i just wanted to open up a discussion, did anyone read my rant
on the list
aaime: Just did
rgould: I glanced at it, but I'm not that familiar with that area of the
code
aaime: Addi
Justin we need your plan :-)
It is getting hard to plan for the future without it. Since it has been
several weeks now, let me try and help. From memory here is the plan
you mentioned to me:
GOAL 1
0. Release GeoTools 2.3 (this was supposed to be the last step of the
Grid Coverage merge :-) )
Here is the problem Justin,
MemoryDataStore implements sorting in GeoTools 2.2 - since this is
against our own GeoTools interface SortBy interface; we need to do the
deprecation dance as we move to GeoAPI. Aside: SortBy2 is our convention
to allow extensions beyond the OGC specifications, the
19 matches
Mail list logo
