Implement support for nested EJBs & WARs in .sar archives

<opalka> dmlloyd, please review - https://github.com/ropalka/jboss-as/tree/sar-nested-archives-support
<dmlloyd> SAR nested archives, eh? not sure I like the sound of that
<opalka> dmlloyd, I'm not sure too
<dmlloyd> what is the motivation and what are the semantics?
<opalka> dmlloyd, we have some legacy tests
<opalka> dmlloyd, and I know that TX team uses .sar archives with nested WS JSE endpoints in it
<opalka> dmlloyd, The tests we have simply include EJB & WAR WS endpoints
<opalka> dmlloyd, in bundled separate archives inside .sar
<dmlloyd> Nihility: what do you think
<opalka> dmlloyd, If we're not going to support it it's fine with me too. But in such case I'd create JBAS jira and we'll mark it as won't fix and I'll exclude the tests with reference to that JIRA
<dmlloyd> my concern is that right now all of our nested deployment code assumes the outer deployment is an EAR
<opalka> dmlloyd, yes I know. In the past there used to be some problems with SAR
<opalka> dmlloyd, for example JNDI doesn't work in web archives bundled in .sar in AS6
<opalka> dmlloyd, maybe U can see some issues here in AS7 too?
<opalka> s/some/similar/
<opalka> dmlloyd, BTW, why do we have support for .sar archives? Was it really required/necessary?
<Nihility> i have no problem with allowing sars to be nested children, as it doesnt really mean much but as deployments that contain children i think we need to discourage that
<dmlloyd> opalka, basically we have SARs for compatibility purposes only. I'm not really that happy that we support them myself
<opalka> Nihility, dmlloyd OK, I'll create feature request JBAS JIRA - implement support for nested EJBs & WARs in .sar archives and will mark it as rejected/won't fix ?
<dmlloyd> yeah I think that's the thing to do, opalka.