Closed kubamarchwicki closed 10 years ago
Keep the tests #JavaEE7 compatible, with minimal code. This will also show the recommended design patterns. Feel free to clean up redundant beans.xml.
There are some samples that would clearly run fine on JavaEE6 and you can consider creating a new profile and specifying them there. OK ?
Fair enough. I'll add a profile and check some obvious examples.
Are we aiming to keep the configuration minimal and be as JEE7 compliant as possible? I'm thinking about beans.xml for example. In some of the cases it's not required at all (though in some cases
.addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml");
is used (due to either issues or commiter's habbits)I was thinking about running these tests against Apache TomEE. The server is not yet JEE7 compliant, but some of the test should work (stateless, stateful, async ejbs, websockets) when beans.xml is included. Worth an effort or shall we keep it as JEE7 pure as possible? @arun-gupta what was the original idea?