I’m progressing nicely with my work on WFS 2.0 stored query support. wfs-ng registers WFS 2.0 services nicely and I’m now implementing the stub methods in StrictWFS_2_0_Strategy. However, the Filter_Capabilities parsers for filter 2.0 are missing.
I’d like to check the following with the XSD gurus here, before I waste time building this the wrong way:
I need to implement EMF parsers for the types involved with Filter_Capabilities. My question is in which module should I write them? gt-xsd-fes contains bindings for the types involved while the EObjects and the factory are defined in net.opengis.fes. Neither depends on each other.
Looking at ows, gt-xsd-ows depends on net.opengis.ows. Should I follow this pattern and add Fes20Factory as a dependency for FESConfiguration? Or is there a reason why this dependency is not there?
This message may contain privileged and/or confidential information. If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate, or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.
I think you will find there is a List properties - and since each PropertyName can use a Name (or XPath) you should have enough information to proceed with?
I’m progressing nicely with my work on WFS 2.0 stored query support. wfs-ng registers WFS 2.0 services nicely and I’m now implementing the stub methods in StrictWFS_2_0_Strategy. However, the Filter_Capabilities parsers for filter 2.0 are missing.
I’d like to check the following with the XSD gurus here, before I waste time building this the wrong way:
I need to implement EMF parsers for the types involved with Filter_Capabilities. My question is in which module should I write them? gt-xsd-fes contains bindings for the types involved while the EObjects and the factory are defined in net.opengis.fes. Neither depends on each other.
Looking at ows, gt-xsd-ows depends on net.opengis.ows. Should I follow this pattern and add Fes20Factory as a dependency for FESConfiguration? Or is there a reason why this dependency is not there?
This message may contain privileged and/or confidential information. If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate, or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.
Correct, the bindings go in the gt-xsd- modules while only the generated model code go in the net.opengis.* modules.
As for the dependency we never actually really needed it for the GeoServer WFS 2.0 implementation because for capabilities operations we don’t use the xsd encoder. But yes, you can add it and that is the pattern to follow.
I’m progressing nicely with my work on WFS 2.0 stored query support. wfs-ng registers WFS 2.0 services nicely and I’m now implementing the stub methods in StrictWFS_2_0_Strategy. However, the Filter_Capabilities parsers for filter 2.0 are missing.
I’d like to check the following with the XSD gurus here, before I waste time building this the wrong way:
I need to implement EMF parsers for the types involved with Filter_Capabilities. My question is in which module should I write them? gt-xsd-fes contains bindings for the types involved while the EObjects and the factory are defined in net.opengis.fes. Neither depends on each other.
Looking at ows, gt-xsd-ows depends on net.opengis.ows. Should I follow this pattern and add Fes20Factory as a dependency for FESConfiguration? Or is there a reason why this dependency is not there?
This message may contain privileged and/or confidential information. If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate, or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.