[
https://issues.apache.org/jira/browse/ATLAS-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342714#comment-17342714
]
ASF subversion and git services commented on ATLAS-4183:
--------------------------------------------------------
Commit 97689b34df747a8ce2a6a6d141340970d746ecbf in atlas's branch
refs/heads/branch-2.0 from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=97689b3 ]
ATLAS-4183: Upgrade deployment descriptor for webapp project
Signed-off-by: Sarath Subramanian <[email protected]>
(cherry picked from commit c5ad5810856e465efa0cbb2d33c1614d52ff3b00)
> web.xml requires external dtd resource
> --------------------------------------
>
> Key: ATLAS-4183
> URL: https://issues.apache.org/jira/browse/ATLAS-4183
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 2.1.0
> Reporter: Deep Singh
> Assignee: Deep Singh
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> We have Servlet 2.3 deployment descriptor (web.xml), which follows J2EE 1.3
> DTDs schema.
> Therefore it requires dtd resource hosted at
> http://java.sun.com/dtd/web-app_2_3.dtd
> In setups that are behind firewalls with limited access to external
> resources, the Atlas server fails to come up without the external dtd
> resource.
> This can be fixed by hosting dtd resource locally or upgrading the deployment
> descriptor.
> We can upgrade it to Servlet 2.5 deployment descriptor which is Java EE 5 XML
> schema and it does not require external dtd resource for validation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
