Embedded must have it's own codebase. It should not reside in AS trunk. This will allow it to have an independent release/life cycles. Thus it won't be released with active snapshots (1), we can continue development post AS release (2) and it won't fall on it's ass when major refactoring takes place (3). 1: See JBoss Embedded Beta2 release 2: See Embedded EJB 3 RCs 3: See Embedded EJB 3 RC 9 It should then become apparent what it takes for AS to be a component in a consuming product. (and thus defining the EAP roadmap) As for what tests should be in AS codebase: all the SPI requirements put down by Bill (under Refactoring) must be tested before AS is delivered. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106254#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...