2 issues in deegree 3.0.0 services/tools

[Just van den Broecke]

Hi,

I am testing with deegree 3.0.0 (services+FSLoader) and found two issues:

1- some namespaces get strange substitutions after loading with FSLoader
e.g. for NET: <NET:beginLifespanVersion ... becomes
<zdef-135035779:beginLifespanVersion
Strangely not for all NSs, e.g. <NET:fictitious ... remains untouched.
(this problem was seen in earlier pre3 versions)

2- the dynamic DescribeFeature URL (e.g.
urn:x-inspire:specification:gmlas:RoadTransportNetwork:3.0
http://sunda:8080/deegree3/services?SERVICE=WFS.....) in the WFS
GetFeature response returns a partial XML document (confirmed with wget,
sunda:8080 is my local deegree3 WFS). This results in a validation error.

This is easy to reproduce with data in SVN. For example when loading
(valid):
http://code.google.com/p/inspire-foss/source/browse/trunk/etl/NL.Kadaster/TransportNetworks/test/tn-roadnetwork-curves.gml
GetFeature response is
http://code.google.com/p/inspire-foss/source/browse/trunk/etl/NL.Kadaster/TransportNetworks/test/wfs-rsp-roadlink.xml

There could be a config issue (all config is in SVN as well).

best,

--Just

[Markus Schneider]

Hi Just,

the second issue (broken DescribeFeatureType response/validation) should
be fixed. It's a config problem.

Currently, the WFS config has to contain the option

...
<DisableDynamicSchema>true</DisableDynamicSchema>
...

Otherwise, deegree will not use the original schema files from the
workspace for DescribeFeatureType responses, but regenerate the schema
from the internal feature model on-the-fly. And this is currently not
possible for INSPIRE due to limitations in the schema exporter. However,
as this works well for simpler schemas -- and even has the benefit of
being able to create GML 2 / 3.0 / 3.1 / 3.2 variants as well -- the
default setting is to create such "dynamic" DescribeFeatureType response.

I will investigate the namespace prefix issue and try to have a fix in
3.0.1 -- however, it's not really fatal.

Best regards,
Markus

[Just van den Broecke]

Hi Markus,

Yes, I see that the second issue is now fixed and the WFS response now
validates. The first issue happens during FSLoading, yes indeed it is
not fatal but looks a bit odd. thanks again,

Just

--
kind regards / met vriendelijke groet,

--Just

Just van den Broecke ju...@justobjects.nl
Just Objects B.V. tel +31 65 4268627 Skype: justb4
The Netherlands http://www.justobjects.nl

[Markus Schneider]

The odd-namespace prefix issue should be fixed in 3.0-SNAPSHOT and will
probably go into 3.0.1.

Do you mind testing if it's really fixed now? Just change the dependencies
to 3.0-SNAPSHOT in your checkout copy.

Best regards,
Markus

[Just van den Broecke]

I have just loaded/queried/validated deegree FSLoader and WFS with
3.0-SNAPSHOT and can confirm that "The odd-namespace prefix issue" has
been resolved. Thanks again Markus ! best,

Just