Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
If the web.xml that the plugin is altering already contains a servlet and/or servlet-mapping element that looks very much like the ones it is adding it should either fail or at least generate a warning. I know that having the pluto-generated config in the web.xml of the portlet to be "plutofied" by the plugin is wrong, but if the plugin makes web.xml invalid because that info already exists, it seems like it should check for it. Please ignore this if it is an invalid request, but I remembered that it worked this way, it caused problems for at least a few people developing portlets for uPortal over the past 2 years reported on the JASIG uportal-user/portlet-dev lists, and Eric Dalquist just mentioned that perhaps this would be a good place to mention it also since uPortal now uses this plugin. Thanks, guys!