Antoine Sabot-Durand this is interesting cause your point can be taken both ways mainly cause weld and OWB for historical reasons didn't take the same path on that topic. So you have app servers in both "camps". So concretely I think the outcome is that the spec doesnt cover startup expectations there and therefore the behavior is not portable (but still valid) and therefore 2.1 (or "2.0 +1 ") should clarify it and probably enable to implement it this way to not break tons of applications and keep the goodness several users like (strong startup validations). I'm not sure how to treat this test since I get the fact the spec writes that if the validation is not done at startup it should behave this way but if the validation is done at startup the test can't pass in its current form. |