[Geoserver-users] features send in wrong namespace using mysql-datastore

Hello Andrea,

might it be possible that the Namespace will not be set to the params for the
GeoTools DatastoreFinder?

I sometimes also have got the problem, that the Namespace is used as
DatabaseName.

Tim

-----Ursprüngliche Nachricht-----
Von: geoserver-users-bounces@lists.sourceforge.net
[mailto:geoserver-users-bounces@lists.sourceforge.net]Im Auftrag von
aaime
Gesendet: Donnerstag, 9. August 2007 12:06
An: geoserver-users@lists.sourceforge.net
Betreff: Re: [Geoserver-users] features send in wrong namespace using
mysql-datastore

Tim Englich-2 wrote:

Hello,

I have got an problem with the getFeature-Response of Geoserver when I
query
data from a MySQL-Datastore.
The features are set to the GML-Namespace and not to the namespace I set
to
the Datastore.
Has anyone an Idea how to solve this problem?

It seems you keep on hitting on datastores that have issues. MySql is barely
mantained,
so I guess you'll have to roll a patch on it.
Oh, before starting have a look at the jira issues for mysql, there are some
patches sitting there made by another user that I still haven't managed to
include in the code, it may be that there's one solving this problem already
(haven't checked).

Cheers
Andrea
--
View this message in context:
http://www.nabble.com/features-send-in-wrong-namespace-using-mysql-datastore-
tf4241376.html#a12069713
Sent from the GeoServer - User mailing list archive at Nabble.com.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

On Thu, August 9, 2007 3:06 pm, Tim Englich wrote:

Hello Andrea,

might it be possible that the Namespace will not be set to the params for
the GeoTools DatastoreFinder?

I sometimes also have got the problem, that the Namespace is used as
DatabaseName.

Hum... no, the namespace is set by GeoServer, but maybe the
MySql datastore factory uses a different name than the other
data stores for the param, or it does not provide the param
to the datastore, or the datastore does not use it to create the
feature types... I have no idea...

Cheers
Andrea

Hi Tim,

Looking at the code I believe you are correct. The DataStoreFactory
correctly looks up the namespace set by GeoServer but the datastore
seems to mishandle it.

The patch should be pretty simple. I could send it your way if you are
interested. I cant really just commit the change since i am not the
mysql module maintainer. Or do I have a mysql install around to test with.

-Justin

Tim Englich wrote:

Hello Andrea,

might it be possible that the Namespace will not be set to the params for the
GeoTools DatastoreFinder?

I sometimes also have got the problem, that the Namespace is used as
DatabaseName.

Tim

-----Ursprüngliche Nachricht-----
Von: geoserver-users-bounces@lists.sourceforge.net
[mailto:geoserver-users-bounces@lists.sourceforge.net]Im Auftrag von
aaime
Gesendet: Donnerstag, 9. August 2007 12:06
An: geoserver-users@lists.sourceforge.net
Betreff: Re: [Geoserver-users] features send in wrong namespace using
mysql-datastore

Tim Englich-2 wrote:

Hello,

I have got an problem with the getFeature-Response of Geoserver when I
query
data from a MySQL-Datastore.
The features are set to the GML-Namespace and not to the namespace I set
to
the Datastore.
Has anyone an Idea how to solve this problem?

It seems you keep on hitting on datastores that have issues. MySql is barely
mantained,
so I guess you'll have to roll a patch on it.
Oh, before starting have a look at the jira issues for mysql, there are some
patches sitting there made by another user that I still haven't managed to
include in the code, it may be that there's one solving this problem already
(haven't checked).

Cheers
Andrea

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org