Together with the code review in JBAS-7500 regarding the 6.0.0.M1/trunk differences, I think it's a good time to remove any dead code, components rarely used, and other things that we want to remove from AS 6 going forward. https://jira.jboss.org/jira/browse/JBAS-7508 Things that come to my mind: - web-console - aop aspects??? - misc varia stuff - jmx remoting impl (there is now the jdk one) - ... add your own

Brian Stansberry wrote: > On 12/04/2009 02:11 AM, Dimitris Andreadis wrote: >> Together with the code review in JBAS-7500 regarding the 6.0.0.M1/trunk differences, I think >> it's a good time to remove any dead code, components rarely used, and other things that we >> want to remove from AS 6 going forward. >> >> https://jira.jboss.org/jira/browse/JBAS-7508 >> >> Things that come to my mind: >> - web-console >> - aop aspects??? >> - misc varia stuff >> - jmx remoting impl (there is now the jdk one) >> - ... add your own >> >> > > JRMPInvoker? > PooledInvoker? Aren't those needed for the old ejb2.x implementation?

_______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Brian Stansberry wrote: > On 12/04/2009 02:11 AM, Dimitris Andreadis wrote: >> Together with the code review in JBAS-7500 regarding the 6.0.0.M1/trunk differences, I think >> it's a good time to remove any dead code, components rarely used, and other things that we >> want to remove from AS 6 going forward. >> >> https://jira.jboss.org/jira/browse/JBAS-7508 >> >> Things that come to my mind: >> - web-console >> - aop aspects??? >> - misc varia stuff >> - jmx remoting impl (there is now the jdk one) >> - ... add your own >> >> > JRMPInvoker? > PooledInvoker? Aren't those needed for the old ejb2.x implementation?

On 12/07/2009 04:47 PM, Alexey Loubyansky wrote: > Dimitris Andreadis wrote: > >> Brian Stansberry wrote: >> >>> On 12/04/2009 02:11 AM, Dimitris Andreadis wrote: >>> >>>> Together with the code review in JBAS-7500 regarding the >>>> 6.0.0.M1/trunk differences, I think >>>> it's a good time to remove any dead code, components rarely used, >>>> and other things that we >>>> want to remove from AS 6 going forward. >>>> >>>> https://jira.jboss.org/jira/browse/JBAS-7508 >>>> >>>> Things that come to my mind: >>>> - web-console >>>> - aop aspects??? >>>> - misc varia stuff >>>> - jmx remoting impl (there is now the jdk one) >>>> - ... add your own >>>> >>>> >>>> >>> JRMPInvoker? >>> PooledInvoker? >>> >> Aren't those needed for the old ejb2.x implementation? >> > - ejb2.x implementation > We actually need that to pass certification. :-) BMP/CMP is delegated to the old containers. On a positive note this is deprecated in the spec itself. I was thinking that maybe we should disable it out of the box for the community version. Carlo

Carlo de Wolf wrote: > On 12/07/2009 04:47 PM, Alexey Loubyansky wrote: >> Dimitris Andreadis wrote: >> >>> Brian Stansberry wrote: >>> >>>> On 12/04/2009 02:11 AM, Dimitris Andreadis wrote: >>>> >>>>> Together with the code review in JBAS-7500 regarding the 6.0.0.M1/trunk differences, I think >>>>> it's a good time to remove any dead code, components rarely used, and other things that we >>>>> want to remove from AS 6 going forward. >>>>> >>>>> https://jira.jboss.org/jira/browse/JBAS-7508 >>>>> >>>>> Things that come to my mind: >>>>> - web-console >>>>> - aop aspects??? >>>>> - misc varia stuff >>>>> - jmx remoting impl (there is now the jdk one) >>>>> - ... add your own >>>>> >>>>> >>>>> >>>> JRMPInvoker? >>>> PooledInvoker? >>>> >>> Aren't those needed for the old ejb2.x implementation? >>> >> - ejb2.x implementation >> > We actually need that to pass certification. :-) > BMP/CMP is delegated to the old containers. > > On a positive note this is deprecated in the spec itself. I was thinking > that maybe we should disable it out of the box for the community version. > Right, we should disable all of the legacy stuff like this for our default config.

Together with the code review in JBAS-7500 regarding the 6.0.0.M1/trunk differences, I think it's a good time to remove any dead code, components rarely used, and other things that we want to remove from AS 6 going forward. https://jira.jboss.org/jira/browse/JBAS-7508 Things that come to my mind: - web-console - aop aspects??? - misc varia stuff - jmx remoting impl (there is now the jdk one) - ... add your own

> It was my impression that the use of > org.jboss.system.ServiceMBeanSupport was discouraged in AS5 in favor of > pojos w/JMX annotations. Are there any plans to officially deprecate > ServiceMBeanSupport in AS6 to further encourage the migration of > existing mbeans (there are several dozen subclasses) to the more loosely > coupled pojo model? If it's not yet officially deprecated, it should be. Once I'm done with this: * http://lists.jboss.org/pipermail/jboss-development/2009-December/015142.html I'll have a closer look on what we can/should do with those existing mbeans. But it will definitely require a joined effort to be completely off mbeans - hence making JMX usage optional as we always promised.

My guess is we still have mbeans for admin and notification purposes? The first one should be replaced with EmbeddedJopr ops, the 2nd one with proper MC's dependencies.