Hey Andrea,

thanks for your reply. This info seems to be present in wfs.xml:

  <gml>
    <entry>
      
<org.geoserver.wfs.WFSInfo_-Version>V_10</org.geoserver.wfs.WFSInfo_-Version>
      <org.geoserver.wfs.GMLInfoImpl>
        <srsNameStyle>XML</srsNameStyle>
      </org.geoserver.wfs.GMLInfoImpl>
    </entry>
    <entry>
      
<org.geoserver.wfs.WFSInfo_-Version>V_11</org.geoserver.wfs.WFSInfo_-Version>
      <org.geoserver.wfs.GMLInfoImpl>
        <srsNameStyle>URN</srsNameStyle>
      </org.geoserver.wfs.GMLInfoImpl>
    </entry>
  </gml>

Could the fact that we are using dbconfig have anything to do with this?

Best regards,
Bart

>       From: Andrea Aime <andrea.a...@geo-solutions.it>
>       Date: January 2, 2012 5:01:37 PM GMT+01:00
>       To: bart...@osgis.nl
>       Cc: geoserver-users@lists.sourceforge.net
>       Subject: Re: [Geoserver-users] error on WMS GetFeatureInfo
> (ArcSDE)
>
>       On Mon, Jan 2, 2012 at 4:06 PM, Bart van den Eijnden (OSGIS)
> <bart...@osgis.nl> wrote:
>
>       Hi,
>
>       using GeoServer 2.1.2 I am getting an error on WMS
> GetFeatureInfo for
>       ArcSDE layers. Is this a known issue, or something specific in
> our setup?
>
>
>
>       That does not sound SDE specific but more specific to your
> install.
>
>       The lines in the code are:
>
>
>
>       223     GMLInfo gml = wfs.getGML().get(WFSInfo.Version.V_10);
>
>       224     transformer.setGmlPrefixing(wfs.isCiteCompliant() ||
> !gml.getOverrideGMLAttributes());
>
>
>
>       which seems to imply you have no gml info for wfs 1.0.
>
>       In your data directory, wfs.xml file, you should have something
> like:
>
>
>
>       <gml>
>
>           <entry>
>
>
> <org.geoserver.wfs.WFSInfo_-Version>V_10</org.geoserver.wfs.WFSInfo_-Ver
> sion>
>
>             <org.geoserver.wfs.GMLInfoImpl>
>
>               <srsNameStyle>XML</srsNameStyle>
>
>               <overrideGMLAttributes>true</overrideGMLAttributes>
>
>             </org.geoserver.wfs.GMLInfoImpl>
>
>           </entry>
>
>           <entry>
>
>
> <org.geoserver.wfs.WFSInfo_-Version>V_11</org.geoserver.wfs.WFSInfo_-Ver
> sion>
>
>             <org.geoserver.wfs.GMLInfoImpl>
>
>               <srsNameStyle>URN</srsNameStyle>
>
>               <overrideGMLAttributes>false</overrideGMLAttributes>
>
>             </org.geoserver.wfs.GMLInfoImpl>
>
>           </entry>
>
>         </gml>
>
>
>
>
>
>       But I guess you're missing both, or missing just the V_10 entry.
>
>       If you go and configure the gml stuff for you wfs service in the
> wfs panel, and
>
>       then save, you should get those filled automatically and the
> problem should
>
>       go away.
>
>
>
>       However I'm curious of how you got there in the first place?
>
>       How was you data directory created?
>
>
>
>       Cheers
>
>       Andrea
>
>
>
>
>
>       --
>       -------------------------------------------------------
>       Ing. Andrea Aime
>       GeoSolutions S.A.S.
>       Tech lead
>
>       Via Poggio alle Viti 1187
>       55054  Massarosa (LU)
>       Italy
>
>       phone: +39 0584 962313
>       fax:      +39 0584 962313
>       mob:    +39 339 8844549
>
>
>       http://www.geo-solutions.it
>       http://geo-solutions.blogspot.com/
>       http://www.youtube.com/user/GeoSolutionsIT
>       http://www.linkedin.com/in/andreaaime
>       http://twitter.com/geowolf
>
>       Please take note that GeoSolutions will be closed for Christmas
> holidays from 27/12 to 30/12
>
>       -------------------------------------------------------
>
>
>
>



------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to