Hi all,
Here is the official proposal for moving the rest module to a core module.
http://geoserver.org/display/GEOS/GSIP+32+-+REST+support+module
Feedback welcome.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Hi all,
Here is the official proposal for moving the rest module to a core module.
http://geoserver.org/display/GEOS/GSIP+32+-+REST+support+module
Feedback welcome.
The documentation page is leaving me with some doubts. Like, for example, the role of a finder in our implementation. Do we have any?
The example does not show how to deal with output formats other
than plain text. Is this still working based on maps, or based
on reflection?
It would also be nice to see some javadocs, probably they would
answer the above questions.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi all,
Here is the official proposal for moving the rest module to a core module.
http://geoserver.org/display/GEOS/GSIP+32+-+REST+support+module
Feedback welcome.
The documentation page is leaving me with some doubts. Like, for example, the role of a finder in our implementation. Do we have any?
The docs are a bit basic at this point. They need some work. I will expand on them. But essentially the finder is used to map different classes of resources, to a single url. And that is just my practical understanding... David probably has better insight since he knows restlet better than I.
The example does not show how to deal with output formats other
than plain text. Is this still working based on maps, or based
on reflection?
Yeah, the example there is based on the most simple thing one can do. Again, I will expand on the docs but essentially there are subclasses of AbstractResource: MapResource, and ReflectiveResource, which can do some automatic serialization for you in json and xml. My plan was to add three tutorials... 1) the very basic 2) the map approach 3) the reflection approach
It would also be nice to see some javadocs, probably they would
answer the above questions.
Added a link from the proposal. But they are available here:
http://gridlock.openplans.org/rest/apidocs/
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
I added two sections to the developer documentation. One is an example of how to build a service/resource with the map based approach. The other is how to build a service/resource with the reflection based approach. Here is the link again:
-Justin
Justin Deoliveira wrote:
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi all,
Here is the official proposal for moving the rest module to a core module.
http://geoserver.org/display/GEOS/GSIP+32+-+REST+support+module
Feedback welcome.
The documentation page is leaving me with some doubts. Like, for example, the role of a finder in our implementation. Do we have any?
The docs are a bit basic at this point. They need some work. I will expand on them. But essentially the finder is used to map different classes of resources, to a single url. And that is just my practical understanding... David probably has better insight since he knows restlet better than I.
The example does not show how to deal with output formats other
than plain text. Is this still working based on maps, or based
on reflection?Yeah, the example there is based on the most simple thing one can do. Again, I will expand on the docs but essentially there are subclasses of AbstractResource: MapResource, and ReflectiveResource, which can do some automatic serialization for you in json and xml. My plan was to add three tutorials... 1) the very basic 2) the map approach 3) the reflection approach
It would also be nice to see some javadocs, probably they would
answer the above questions.Added a link from the proposal. But they are available here:
http://gridlock.openplans.org/rest/apidocs/
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
I am enjoying the documentation thus far; can I confirm that we are talking about moving the rest “displatch” code into core; similar to how the ows dispatch code is in core already? ie. “resut support module” is about enabling REST support; and does not expose any rest services on its own?
Jody
PS. I like the look of the new docs; although I miss the maven and eclipse quickstart information which I have handed out to new developers a couple times in the last month
On Fri, Feb 6, 2009 at 3:28 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
I added two sections to the developer documentation. One is an example
of how to build a service/resource with the map based approach. The
other is how to build a service/resource with the reflection based
approach. Here is the link again:-Justin
Justin Deoliveira wrote:
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi all,
Here is the official proposal for moving the rest module to a core
module.http://geoserver.org/display/GEOS/GSIP+32±+REST+support+module
Feedback welcome.
The documentation page is leaving me with some doubts. Like, for
example, the role of a finder in our implementation. Do we have any?The docs are a bit basic at this point. They need some work. I will
expand on them. But essentially the finder is used to map different
classes of resources, to a single url. And that is just my practical
understanding… David probably has better insight since he knows
restlet better than I.The example does not show how to deal with output formats other
than plain text. Is this still working based on maps, or based
on reflection?
Yeah, the example there is based on the most simple thing one can do.
Again, I will expand on the docs but essentially there are subclasses of
AbstractResource: MapResource, and ReflectiveResource, which can do some
automatic serialization for you in json and xml. My plan was to add
three tutorials… 1) the very basic 2) the map approach 3) the
reflection approach
It would also be nice to see some javadocs, probably they would
answer the above questions.Added a link from the proposal. But they are available here:
http://gridlock.openplans.org/rest/apidocs/
Cheers
Andrea–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR™
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
The short answer is, no, the rest support module doesn't expose any rest
services.
The longer, but more technically accurate answer is that it does expose
one endpoint; that being an index page which lists all non-parameterized
REST pages. The idea is that you can find out what services are
provided and, if the developers have made the effort to keep them
HTML-friendly, navigate them through the browser.
--
David Winslow
OpenGeo - http://opengeo.org/
On Mon, 2009-02-09 at 11:05 +1100, Jody Garnett wrote:
I am enjoying the documentation thus far; can I confirm that we are
talking about moving the rest "displatch" code into core; similar to
how the ows dispatch code is in core already? ie. "resut support
module" is about enabling REST support; and does not expose any rest
services on its own?Jody
PS. I like the look of the new docs; although I miss the maven and
eclipse quickstart information which I have handed out to new
developers a couple times in the last monthOn Fri, Feb 6, 2009 at 3:28 PM, Justin Deoliveira
<jdeolive@anonymised.com> wrote:
I added two sections to the developer documentation. One is an
example
of how to build a service/resource with the map based
approach. The
other is how to build a service/resource with the reflection
based
approach. Here is the link again:
http://gridlock.openplans.org/geoserver/1.7.x/doc/developer/programming-guide/rest-services/index.html
-Justin
Justin Deoliveira wrote:
> Andrea Aime wrote:
>> Justin Deoliveira ha scritto:
>>> Hi all,
>>>
>>> Here is the official proposal for moving the rest module
to a core
>>> module.
>>>
>>> http://geoserver.org/display/GEOS/GSIP+32+-+REST+support
+module
>>>
>>> Feedback welcome.
>> The documentation page is leaving me with some doubts.
Like, for
>> example, the role of a finder in our implementation. Do we
have any?
>
> The docs are a bit basic at this point. They need some work.
I will
> expand on them. But essentially the finder is used to map
different
> classes of resources, to a single url. And that is just my
practical
> understanding... David probably has better insight since he
knows
> restlet better than I.
>> The example does not show how to deal with output formats
other
>> than plain text. Is this still working based on maps, or
based
>> on reflection?
> Yeah, the example there is based on the most simple thing
one can do.
> Again, I will expand on the docs but essentially there are
subclasses of
> AbstractResource: MapResource, and ReflectiveResource, which
can do some
> automatic serialization for you in json and xml. My plan was
to add
> three tutorials... 1) the very basic 2) the map approach 3)
the
> reflection approach
>> It would also be nice to see some javadocs, probably they
would
>> answer the above questions.
>
> Added a link from the proposal. But they are available here:
>
> http://gridlock.openplans.org/rest/apidocs/
>> Cheers
>> Andrea
>>
>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with
Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing
skills and code to
build responsive, highly engaging applications that combine
the power of local
resources and data with the reach of the web. Download the
Adobe AIR SDK and
Ajax docs to start building applications
today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Thanks for the clarification (I am glad I understood the proposal correctly). It sounds like you are working through the documentation issues as they arise; I am in favor of the technical direction so this proposal gets a +1 from me.
Jody
On Mon, Feb 9, 2009 at 2:04 PM, David Winslow <dwinslow@anonymised.com> wrote:
The short answer is, no, the rest support module doesn’t expose any rest
services.The longer, but more technically accurate answer is that it does expose
one endpoint; that being an index page which lists all non-parameterized
REST pages. The idea is that you can find out what services are
provided and, if the developers have made the effort to keep them
HTML-friendly, navigate them through the browser.–
David Winslow
OpenGeo - http://opengeo.org/On Mon, 2009-02-09 at 11:05 +1100, Jody Garnett wrote:
I am enjoying the documentation thus far; can I confirm that we are
talking about moving the rest “displatch” code into core; similar to
how the ows dispatch code is in core already? ie. “resut support
module” is about enabling REST support; and does not expose any rest
services on its own?Jody
PS. I like the look of the new docs; although I miss the maven and
eclipse quickstart information which I have handed out to new
developers a couple times in the last monthOn Fri, Feb 6, 2009 at 3:28 PM, Justin Deoliveira
<jdeolive@anonymised.com> wrote:
I added two sections to the developer documentation. One is an
example
of how to build a service/resource with the map based
approach. The
other is how to build a service/resource with the reflection
based
approach. Here is the link again:-Justin
Justin Deoliveira wrote:
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi all,
Here is the official proposal for moving the rest module
to a core
module.http://geoserver.org/display/GEOS/GSIP+32±+REST+support
+moduleFeedback welcome.
The documentation page is leaving me with some doubts.
Like, for
example, the role of a finder in our implementation. Do we
have any?The docs are a bit basic at this point. They need some work.
I will
expand on them. But essentially the finder is used to map
different
classes of resources, to a single url. And that is just my
practical
understanding… David probably has better insight since he
knows
restlet better than I.The example does not show how to deal with output formats
other
than plain text. Is this still working based on maps, or
based
on reflection?
Yeah, the example there is based on the most simple thing
one can do.
Again, I will expand on the docs but essentially there are
subclasses of
AbstractResource: MapResource, and ReflectiveResource, which
can do some
automatic serialization for you in json and xml. My plan was
to add
three tutorials… 1) the very basic 2) the map approach 3)
the
reflection approach
It would also be nice to see some javadocs, probably they
would
answer the above questions.Added a link from the proposal. But they are available here:
http://gridlock.openplans.org/rest/apidocs/
Cheers
Andrea–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Create and Deploy Rich Internet Apps outside the browser with
Adobe(R)AIR™
software. With Adobe AIR, Ajax developers can use existing
skills and code to
build responsive, highly engaging applications that combine
the power of local
resources and data with the reach of the web. Download the
Adobe AIR SDK and
Ajax docs to start building applications
today-http://p.sf.net/sfu/adobe-com
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR™
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Hi guys, here Alessio++
Cheers.
-------------------------------------------------------
Eng. Alessio Fabiani
Vice-President /CTO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584 980933
fax: +39 0584 983027
mob: +39 349 8227000
-------------------------------------------------------
On Tue, Feb 10, 2009 at 1:25 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Thanks for the clarification (I am glad I understood the proposal
correctly). It sounds like you are working through the documentation issues
as they arise; I am in favor of the technical direction so this proposal
gets a +1 from me.Jody
On Mon, Feb 9, 2009 at 2:04 PM, David Winslow <dwinslow@anonymised.com> wrote:
The short answer is, no, the rest support module doesn't expose any rest
services.The longer, but more technically accurate answer is that it does expose
one endpoint; that being an index page which lists all non-parameterized
REST pages. The idea is that you can find out what services are
provided and, if the developers have made the effort to keep them
HTML-friendly, navigate them through the browser.--
David Winslow
OpenGeo - http://opengeo.org/On Mon, 2009-02-09 at 11:05 +1100, Jody Garnett wrote:
> I am enjoying the documentation thus far; can I confirm that we are
> talking about moving the rest "displatch" code into core; similar to
> how the ows dispatch code is in core already? ie. "resut support
> module" is about enabling REST support; and does not expose any rest
> services on its own?
>
> Jody
> PS. I like the look of the new docs; although I miss the maven and
> eclipse quickstart information which I have handed out to new
> developers a couple times in the last month
>
> On Fri, Feb 6, 2009 at 3:28 PM, Justin Deoliveira
> <jdeolive@anonymised.com> wrote:
> I added two sections to the developer documentation. One is an
> example
> of how to build a service/resource with the map based
> approach. The
> other is how to build a service/resource with the reflection
> based
> approach. Here is the link again:
>
>
> http://gridlock.openplans.org/geoserver/1.7.x/doc/developer/programming-guide/rest-services/index.html
>
> -Justin
>
>
> Justin Deoliveira wrote:
> > Andrea Aime wrote:
> >> Justin Deoliveira ha scritto:
> >>> Hi all,
> >>>
> >>> Here is the official proposal for moving the rest module
> to a core
> >>> module.
> >>>
> >>> http://geoserver.org/display/GEOS/GSIP+32+-+REST+support
> +module
> >>>
> >>> Feedback welcome.
> >> The documentation page is leaving me with some doubts.
> Like, for
> >> example, the role of a finder in our implementation. Do we
> have any?
> >
> > The docs are a bit basic at this point. They need some work.
> I will
> > expand on them. But essentially the finder is used to map
> different
> > classes of resources, to a single url. And that is just my
> practical
> > understanding... David probably has better insight since he
> knows
> > restlet better than I.
> >> The example does not show how to deal with output formats
> other
> >> than plain text. Is this still working based on maps, or
> based
> >> on reflection?
> > Yeah, the example there is based on the most simple thing
> one can do.
> > Again, I will expand on the docs but essentially there are
> subclasses of
> > AbstractResource: MapResource, and ReflectiveResource, which
> can do some
> > automatic serialization for you in json and xml. My plan was
> to add
> > three tutorials... 1) the very basic 2) the map approach 3)
> the
> > reflection approach
> >> It would also be nice to see some javadocs, probably they
> would
> >> answer the above questions.
> >
> > Added a link from the proposal. But they are available here:
> >
> > http://gridlock.openplans.org/rest/apidocs/
> >> Cheers
> >> Andrea
> >>
> >
> >
>
>
> --
> Justin Deoliveira
> OpenGeo - http://opengeo.org
> Enterprise support for open source geospatial.
>
>
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with
> Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing
> skills and code to
> build responsive, highly engaging applications that combine
> the power of local
> resources and data with the reach of the web. Download the
> Adobe AIR SDK and
> Ajax docs to start building applications
> today-http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
>
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with
> Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills and
> code to
> build responsive, highly engaging applications that combine the power of
> local
> resources and data with the reach of the web. Download the Adobe AIR SDK
> and
> Ajax docs to start building applications
> today-http://p.sf.net/sfu/adobe-com
> _______________________________________________ Geoserver-devel mailing
> list Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with
Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code
to
build responsive, highly engaging applications that combine the power of
local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Justin Deoliveira ha scritto:
I added two sections to the developer documentation. One is an example of how to build a service/resource with the map based approach. The other is how to build a service/resource with the reflection based approach. Here is the link again:
Sorry for the late feedback. Docs look very nice now 
+1 on the proposal for me
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.