I'm sure the fellows working on the WPS module are curious why it didn't
meet your needs. In the long term, a WPS based on the OWS dispatcher
system is probably the only implementation that will make it into
officially supported status, so you might want to look into helping out
with that effort instead of tacking an independent servlet onto GeoServer.
That said, the printing community module does very little aside from
wrapping a plain servlet so that it can hook into Spring; you may find
it a useful example:
http://svn.codehaus.org/geoserver/trunk/src/community/printing/
There currently needs to be a mapping added to web.xml for such mappings
to apply, however.
Hope this helps.
--
David Winslow
OpenGeo - http://opengeo.org/
On 12/22/2009 08:48 AM, maven apache wrote:
Hi:
We have implemented a WPS instance, and now we want to integrate it to
gs to replace the wps under the community module of geoserver
2.0.0(for easily written, I call it gs-wps).
The problem is that our wps have a different architecture with the
gs-wps. I found the other ows such as wcs wms and wfs all have some
common struts: the kvp-parser, response and so on. Also they all
communicate with spring. And each operation of a ows will be built as
a java object for example the
“org.vfny.geoserver.wms.servlets.DescribeLayer” in the wms and so on.
However in our wps there is only a WPSServlet acted as a front
controller which receive the httpservletrequest and
httpservletResponse as parameters. No matter which kind of request is
received (getCapabilities or DescribeProcess) , they are all handled
by the front controller
So I do not know how to dispatch the request from the client to the
WPSServlet and do some initialization work.
I have seen the gs sources for a long time ,but I have no idea because
of my unfamiliar with the spring.
I also referred to the hello plugin at
http://geoserver.org/display/GEOSDOC/3+A+Simple+PlugIn
But it seems that it does not work.
I hope someone can give me some further advise.
Sorry to bother you.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel