Hey
> With this, the client application ran exactly as described in
> Monsoon-Haefel's book, Client_1.java from Ch 4 of "Enterprise Java Beans,
> 2d" (O'Reilly:2000).
Excellent :-)
> Please allow me a brief testimonial: I have had more success these past 4
> days with jBoss than I had in *twice* the time with Allaire's JRun (the
> single developer license). Hands down, jBoss is easier to use. For
> example, beans deploy themselves, even on updates. In JRun, you have to
> uninstall the bean, restart the server, install the new bean, restart the
> server. In jBoss, configuration changes were easy, if not always well
> documented. As for tech support, I was able to get clear, understandable
> answers from this new group whereas scores of messages were of no help on
> Allaire's message board.
I'm very happy that our efforts have not been in vain 8-)
> Finally, from the way I read it, jBoss
> ***actually complies with the EJB spec***!
That is the primary goal, for sure.
BTW, I'm just about to finish the exception handling cleanup, after which
you should never ever again see an "InvocationTargetException", but only
what the spec actually says you should see 8-)
> JRun, OTOH, *requires* me to
> write my own ejbFindByPrimaryKey() method in the ProgramBean.java
> file. (In fact, jBoss seems to go extra mile by writing other finders for
> me as well.)
Well, if you're BMP there's no choice: you have to do all of it yourself.
So, I assume you're talking CMP in which case we do try to make things as
automatic as possible.
> Now it's on to adding TomCat!
We are working on the Tomcat integration right this minute. When we're done
the "distance" between Tomcat and jBoss is zero (0), which means that you
can turn off parameter serialization for optimized in-VM performance. Pretty
neat.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
