You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@marmotta.apache.org by "Sergio Fernández (JIRA)" <ji...@apache.org> on 2013/10/11 20:28:42 UTC
[jira] [Commented] (MARMOTTA-196) Find a modular way to update
web.xml
[ https://issues.apache.org/jira/browse/MARMOTTA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792918#comment-13792918 ]
Sergio Fernández commented on MARMOTTA-196:
-------------------------------------------
Since we upgraded to Servlet API 3.0 (see MARMOTTA-224), w could move all the possoble things from the web.xml to annotations directly in the code.
Good article talking about this: http://www.javacodegeeks.com/2012/12/checking-out-what-is-new-with-servlet-3-0.html
> Find a modular way to update web.xml
> ------------------------------------
>
> Key: MARMOTTA-196
> URL: https://issues.apache.org/jira/browse/MARMOTTA-196
> Project: Marmotta
> Issue Type: Improvement
> Components: Platform
> Affects Versions: 3.0-incubating
> Reporter: Sergio Fernández
> Assignee: Sergio Fernández
> Priority: Minor
> Fix For: 4.0
>
>
> MARMOTTA-195 shows how weak is Marmotta to changes on web.xml; i.e., every single change in the main web.xml needs to be properly updated on all the running webapps.
> I don't know a proper solution to this issue. But it is clear to me that we should find a way to modify the web.xml, on compile phase or whatever, but chnages cannot break already running systems.
--
This message was sent by Atlassian JIRA
(v6.1#6144)