September 1st,

Hello,

this is following the "case studies" stuff. I found very interesting to read
on the positive and negative both with j2ee at large and with jboss in
particular.

This mail is to address something I feel came up as an issue with jboss.
This is the "when?" of jboss.  As I am coding the final features and
debugging I feel that jboss is there (I know it) and that it's a matter of
ironing out the last stuff, making it way easier (still) to use and heavily
documenting the user side of it.  We need to move to "real life" bugs, the
deep stuff as was pointed out.

I announce that we will be done with alpha by the end of this month.  That
means that by September 1st we will put out a real beta with all the
features and QA done so that folks can use this in development and
production with the ease of mind that must come with it.  Telkel needs that
container ASAP and we will be running our internal deployment framework
(heavily j2ee) on it.  Last time we did that, when we developed it, it
brought jboss1.0 to a level where the bugs we were uncovering were "heavy
duty" and non trivial, i.e. "real life" bugs and that really really
stabilized the code base.

My feeling with jboss2.0 is that in forcing the switch to it, we did the
right thing.  Also and that credit goes to the kid, by rearchitecting the
container with "open source" development in mind and the series of plugins
and interceptors, Rickard has put out a container in advance of its time,
truly the "future technology" we take some much pride in coding and sharing.
The first really pluggable interceptor-based, JMX managed j2ee server.
WebLogic isn't there :) (butitworks:)

The independent plugins that have been developed prove that (btw the ZOAP
plugin is shipping in CVS today :))) and the security and jaws rewrite also
prove that point.  The "open source" development of this container is real
and that is an achievement in itself, we were not there with jboss1.0, the
model works. A la linux 2.0.  Let's move on.

We also took a necessary hit since it left us in "alpha" stage with
jboss2.0, our public face, for an additional 4 month.  I realize many users
that came by in april took the brunt of jboss2.0 development status and I
want to apologize for the early frustrations and thank you all for your
patience, code work doco and feedback... it is bringing jboss to a stage
where it will play with the big boys.  Collectively implemented,
collectively debugged, (collectively loved?) nobody can touch that...


By september 1st you will have a production quality container.

At ease, and now let's go kick some code ass, fire at will!

<heroic trumpets in the background/>

kind regards

"let there be house, this is our house"

________________________
Marc Fleury
Chief Technology Officer
Telkel, Inc.
________________________


Reply via email to