Martin Desruisseaux wrote:
> I just read the ConnectionPools very quickly (I have to go soon) and found the
> following sentence:
>
>"The Oracle datastore wants to have direct access to an OracleConnection
> (so it can play directly with the Oracle STRUCT interface etc...). To do
>that
Does anybody want to do a GeoTools workshop?
A few more direct links this time:
- http://www.foss4g2007.org/workshops/ (this page contains word and
open office templates for your submission)
- http://www.foss4g2007.org/important_dates/ (this page lists the "call
for workshops" as closing Febru
I just read the ConnectionPools very quickly (I have to go soon) and found the
following sentence:
"The Oracle datastore wants to have direct access to an OracleConnection
(so it can play directly with the Oracle STRUCT interface etc...). To do
that we need to "unwrapp" the Connection pr
Hi Gabriel -
I always find that discussions of FM are best handled on the GeoAPI list
- in least in terms of feedback.
> Hi guys,
>
> an old issue gets to the scene again at complex-features land: how to model
> an
> xsd simple type with List binding.
>
Perhaps you better provide context her
http://geo.openplans.org:9090/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/224/buildId/735
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get th
On Thursday 22 February 2007 23:18, Rob Atkinson wrote:
> Gabriel Roldán wrote:
>
> One issue at a time..
>
> > NOTE: if an xsd type with scalar content has attributes, it is a complex
> > type with a "simpleContent" content definition. But that's just xsd
> > rules: simple types don't have attribu
Gabriel Roldán wrote:
One issue at a time..
>
> NOTE: if an xsd type with scalar content has attributes, it is a complex type
> with a "simpleContent" content definition. But that's just xsd rules: simple
> types don't have attributes. We don't have attributes anyway.
>
Schemas often do have
Hi guys,
an old issue gets to the scene again at complex-features land: how to model an
xsd simple type with List binding.
Guess this is touching the limits of what we can do with the feature model.
Short and tempting answer would be to create just an AttributeType whose
binding is a List. But
http://geo.openplans.org:9090/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/224/buildId/733
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get th
Note that there's been a bug fix for jndi connection pools to work with
Oracle. See: http://jira.codehaus.org/browse/GEOS-778
It has an attached zip that shows how they did it.
Jody Garnett wrote:
Thanks for the informative discussion .. as promised here is my tough plan:
- http://docs.codeha
Thanks for the informative discussion .. as promised here is my tough plan:
- http://docs.codehaus.org/display/GEOTOOLS/J2EE+and+Connection+Pools
Currently I only have scope to fix this problem for EPSGDefaultFactory
... I have outlined
the plan for JDBCDataStore as well.
Cheers,
Jody
Jody Garn
Thanks for your input everyone (in IRC and email). I have assembled the
result here:
- http://docs.codehaus.org/display/GEOTOOLS/GTSteering+2007+Q1
I will write this up formally next week (with an "official" OSGeo
template or something).
Cheers,
Jody
---
Merge or just rename - either way the IndexedShapefileDataStore should
be named ShapefileDataStore. The index is an option in the factory to
turn off or on.
+1 on this, I've been trying to push for it for a long time, since that
was always the intent of the indexedshapefile.
C
Jody Garnett
Hmmm... looks like the parser isn't managing to parse your application
feature type correctly into a geotools feature type. Which method of
stream pasring are you using? Are you passing in your wfs configuration,
or an ApplicationSchema configuration?
Michael Lutz wrote:
> Ok, now I'm getting this
Hi Andrea got some answers by virtue of taking Jesse to coffee.
Apparently the original ShapefileDataStore can be retired (constructors
set to protected, factory unplugged etc...), although perhaps it would
be nicer to merge the two implementations.
Jody
Andrea Aime wrote:
>> For the case of t
I faced this in my recent experiment with h2. And I foudn the interface
was ConnectionPoolDataSource. Adapting what we have to that interace
would not be too hard.
>
> +1. The current state is that we've essentially rolled our own (less
> feature complete) version of DBCP. I looked in to it a
Andrea Aime wrote:
Jody Garnett ha scritto:
Thanks Andrea! That was a great overview of the trade-offs.
I am looking at how we do connection pools in GeoTools - but more
towards JNDI lookup then
handling of prepared statements. Is there anything you would like me to
look out for when
I do
Andrea Aime wrote:
> Jody Garnett ha scritto:
>> Thanks Andrea! That was a great overview of the trade-offs.
>>
>> I am looking at how we do connection pools in GeoTools - but more
>> towards JNDI lookup then
>> handling of prepared statements. Is there anything you would like me
>> to look out f
Jody Garnett ha scritto:
> Thanks Andrea! That was a great overview of the trade-offs.
>
> I am looking at how we do connection pools in GeoTools - but more
> towards JNDI lookup then
> handling of prepared statements. Is there anything you would like me to
> look out for when
> I do this work?
Thanks Andrea! That was a great overview of the trade-offs.
I am looking at how we do connection pools in GeoTools - but more
towards JNDI lookup then
handling of prepared statements. Is there anything you would like me to
look out for when
I do this work?
It sounds from your email that a share
Ok, now I'm getting this exception:
java.lang.RuntimeException: Parsing failed for ff_portugal_2002_4326:
org.geotools.feature.IllegalAttributeException: No attribute named fireID
at org.geotools.xml.impl.ParseExecutor.visit(ParseExecutor.java:96)
at
org.geotools.xml.impl.Binding
It's worth reading up on, if you care. The move to the new client/server
protocol did add support for a number of things which were emulated in
the past, like prepared statements. Not sure how much of this is
reflected in JDBC code, but hopefully a good deal.
P
Andrea Aime wrote:
> Justin Deol
Michael Lutz wrote:
> Thanks. The StreamingParser works considerably better (if a little
> slower). Note that the xPath expression must be "//featureMember"
> (without the prefix).
Right.. :) JXPath seems to not like the prefixes..., probably how the
context is being setup.
Yeah the streaming pa
Justin Deoliveira ha scritto:
> Andrea Aime wrote:
>> Justin Deoliveira ha scritto:
>>> Hi Andrea,
>
>> It really depends on the dbms. With Oracle the situation is as I
>> explained, with old Postgres jdbc driver prepared statements were fake,
>> in that the driver really built a full sql query an
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> Hi Andrea,
>
> It really depends on the dbms. With Oracle the situation is as I
> explained, with old Postgres jdbc driver prepared statements were fake,
> in that the driver really built a full sql query and then sent it
> to the server, with
Justin Deoliveira ha scritto:
> Hi Andrea,
>
> You sure know your JDBC stuff!! :). I would love to see us use batched
> prepared statements across the board, and in a more structured efficient
> manner. Problem is as usual the jdbc beast is somewhat untamable.
Unfortunately, agreed :-(
> Not sur
Hi Andrea,
You sure know your JDBC stuff!! :). I would love to see us use batched
prepared statements across the board, and in a more structured efficient
manner. Problem is as usual the jdbc beast is somewhat untamable.
Not sure how to proceed. Perhaps I will do some benchmarking to see how
sign
The "epsg-hsql" plugin has been upgrated to EPSG database 6.12 on trunk and the
2.3 branch, available on SVN. Attached is the EPSG release notice.
Martin
--- Begin Message ---
Release of EPSG Geodetic Parameter Dataset v6.12 (February 8, 2007)
This release (Version 6.12) of the EPSG Geod
WMS GetFeatureInfoRequest creation
--
Key: GEOT-1166
URL: http://jira.codehaus.org/browse/GEOT-1166
Project: GeoTools
Issue Type: Bug
Affects Versions: 2.3.0
Environment: Win32 (2000), JDK 1.6
Thanks. The StreamingParser works considerably better (if a little
slower). Note that the xPath expression must be "//featureMember"
(without the prefix).
I also tried "Alternative 2: Ignoring the Application Schema", but this
didn't work. I get
org.xml.sax.SAXException: Handler for wfs:Featur
30 matches
Mail list logo
