TomEE is behaving unexpectedly when handling env-entry elements in a web.xml/web-fragment.xml along with a context.xml containing Environment elements. TomEE acts correctly if env-entry-value elements are present, but if they are left out and delegated to the context.xml TomEE does not always pickup the value. I've attached a test case below which should reproduce this easily. I have run the test cases in the latest snapshot (apache-tomee-1.6.0-20130805.041250-144-webprofile) and the issue is present.
Cases working web.xml (w/o env-entry-value) + context.xml (w/Environment) web.xml (w/ env-entry-value) (no web.xml) web-fragment.xml (w/ env-entry-value) Not Working (no web.xml) web-fragment.xml (w/o env-entry-value) + context.xml (w/Environment) web.xml (w/o env-entry-value) + web-fragment.xml (w/o env-entry-value) + context.xml (w/Environment) Test case: https://www.dropbox.com/s/oh53kq4nn4q294y/enventry-override.zip Thanks, Trevor Stevens [email protected]
