[MAGNOLIA-5708] A way for Servlet to "self map" - so that mapping can be shared with other components Created: 12/Mar/14  Updated: 10/Mar/15  Resolved: 12/Mar/14

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 5.3

Type: New Feature Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: architecture
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLDAM-409 Links - DamDownloadServlet, Imaging Closed
dependency
is depended upon by MGNLIMG-81 Provide link generator Closed
Template:
Acceptance criteria:
Empty
Release notes required:
Yes
Epic Link: DAM / CMIS
Sprint: 5.3 Sprint 3, 5.3 Sprint 4

 Description   

Currently, the mapping of a servlet is configured under the ServletWrappingFilter's mappings node. This works nicely when integrating third-party filter, and is a good reflection of how one typically maps servlet in web.xml.
However, with Magnolia's IoC and configuration mechanisms, one would tend to think that this mapping shouldn't be hardcoded anywhere. It currently has to - say, if some other components needs to generate links to a servlet, it needs to know where/how the servlet is mapped, and that generally ends up with either a hardcoded path, or a duplicate configuration.

Here's a mechanism that will let Servlet declare their own mapping (i.e. if they implement SelfMappingServlet), so that the mapping can be configured centrally (i.e in MyModule, i.e /modules/mymod/configuration) and used in multiple places.

http://wiki.magnolia-cms.com/display/DEV/Concept+Dynamic+Servlet+Mapping


Generated at Mon Feb 12 04:07:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.