[jboss-dev] Remove unused components from trunk
Brian Stansberry
brian.stansberry at redhat.com
Thu Dec 17 16:02:30 EST 2009
On 12/07/2009 11:06 AM, Jason T. Greene wrote:
> 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.
>
For EJB2: https://jira.jboss.org/jira/browse/JBAS-7562
That JIRA's for removal from 'default', i.e. it remains in 'standard'
and 'all'. The testsuite mostly uses 'all' so hopefully the testsuite
implications will be minor.
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat
More information about the jboss-development
mailing list