[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] 3.0 plan update
- From: Glyn Normington <gnormington@xxxxxxxxxx>
- Date: Fri, 11 Mar 2011 09:31:11 +0000
- Delivered-to: email@example.com
I'm not sure if Spring DM -> blueprint will cause any JMX changes, but other features have already added more mxbeans.
Depending on how the Virgo tooling donation goes, we may change the deployer related mxbeans too.
In general, we would only disturb current JMX interfaces for good reasons.
On 10 Mar 2011, at 18:44, Dan Tran wrote:
> is there any JMX interface changes due to feature upgrade ( spring-dm
> --> blueprint )??
> On Thu, Mar 10, 2011 at 10:16 AM, Wolfgang Schell <lists@xxxxxxxxxxxxx> wrote:
>> Hi Glyn,
>> how about bug 335689 "Support a deployment type which is a hybrid of both
>> PLAN and PAR" ? I would really like to see this feature in 3.0 if time
>>  https://bugs.eclipse.org/bugs/show_bug.cgi?id=335689
>> Am 10.03.11 15:32, schrieb Glyn Normington:
>>> After a user on the forums pointed at the 3.0 plan  I had a look
>>> through it and marked a couple of items as unlikely to fit in the plan:
>>> * Admin console administration of remote Virgo instances (unlikely
>>> to fit in the 3.0 plan)
>>> * Multiple user regions (unlikely to fit in the 3.0 plan)
>>> If anyone disagrees, please let me know and we can discuss.
>>>  http://wiki.eclipse.org/Virgo/Future#3.0.0_Release
>>> virgo-dev mailing list
>> virgo-dev mailing list
> virgo-dev mailing list