[
https://issues.apache.org/jira/browse/ISIS-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597100#comment-16597100
]
Andi Huber commented on ISIS-1895:
----------------------------------
Setting up the ServletContext requires some configuration values, prior to the
Isis framework being bootstrapped (currently by google's Guice). Among others
these are:
* URL-Mapping for Wicket
* Deployment type for Wicket
* WebApplication's class-name for Wicket
* URL Mapping for the Rest API
One obvious interim solution is to again use the web.xml deployment descriptor
and place those config values there (using context-parameters).
But certainly we want a single configuration infrastructure for Isis, not
spreading out config values all over the place.
So I'm still looking for a solution to this issue.
*Any comments appreciated!*
> Remove the need for deployment descriptors (web.xml)
> ----------------------------------------------------
>
> Key: ISIS-1895
> URL: https://issues.apache.org/jira/browse/ISIS-1895
> Project: Isis
> Issue Type: Improvement
> Components: Core, Core Plugins
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-M2
>
>
> Instead of having users configure filters, listeners and servlets within
> their web.xml files, we'd rather provide a programmatic approach to setting
> up the ServletContext.
> We introduce a new interface WebModule, that encapsulates the configuration
> required for a set of filters, listeners and servlets.
> We also introduce a new WebContextLister that acts as the single
> web-Application entry-point for setting up the ServletContext using these new
> WebModules.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
