If a Forge class needs to work with web.xml, then the best way to do that is via the classes in the org.jboss.shrinkwrap.descriptor.api.webapp* packages coming from the org.jboss.forge.descriptors:javaee-descriptors-api artifact.

There is one Servlet spec independent package there org.jboss.shrinkwrap.descriptor.api.webapp and few others for every other version of the speck: org.jboss.shrinkwrap.descriptor.api.webapp25, org.jboss.shrinkwrap.descriptor.api.webapp30 and org.jboss.shrinkwrap.descriptor.api.webapp31. The thing is that the common package does not provide much capabilities and the users of this API should go to the release specific classes. Which leads to a lot of code duplication and defining otherwise common abstractions (like a security constraint for example) in the client code instead of using the one from the API.

The purpose of this task is to come up with a proposal and finally implement a refactoring of the API so that much more functionality is abstracted away from the webappXX packages into the common one