1:28 p.m.
Hello Everyone,
I am happy to announce a proposed roadmap for AS8. After some discussions with various AS
developers and community members, the goals we think are important are:
1. Java EE7
2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
3. Patching
4. Migration from JacORB to the JDK Orb
5. Transition to the new yet to be announced name
I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
May 7 - Release Alpha1
+ Includes undertow, some ee7
June 11 - Release Beta
+ more progress on EE7
July 11 - Release CR1
+ EE7 feature complete
July 25 - Release CR2 if needed
(Hopefully TCK 100% by this date)
August 8 - Release Final
As usual the August 8th date is conditional on the Java EE certification process.
I look forward to any and all feedback. Thanks!
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
1:40 p.m.
Hi Jason,
On 03/27/2013 01:28 PM, Jason Greene wrote:
I am happy to announce a proposed roadmap for AS8. After some
discussions with various AS developers and community members, the goals we think are
important are:
1. Java EE7
2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
3. Patching
4. Migration from JacORB to the JDK Orb
5. Transition to the new yet to be announced name
I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
May 7 - Release Alpha1
+ Includes undertow, some ee7
June 11 - Release Beta
+ more progress on EE7
July 11 - Release CR1
+ EE7 feature complete
July 25 - Release CR2 if needed
(Hopefully TCK 100% by this date)
August 8 - Release Final
As usual the August 8th date is conditional on the Java EE certification process.
I look forward to any and all feedback. Thanks!
Looks good, thanks !
I would suggest to move the June 11 date to June 7 instead, such that
the Beta release is out for JUDCon/Boston.
Best regards,
Jesper
1:09 p.m.
On Mar 27, 2013, at 12:40 PM, Jesper Pedersen <jesper.pedersen(a)jboss.org> wrote:
Hi Jason,
On 03/27/2013 01:28 PM, Jason Greene wrote:
> I am happy to announce a proposed roadmap for AS8. After some discussions with
various AS developers and community members, the goals we think are important are:
>
> 1. Java EE7
> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
> 3. Patching
> 4. Migration from JacORB to the JDK Orb
> 5. Transition to the new yet to be announced name
>
> I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
>
> May 7 - Release Alpha1
> + Includes undertow, some ee7
> June 11 - Release Beta
> + more progress on EE7
> July 11 - Release CR1
> + EE7 feature complete
> July 25 - Release CR2 if needed
> (Hopefully TCK 100% by this date)
> August 8 - Release Final
>
> As usual the August 8th date is conditional on the Java EE certification process.
>
> I look forward to any and all feedback. Thanks!
Looks good, thanks !
I would suggest to move the June 11 date to June 7 instead, such that
the Beta release is out for JUDCon/Boston.
Hmm. I would rather not release on a Friday (releases tend to go unnoticed), and I think
the schedule is pretty tight as it is.
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
6:57 p.m.
Can we get Versions in JIRA for all these* plus a 9.0.0.CR1 to track
main items for the next big dev cycle? I volunteer to do it. I'm itching
to get my big pile of issues properly sorted into buckets. :-)
* Well, not CR2 and Final which should only have stuff discovered after CR1
On 3/27/13 12:28 PM, Jason Greene wrote:
Hello Everyone,
I am happy to announce a proposed roadmap for AS8. After some discussions with various AS
developers and community members, the goals we think are important are:
1. Java EE7
2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
3. Patching
4. Migration from JacORB to the JDK Orb
5. Transition to the new yet to be announced name
I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
May 7 - Release Alpha1
+ Includes undertow, some ee7
June 11 - Release Beta
+ more progress on EE7
July 11 - Release CR1
+ EE7 feature complete
July 25 - Release CR2 if needed
(Hopefully TCK 100% by this date)
August 8 - Release Final
As usual the August 8th date is conditional on the Java EE certification process.
I look forward to any and all feedback. Thanks!
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
7:27 p.m.
Be my guest :)
Sent from my iPhone
On Mar 27, 2013, at 5:57 PM, Brian Stansberry <brian.stansberry(a)redhat.com> wrote:
Can we get Versions in JIRA for all these* plus a 9.0.0.CR1 to track
main items for the next big dev cycle? I volunteer to do it. I'm itching
to get my big pile of issues properly sorted into buckets. :-)
* Well, not CR2 and Final which should only have stuff discovered after CR1
On 3/27/13 12:28 PM, Jason Greene wrote:
> Hello Everyone,
>
> I am happy to announce a proposed roadmap for AS8. After some discussions with
various AS developers and community members, the goals we think are important are:
>
> 1. Java EE7
> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
> 3. Patching
> 4. Migration from JacORB to the JDK Orb
> 5. Transition to the new yet to be announced name
>
> I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
>
> May 7 - Release Alpha1
> + Includes undertow, some ee7
> June 11 - Release Beta
> + more progress on EE7
> July 11 - Release CR1
> + EE7 feature complete
> July 25 - Release CR2 if needed
> (Hopefully TCK 100% by this date)
> August 8 - Release Final
>
> As usual the August 8th date is conditional on the Java EE certification process.
>
> I look forward to any and all feedback. Thanks!
>
> --
> Jason T. Greene
> JBoss AS Lead / EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
8:42 p.m.
Done. I used the dates you provided below, although I think Jesper's
suggestion re June 7 and JUDCon makes sense.
On 3/27/13 6:27 PM, Jason Greene wrote:
Be my guest :)
Sent from my iPhone
On Mar 27, 2013, at 5:57 PM, Brian Stansberry <brian.stansberry(a)redhat.com> wrote:
> Can we get Versions in JIRA for all these* plus a 9.0.0.CR1 to track
> main items for the next big dev cycle? I volunteer to do it. I'm itching
> to get my big pile of issues properly sorted into buckets. :-)
>
> * Well, not CR2 and Final which should only have stuff discovered after CR1
>
> On 3/27/13 12:28 PM, Jason Greene wrote:
>> Hello Everyone,
>>
>> I am happy to announce a proposed roadmap for AS8. After some discussions with
various AS developers and community members, the goals we think are important are:
>>
>> 1. Java EE7
>> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
>> 3. Patching
>> 4. Migration from JacORB to the JDK Orb
>> 5. Transition to the new yet to be announced name
>>
>> I am proposing an agressive 6 month timeline for this release, with the following
key milestones:
>>
>> May 7 - Release Alpha1
>> + Includes undertow, some ee7
>> June 11 - Release Beta
>> + more progress on EE7
>> July 11 - Release CR1
>> + EE7 feature complete
>> July 25 - Release CR2 if needed
>> (Hopefully TCK 100% by this date)
>> August 8 - Release Final
>>
>> As usual the August 8th date is conditional on the Java EE certification
process.
>>
>> I look forward to any and all feedback. Thanks!
>>
>> --
>> Jason T. Greene
>> JBoss AS Lead / EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
> --
> Brian Stansberry
> Principal Software Engineer
> JBoss by Red Hat
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
2:29 a.m.
I agree, I'm sure a lot of subsystem devs are hoping to talk about features scheduled
for a component upgrade in AS Beta1.
It would be great to say in my (potential) talk, that you can use these features in the
latest AS release, rather than a recent AS snapshot.
Paul
On 28 Mar 2013, at 00:43, Brian Stansberry <brian.stansberry(a)redhat.com> wrote:
Done. I used the dates you provided below, although I think
Jesper's
suggestion re June 7 and JUDCon makes sense.
On 3/27/13 6:27 PM, Jason Greene wrote:
> Be my guest :)
>
> Sent from my iPhone
>
> On Mar 27, 2013, at 5:57 PM, Brian Stansberry <brian.stansberry(a)redhat.com>
wrote:
>
>> Can we get Versions in JIRA for all these* plus a 9.0.0.CR1 to track
>> main items for the next big dev cycle? I volunteer to do it. I'm itching
>> to get my big pile of issues properly sorted into buckets. :-)
>>
>> * Well, not CR2 and Final which should only have stuff discovered after CR1
>>
>> On 3/27/13 12:28 PM, Jason Greene wrote:
>>> Hello Everyone,
>>>
>>> I am happy to announce a proposed roadmap for AS8. After some discussions
with various AS developers and community members, the goals we think are important are:
>>>
>>> 1. Java EE7
>>> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
>>> 3. Patching
>>> 4. Migration from JacORB to the JDK Orb
>>> 5. Transition to the new yet to be announced name
>>>
>>> I am proposing an agressive 6 month timeline for this release, with the
following key milestones:
>>>
>>> May 7 - Release Alpha1
>>> + Includes undertow, some ee7
>>> June 11 - Release Beta
>>> + more progress on EE7
>>> July 11 - Release CR1
>>> + EE7 feature complete
>>> July 25 - Release CR2 if needed
>>> (Hopefully TCK 100% by this date)
>>> August 8 - Release Final
>>>
>>> As usual the August 8th date is conditional on the Java EE certification
process.
>>>
>>> I look forward to any and all feedback. Thanks!
>>>
>>> --
>>> Jason T. Greene
>>> JBoss AS Lead / EAP Platform Architect
>>> JBoss, a division of Red Hat
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>>
>> --
>> Brian Stansberry
>> Principal Software Engineer
>> JBoss by Red Hat
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
2:39 a.m.
The roadmap looks nice. I must say the Undertow project is very ambitious,
aside from performance I am sure it will bring AS-integration of the web
layer to a completely new level. From a user perspective it might be tricky
to find replacements for many -D switches that might disappear, many
applications probably also depend on vague spec implementations that just
happened to work for them. Are you trying to squeeze in the transactional
MSC also or is that for a later relase?
On Thu, Mar 28, 2013 at 8:29 AM, Paul Robinson <probinso(a)redhat.com> wrote:
I agree, I'm sure a lot of subsystem devs are hoping to talk
about
features scheduled for a component upgrade in AS Beta1.
It would be great to say in my (potential) talk, that you can use these
features in the latest AS release, rather than a recent AS snapshot.
Paul
On 28 Mar 2013, at 00:43, Brian Stansberry <brian.stansberry(a)redhat.com>
wrote:
> Done. I used the dates you provided below, although I think Jesper's
> suggestion re June 7 and JUDCon makes sense.
>
> On 3/27/13 6:27 PM, Jason Greene wrote:
>> Be my guest :)
>>
>> Sent from my iPhone
>>
>> On Mar 27, 2013, at 5:57 PM, Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
>>
>>> Can we get Versions in JIRA for all these* plus a 9.0.0.CR1 to track
>>> main items for the next big dev cycle? I volunteer to do it. I'm
itching
>>> to get my big pile of issues properly sorted into buckets. :-)
>>>
>>> * Well, not CR2 and Final which should only have stuff discovered
after CR1
>>>
>>> On 3/27/13 12:28 PM, Jason Greene wrote:
>>>> Hello Everyone,
>>>>
>>>> I am happy to announce a proposed roadmap for AS8. After some
discussions with various AS developers and community members, the goals we
think are important are:
>>>>
>>>> 1. Java EE7
>>>> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking
i/o)
>>>> 3. Patching
>>>> 4. Migration from JacORB to the JDK Orb
>>>> 5. Transition to the new yet to be announced name
>>>>
>>>> I am proposing an agressive 6 month timeline for this release, with
the following key milestones:
>>>>
>>>> May 7 - Release Alpha1
>>>> + Includes undertow, some ee7
>>>> June 11 - Release Beta
>>>> + more progress on EE7
>>>> July 11 - Release CR1
>>>> + EE7 feature complete
>>>> July 25 - Release CR2 if needed
>>>> (Hopefully TCK 100% by this date)
>>>> August 8 - Release Final
>>>>
>>>> As usual the August 8th date is conditional on the Java EE
certification process.
>>>>
>>>> I look forward to any and all feedback. Thanks!
>>>>
>>>> --
>>>> Jason T. Greene
>>>> JBoss AS Lead / EAP Platform Architect
>>>> JBoss, a division of Red Hat
>>>>
>>>>
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>>
>>> --
>>> Brian Stansberry
>>> Principal Software Engineer
>>> JBoss by Red Hat
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
> --
> Brian Stansberry
> Principal Software Engineer
> JBoss by Red Hat
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Nicklas Karlsson, +358 40 5062266
Vaakunatie 10 as 7, 20780 Kaarina
9:28 a.m.
Unfortunately transactional MSC won't make it in time for 8. We are
however making some good progress on it. I'm fairly optimistic it'll
make it in time for 9. This is the official email you can refer to in
the future to mock me if we miss. :)
On 03/28/2013 01:39 AM, Nicklas Karlsson wrote:
The roadmap looks nice. I must say the Undertow project is very
ambitious, aside from performance I am sure it will bring AS-integration
of the web layer to a completely new level. From a user perspective it
might be tricky to find replacements for many -D switches that might
disappear, many applications probably also depend on vague spec
implementations that just happened to work for them. Are you trying to
squeeze in the transactional MSC also or is that for a later relase?
On Thu, Mar 28, 2013 at 8:29 AM, Paul Robinson <probinso(a)redhat.com
<mailto:probinso@redhat.com>> wrote:
I agree, I'm sure a lot of subsystem devs are hoping to talk about
features scheduled for a component upgrade in AS Beta1.
It would be great to say in my (potential) talk, that you can use
these features in the latest AS release, rather than a recent AS
snapshot.
Paul
On 28 Mar 2013, at 00:43, Brian Stansberry
<brian.stansberry(a)redhat.com <mailto:brian.stansberry@redhat.com>>
wrote:
> Done. I used the dates you provided below, although I think Jesper's
> suggestion re June 7 and JUDCon makes sense.
>
> On 3/27/13 6:27 PM, Jason Greene wrote:
>> Be my guest :)
>>
>> Sent from my iPhone
>>
>> On Mar 27, 2013, at 5:57 PM, Brian Stansberry
<brian.stansberry(a)redhat.com <mailto:brian.stansberry@redhat.com>>
wrote:
>>
>>> Can we get Versions in JIRA for all these* plus a 9.0.0.CR1 to
track
>>> main items for the next big dev cycle? I volunteer to do it.
I'm itching
>>> to get my big pile of issues properly sorted into buckets. :-)
>>>
>>> * Well, not CR2 and Final which should only have stuff
discovered after CR1
>>>
>>> On 3/27/13 12:28 PM, Jason Greene wrote:
>>>> Hello Everyone,
>>>>
>>>> I am happy to announce a proposed roadmap for AS8. After some
discussions with various AS developers and community members, the
goals we think are important are:
>>>>
>>>> 1. Java EE7
>>>> 2. Integration of Undertow (EE7 Web Sockets + performant
non-blocking i/o)
>>>> 3. Patching
>>>> 4. Migration from JacORB to the JDK Orb
>>>> 5. Transition to the new yet to be announced name
>>>>
>>>> I am proposing an agressive 6 month timeline for this release,
with the following key milestones:
>>>>
>>>> May 7 - Release Alpha1
>>>> + Includes undertow, some ee7
>>>> June 11 - Release Beta
>>>> + more progress on EE7
>>>> July 11 - Release CR1
>>>> + EE7 feature complete
>>>> July 25 - Release CR2 if needed
>>>> (Hopefully TCK 100% by this date)
>>>> August 8 - Release Final
>>>>
>>>> As usual the August 8th date is conditional on the Java EE
certification process.
>>>>
>>>> I look forward to any and all feedback. Thanks!
>>>>
>>>> --
>>>> Jason T. Greene
>>>> JBoss AS Lead / EAP Platform Architect
>>>> JBoss, a division of Red Hat
>>>>
>>>>
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev(a)lists.jboss.org
<mailto:jboss-as7-dev@lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>>
>>> --
>>> Brian Stansberry
>>> Principal Software Engineer
>>> JBoss by Red Hat
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
<mailto:jboss-as7-dev@lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
> --
> Brian Stansberry
> Principal Software Engineer
> JBoss by Red Hat
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Nicklas Karlsson, +358 40 5062266
Vaakunatie 10 as 7, 20780 Kaarina
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
- DML
9:39 a.m.
Important note: all mocking must be directed at David. He has thicker
skin than the rest of us.
On 3/28/13 8:28 AM, David M. Lloyd wrote:
Unfortunately transactional MSC won't make it in time for 8. We
are
however making some good progress on it. I'm fairly optimistic it'll
make it in time for 9. This is the official email you can refer to in
the future to mock me if we miss. :)
On 03/28/2013 01:39 AM, Nicklas Karlsson wrote:
> The roadmap looks nice. I must say the Undertow project is very
> ambitious, aside from performance I am sure it will bring AS-integration
> of the web layer to a completely new level. From a user perspective it
> might be tricky to find replacements for many -D switches that might
> disappear, many applications probably also depend on vague spec
> implementations that just happened to work for them. Are you trying to
> squeeze in the transactional MSC also or is that for a later relase?
>
>
> On Thu, Mar 28, 2013 at 8:29 AM, Paul Robinson <probinso(a)redhat.com
> <mailto:probinso@redhat.com>> wrote:
>
> I agree, I'm sure a lot of subsystem devs are hoping to talk about
> features scheduled for a component upgrade in AS Beta1.
>
> It would be great to say in my (potential) talk, that you can use
> these features in the latest AS release, rather than a recent AS
> snapshot.
>
> Paul
>
> On 28 Mar 2013, at 00:43, Brian Stansberry
> <brian.stansberry(a)redhat.com <mailto:brian.stansberry@redhat.com>>
> wrote:
>
> > Done. I used the dates you provided below, although I think Jesper's
> > suggestion re June 7 and JUDCon makes sense.
> >
> > On 3/27/13 6:27 PM, Jason Greene wrote:
> >> Be my guest :)
> >>
> >> Sent from my iPhone
> >>
> >> On Mar 27, 2013, at 5:57 PM, Brian Stansberry
> <brian.stansberry(a)redhat.com <mailto:brian.stansberry@redhat.com>>
> wrote:
> >>
> >>> Can we get Versions in JIRA for all these* plus a 9.0.0.CR1 to
> track
> >>> main items for the next big dev cycle? I volunteer to do it.
> I'm itching
> >>> to get my big pile of issues properly sorted into buckets. :-)
> >>>
> >>> * Well, not CR2 and Final which should only have stuff
> discovered after CR1
> >>>
> >>> On 3/27/13 12:28 PM, Jason Greene wrote:
> >>>> Hello Everyone,
> >>>>
> >>>> I am happy to announce a proposed roadmap for AS8. After some
> discussions with various AS developers and community members, the
> goals we think are important are:
> >>>>
> >>>> 1. Java EE7
> >>>> 2. Integration of Undertow (EE7 Web Sockets + performant
> non-blocking i/o)
> >>>> 3. Patching
> >>>> 4. Migration from JacORB to the JDK Orb
> >>>> 5. Transition to the new yet to be announced name
> >>>>
> >>>> I am proposing an agressive 6 month timeline for this
release,
> with the following key milestones:
> >>>>
> >>>> May 7 - Release Alpha1
> >>>> + Includes undertow, some ee7
> >>>> June 11 - Release Beta
> >>>> + more progress on EE7
> >>>> July 11 - Release CR1
> >>>> + EE7 feature complete
> >>>> July 25 - Release CR2 if needed
> >>>> (Hopefully TCK 100% by this date)
> >>>> August 8 - Release Final
> >>>>
> >>>> As usual the August 8th date is conditional on the Java EE
> certification process.
> >>>>
> >>>> I look forward to any and all feedback. Thanks!
> >>>>
> >>>> --
> >>>> Jason T. Greene
> >>>> JBoss AS Lead / EAP Platform Architect
> >>>> JBoss, a division of Red Hat
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> jboss-as7-dev mailing list
> >>>> jboss-as7-dev(a)lists.jboss.org
> <mailto:jboss-as7-dev@lists.jboss.org>
> >>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> >>>
> >>>
> >>> --
> >>> Brian Stansberry
> >>> Principal Software Engineer
> >>> JBoss by Red Hat
> >>> _______________________________________________
> >>> jboss-as7-dev mailing list
> >>> jboss-as7-dev(a)lists.jboss.org
> <mailto:jboss-as7-dev@lists.jboss.org>
> >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> >
> >
> > --
> > Brian Stansberry
> > Principal Software Engineer
> > JBoss by Red Hat
> > _______________________________________________
> > jboss-as7-dev mailing list
> > jboss-as7-dev(a)lists.jboss.org
<mailto:jboss-as7-dev@lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
>
>
> --
> Nicklas Karlsson, +358 40 5062266
> Vaakunatie 10 as 7, 20780 Kaarina
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
1:16 p.m.
I see others replied to the MSC 2 topic. To answer your other question about Undertow
though, a lot of the deployment code is shared between JBossWeb and undertow, and we have
been attempting to add compatibility for things like valves. I am hoping that once we have
a release that's integrated, that you guys could kick the tires a bit, and point out
any areas you think we should also emulate.
-Jason
On Mar 28, 2013, at 1:39 AM, Nicklas Karlsson <nickarls(a)gmail.com> wrote:
The roadmap looks nice. I must say the Undertow project is very
ambitious, aside from performance I am sure it will bring AS-integration of the web layer
to a completely new level. From a user perspective it might be tricky to find replacements
for many -D switches that might disappear, many applications probably also depend on vague
spec implementations that just happened to work for them. Are you trying to squeeze in the
transactional MSC also or is that for a later relase?
On Thu, Mar 28, 2013 at 8:29 AM, Paul Robinson <probinso(a)redhat.com> wrote:
I agree, I'm sure a lot of subsystem devs are hoping to talk about features
scheduled for a component upgrade in AS Beta1.
It would be great to say in my (potential) talk, that you can use these features in the
latest AS release, rather than a recent AS snapshot.
Paul
On 28 Mar 2013, at 00:43, Brian Stansberry <brian.stansberry(a)redhat.com> wrote:
> Done. I used the dates you provided below, although I think Jesper's
> suggestion re June 7 and JUDCon makes sense.
>
> On 3/27/13 6:27 PM, Jason Greene wrote:
>> Be my guest :)
>>
>> Sent from my iPhone
>>
>> On Mar 27, 2013, at 5:57 PM, Brian Stansberry
<brian.stansberry(a)redhat.com> wrote:
>>
>>> Can we get Versions in JIRA for all these* plus a 9.0.0.CR1 to track
>>> main items for the next big dev cycle? I volunteer to do it. I'm
itching
>>> to get my big pile of issues properly sorted into buckets. :-)
>>>
>>> * Well, not CR2 and Final which should only have stuff discovered after CR1
>>>
>>> On 3/27/13 12:28 PM, Jason Greene wrote:
>>>> Hello Everyone,
>>>>
>>>> I am happy to announce a proposed roadmap for AS8. After some
discussions with various AS developers and community members, the goals we think are
important are:
>>>>
>>>> 1. Java EE7
>>>> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking
i/o)
>>>> 3. Patching
>>>> 4. Migration from JacORB to the JDK Orb
>>>> 5. Transition to the new yet to be announced name
>>>>
>>>> I am proposing an agressive 6 month timeline for this release, with the
following key milestones:
>>>>
>>>> May 7 - Release Alpha1
>>>> + Includes undertow, some ee7
>>>> June 11 - Release Beta
>>>> + more progress on EE7
>>>> July 11 - Release CR1
>>>> + EE7 feature complete
>>>> July 25 - Release CR2 if needed
>>>> (Hopefully TCK 100% by this date)
>>>> August 8 - Release Final
>>>>
>>>> As usual the August 8th date is conditional on the Java EE certification
process.
>>>>
>>>> I look forward to any and all feedback. Thanks!
>>>>
>>>> --
>>>> Jason T. Greene
>>>> JBoss AS Lead / EAP Platform Architect
>>>> JBoss, a division of Red Hat
>>>>
>>>>
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>>
>>> --
>>> Brian Stansberry
>>> Principal Software Engineer
>>> JBoss by Red Hat
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
> --
> Brian Stansberry
> Principal Software Engineer
> JBoss by Red Hat
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Nicklas Karlsson, +358 40 5062266
Vaakunatie 10 as 7, 20780 Kaarina
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
3:02 p.m.
Jason, Darran and I were chatting recently that if Undertow could be
embeddable for junit tests, we can kick the tires a lot via PicketLink
testsuite. Creating a thread in the UT mailing list right now.
On 03/28/2013 12:16 PM, Jason Greene wrote:
I see others replied to the MSC 2 topic. To answer your other
question about Undertow though, a lot of the deployment code is shared between JBossWeb
and undertow, and we have been attempting to add compatibility for things like valves. I
am hoping that once we have a release that's integrated, that you guys could kick the
tires a bit, and point out any areas you think we should also emulate.
-Jason
On Mar 28, 2013, at 1:39 AM, Nicklas Karlsson <nickarls(a)gmail.com> wrote:
> The roadmap looks nice. I must say the Undertow project is very ambitious, aside from
performance I am sure it will bring AS-integration of the web layer to a completely new
level. From a user perspective it might be tricky to find replacements for many -D
switches that might disappear, many applications probably also depend on vague spec
implementations that just happened to work for them. Are you trying to squeeze in the
transactional MSC also or is that for a later relase?
>
>
> On Thu, Mar 28, 2013 at 8:29 AM, Paul Robinson <probinso(a)redhat.com> wrote:
> I agree, I'm sure a lot of subsystem devs are hoping to talk about features
scheduled for a component upgrade in AS Beta1.
>
> It would be great to say in my (potential) talk, that you can use these features in
the latest AS release, rather than a recent AS snapshot.
>
> Paul
>
> On 28 Mar 2013, at 00:43, Brian Stansberry <brian.stansberry(a)redhat.com>
wrote:
>
>> Done. I used the dates you provided below, although I think Jesper's
>> suggestion re June 7 and JUDCon makes sense.
>>
>> On 3/27/13 6:27 PM, Jason Greene wrote:
>>> Be my guest :)
>>>
>>> Sent from my iPhone
>>>
>>> On Mar 27, 2013, at 5:57 PM, Brian Stansberry
<brian.stansberry(a)redhat.com> wrote:
>>>
>>>> Can we get Versions in JIRA for all these* plus a 9.0.0.CR1 to track
>>>> main items for the next big dev cycle? I volunteer to do it. I'm
itching
>>>> to get my big pile of issues properly sorted into buckets. :-)
>>>>
>>>> * Well, not CR2 and Final which should only have stuff discovered after
CR1
>>>>
>>>> On 3/27/13 12:28 PM, Jason Greene wrote:
>>>>> Hello Everyone,
>>>>>
>>>>> I am happy to announce a proposed roadmap for AS8. After some
discussions with various AS developers and community members, the goals we think are
important are:
>>>>>
>>>>> 1. Java EE7
>>>>> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking
i/o)
>>>>> 3. Patching
>>>>> 4. Migration from JacORB to the JDK Orb
>>>>> 5. Transition to the new yet to be announced name
>>>>>
>>>>> I am proposing an agressive 6 month timeline for this release, with
the following key milestones:
>>>>>
>>>>> May 7 - Release Alpha1
>>>>> + Includes undertow, some ee7
>>>>> June 11 - Release Beta
>>>>> + more progress on EE7
>>>>> July 11 - Release CR1
>>>>> + EE7 feature complete
>>>>> July 25 - Release CR2 if needed
>>>>> (Hopefully TCK 100% by this date)
>>>>> August 8 - Release Final
>>>>>
>>>>> As usual the August 8th date is conditional on the Java EE
certification process.
>>>>>
>>>>> I look forward to any and all feedback. Thanks!
>>>>>
>>>>> --
>>>>> Jason T. Greene
>>>>> JBoss AS Lead / EAP Platform Architect
>>>>> JBoss, a division of Red Hat
>>>>>
>>>>>
5:34 a.m.
Some comments from me:
- This is essentially 18.5 weeks remaining development time (including vacation) for a
major
release that encompasses non-timeboxable items (e.g. EE7 updates & TCK). Risky IMHO.
Looking
back to AS history I don't think we ever had such a short cycle for a major release,
although I know we want to reduce the scope of major releases going forward.
- I think BLOCKER Jiras per milestone should be used. E.g TCK passing items for CR1, EE7
feature completeness for Beta. Tracked items JIRAs should have the same priority with the
tracker JIRA (e.g. AS7-6553 for EE) to have a better view of the work that needs to be
done.
- Overlap with any to-be-committed backportable EAP functionality (e.g. patching) will
also
drag things back, resource wise.
- We need to align work with component leads for any potential updates that will bring in
new features. Specify a component freeze date (AS8 Beta, June 11th? CR July 11th?) and try
to stick to it. Clarify what exactly that date means because some teams interpret this as
a
cut off date for a Final component version, some other teams just provide a CR and
infinite
updates for an unspecified period of time :)
Overall the plan is great, we may need to add some more buffers.
/D
On 27/03/2013 23:57, Brian Stansberry wrote:
Can we get Versions in JIRA for all these* plus a 9.0.0.CR1 to track
main items for the next big dev cycle? I volunteer to do it. I'm itching
to get my big pile of issues properly sorted into buckets. :-)
* Well, not CR2 and Final which should only have stuff discovered after CR1
On 3/27/13 12:28 PM, Jason Greene wrote:
> Hello Everyone,
>
> I am happy to announce a proposed roadmap for AS8. After some discussions with
various AS developers and community members, the goals we think are important are:
>
> 1. Java EE7
> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
> 3. Patching
> 4. Migration from JacORB to the JDK Orb
> 5. Transition to the new yet to be announced name
>
> I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
>
> May 7 - Release Alpha1
> + Includes undertow, some ee7
> June 11 - Release Beta
> + more progress on EE7
> July 11 - Release CR1
> + EE7 feature complete
> July 25 - Release CR2 if needed
> (Hopefully TCK 100% by this date)
> August 8 - Release Final
>
> As usual the August 8th date is conditional on the Java EE certification process.
>
> I look forward to any and all feedback. Thanks!
>
> --
> Jason T. Greene
> JBoss AS Lead / EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dimitris Andreadis
Software Engineering Manager
JBoss Application Server
by Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
http://dandreadis.blogspot.com/
1:02 p.m.
Great to see the as8 plan. For such a major release, I feel it's a
very aggressive schedule, with the bulk of milestones to be achieved
during the summer time (April - July).
I'd suggest add more buffer time in between to allow for various risks.
How about targeting 9/22 (Java One week) for final?
Cheng
On 3/27/13 1:28 PM, Jason Greene wrote:
Hello Everyone,
I am happy to announce a proposed roadmap for AS8. After some discussions with various AS
developers and community members, the goals we think are important are:
1. Java EE7
2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
3. Patching
4. Migration from JacORB to the JDK Orb
5. Transition to the new yet to be announced name
I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
May 7 - Release Alpha1
+ Includes undertow, some ee7
June 11 - Release Beta
+ more progress on EE7
July 11 - Release CR1
+ EE7 feature complete
July 25 - Release CR2 if needed
(Hopefully TCK 100% by this date)
August 8 - Release Final
As usual the August 8th date is conditional on the Java EE certification process.
I look forward to any and all feedback. Thanks!
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
1:13 p.m.
Thanks for the feedback Cheng.
That could be a good fall back option if we miss a milestone. If you do discover a
schedule alignment problem (e.g. component release not lining up), then we could shift the
related milestone. Let me know if you become aware of one.
On Mar 28, 2013, at 12:02 PM, Cheng Fang <cfang(a)redhat.com> wrote:
Great to see the as8 plan. For such a major release, I feel
it's a
very aggressive schedule, with the bulk of milestones to be achieved
during the summer time (April - July).
I'd suggest add more buffer time in between to allow for various risks.
How about targeting 9/22 (Java One week) for final?
Cheng
On 3/27/13 1:28 PM, Jason Greene wrote:
> Hello Everyone,
>
> I am happy to announce a proposed roadmap for AS8. After some discussions with
various AS developers and community members, the goals we think are important are:
>
> 1. Java EE7
> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
> 3. Patching
> 4. Migration from JacORB to the JDK Orb
> 5. Transition to the new yet to be announced name
>
> I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
>
> May 7 - Release Alpha1
> + Includes undertow, some ee7
> June 11 - Release Beta
> + more progress on EE7
> July 11 - Release CR1
> + EE7 feature complete
> July 25 - Release CR2 if needed
> (Hopefully TCK 100% by this date)
> August 8 - Release Final
>
> As usual the August 8th date is conditional on the Java EE certification process.
>
> I look forward to any and all feedback. Thanks!
>
> --
> Jason T. Greene
> JBoss AS Lead / EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
3:50 p.m.
New subject: Community AS8 Management API Changes and Freeze Dates
A couple points re: allowing teams who provide management tooling for
the AS to plan for AS 8:
1) Major subsystem changes
If you are responsible for a subsystem and expect to create a new
subsystem for AS 8 or to make significant modifications to the
management API exposed by an existing one, please reply to this thread
with a brief summary of what you expect to do. This will give Heiko
Braun a chance to plan.
2) Management API Freeze Dates
The roadmap Jason has laid out will of course involve some changes to
the management APIs exposed by the AS core and by its subsystems. In
order to allow tooling that depends on the management APIs to react to
any changes we make, we'll need to complete changes to the management
APIs in advance of the July 11 CR1 date.
After discussions with Heiko Braun, we agreed upon the following
"freeze" dates for the management APIs:
1) June 11 (Beta release date) -- no new subsystems after this date, no
substantial changes to the core management API after this date, no large
new features in existing subsystems after this date.
2) June 25 -- final management API freeze. No further management API
changes except minor bug fixes that will not affect the console.
If you have any concerns about making any of these dates, please speak
up now.
Thanks,
-- Brian
On 3/27/13 12:28 PM, Jason Greene wrote:
Hello Everyone,
I am happy to announce a proposed roadmap for AS8. After some discussions with various AS
developers and community members, the goals we think are important are:
1. Java EE7
2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
3. Patching
4. Migration from JacORB to the JDK Orb
5. Transition to the new yet to be announced name
I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
May 7 - Release Alpha1
+ Includes undertow, some ee7
June 11 - Release Beta
+ more progress on EE7
July 11 - Release CR1
+ EE7 feature complete
July 25 - Release CR2 if needed
(Hopefully TCK 100% by this date)
August 8 - Release Final
As usual the August 8th date is conditional on the Java EE certification process.
I look forward to any and all feedback. Thanks!
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
4:29 p.m.
New subject: Community AS8 Management API Changes and Freeze Dates
Hi,
As it goes for new subsystems and changes, on my todo list are:
- new undertow subsystem - we have pretty clear idea of what it should look
like in the end. This should be finalized for beta
- new io subsystem, this is essentially split part part of current undertow
subsystem (workers, buffer-pools) into its own subsystem, so all other
subsystems can utilize it (i.e. remoting and undertow)
- addition to security subsystem for global configuration of SSL so all
subsystem will be able to use it. i will send mail about describing this in
more detail shortly.
There might be some minor changes to mail subsystem, but i cannot confirm
that yet.
--
tomaz
On Fri, Apr 5, 2013 at 9:50 PM, Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
A couple points re: allowing teams who provide management tooling
for
the AS to plan for AS 8:
1) Major subsystem changes
If you are responsible for a subsystem and expect to create a new
subsystem for AS 8 or to make significant modifications to the
management API exposed by an existing one, please reply to this thread
with a brief summary of what you expect to do. This will give Heiko
Braun a chance to plan.
2) Management API Freeze Dates
The roadmap Jason has laid out will of course involve some changes to
the management APIs exposed by the AS core and by its subsystems. In
order to allow tooling that depends on the management APIs to react to
any changes we make, we'll need to complete changes to the management
APIs in advance of the July 11 CR1 date.
After discussions with Heiko Braun, we agreed upon the following
"freeze" dates for the management APIs:
1) June 11 (Beta release date) -- no new subsystems after this date, no
substantial changes to the core management API after this date, no large
new features in existing subsystems after this date.
2) June 25 -- final management API freeze. No further management API
changes except minor bug fixes that will not affect the console.
If you have any concerns about making any of these dates, please speak
up now.
Thanks,
-- Brian
On 3/27/13 12:28 PM, Jason Greene wrote:
> Hello Everyone,
>
> I am happy to announce a proposed roadmap for AS8. After some
discussions with various AS developers and community members, the goals we
think are important are:
>
> 1. Java EE7
> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking
i/o)
> 3. Patching
> 4. Migration from JacORB to the JDK Orb
> 5. Transition to the new yet to be announced name
>
> I am proposing an agressive 6 month timeline for this release, with the
following key milestones:
>
> May 7 - Release Alpha1
> + Includes undertow, some ee7
> June 11 - Release Beta
> + more progress on EE7
> July 11 - Release CR1
> + EE7 feature complete
> July 25 - Release CR2 if needed
> (Hopefully TCK 100% by this date)
> August 8 - Release Final
>
> As usual the August 8th date is conditional on the Java EE certification
process.
>
> I look forward to any and all feedback. Thanks!
>
> --
> Jason T. Greene
> JBoss AS Lead / EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
9:05 a.m.
New subject: Community AS8 Management API Changes and Freeze Dates
On 04/05/2013 09:50 PM, Brian Stansberry wrote:
A couple points re: allowing teams who provide management tooling
for
the AS to plan for AS 8:
1) Major subsystem changes
We will have some changes/additions to our JCA, ResourceAdapters and
Datasources subsystems.
Here you have the main point I'm changing, and reasons for that. Those
points should be quite stable, but I'l get back to you next week if I
realize during implementation I need something else.
JCA:
Reasons: Adding support for Distrubuted Work Manager.
Changes: WorkManager will have more parameters to support distributable
configuaration. There will be for sure those parameters (don't consider
definition definitive, I'm still working on it):
DISTRIBUTED(SimpleAttributeDefinitionBuilder.create("distributed",
ModelType.BOOLEAN)
.setDefaultValue(new ModelNode(false))
.setAllowExpression(true)
.setAllowNull(true)
.setMeasurementUnit(MeasurementUnit.NONE)
.setRestartAllServices()
.setRequires("selector", "policy")
.build()),
SELECTOR(SimpleAttributeDefinitionBuilder.create("selector",
ModelType.STRING)
.setAllowExpression(true)
.setAllowNull(true)
.setMeasurementUnit(MeasurementUnit.NONE)
.setRestartAllServices()
.setXmlName("selector")
.setValidator(new
EnumValidator<SelectorValue>(SelectorValue.class, true, true ))
.build()),
POLICY(SimpleAttributeDefinitionBuilder.create("policy",
ModelType.STRING)
.setAllowExpression(true)
.setAllowNull(true)
.setMeasurementUnit(MeasurementUnit.NONE)
.setRestartAllServices()
.setXmlName("policy")
.setValidator(new
EnumValidator<PolicyValue>(PolicyValue.class, true, true))
.build());
There will be also a parameter to point a channel name (JGroups Channel)
that is defined in a new subresource at subsystem level (to be verified)
ResourceAdapters:
1)
Reasons: support inflow security
Changes: there will be a workmanager-security subresource into
resource-adapter containing configuration for security. I've not yet a
DMR definition, I'll send you in next days as an update. If you want to
get an idea take a look to workmanagerType and referenced type in
resource_adapters_1_1.xsd of Ironjacamar Beta4
2)
Reasons: changes to connection-definition to support new attributes:
changes: we will have new attributes called sharable (boolean),
enlistment(boolean), initial-pool-size(int),
capacity-incrementer-class(string),
capacity-incrementer-properties("type" => OBJECT, "value-type"
=> STRING),
capacity-decrementer-class(string),
capacity-decrementer-properties("type" => OBJECT, "value-type"
=> STRING)
3)
Reasons: new flush strategy
Channges: constant accepted for flush-strategy will changes
Datasources
Reasons: changes to support new attributes:
changes: we will have new attributes called initial-pool-size(int),
capacity-incrementer-class(string),
capacity-incrementer-properties("type" => OBJECT, "value-type"
=> STRING),
capacity-decrementer-class(string),
capacity-decrementer-properties("type" => OBJECT, "value-type"
=> STRING),
url-property (string)
I'm working on all those points. I'll follow up on this thread if I
realize I need more changes.
regards
S
10:33 a.m.
New subject: Community AS8 Management API Changes and Freeze Dates
Thanks, Stefano.
On 4/12/13 8:05 AM, Stefano Maestri wrote:
On 04/05/2013 09:50 PM, Brian Stansberry wrote:
> A couple points re: allowing teams who provide management tooling for
> the AS to plan for AS 8:
>
> 1) Major subsystem changes
>
>
We will have some changes/additions to our JCA, ResourceAdapters and
Datasources subsystems.
Here you have the main point I'm changing, and reasons for that. Those
points should be quite stable, but I'l get back to you next week if I
realize during implementation I need something else.
JCA:
Reasons: Adding support for Distrubuted Work Manager.
Changes: WorkManager will have more parameters to support distributable
configuaration. There will be for sure those parameters (don't consider
definition definitive, I'm still working on it):
DISTRIBUTED(SimpleAttributeDefinitionBuilder.create("distributed",
ModelType.BOOLEAN)
.setDefaultValue(new ModelNode(false))
.setAllowExpression(true)
.setAllowNull(true)
.setMeasurementUnit(MeasurementUnit.NONE)
.setRestartAllServices()
.setRequires("selector", "policy")
.build()),
SELECTOR(SimpleAttributeDefinitionBuilder.create("selector",
ModelType.STRING)
.setAllowExpression(true)
.setAllowNull(true)
.setMeasurementUnit(MeasurementUnit.NONE)
.setRestartAllServices()
.setXmlName("selector")
.setValidator(new
EnumValidator<SelectorValue>(SelectorValue.class, true, true ))
.build()),
POLICY(SimpleAttributeDefinitionBuilder.create("policy",
ModelType.STRING)
.setAllowExpression(true)
.setAllowNull(true)
.setMeasurementUnit(MeasurementUnit.NONE)
.setRestartAllServices()
.setXmlName("policy")
.setValidator(new
EnumValidator<PolicyValue>(PolicyValue.class, true, true))
.build());
There will be also a parameter to point a channel name (JGroups Channel)
that is defined in a new subresource at subsystem level (to be verified)
ResourceAdapters:
1)
Reasons: support inflow security
Changes: there will be a workmanager-security subresource into
resource-adapter containing configuration for security. I've not yet a
DMR definition, I'll send you in next days as an update. If you want to
get an idea take a look to workmanagerType and referenced type in
resource_adapters_1_1.xsd of Ironjacamar Beta4
2)
Reasons: changes to connection-definition to support new attributes:
changes: we will have new attributes called sharable (boolean),
enlistment(boolean), initial-pool-size(int),
capacity-incrementer-class(string),
capacity-incrementer-properties("type" => OBJECT, "value-type"
=> STRING),
capacity-decrementer-class(string),
capacity-decrementer-properties("type" => OBJECT, "value-type"
=> STRING)
3)
Reasons: new flush strategy
Channges: constant accepted for flush-strategy will changes
Datasources
Reasons: changes to support new attributes:
changes: we will have new attributes called initial-pool-size(int),
capacity-incrementer-class(string),
capacity-incrementer-properties("type" => OBJECT, "value-type"
=> STRING),
capacity-decrementer-class(string),
capacity-decrementer-properties("type" => OBJECT, "value-type"
=> STRING),
url-property (string)
I'm working on all those points. I'll follow up on this thread if I
realize I need more changes.
regards
S
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
10:38 a.m.
New subject: Community AS8 Management API Changes and Freeze Dates
For batch integration into AS 8, we will add some basic management
capabilities for batch jobs, executions, and step metrics. They can be
accessed from both admin console and cli. Initially these are mostly
read operations and I expect the management framework already fully
support them.
Cheng
On 4/5/13 3:50 PM, Brian Stansberry wrote:
A couple points re: allowing teams who provide management tooling
for
the AS to plan for AS 8:
1) Major subsystem changes
If you are responsible for a subsystem and expect to create a new
subsystem for AS 8 or to make significant modifications to the
management API exposed by an existing one, please reply to this thread
with a brief summary of what you expect to do. This will give Heiko
Braun a chance to plan.
2) Management API Freeze Dates
The roadmap Jason has laid out will of course involve some changes to
the management APIs exposed by the AS core and by its subsystems. In
order to allow tooling that depends on the management APIs to react to
any changes we make, we'll need to complete changes to the management
APIs in advance of the July 11 CR1 date.
After discussions with Heiko Braun, we agreed upon the following
"freeze" dates for the management APIs:
1) June 11 (Beta release date) -- no new subsystems after this date, no
substantial changes to the core management API after this date, no large
new features in existing subsystems after this date.
2) June 25 -- final management API freeze. No further management API
changes except minor bug fixes that will not affect the console.
If you have any concerns about making any of these dates, please speak
up now.
Thanks,
-- Brian
On 3/27/13 12:28 PM, Jason Greene wrote:
> Hello Everyone,
>
> I am happy to announce a proposed roadmap for AS8. After some discussions with
various AS developers and community members, the goals we think are important are:
>
> 1. Java EE7
> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
> 3. Patching
> 4. Migration from JacORB to the JDK Orb
> 5. Transition to the new yet to be announced name
>
> I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
>
> May 7 - Release Alpha1
> + Includes undertow, some ee7
> June 11 - Release Beta
> + more progress on EE7
> July 11 - Release CR1
> + EE7 feature complete
> July 25 - Release CR2 if needed
> (Hopefully TCK 100% by this date)
> August 8 - Release Final
>
> As usual the August 8th date is conditional on the Java EE certification process.
>
> I look forward to any and all feedback. Thanks!
>
> --
> Jason T. Greene
> JBoss AS Lead / EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
10:41 a.m.
New subject: Community AS8 Management API Changes and Freeze Dates
On 4/12/13 9:38 AM, Cheng Fang wrote:
For batch integration into AS 8, we will add some basic management
capabilities for batch jobs, executions, and step metrics. They can be
accessed from both admin console and cli. Initially these are mostly
read operations and I expect the management framework already fully
support them.
Thanks; this is helpful for the console guys. Re: the management
framewok, I expect so too. :)
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
3:19 a.m.
New subject: Community AS8 Management API Changes and Freeze Dates
what subsystem will this be?
On Apr 12, 2013, at 4:38 PM, Cheng Fang <cfang(a)redhat.com> wrote:
For batch integration into AS 8, we will add some basic management
capabilities for batch jobs, executions, and step metrics. They can be
accessed from both admin console and cli. Initially these are mostly
read operations and I expect the management framework already fully
support them.
Cheng
On 4/5/13 3:50 PM, Brian Stansberry wrote:
> A couple points re: allowing teams who provide management tooling for
> the AS to plan for AS 8:
>
> 1) Major subsystem changes
>
> If you are responsible for a subsystem and expect to create a new
> subsystem for AS 8 or to make significant modifications to the
> management API exposed by an existing one, please reply to this thread
> with a brief summary of what you expect to do. This will give Heiko
> Braun a chance to plan.
>
> 2) Management API Freeze Dates
>
> The roadmap Jason has laid out will of course involve some changes to
> the management APIs exposed by the AS core and by its subsystems. In
> order to allow tooling that depends on the management APIs to react to
> any changes we make, we'll need to complete changes to the management
> APIs in advance of the July 11 CR1 date.
>
> After discussions with Heiko Braun, we agreed upon the following
> "freeze" dates for the management APIs:
>
> 1) June 11 (Beta release date) -- no new subsystems after this date, no
> substantial changes to the core management API after this date, no large
> new features in existing subsystems after this date.
>
> 2) June 25 -- final management API freeze. No further management API
> changes except minor bug fixes that will not affect the console.
>
> If you have any concerns about making any of these dates, please speak
> up now.
>
> Thanks,
> -- Brian
>
> On 3/27/13 12:28 PM, Jason Greene wrote:
>> Hello Everyone,
>>
>> I am happy to announce a proposed roadmap for AS8. After some discussions with
various AS developers and community members, the goals we think are important are:
>>
>> 1. Java EE7
>> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
>> 3. Patching
>> 4. Migration from JacORB to the JDK Orb
>> 5. Transition to the new yet to be announced name
>>
>> I am proposing an agressive 6 month timeline for this release, with the following
key milestones:
>>
>> May 7 - Release Alpha1
>> + Includes undertow, some ee7
>> June 11 - Release Beta
>> + more progress on EE7
>> July 11 - Release CR1
>> + EE7 feature complete
>> July 25 - Release CR2 if needed
>> (Hopefully TCK 100% by this date)
>> August 8 - Release Final
>>
>> As usual the August 8th date is conditional on the Java EE certification
process.
>>
>> I look forward to any and all feedback. Thanks!
>>
>> --
>> Jason T. Greene
>> JBoss AS Lead / EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
10:10 a.m.
New subject: Community AS8 Management API Changes and Freeze Dates
We haven't created this subsystem yet. Most likely it will be something
like as8/batch, or as8/batch-integration. Currently we are focusing on
the standalone implementation, and once the batch spec (JSR 352) goes
final, which will happen very soon, we will work on the integration.
Cheng
On 4/15/13 3:19 AM, Heiko Braun wrote:
what subsystem will this be?
On Apr 12, 2013, at 4:38 PM, Cheng Fang <cfang(a)redhat.com> wrote:
> For batch integration into AS 8, we will add some basic management
> capabilities for batch jobs, executions, and step metrics. They can be
> accessed from both admin console and cli. Initially these are mostly
> read operations and I expect the management framework already fully
> support them.
>
> Cheng
>
> On 4/5/13 3:50 PM, Brian Stansberry wrote:
>> A couple points re: allowing teams who provide management tooling for
>> the AS to plan for AS 8:
>>
>> 1) Major subsystem changes
>>
>> If you are responsible for a subsystem and expect to create a new
>> subsystem for AS 8 or to make significant modifications to the
>> management API exposed by an existing one, please reply to this thread
>> with a brief summary of what you expect to do. This will give Heiko
>> Braun a chance to plan.
>>
>> 2) Management API Freeze Dates
>>
>> The roadmap Jason has laid out will of course involve some changes to
>> the management APIs exposed by the AS core and by its subsystems. In
>> order to allow tooling that depends on the management APIs to react to
>> any changes we make, we'll need to complete changes to the management
>> APIs in advance of the July 11 CR1 date.
>>
>> After discussions with Heiko Braun, we agreed upon the following
>> "freeze" dates for the management APIs:
>>
>> 1) June 11 (Beta release date) -- no new subsystems after this date, no
>> substantial changes to the core management API after this date, no large
>> new features in existing subsystems after this date.
>>
>> 2) June 25 -- final management API freeze. No further management API
>> changes except minor bug fixes that will not affect the console.
>>
>> If you have any concerns about making any of these dates, please speak
>> up now.
>>
>> Thanks,
>> -- Brian
>>
>> On 3/27/13 12:28 PM, Jason Greene wrote:
>>> Hello Everyone,
>>>
>>> I am happy to announce a proposed roadmap for AS8. After some discussions
with various AS developers and community members, the goals we think are important are:
>>>
>>> 1. Java EE7
>>> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
>>> 3. Patching
>>> 4. Migration from JacORB to the JDK Orb
>>> 5. Transition to the new yet to be announced name
>>>
>>> I am proposing an agressive 6 month timeline for this release, with the
following key milestones:
>>>
>>> May 7 - Release Alpha1
>>> + Includes undertow, some ee7
>>> June 11 - Release Beta
>>> + more progress on EE7
>>> July 11 - Release CR1
>>> + EE7 feature complete
>>> July 25 - Release CR2 if needed
>>> (Hopefully TCK 100% by this date)
>>> August 8 - Release Final
>>>
>>> As usual the August 8th date is conditional on the Java EE certification
process.
>>>
>>> I look forward to any and all feedback. Thanks!
>>>
>>> --
>>> Jason T. Greene
>>> JBoss AS Lead / EAP Platform Architect
>>> JBoss, a division of Red Hat
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
10:45 a.m.
New subject: Community AS8 Management API Changes and Freeze Dates
On 04/05/2013 03:50 PM, Brian Stansberry wrote:
A couple points re: allowing teams who provide management tooling
for
the AS to plan for AS 8:
1) Major subsystem changes
If you are responsible for a subsystem and expect to create a new
subsystem for AS 8 or to make significant modifications to the
management API exposed by an existing one, please reply to this thread
with a brief summary of what you expect to do. This will give Heiko
Braun a chance to plan.
I'm moving the persistence provider specific integration code into a
separate repo that includes some of the JPA related management code.
The AS8 JPA subsystem management api that is exposed for deployed
applications, will not change (jboss-cli + management console will not
need changes). Which is why I didn't respond before (since there will
be no API changes). I'm responding anyway, just to keep people informed
about the pending changes.
2) Management API Freeze Dates
The roadmap Jason has laid out will of course involve some changes to
the management APIs exposed by the AS core and by its subsystems. In
order to allow tooling that depends on the management APIs to react to
any changes we make, we'll need to complete changes to the management
APIs in advance of the July 11 CR1 date.
After discussions with Heiko Braun, we agreed upon the following
"freeze" dates for the management APIs:
1) June 11 (Beta release date) -- no new subsystems after this date, no
substantial changes to the core management API after this date, no large
new features in existing subsystems after this date.
2) June 25 -- final management API freeze. No further management API
changes except minor bug fixes that will not affect the console.
If you have any concerns about making any of these dates, please speak
up now.
Thanks,
-- Brian
On 3/27/13 12:28 PM, Jason Greene wrote:
> Hello Everyone,
>
> I am happy to announce a proposed roadmap for AS8. After some discussions with
various AS developers and community members, the goals we think are important are:
>
> 1. Java EE7
> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
> 3. Patching
> 4. Migration from JacORB to the JDK Orb
> 5. Transition to the new yet to be announced name
>
> I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
>
> May 7 - Release Alpha1
> + Includes undertow, some ee7
> June 11 - Release Beta
> + more progress on EE7
> July 11 - Release CR1
> + EE7 feature complete
> July 25 - Release CR2 if needed
> (Hopefully TCK 100% by this date)
> August 8 - Release Final
>
> As usual the August 8th date is conditional on the Java EE certification process.
>
> I look forward to any and all feedback. Thanks!
>
> --
> Jason T. Greene
> JBoss AS Lead / EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
3:13 p.m.
New subject: Community AS8 Management API Changes and Freeze Dates
Projected changes to clustering management APIs:
1. addition of runtime metrics to JGroups and Infinispan subsystems (a
definite)
2. x-site (cross site) management configuration (a definite)
3. clustering subsystem (a possible)
1. involves:
(i) adding run-time metrics to existing Infinispan resources
/subsystem=infinispan/cache-container=X
/subsystem=infinispan/cache-container=X/cache=Y
(ii) adding run-time metrics to new resources
/subsystem=jgroups/channel=X
/subsystem=jgroups/channel=X/protocol=Y
2. involves adding new resources for managing cross-site replication
- see
http://lists.jboss.org/pipermail/infinispan-dev/2012-October/011486.html
3. involves creating a new subsystem which permits viewing the
participation of a node in a cluster
This is experimental at the moment.
See https://issues.jboss.org/browse/AS7-4388
Richard
On 04/05/2013 08:50 PM, Brian Stansberry wrote:
A couple points re: allowing teams who provide management tooling
for
the AS to plan for AS 8:
1) Major subsystem changes
If you are responsible for a subsystem and expect to create a new
subsystem for AS 8 or to make significant modifications to the
management API exposed by an existing one, please reply to this thread
with a brief summary of what you expect to do. This will give Heiko
Braun a chance to plan.
2) Management API Freeze Dates
The roadmap Jason has laid out will of course involve some changes to
the management APIs exposed by the AS core and by its subsystems. In
order to allow tooling that depends on the management APIs to react to
any changes we make, we'll need to complete changes to the management
APIs in advance of the July 11 CR1 date.
After discussions with Heiko Braun, we agreed upon the following
"freeze" dates for the management APIs:
1) June 11 (Beta release date) -- no new subsystems after this date, no
substantial changes to the core management API after this date, no large
new features in existing subsystems after this date.
2) June 25 -- final management API freeze. No further management API
changes except minor bug fixes that will not affect the console.
If you have any concerns about making any of these dates, please speak
up now.
Thanks,
-- Brian
On 3/27/13 12:28 PM, Jason Greene wrote:
> Hello Everyone,
>
> I am happy to announce a proposed roadmap for AS8. After some discussions with
various AS developers and community members, the goals we think are important are:
>
> 1. Java EE7
> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
> 3. Patching
> 4. Migration from JacORB to the JDK Orb
> 5. Transition to the new yet to be announced name
>
> I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
>
> May 7 - Release Alpha1
> + Includes undertow, some ee7
> June 11 - Release Beta
> + more progress on EE7
> July 11 - Release CR1
> + EE7 feature complete
> July 25 - Release CR2 if needed
> (Hopefully TCK 100% by this date)
> August 8 - Release Final
>
> As usual the August 8th date is conditional on the Java EE certification process.
>
> I look forward to any and all feedback. Thanks!
>
> --
> Jason T. Greene
> JBoss AS Lead / EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
3:19 p.m.
New subject: Community AS8 Management API Changes and Freeze Dates
That sounds like a lot for a short schedule.
On 4/12/13 2:13 PM, Richard Achmatowicz wrote:
Projected changes to clustering management APIs:
1. addition of runtime metrics to JGroups and Infinispan subsystems (a
definite)
2. x-site (cross site) management configuration (a definite)
3. clustering subsystem (a possible)
1. involves:
(i) adding run-time metrics to existing Infinispan resources
/subsystem=infinispan/cache-container=X
/subsystem=infinispan/cache-container=X/cache=Y
(ii) adding run-time metrics to new resources
/subsystem=jgroups/channel=X
/subsystem=jgroups/channel=X/protocol=Y
2. involves adding new resources for managing cross-site replication
- see
http://lists.jboss.org/pipermail/infinispan-dev/2012-October/011486.html
3. involves creating a new subsystem which permits viewing the
participation of a node in a cluster
This is experimental at the moment.
See https://issues.jboss.org/browse/AS7-4388
Richard
On 04/05/2013 08:50 PM, Brian Stansberry wrote:
> A couple points re: allowing teams who provide management tooling for
> the AS to plan for AS 8:
>
> 1) Major subsystem changes
>
> If you are responsible for a subsystem and expect to create a new
> subsystem for AS 8 or to make significant modifications to the
> management API exposed by an existing one, please reply to this thread
> with a brief summary of what you expect to do. This will give Heiko
> Braun a chance to plan.
>
> 2) Management API Freeze Dates
>
> The roadmap Jason has laid out will of course involve some changes to
> the management APIs exposed by the AS core and by its subsystems. In
> order to allow tooling that depends on the management APIs to react to
> any changes we make, we'll need to complete changes to the management
> APIs in advance of the July 11 CR1 date.
>
> After discussions with Heiko Braun, we agreed upon the following
> "freeze" dates for the management APIs:
>
> 1) June 11 (Beta release date) -- no new subsystems after this date, no
> substantial changes to the core management API after this date, no large
> new features in existing subsystems after this date.
>
> 2) June 25 -- final management API freeze. No further management API
> changes except minor bug fixes that will not affect the console.
>
> If you have any concerns about making any of these dates, please speak
> up now.
>
> Thanks,
> -- Brian
>
> On 3/27/13 12:28 PM, Jason Greene wrote:
>> Hello Everyone,
>>
>> I am happy to announce a proposed roadmap for AS8. After some discussions with
various AS developers and community members, the goals we think are important are:
>>
>> 1. Java EE7
>> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
>> 3. Patching
>> 4. Migration from JacORB to the JDK Orb
>> 5. Transition to the new yet to be announced name
>>
>> I am proposing an agressive 6 month timeline for this release, with the following
key milestones:
>>
>> May 7 - Release Alpha1
>> + Includes undertow, some ee7
>> June 11 - Release Beta
>> + more progress on EE7
>> July 11 - Release CR1
>> + EE7 feature complete
>> July 25 - Release CR2 if needed
>> (Hopefully TCK 100% by this date)
>> August 8 - Release Final
>>
>> As usual the August 8th date is conditional on the Java EE certification
process.
>>
>> I look forward to any and all feedback. Thanks!
>>
>> --
>> Jason T. Greene
>> JBoss AS Lead / EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
3:32 p.m.
New subject: Community AS8 Management API Changes and Freeze Dates
1. is going to be complete in a day or two.
2. Starting on 2 next week.
If time permits (I think it will), i'll resurrect some existing work
done on 3.
On 04/12/2013 08:19 PM, Brian Stansberry wrote:
That sounds like a lot for a short schedule.
On 4/12/13 2:13 PM, Richard Achmatowicz wrote:
> Projected changes to clustering management APIs:
>
> 1. addition of runtime metrics to JGroups and Infinispan subsystems (a
> definite)
> 2. x-site (cross site) management configuration (a definite)
> 3. clustering subsystem (a possible)
>
> 1. involves:
> (i) adding run-time metrics to existing Infinispan resources
> /subsystem=infinispan/cache-container=X
> /subsystem=infinispan/cache-container=X/cache=Y
> (ii) adding run-time metrics to new resources
> /subsystem=jgroups/channel=X
> /subsystem=jgroups/channel=X/protocol=Y
>
> 2. involves adding new resources for managing cross-site replication
> - see
> http://lists.jboss.org/pipermail/infinispan-dev/2012-October/011486.html
>
> 3. involves creating a new subsystem which permits viewing the
> participation of a node in a cluster
> This is experimental at the moment.
> See https://issues.jboss.org/browse/AS7-4388
>
> Richard
>
> On 04/05/2013 08:50 PM, Brian Stansberry wrote:
>> A couple points re: allowing teams who provide management tooling for
>> the AS to plan for AS 8:
>>
>> 1) Major subsystem changes
>>
>> If you are responsible for a subsystem and expect to create a new
>> subsystem for AS 8 or to make significant modifications to the
>> management API exposed by an existing one, please reply to this thread
>> with a brief summary of what you expect to do. This will give Heiko
>> Braun a chance to plan.
>>
>> 2) Management API Freeze Dates
>>
>> The roadmap Jason has laid out will of course involve some changes to
>> the management APIs exposed by the AS core and by its subsystems. In
>> order to allow tooling that depends on the management APIs to react to
>> any changes we make, we'll need to complete changes to the management
>> APIs in advance of the July 11 CR1 date.
>>
>> After discussions with Heiko Braun, we agreed upon the following
>> "freeze" dates for the management APIs:
>>
>> 1) June 11 (Beta release date) -- no new subsystems after this date, no
>> substantial changes to the core management API after this date, no large
>> new features in existing subsystems after this date.
>>
>> 2) June 25 -- final management API freeze. No further management API
>> changes except minor bug fixes that will not affect the console.
>>
>> If you have any concerns about making any of these dates, please speak
>> up now.
>>
>> Thanks,
>> -- Brian
>>
>> On 3/27/13 12:28 PM, Jason Greene wrote:
>>> Hello Everyone,
>>>
>>> I am happy to announce a proposed roadmap for AS8. After some discussions
with various AS developers and community members, the goals we think are important are:
>>>
>>> 1. Java EE7
>>> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
>>> 3. Patching
>>> 4. Migration from JacORB to the JDK Orb
>>> 5. Transition to the new yet to be announced name
>>>
>>> I am proposing an agressive 6 month timeline for this release, with the
following key milestones:
>>>
>>> May 7 - Release Alpha1
>>> + Includes undertow, some ee7
>>> June 11 - Release Beta
>>> + more progress on EE7
>>> July 11 - Release CR1
>>> + EE7 feature complete
>>> July 25 - Release CR2 if needed
>>> (Hopefully TCK 100% by this date)
>>> August 8 - Release Final
>>>
>>> As usual the August 8th date is conditional on the Java EE certification
process.
>>>
>>> I look forward to any and all feedback. Thanks!
>>>
>>> --
>>> Jason T. Greene
>>> JBoss AS Lead / EAP Platform Architect
>>> JBoss, a division of Red Hat
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
4:31 p.m.
New subject: Community AS8 Management API Changes and Freeze Dates
I would like to see runtime statistics be off by default and have an attribute to enable
them. We talked about this in the AS 8 development meetings in Brno.
Andy
----- Original Message -----
From: "Richard Achmatowicz" <rachmato(a)redhat.com>
To: jboss-as7-dev(a)lists.jboss.org
Sent: Friday, April 12, 2013 1:13:59 PM
Subject: Re: [jboss-as7-dev] Community AS8 Management API Changes and Freeze Dates
Projected changes to clustering management APIs:
1. addition of runtime metrics to JGroups and Infinispan subsystems
(a
definite)
2. x-site (cross site) management configuration (a definite)
3. clustering subsystem (a possible)
1. involves:
(i) adding run-time metrics to existing Infinispan resources
/subsystem=infinispan/cache-container=X
/subsystem=infinispan/cache-container=X/cache=Y
(ii) adding run-time metrics to new resources
/subsystem=jgroups/channel=X
/subsystem=jgroups/channel=X/protocol=Y
2. involves adding new resources for managing cross-site replication
- see
http://lists.jboss.org/pipermail/infinispan-dev/2012-October/011486.html
3. involves creating a new subsystem which permits viewing the
participation of a node in a cluster
This is experimental at the moment.
See https://issues.jboss.org/browse/AS7-4388
Richard
On 04/05/2013 08:50 PM, Brian Stansberry wrote:
> A couple points re: allowing teams who provide management tooling
> for
> the AS to plan for AS 8:
>
> 1) Major subsystem changes
>
> If you are responsible for a subsystem and expect to create a new
> subsystem for AS 8 or to make significant modifications to the
> management API exposed by an existing one, please reply to this
> thread
> with a brief summary of what you expect to do. This will give Heiko
> Braun a chance to plan.
>
> 2) Management API Freeze Dates
>
> The roadmap Jason has laid out will of course involve some changes
> to
> the management APIs exposed by the AS core and by its subsystems.
> In
> order to allow tooling that depends on the management APIs to react
> to
> any changes we make, we'll need to complete changes to the
> management
> APIs in advance of the July 11 CR1 date.
>
> After discussions with Heiko Braun, we agreed upon the following
> "freeze" dates for the management APIs:
>
> 1) June 11 (Beta release date) -- no new subsystems after this
> date, no
> substantial changes to the core management API after this date, no
> large
> new features in existing subsystems after this date.
>
> 2) June 25 -- final management API freeze. No further management
> API
> changes except minor bug fixes that will not affect the console.
>
> If you have any concerns about making any of these dates, please
> speak
> up now.
>
> Thanks,
> -- Brian
>
> On 3/27/13 12:28 PM, Jason Greene wrote:
>> Hello Everyone,
>>
>> I am happy to announce a proposed roadmap for AS8. After some
>> discussions with various AS developers and community members, the
>> goals we think are important are:
>>
>> 1. Java EE7
>> 2. Integration of Undertow (EE7 Web Sockets + performant
>> non-blocking i/o)
>> 3. Patching
>> 4. Migration from JacORB to the JDK Orb
>> 5. Transition to the new yet to be announced name
>>
>> I am proposing an agressive 6 month timeline for this release,
>> with the following key milestones:
>>
>> May 7 - Release Alpha1
>> + Includes undertow, some ee7
>> June 11 - Release Beta
>> + more progress on EE7
>> July 11 - Release CR1
>> + EE7 feature complete
>> July 25 - Release CR2 if needed
>> (Hopefully TCK 100% by this date)
>> August 8 - Release Final
>>
>> As usual the August 8th date is conditional on the Java EE
>> certification process.
>>
>> I look forward to any and all feedback. Thanks!
>>
>> --
>> Jason T. Greene
>> JBoss AS Lead / EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
5:46 p.m.
New subject: Community AS8 Management API Changes and Freeze Dates
Andrig and I had a brief side-exchange and agreed that this will be an
AS 9 item:
https://issues.jboss.org/browse/AS7-6889
Thanks for mentioning this, Andy -- I thought it was in JIRA, but didn't
see anything.
On 4/12/13 3:31 PM, Andrig Miller wrote:
I would like to see runtime statistics be off by default and have an
attribute to enable them. We talked about this in the AS 8 development meetings in Brno.
Andy
----- Original Message -----
> From: "Richard Achmatowicz" <rachmato(a)redhat.com>
> To: jboss-as7-dev(a)lists.jboss.org
> Sent: Friday, April 12, 2013 1:13:59 PM
> Subject: Re: [jboss-as7-dev] Community AS8 Management API Changes and Freeze Dates
>
> Projected changes to clustering management APIs:
>
> 1. addition of runtime metrics to JGroups and Infinispan subsystems
> (a
> definite)
> 2. x-site (cross site) management configuration (a definite)
> 3. clustering subsystem (a possible)
>
> 1. involves:
> (i) adding run-time metrics to existing Infinispan resources
> /subsystem=infinispan/cache-container=X
> /subsystem=infinispan/cache-container=X/cache=Y
> (ii) adding run-time metrics to new resources
> /subsystem=jgroups/channel=X
> /subsystem=jgroups/channel=X/protocol=Y
>
> 2. involves adding new resources for managing cross-site replication
> - see
> http://lists.jboss.org/pipermail/infinispan-dev/2012-October/011486.html
>
> 3. involves creating a new subsystem which permits viewing the
> participation of a node in a cluster
> This is experimental at the moment.
> See https://issues.jboss.org/browse/AS7-4388
>
> Richard
>
> On 04/05/2013 08:50 PM, Brian Stansberry wrote:
>> A couple points re: allowing teams who provide management tooling
>> for
>> the AS to plan for AS 8:
>>
>> 1) Major subsystem changes
>>
>> If you are responsible for a subsystem and expect to create a new
>> subsystem for AS 8 or to make significant modifications to the
>> management API exposed by an existing one, please reply to this
>> thread
>> with a brief summary of what you expect to do. This will give Heiko
>> Braun a chance to plan.
>>
>> 2) Management API Freeze Dates
>>
>> The roadmap Jason has laid out will of course involve some changes
>> to
>> the management APIs exposed by the AS core and by its subsystems.
>> In
>> order to allow tooling that depends on the management APIs to react
>> to
>> any changes we make, we'll need to complete changes to the
>> management
>> APIs in advance of the July 11 CR1 date.
>>
>> After discussions with Heiko Braun, we agreed upon the following
>> "freeze" dates for the management APIs:
>>
>> 1) June 11 (Beta release date) -- no new subsystems after this
>> date, no
>> substantial changes to the core management API after this date, no
>> large
>> new features in existing subsystems after this date.
>>
>> 2) June 25 -- final management API freeze. No further management
>> API
>> changes except minor bug fixes that will not affect the console.
>>
>> If you have any concerns about making any of these dates, please
>> speak
>> up now.
>>
>> Thanks,
>> -- Brian
>>
>> On 3/27/13 12:28 PM, Jason Greene wrote:
>>> Hello Everyone,
>>>
>>> I am happy to announce a proposed roadmap for AS8. After some
>>> discussions with various AS developers and community members, the
>>> goals we think are important are:
>>>
>>> 1. Java EE7
>>> 2. Integration of Undertow (EE7 Web Sockets + performant
>>> non-blocking i/o)
>>> 3. Patching
>>> 4. Migration from JacORB to the JDK Orb
>>> 5. Transition to the new yet to be announced name
>>>
>>> I am proposing an agressive 6 month timeline for this release,
>>> with the following key milestones:
>>>
>>> May 7 - Release Alpha1
>>> + Includes undertow, some ee7
>>> June 11 - Release Beta
>>> + more progress on EE7
>>> July 11 - Release CR1
>>> + EE7 feature complete
>>> July 25 - Release CR2 if needed
>>> (Hopefully TCK 100% by this date)
>>> August 8 - Release Final
>>>
>>> As usual the August 8th date is conditional on the Java EE
>>> certification process.
>>>
>>> I look forward to any and all feedback. Thanks!
>>>
>>> --
>>> Jason T. Greene
>>> JBoss AS Lead / EAP Platform Architect
>>> JBoss, a division of Red Hat
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
3:28 a.m.
New subject: Community AS8 Management API Changes and Freeze Dates
1) June 11 (Beta release date) -- no new subsystems after this date, no
substantial changes to the core management API after this date, no large
new features in existing subsystems after this date.
2) June 25 -- final management API freeze. No further management API
changes except minor bug fixes that will not affect the console.
Thanks for the updates. I've created a number of Jira issues to track progress on each
subsystem. Please aim for completion of new subsystems and subsystem API changes for Beta1
(Jun 11). But the earlier we get it the better.
Undertow:
https://issues.jboss.org/browse/AS7-6894
Infinispan:
https://issues.jboss.org/browse/AS7-6902
Batch Integration:
https://issues.jboss.org/browse/AS7-6899
(What subsystem?)
JCA:
https://issues.jboss.org/browse/AS7-6897
IO Subsystem:
https://issues.jboss.org/browse/AS7-6895
Regards, Heiko
5:51 a.m.
New subject: Community AS8 Management API Changes and Freeze Dates
I will be adding support for audit logging which will need configuring
On 5 Apr 2013, at 20:50, Brian Stansberry wrote:
A couple points re: allowing teams who provide management tooling for
the AS to plan for AS 8:
1) Major subsystem changes
If you are responsible for a subsystem and expect to create a new
subsystem for AS 8 or to make significant modifications to the
management API exposed by an existing one, please reply to this thread
with a brief summary of what you expect to do. This will give Heiko
Braun a chance to plan.
2) Management API Freeze Dates
The roadmap Jason has laid out will of course involve some changes to
the management APIs exposed by the AS core and by its subsystems. In
order to allow tooling that depends on the management APIs to react to
any changes we make, we'll need to complete changes to the management
APIs in advance of the July 11 CR1 date.
After discussions with Heiko Braun, we agreed upon the following
"freeze" dates for the management APIs:
1) June 11 (Beta release date) -- no new subsystems after this date, no
substantial changes to the core management API after this date, no large
new features in existing subsystems after this date.
2) June 25 -- final management API freeze. No further management API
changes except minor bug fixes that will not affect the console.
If you have any concerns about making any of these dates, please speak
up now.
Thanks,
-- Brian
On 3/27/13 12:28 PM, Jason Greene wrote:
> Hello Everyone,
>
> I am happy to announce a proposed roadmap for AS8. After some discussions with
various AS developers and community members, the goals we think are important are:
>
> 1. Java EE7
> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
> 3. Patching
> 4. Migration from JacORB to the JDK Orb
> 5. Transition to the new yet to be announced name
>
> I am proposing an agressive 6 month timeline for this release, with the following key
milestones:
>
> May 7 - Release Alpha1
> + Includes undertow, some ee7
> June 11 - Release Beta
> + more progress on EE7
> July 11 - Release CR1
> + EE7 feature complete
> July 25 - Release CR2 if needed
> (Hopefully TCK 100% by this date)
> August 8 - Release Final
>
> As usual the August 8th date is conditional on the Java EE certification process.
>
> I look forward to any and all feedback. Thanks!
>
> --
> Jason T. Greene
> JBoss AS Lead / EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
---------------------------------------
Kabir Khan
Prinicipal Software Engineer
JBoss by Red Hat
6:06 a.m.
New subject: Community AS8 Management API Changes and Freeze Dates
https://issues.jboss.org/browse/AS7-6906
On Apr 15, 2013, at 11:51 AM, Kabir Khan <kabir.khan(a)jboss.com> wrote:
I will be adding support for audit logging which will need
configuring
On 5 Apr 2013, at 20:50, Brian Stansberry wrote:
> A couple points re: allowing teams who provide management tooling for
> the AS to plan for AS 8:
>
> 1) Major subsystem changes
>
> If you are responsible for a subsystem and expect to create a new
> subsystem for AS 8 or to make significant modifications to the
> management API exposed by an existing one, please reply to this thread
> with a brief summary of what you expect to do. This will give Heiko
> Braun a chance to plan.
>
> 2) Management API Freeze Dates
>
> The roadmap Jason has laid out will of course involve some changes to
> the management APIs exposed by the AS core and by its subsystems. In
> order to allow tooling that depends on the management APIs to react to
> any changes we make, we'll need to complete changes to the management
> APIs in advance of the July 11 CR1 date.
>
> After discussions with Heiko Braun, we agreed upon the following
> "freeze" dates for the management APIs:
>
> 1) June 11 (Beta release date) -- no new subsystems after this date, no
> substantial changes to the core management API after this date, no large
> new features in existing subsystems after this date.
>
> 2) June 25 -- final management API freeze. No further management API
> changes except minor bug fixes that will not affect the console.
>
> If you have any concerns about making any of these dates, please speak
> up now.
>
> Thanks,
> -- Brian
>
> On 3/27/13 12:28 PM, Jason Greene wrote:
>> Hello Everyone,
>>
>> I am happy to announce a proposed roadmap for AS8. After some discussions with
various AS developers and community members, the goals we think are important are:
>>
>> 1. Java EE7
>> 2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
>> 3. Patching
>> 4. Migration from JacORB to the JDK Orb
>> 5. Transition to the new yet to be announced name
>>
>> I am proposing an agressive 6 month timeline for this release, with the following
key milestones:
>>
>> May 7 - Release Alpha1
>> + Includes undertow, some ee7
>> June 11 - Release Beta
>> + more progress on EE7
>> July 11 - Release CR1
>> + EE7 feature complete
>> July 25 - Release CR2 if needed
>> (Hopefully TCK 100% by this date)
>> August 8 - Release Final
>>
>> As usual the August 8th date is conditional on the Java EE certification
process.
>>
>> I look forward to any and all feedback. Thanks!
>>
>> --
>> Jason T. Greene
>> JBoss AS Lead / EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
>
> --
> Brian Stansberry
> Principal Software Engineer
> JBoss by Red Hat
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
---------------------------------------
Kabir Khan
Prinicipal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
4025
days inactive
4045
days old
31 comments
17 participants
participants (17)
-
Andrig Miller -
Anil Saldhana -
Brian Stansberry -
Cheng Fang -
David M. Lloyd -
Dimitris Andreadis -
Heiko Braun -
Jason Greene -
Jason Greene -
Jesper Pedersen -
Kabir Khan -
Nicklas Karlsson -
Paul Robinson -
Richard Achmatowicz -
Scott Marlow -
Stefano Maestri -
Tomaž Cerar