Pavan
it doesn't help to post the same question twice. Anyhow, to answer your question again - the order of elements doesn't matter in a 2.4 descriptor. You can verify this for yourself by reading the documentation contained in the Schema definition itself, which you can find at:
web-app_2_4.xsd But to give you the relevant extract:
The web-app element is the root of the deployment
descriptor for a web application. Note that the sub-elements
of this element can be in the arbitrary order. Because of
that, the multiplicity of the elements of distributable,
session-config, welcome-file-list, jsp-config, login-config,
and locale-encoding-mapping-list was changed from "?" to "*"
in this schema. However, the deployment descriptor instance
file must not contain multiple elements of session-config,
jsp-config, and login-config. When there are multiple elements of
welcome-file-list or locale-encoding-mapping-list, the container
must concatinate the element contents. The multiple occurance
of the element distributable is redundant and the container
treats that case exactly in the same way when there is only
one distributable.
As I mentioned previously, for the 2.3 descriptor, order
was important, and there are still lots of mock questions floating around which are based on the 2.3 spec.
Hope that helps.
