Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the relation between web.xml and jboss-web.xml? Seems like:
I don’t understand what happens when jboss-web.xml specifies a weak security domain. Ie: one that cannot do what web.xml specifies. What happens then?
To answer your general question, web.xml is the standard J2EE configuration file and is server-agnostic and its configurations will work with any J2EE compliant application server.
jboss-web.xml are JBoss specific extensions and abilities that exist only in JBoss (that is, another application server from another vendor may do that function, but it configures it differently). login-config.xml is also jboss specific, which is why you need a vendor specific configuration to tie the war and the login together.
I don’t know if it is possible to have a configuration problem other than the JBoss security being too lax, but if there is a serious misconfiguration, I would expect JBoss to throw an error on deployment and fail to deploy the war.