Hi all,
Looking at adapting the kml reflector to the new dispatcher I notice that it overrides most of the logic in the old dispatcher. It uses the same workflow of service -> kvp request reader -> request object -> response but seems to do it on its own.
Question is was this done intentionally, or we can tie it up to the dispatcher like the other operations are.
-Justin
--
Justin Deoliveira
jdeolive@anonymised.com
The Open Planning Project
http://topp.openplans.org
We can tie it up. It just has to fill in some blanks for the user and look up some information.
Brent Owens
(The Open Planning Project)
Justin Deoliveira wrote:
Hi all,
Looking at adapting the kml reflector to the new dispatcher I notice that it overrides most of the logic in the old dispatcher. It uses the same workflow of service -> kvp request reader -> request object -> response but seems to do it on its own.
Question is was this done intentionally, or we can tie it up to the dispatcher like the other operations are.
-Justin