marc fleury wrote:
>
> > Actually, my experience was that (with IBM's 1.3 jdk, anyway -
> > thankyouverymuch) getting jBoss to run isn't tough at all - getting the
> > first bean to deploy, on the other hand, is an excercise in frustration
>
> Yes, I want to officialy apologize for this.
>
> See most of our reputation, and what we boast about on the website, is the
> "ease of use" in deployment of jBoss. That is something we had in jBoss 1.0
> due to the hot-deploy feature and the "drop and run" approach to compilation
> (i.e. none:). This has made droves of developers/IT shops come our way, we
> are aware that our success is due to the "admin-friendly" features.
Yup. But I do realize that jboss 2.0 isn't done yet. I knew what I was
getting into. Also, some of the commercial products I've dealt with are
really no better as far as telling you exactly what went wrong; at least
with jboss, I've got the source!
>
> jBoss 2.0 goes even further, with dev-friendly features as well (monitoring
> an open directory) you just touch your ejb-jar.xml file and it redeploys
> AUTOMATICALLY when you press that save button in your IDE. You have to see
> it to believe it!!
Have already seen it. Slick.
thanks for a great container
danch
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
