Enhancement #76
Default Service Mapping
| Status: | Closed | Start date: | 06/14/2010 | |
|---|---|---|---|---|
| Priority: | Urgente | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
For now for each service to be available we need to write an entry in the kow_view_mappings service. This is error prone and thanks to the array syntax in the KOW Config it is quite hard to maintain.
Each component could implement two things:- a factory for default services (will me explained in a bit)
- the current factory for named services
- when accessing /component_name the factory for default service is called. This factory would have a default implementation which shows a 404 (not found) error page (other solution is to have a default service variable in every service, which in turn would make the framework easier to use).
- when acessing /component_name.service_name (the syntax for this should be discussed) it would then call the service service_name from the component component_name, using the already existent component.
This would easy the development of new services and maintenance of the existing projects (and would also make all services available out of the box as soon as the application is loaded into new projects).
History
Updated by Marcelo Coraça de Freitas about 1 year ago
- Status changed from New to Accepted
Finally I'll be working on this one. :)
Updated by Marcelo Coraça de Freitas about 1 year ago
I'm designin this (and other changes) at Refactoring
Updated by Marcelo Coraça de Freitas 12 months ago
- Status changed from Accepted to Fixed
done last december...
well tested now :)
Updated by Marcelo Coraça de Freitas 12 months ago
- Status changed from Fixed to Closed