RE: [JBoss-dev] JB4DR1 Deadline MAY 26
I talked with Dr Jung yesterday, the Webservices part is going pretty well but JAXR is 70% there and W2EE is still 80% to go (but easy) (Dr. Jung's words) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dain Sundstrom Sent: vendredi, 4. avril 2003 00:48 To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I don't think we can support J2EE 1.4 for the DR1 release unless someone gets in and makes whatever changes are required to get our metadata classes to support the XML schemas used in J2EE 1.4. Besides meta data are there other big things in J2EE 1.4 that we haven't addressed yet? -dain On Thursday, April 3, 2003, at 04:30 PM, Igor Fedorenko wrote: What J2EE specification version are you planning to support in JBoss 4.0? J2EE 1.4 is not final as far as I know... -Original Message- From: marc fleury [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 3:47 PM To: [EMAIL PROTECTED] Sourceforge. Net Subject: [JBoss-dev] JB4DR1 Deadline MAY 26 Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. Do you mean JB4 AOP persistence? Acid, security, transactions, cache (!) are all almost ready. Are you saying the new AOP persistence is far from done? What about the old CMP2.0 engine? marcf --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
Ok then there are 4 weeks to get the new stuff done? Marc, Bill, sure we could do a release but what difference would it make if the new features are not in it. Is this a release just to show off AOP? What about any of the other new stuff? Just give the users a solid 3.2 and they will be happy. -dain On Thursday, April 3, 2003, at 03:30 PM, Bill Burke wrote: It will be ready and stable. Functionality freeze is May 5th. What functionality doesn't make it by then will be left out of the release. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
It will be ready and stable. Functionality freeze is May 5th. What functionality doesn't make it by then will be left out of the release. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
JBoss Remoting AOP + tx, security, versioning, remoting, clustering, txlock, caching DTM (waiting on David's response) EMB (Enterprise Media Beans) JUDDI integration If I can get it done: AOP + EJB (packaged extensions to EJB) and don't forget Nukes! Anybody got anything to add to this list? Who doesn't think they'll be done by May 5th? Who thinks they'll be cutting it close? Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:48 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 Ok then there are 4 weeks to get the new stuff done? Marc, Bill, sure we could do a release but what difference would it make if the new features are not in it. Is this a release just to show off AOP? What about any of the other new stuff? Just give the users a solid 3.2 and they will be happy. -dain On Thursday, April 3, 2003, at 03:30 PM, Bill Burke wrote: It will be ready and stable. Functionality freeze is May 5th. What functionality doesn't make it by then will be left out of the release. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
What J2EE specification version are you planning to support in JBoss 4.0? J2EE 1.4 is not final as far as I know... -Original Message- From: marc fleury [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 3:47 PM To: [EMAIL PROTECTED] Sourceforge. Net Subject: [JBoss-dev] JB4DR1 Deadline MAY 26 Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
1.3 Some 1.4 stuff will probably sneek in though. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Igor Fedorenko Sent: Thursday, April 03, 2003 5:31 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 What J2EE specification version are you planning to support in JBoss 4.0? J2EE 1.4 is not final as far as I know... -Original Message- From: marc fleury [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 3:47 PM To: [EMAIL PROTECTED] Sourceforge. Net Subject: [JBoss-dev] JB4DR1 Deadline MAY 26 Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
I don't think we can support J2EE 1.4 for the DR1 release unless someone gets in and makes whatever changes are required to get our metadata classes to support the XML schemas used in J2EE 1.4. Besides meta data are there other big things in J2EE 1.4 that we haven't addressed yet? -dain On Thursday, April 3, 2003, at 04:30 PM, Igor Fedorenko wrote: What J2EE specification version are you planning to support in JBoss 4.0? J2EE 1.4 is not final as far as I know... -Original Message- From: marc fleury [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 3:47 PM To: [EMAIL PROTECTED] Sourceforge. Net Subject: [JBoss-dev] JB4DR1 Deadline MAY 26 Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
Persistence will not be done. -dain On Thursday, April 3, 2003, at 04:27 PM, Bill Burke wrote: JBoss Remoting AOP + tx, security, versioning, remoting, clustering, txlock, caching DTM (waiting on David's response) EMB (Enterprise Media Beans) JUDDI integration If I can get it done: AOP + EJB (packaged extensions to EJB) and don't forget Nukes! Anybody got anything to add to this list? Who doesn't think they'll be done by May 5th? Who thinks they'll be cutting it close? Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:48 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 Ok then there are 4 weeks to get the new stuff done? Marc, Bill, sure we could do a release but what difference would it make if the new features are not in it. Is this a release just to show off AOP? What about any of the other new stuff? Just give the users a solid 3.2 and they will be happy. -dain On Thursday, April 3, 2003, at 03:30 PM, Bill Burke wrote: It will be ready and stable. Functionality freeze is May 5th. What functionality doesn't make it by then will be left out of the release. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
1.3 with ongoing development for 1.4 marcf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Igor Fedorenko Sent: Thursday, April 03, 2003 5:31 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 What J2EE specification version are you planning to support in JBoss 4.0? J2EE 1.4 is not final as far as I know... -Original Message- From: marc fleury [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 3:47 PM To: [EMAIL PROTECTED] Sourceforge. Net Subject: [JBoss-dev] JB4DR1 Deadline MAY 26 Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020 aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
Bill Burke wrote: I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. With respect to the cache. I have 3 major tasks that need to be done before it is ready: 1. [Bela] Implement pessimistic and optimistic locking (transactability) on a cluster of caches. I should be done by mid April with this 2. [Bill, Bela] (Stupid) integration into an Interceptor (AOP). Here we need to flesh out some of the difficulties we encountered talking on the phone today, e.g. instrumenting collections, primitive types, recursive instrumentation of an object graph etc. 3. [Jeremy, Dain] Integration of the cache into the PersistenceManager. The first version will have the PersistenceManager use the Cache as a replicated in-memory cache. Our use case will initially be shared DB, so all nodes use the same database. At a later stage (probably not JB4) we will provide unshared DBs. This involves some more efforts, e.g. retrieving full DB state for new nodes (from existing nodes). Tasks #1, #2 and #3 can be done in parallel. Although #1 is not yet done, the API will remain the same, so the Cache can already be used (without transactability though). #2 requires some effort by Bill, and Bela (if locking is done before mid-April). Task #3 will be done by Jeremy and Dain. I don't know what issues we will encounter there. Jeremy/Dain, can you comment on this ? -- Bela Ban --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
DR1 is a showcase for the geralized services architecture. Its not a showcase for J2EE 1.4 views of these services as this will be built on top of the core. Having the HTTP IL in these release is irrelevant. I'm not porting the RMI/HTTP invokers until the remoting, pooling, proxy+interceptor factories, etc are in place. There is no reason to panic, go back to working on the grand vision of generalized services intersecting with POJOs to give your version of an enterprise application server as per your specification. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Nathan Phelps [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 03, 2003 2:48 PM Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
On Thursday, April 3, 2003, at 05:26 PM, Bela Ban wrote: 3. [Jeremy, Dain] Integration of the cache into the PersistenceManager. The first version will have the PersistenceManager use the Cache as a replicated in-memory cache. Our use case will initially be shared DB, so all nodes use the Our need for caching is very different from what the other two, so I don't think that it can be done in parallel as it requires some very things in the implementation. I'm still not convinced that we don't need a completely different cache from what the rest of the server will use. Of course we will use the same low level APIs, but I think the rest will need to be custom. I know you and Jeremy have been working these issues out, so I'll have to wait and see what happens. same database. At a later stage (probably not JB4) we will provide unshared DBs. This involves some more efforts, e.g. retrieving full DB state for new nodes (from existing nodes). I think this is a third system that will be very different from the other two. I am concerned that if we try to support all of these different requirements we will end up difficult to use and maintain code, but you are a coding Jedi. Anyway, my point is I don't think they can be done in parallel. -dain --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
--- Dain Sundstrom [EMAIL PROTECTED] wrote: Our need for caching is very different from what the other two, so I don't think that it can be done in parallel as it requires some very things in the implementation. I'm still not convinced that we don't need a completely different cache from what the rest of the server will use. I have discussed the requirements for the cache from the CMP's perspective (PersistenceManager) with Jeremy twice (and we'll meet this Monday again). I think we came up with a workable solution, the first cache iteration was unusable (hashmap based). The new tree-structured cache should suit your requirements much better. For stuff like delete all order items form customer with id=34425, we need some custom functionality, agreed. But I think I have a solution for this, and Jeremy and I will discuss it Monday. Other than that, I *hope* that the current API more or less satisfies your requirements. I think this is a third system that will be very different from the other two. Maybe, but I do hope the cache can be used by both. I am concerned that if we try to support all of these different requirements we will end up difficult to use and maintain code, but you are a coding Jedi. Anyway, my point is I don't think they can be done in parallel. Why not ? If the cache satisfies both requirements I don't see why we could not proceed in parallel. Bela __ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
Jboss Remoting callbacks are in - I wil commit in the next day or so when tom and I finish testing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 6:06 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
Did you guys end up doing it in such a way so that you can use one protocol one way and another protocol the other way like you had mentioned? Secondly, what is really going to be cool when we expose this via AOP remoting... Bill, what are your plans for that? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Haynie Sent: Thursday, April 03, 2003 8:21 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Jboss Remoting callbacks are in - I wil commit in the next day or so when tom and I finish testing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 6:06 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
We haven't added the different protocols, but that should be easy enough to do and a great idea. I sent bill a note tonight about doing a generic AOP remoting event/listener framework for POJOs. My thought is using generic JavaBean style java.util.EventListener/java.util.EventObject (or bounded properties, etc) so you could dynamically attach remote listeners to regular POJOs to get remote events. Nathan, do you want me to help you with doing a JMSServerInvocationHandler? -- I would like to refactor down the async event stuff in JMX into the base remoting framework so that you just deal with the functionality pieces of listeners/events in the invocation handler. I really need another good subsystem to make sure it gets refactored properly. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 11:44 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Did you guys end up doing it in such a way so that you can use one protocol one way and another protocol the other way like you had mentioned? Secondly, what is really going to be cool when we expose this via AOP remoting... Bill, what are your plans for that? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Haynie Sent: Thursday, April 03, 2003 8:21 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Jboss Remoting callbacks are in - I wil commit in the next day or so when tom and I finish testing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 6:06 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE
