In general the reason why the code resides with the EJB3 project is that WS just specifies
the requirements (a bunch of interfaces) and _initially_ implements it in the EJB3 code
base. Subsequent changes however should be implemented and verified (WS test suite) by the
EJB3 team.
Maybe I don't understand you correctly, but I still don't see a reason why any of
the upcoming changes, may it be deployment or injection should affect the API in place.
If you still see something missing please document the lacking features in terms of test
cases.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144180#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...