My suggestion is optimization, clean-up, and irksome details be patched as
updates to the final release. Seriously. For your beta cycle, I suggest
creating a wish list to go with your bug list (should be an eXtreme
Programming practice). Try putting everything there and fix what you can't
and voila! Product.
The toughest part of programming (as perfectionists) is that we're
immediately privy to our design mistakes. Hindsight is not always a friend.
:)
The less moving targets, like changing XML descriptors, you guys have the
easier it is for developers to get onto testing more interesting things.
To me, the most posts are of the "My _blank_ won't deploy" or "I get a
RuntimeMBeanException" variety. These should be areas of concern. Once I
can deploy testbeans.jar out of the box, I'll be happy. I can only spend 1
hour a day debugging jBoss and am stuck wondering what's inside the
MBeanServer.java file (that I can't get) that's crashing (for many of us).
It's not a solution to delete a file and reconstruct it from scratch. I'm
now working to get jBoss compile so I can track down and fix bugs myself.
Should be easy now with 4 weeks of Java experience (1033 xp)...
You guys seem to be working too hard, but for the good of mankind. Are you
working the suggested XProgramming 8 hours/day and no more? Time
constraints make it easier to throw things into the wish list. :)
Jeff Mc. -verbose -caffeinated -?
p.s. - Dude, not everyone from California talks like that, dude, unless it's
after the _free_ beer mentioned in the FAQ! Dudes, free beer!
From: Rickard �berg [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 23, 2000 8:40 AM
To: jBoss
Subject: Re: [jBoss-User] ejb-ref question
marc fleury wrote:
> you do that in other parts of the code (factor out metadata information)
and
> I don't think it is a good idea. Byproduct of "design talk" but not real.
> So if the variable is in the metadata and you don't need it for
> MessageBeans? well don't use it!!! but don't put a hierarchy of 10 depth
> just to cover simple metadata squeakiness not worth it, really not.
>
> Flat metadata is good (simple), metadata with gazillion hierarchy classes
is
> silly... we have been there, done that (twice!) and we know it's useless.
>
> Even though I am no expert on non-object languages, I can relate to the
> critics of java and OO in general that "extensive" hierarchies is
OO-goop...
> A little is good, most notably interfaces are good, but the 10 depth
> metadata structures only impress little girls.
Absolutely, and why separate the containers into three separate ones? I
mean, cause like, "DaContainer" would work, right. And it would be,
like, awesome, coz it could do just about anything. You know. And then
and then, like when MessageBeans are implemented, right, it also goes
into DaContainer... like "Resistance is futile" and just assimilate its
bad butt. And then everything is like one class! Whoa! And its like
simple, because I only have to import One Class! YEAH!
Right.
Not.
Don't agree with you, but that's just my silly little OO-head talking.
And I'm not talking "extensive" hear, just two levels, just like the
containers.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
