[Geoserver-devel] MIFDataStore

Hi all, I am trying to make work the MIFDataStore with GeoServer 1.2, I am changing and moving libs, adding methods but there are too many inconsistencies. Is there some version the MIFDataStore that works with GeoServer1.2? Or some recommendation for this problem.
Regards.
OZB.
P.D. I have tried to work with the code of GeoServer 1.3, but this needs many extra librarys and I already studied the code of GeoServer 1.2.

Quoting Omar Zevallos <omzeta@anonymised.com>:

Hi all, I am trying to make work the MIFDataStore with GeoServer 1.2,
I am changing and moving libs, adding methods but there are too many
inconsistencies. Is there some version the MIFDataStore that works
with GeoServer1.2? Or some recommendation for this problem.
Regards.
OZB.
P.D. I have tried to work with the code of GeoServer 1.3, but this
needs many extra librarys and I already studied the code of GeoServer
1.2.

There's pretty much no way to do it. Sorry we didn't emphasize this
strongly enough last time, but MIF was developed against GeoTools 2.1,
which is not compatible with GeoTools 2.0 (which we at geoserver were
quite upset about, but there was nothing we could really do), and thus
not with GeoServer 1.2. There were too many inconsistencies, as you've
unfortunately had to find out for yourself.

GeoServer 1.3 does not need all that many extra libraries? Are you
extending the code? It should be pretty similar to 1.2, especially at
the GeoServer level. Perhaps we could point you in the right direction
to do what you're trying to achieve with 1.3? It's really a lot
better, definitely worth learning the updated codebase.

best regards,

Chris

----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/

Hi all, thanks for you support.
the question of the day. Is there some way to transform the response of
Geoserver 1.3 in WSDL?
regards.
OZB

Quoting Omar Zevallos <omzeta@anonymised.com>:

Hi all, thanks for you support.
the question of the day. Is there some way to transform the response
of
Geoserver 1.3 in WSDL?

I assume you mean the capabilities response? I think that's the only
thing that makes sense to do as WSDL, to describe what the service has.
I'm sure it's possible in some way, but afaik there's no official
spec. Way back in WFS 0.15 or something they actually did define the
capabilities document in wsdl (I actually had to implement this :frowning: ),
but in 1.0.0 it vanished without a trace.

I'm pretty postivie 1.1 defines how to wrap responses in SOAP, but I
don't think they make mention of wsdl (I could be wrong, I've not
looked at it extensively).

best regards,

Chris

regards.
OZB

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration
Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/

WSDL could be used for the generic WFS spec to (to define the requests and messages) and I suppose you could describe messages as a data type which is a union of the supported feature types.

But why would you?

    * WSDL tells you nothing about the content.

    * The interface is well-known, so using WSDL to create a stub in
      some programming language doesnt buy you very much.

WSDL could be used as a framework for the getCapabilities responses to enforce all OGC interfaces to be self consistent with each as a suite, but is not very relevant to specific services instances IMHO.

Likewise, SOAP is a different layer - its certainly possible to wrap WFS querys and responses in SOAP. Why you would want to would be a function of the infrastructure you are deploying into, and to date not much cross-enterprise standardisation seems to have taken place.

Rob Atkinson

Chris Holmes wrote:

Quoting Omar Zevallos <omzeta@anonymised.com>:

Hi all, thanks for you support.
the question of the day. Is there some way to transform the response
of
Geoserver 1.3 in WSDL?
   

I assume you mean the capabilities response? I think that's the only
thing that makes sense to do as WSDL, to describe what the service has.
I'm sure it's possible in some way, but afaik there's no official
spec. Way back in WFS 0.15 or something they actually did define the
capabilities document in wsdl (I actually had to implement this :frowning: ),
but in 1.0.0 it vanished without a trace.

I'm pretty postivie 1.1 defines how to wrap responses in SOAP, but I
don't think they make mention of wsdl (I could be wrong, I've not
looked at it extensively).

best regards,

Chris

regards.
OZB

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration
Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel