Hi,
We documented the Sample Plugin helloapp http://docs.codehaus.org/display/GEOSDEV/3+Bundling+your+Plugin,
Issues I need to sort out.
* To Run Hello Application: The link is incorrect, I need hello to
compile before my helloapp will grab the appropriate jar to place
into war.
* Setup: Where does this application sit, I am under the impression
this can sit anywhere on the file system but there is a parent in
the community pom, so that would mean that this application needs
to be inside community?
* Otherwise please review and let me know what you think
http://docs.codehaus.org/display/GEOSDEV/3+Bundling+your+Plugin
--
Kind Regards
Clint Lewis
Clint Lewis ha scritto:
Hi,
We documented the Sample Plugin helloapp http://docs.codehaus.org/display/GEOSDEV/3+Bundling+your+Plugin,
Issues I need to sort out.
* To Run Hello Application: The link is incorrect, I need hello to
compile before my helloapp will grab the appropriate jar to place
into war.
* Setup: Where does this application sit, I am under the impression
this can sit anywhere on the file system but there is a parent in
the community pom, so that would mean that this application needs
to be inside community?
* Otherwise please review and let me know what you think
http://docs.codehaus.org/display/GEOSDEV/3+Bundling+your+Plugin
Ah, I'm disappointed. I hoped that it would have been possible to
avoid modifying the web part just to add a new service, just have a single
dispatcher class mapped on http://locahost:8080/geoserver/serv that forward
requests to the actual executors:
http://locahost:8080/geoserver/serv/wfs/… -> wfs service
http://locahost:8080/geoserver/serv/wms/… -> wms service
http://locahost:8080/geoserver/serv/hello/… -> hello service
Is there any technical or timing related problem that prevents this kind of
solution?
Cheers
Andrea
Andrea Aime wrote:
Clint Lewis ha scritto:
Hi,
We documented the Sample Plugin helloapp http://docs.codehaus.org/display/GEOSDEV/3+Bundling+your+Plugin,
Issues I need to sort out.
* To Run Hello Application: The link is incorrect, I need hello to
compile before my helloapp will grab the appropriate jar to place
into war.
* Setup: Where does this application sit, I am under the impression
this can sit anywhere on the file system but there is a parent in
the community pom, so that would mean that this application needs
to be inside community?
* Otherwise please review and let me know what you think
http://docs.codehaus.org/display/GEOSDEV/3+Bundling+your+Plugin
Ah, I'm disappointed. I hoped that it would have been possible to
avoid modifying the web part just to add a new service, just have a single
dispatcher class mapped on http://locahost:8080/geoserver/serv that forward
requests to the actual executors:
This is a different use case then just adding a new service. The actual target in this example is to create a new application (ie, not geoserver), which is made out of geoserver components. Analogous to creating your own Rich Client Platform with Eclipse.
http://locahost:8080/geoserver/serv/wfs/… -> wfs service
http://locahost:8080/geoserver/serv/wms/… -> wms service
http://locahost:8080/geoserver/serv/hello/… -> hello service
Is there any technical or timing related problem that prevents this kind of
solution?
Nope, and its already done.
Cheers
Andrea
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:1004,44893cad14041336712104!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Andrea Aime wrote:
Clint Lewis ha scritto:
Hi,
We documented the Sample Plugin helloapp http://docs.codehaus.org/display/GEOSDEV/3+Bundling+your+Plugin,
Issues I need to sort out.
* To Run Hello Application: The link is incorrect, I need hello to
compile before my helloapp will grab the appropriate jar to place
into war.
* Setup: Where does this application sit, I am under the impression
this can sit anywhere on the file system but there is a parent in
the community pom, so that would mean that this application needs
to be inside community?
* Otherwise please review and let me know what you think
http://docs.codehaus.org/display/GEOSDEV/3+Bundling+your+Plugin
Ah, I'm disappointed. I hoped that it would have been possible to
avoid modifying the web part just to add a new service, just have a single
dispatcher class mapped on http://locahost:8080/geoserver/serv that forward
requests to the actual executors:
http://locahost:8080/geoserver/serv/wfs/… -> wfs service
http://locahost:8080/geoserver/serv/wms/… -> wms service
http://locahost:8080/geoserver/serv/hello/… -> hello service
Is there any technical or timing related problem that prevents this kind of
solution?
Hey Andrea, I think there was a small problem tripping over the "config" system. For actual normal OWS use
it would be nice to have:
- http://localhost:8080/geoserver?SERVICE=WFS&VERSION=1.0&…
- http://localhost:8080/geoserver?SERVICE=WMS&VERSION=1.0&…
- http://localhost:8080/geoserver?SERVICE=HELLO&VERSION=1.0&…
Aka a single entry point ...
For 1.4.M2 we should do a formal code review and figure out how to separate the "GeoServer Platform" into a LGPL
module that can be used to back uDig "Issues Module" and provide a "Configuration Module" for both uDig and other
GeoServer modules.
Those two examples would probably want to use spring remoting rather then OWS dispatch - making this more of
a "build time" platform rather then "run time" platform.
Perhaps next GeoServer meeting we can do a formal review? Note I missed talking about meeting times at the last
IRC meeting (we were out of time). It seems that Brent is back in North America and has no interest in keeping
the 7am morning slot going. With Brent running the 9pm we can expect it to be limited to an hour.
So meeting times are kind of your call, we can move the morning meeting back a couple of hours and then Brent
can pick up our agenda? Either that or we stay up late.
Jody
Jody Garnett ha scritto:
Andrea Aime wrote:
Hey Andrea, I think there was a small problem tripping over the "config" system. For actual normal OWS use
it would be nice to have:
- http://localhost:8080/geoserver?SERVICE=WFS&VERSION=1.0&…
- http://localhost:8080/geoserver?SERVICE=WMS&VERSION=1.0&…
- http://localhost:8080/geoserver?SERVICE=HELLO&VERSION=1.0&…
Aka a single entry point ...
For 1.4.M2 we should do a formal code review and figure out how to separate the "GeoServer Platform" into a LGPL
module that can be used to back uDig "Issues Module" and provide a "Configuration Module" for both uDig and other
GeoServer modules.
Cool
Those two examples would probably want to use spring remoting rather then OWS dispatch - making this more of
a "build time" platform rather then "run time" platform.
Yes, for sure.
Perhaps next GeoServer meeting we can do a formal review? Note I missed talking about meeting times at the last
IRC meeting (we were out of time). It seems that Brent is back in North America and has no interest in keeping
the 7am morning slot going. With Brent running the 9pm we can expect it to be limited to an hour.
So meeting times are kind of your call, we can move the morning meeting back a couple of hours and then Brent
can pick up our agenda? Either that or we stay up late.
I don't have problem with the late meeting time, it's the day: on Tuesday
and Thursday I'm busy during the evening, every week (tennis course).
But yeah, I can participate to the morning meeting if it falls at 9.00am
in my timezone.
Cheers
Andrea
Justin Deoliveira ha scritto:
...
This is a different use case then just adding a new service. The actual target in this example is to create a new application (ie, not geoserver), which is made out of geoserver components. Analogous to creating your own Rich Client Platform with Eclipse.
http://locahost:8080/geoserver/serv/wfs/… -> wfs service
http://locahost:8080/geoserver/serv/wms/… -> wms service
http://locahost:8080/geoserver/serv/hello/… -> hello service
Is there any technical or timing related problem that prevents this kind of
solution?
Nope, and its already done.
Cool, and sorry for complaining then. I did not understand the aim was
to reuse the geoserver modules in a different application.
Cheers
Andrea