I have encountered a strange problem using GeoServer 1.7.6
WFS, with the data in an Oracle NG data store. Attribute
values in the returned GML are truncated to 28 characters
length. Have I misconfigured something?
--
mogul | nils weinander |
hudiksvallsgatan 4 113 30 stockholm sweden |
+46 8 4100 6456 | +46 709 78 28 37 |
nils.weinander@anonymised.com | skype: nils.weinander |
www.mogul.com
Nils Weinander wrote:
I have encountered a strange problem using GeoServer 1.7.6
WFS, with the data in an Oracle NG data store. Attribute
values in the returned GML are truncated to 28 characters
length. Have I misconfigured something?
One more detail: attribute values are truncated with WFS 1.0.0,
but not with WFS 1.1.0.
--
View this message in context: http://www.nabble.com/GeoServer-1.7.6-WFS-Oracle-NG-truncated-attribute-values-tp25768404p25781441.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
Nils Weinander wrote:
One more detail: attribute values are truncated with WFS 1.0.0,
but not with WFS 1.1.0.
Even more detail: version doesn't seem to be the determining factor.
Attribute values get truncated with WFDS 1.1.0 too, about every other
request. Usually at 28 characters, but sometimes at other lengths.
What to do?
--
View this message in context: http://www.nabble.com/GeoServer-1.7.6-WFS-Oracle-NG-truncated-attribute-values-tp25768404p25781788.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
Nils Weinander ha scritto:
Nils Weinander wrote:
One more detail: attribute values are truncated with WFS 1.0.0, but not with WFS 1.1.0.
Even more detail: version doesn't seem to be the determining factor. Attribute values get truncated with WFDS 1.1.0 too, about every other
request. Usually at 28 characters, but sometimes at other lengths.What to do?
I have no idea of what might be going on as I've never seen this
happen. I cannot think of any code cutting strings on purpose
once in memory... very weird.
I guess we'll need a fully reproducable test case: a dunmp of
your data, your requests, so that we can try this out.
When I first read your msg I thought that maybe the data was
truncated on the database already, but if data is truncated
is some requests and not in others, there is something going on...
Is the same record being truncated in some requests and not
in others?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Nils Weinander ha scritto:
Nils Weinander wrote:
One more detail: attribute values are truncated with WFS 1.0.0, but not with WFS 1.1.0.
Even more detail: version doesn't seem to be the determining factor. Attribute values get truncated with WFDS 1.1.0 too, about every other
request. Usually at 28 characters, but sometimes at other lengths.What to do?
I have no idea of what might be going on as I've never seen this
happen. I cannot think of any code cutting strings on purpose
once in memory... very weird.I guess we'll need a fully reproducable test case: a dunmp of
your data, your requests, so that we can try this out.When I first read your msg I thought that maybe the data was
truncated on the database already, but if data is truncated
is some requests and not in others, there is something going on...
Is the same record being truncated in some requests and not
in others?
I have just redefined my data and I think I have found what causes
the problem, but not why (I am not 100% sure as the combination
that now works did cause problems yesterday).
I have a table with one CLOB column. GeoServer works against
a view which transforms the CLOB column to varchar with
to_char() (using the CLOB column straight did not work, I
got the toString() value of the Oracle LOB java object
rather than the text).
Changing the underlying table so that the long text column
is varchar2(4000) instead I can no longer reproduce the
truncation. I did test that yesterday too, but I can only
think that I made some other error then.
Now I get problems with the proxy service I need for OpenLayers
to work with the WFS, but that is another issue.
--
mogul | nils weinander |
hudiksvallsgatan 4 113 30 stockholm sweden |
+46 8 4100 6456 | +46 709 78 28 37 |
nils.weinander@anonymised.com | skype: nils.weinander |
www.mogul.com
Hello,
I want to active the cache of an entity, so that my web browser caches the tiles. I check the appropriate box in the entity's configuration.
Then the tiles have Cache-Control: max-age=60000, must-revalidate.
My issue is that the must-revalidate gives my web browser some trouble and caches nothing; moreover I would like the "public" keyword in cache control directive.
Is there a way to change the cache-control directive send by the geoserver?
Thanks for your help.
Cordially,
Fabien Fleurier.
=============================
FLEURIER Fabien
Atos Worldline - Lyon
fabien.fleurier@anonymised.com
http://www.atosorigin.com
Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
GeoServer does not provide fine grained control directly.
You may be able to add it using generic servlet filters. Alternatively, if you proxy through Apache (httpd) then you can clobber the HTTP headers any way you like.
-Arne
Fleurier Fabien wrote:
Hello,
I want to active the cache of an entity, so that my web browser caches the tiles. I check the appropriate box in the entity's configuration.
Then the tiles have Cache-Control: max-age=60000, must-revalidate.My issue is that the must-revalidate gives my web browser some trouble and caches nothing; moreover I would like the "public" keyword in cache control directive.
Is there a way to change the cache-control directive send by the geoserver?
Thanks for your help.
Cordially,
Fabien Fleurier.=============================
FLEURIER Fabien
Atos Worldline - Lyon
fabien.fleurier@anonymised.com
http://www.atosorigin.com