Thanks again Ben. As answers to your questions...
I started from scratch with GeoServer 2.3.5 on Windows. My simple feature
WFS services work great, even with the app-schema extension loaded.
However, the errors start when I create a layer with app-schema (by
creating the layer first with the original data store, then editing the
datastore.aml file and creating a new mapping file, then restarting
Tomcat.) The new schema xsd is downloaded and stored in appo-schema-cache,
as would be expected. The error is thrown with a WFS GetFeature request
and is always something like:
The prefix "null" for element "null:GeologicUnitView" is not bound.
with of course GeologicUnitView is sometimes the simple feature WFS layer
name. I still cannot determine a pattern on when the app-schema service
throws the error or when the simple feature WFS service throws the error,
but it is always one or the other. I cannot get both of them to work
simultaneously. (I can always force one of them to work by setting that
workspace as the default workspace.)
I have full verbose logging turned on. Not many errors when starting
GeoServer, except for the standard JP2/ECW/MrSID errors. I do see plenty
of
2013-09-01 12:11:45,210 DEBUG [referencing.factory] - Failure in the
primary factory: No code "EPSG:26957" from authority "European Petroleum
Survey Group" found for object of type "IdentifiedObject". Now trying the
fallback factory...
for each of my layers. Doubt this has anything to do with the problems
since all my WMS services continue to work great.
Strange. Does anyone have a configuration of WFS simple feature and
app-schema services both working fine? Would you be willing to share the
config xml docs?
- John
John Callahan
Research Scientist
Delaware Geological Survey
University of Delaware
http://www.dgs.udel.edu
[email protected]
On Thu, Aug 29, 2013 at 1:14 AM, John Callahan <[email protected]>wrote:
> Thanks Ben. Yes, it is perplexing. The gsmlp (app-schema) service now
> has been working well but the simple feature WFS services, for all
> workspaces other then gsmlp, continue to return errors.
>
> I have noticed that for the responses that return errors, the gsmlp
> namespace is included rather than the namespace being being called. This
> in turn (I think) leads to the null prefix for the featureMembers. For
> example, the call
>
>
> http://maps.dgs.udel.edu/geoserver/DGS_Surficial_and_Contact_Geology/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=DGS_Surficial_and_Contact_Geology:US-DE_DGS_100k_Surficial_Geology&maxFeatures=1
>
> includes in the response the following xmlns:
>
> xmlns:gsmlp="http://xmlns.geosciml.org/geosciml-portrayal/2.0"
>
> but should instead include:
>
> xmlns:DGS_Surficial_and_Contact_Geology="
> http://www.dgs.udel.edu/surficial_geology"
>
>
> I will look into your other questions. Good points.
>
> - John
>
>
>
>
> On Thu, Aug 29, 2013 at 12:18 AM, Ben Caradoc-Davies <
> [email protected]> wrote:
>
>> John,
>>
>> this is perplexing. I have had a look at the capabilities responses and
>> the responses for the top-level and workspace service URLs and I cannot see
>> a pattern or anything obviously wrong.
>>
>> - Do you get any errors in the logs when you start GeoServer?
>>
>> - What happens if you remove the app-schema plugin and restart GeoServer?
>> Do you still have problems with your simple feature response encoding?
>>
>> - Please check that your app-schema plugin is from the same build as
>> GeoServer core.
>>
>> As a last resort, you could send me your workspaces folder.
>>
>> Kind regards,
>> Ben.
>>
>>
>> On 29/08/13 02:27, John Callahan wrote:
>>
>>> Thank you Ben for your explanations. You are right, that service was
>>> working fine. However, it is not anymore. ;) It stopped working when
>>> I changed the default workspace. I reviewed the app-schema tutorial and
>>> matched everything the best I can. It does work great when "gsmlp" is
>>> the default workspace (and occassionally other times but I cannot figure
>>> out a pattern.)
>>>
>>> http://maps.dgs.udel.edu/**geoserver/gsmlp/ows?service=**
>>> WFS&version=1.1.0&request=**GetFeature&typeName=gsmlp:**
>>> GeologicUnitView&maxFeatures=1<http://maps.dgs.udel.edu/geoserver/gsmlp/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=gsmlp:GeologicUnitView&maxFeatures=1>
>>>
>>>
>>> Perhaps the error is not app-schema related. Other services, not
>>> app-schema related, are also throwing the same "null" errors on WFS
>>> requests, shown below. I thought app-schema was involved because the
>>> problems started when the app-schema extension was installed and
>>> services created. My default workspace is now "dgs" (in second service
>>> below).
>>>
>>>
>>> http://maps.dgs.udel.edu/**geoserver/DGS_Surficial_and_**
>>> Contact_Geology/ows?service=**WFS&version=1.1.0&request=**
>>> GetFeature&typeName=DGS_**Surficial_and_Contact_Geology:**
>>> US-DE_DGS_100k_Surficial_**Geology&maxFeatures=1<http://maps.dgs.udel.edu/geoserver/DGS_Surficial_and_Contact_Geology/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=DGS_Surficial_and_Contact_Geology:US-DE_DGS_100k_Surficial_Geology&maxFeatures=1>
>>> (does not work)
>>>
>>> http://maps.dgs.udel.edu/**geoserver/dgs/ows?service=WFS&**
>>> version=1.1.0&request=**GetFeature&typeName=dgs:**geomap18&maxFeatures=1<http://maps.dgs.udel.edu/geoserver/dgs/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=dgs:geomap18&maxFeatures=1>(works)
>>>
>>>
>>> Thanks for any thoughts you might have. I am running GeoServer 2.3.4 on
>>> Windows.
>>>
>>>
>>> - John
>>>
>>>
>>> John Callahan
>>> Research Scientist
>>> Delaware Geological Survey
>>> University of Delaware
>>> http://www.dgs.udel.edu
>>> [email protected] <mailto:[email protected]**>
>>>
>>>
>>>
>>>
>>> On Wed, Aug 28, 2013 at 4:26 AM, Ben Caradoc-Davies
>>> <[email protected]
>>> <mailto:Ben.Caradoc-Davies@**csiro.au<[email protected]>>>
>>> wrote:
>>>
>>> Also:
>>>
>>>
>>> On 28/08/13 14:33, John Callahan wrote:
>>>
>>> It also fails using WFS 1.0.0 (java.lang.ClassCastException:
>>> org.geotools.feature.type.__**ComplexFeatureTypeImpl cannot be
>>> cast to
>>> org.opengis.feature.simple.__**SimpleFeatureType)
>>>
>>>
>>>
>>> app-schema does not support WFS 1.0.0 (which uses GML 2). Your GML
>>> 3.1.1 application schema should work fine with WFS 1.1.0, which
>>> defaults to GML 3.1.1 output. See:
>>> http://docs.geoserver.org/__**latest/en/user/data/app-__**
>>> schema/supported-gml-versions.**__html<http://docs.geoserver.org/__latest/en/user/data/app-__schema/supported-gml-versions.__html>
>>>
>>> <http://docs.geoserver.org/**latest/en/user/data/app-**
>>> schema/supported-gml-versions.**html<http://docs.geoserver.org/latest/en/user/data/app-schema/supported-gml-versions.html>
>>> >
>>>
>>>
>>> but actually returns a response with WFS 2.0.0
>>>
>>>
>>> If you look closely you will likely discover missing elements and
>>> other problems as there are type mismatches between the GML 3.2.1
>>> encoder configuration that is the default for WFS 2.0.0 responses
>>> and the GML 3.1.1 information model in your application schema.
>>> GeoServer tries its best, but will make a hash of things.
>>>
>>> Kind regards,
>>>
>>>
>>> --
>>> Ben Caradoc-Davies <[email protected]>
>>> Software Engineer
>>> CSIRO Earth Science and Resource Engineering
>>> Australian Resources Research Centre
>>>
>>>
>>>
>> --
>> Ben Caradoc-Davies <[email protected]>
>> Software Engineer
>> CSIRO Earth Science and Resource Engineering
>> Australian Resources Research Centre
>>
>
>
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users