It's not only reliability that can make your life harder.
As far as I have seen, JBoss cannot handle object relationships
and dependencies, which is bad. Some people seem to serialize
Java objects to database blobs, which is even worse.
This means that you have to track those relationships on your own
using primary and foreign keys in your application logic. Although
this is not too comlicated, it may get confusing once the application
gets larger. And in some way it's against the EJB design principles.
If someone with more JBoss/JAWS experience (I'm new to JBoss)
decides to implement this feature, I would really like to help :-)
> -----Original Message-----
> From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 11, 2001 8:10 PM
> To: [EMAIL PROTECTED]
> Subject: [jBoss-User] Reliability
>
>
> I was wondering if anyone has been using the 2.0 final JBoss/Tomcat
> implementation in production for their system? I'm sure it's a great
> product and everything, but if we decided to use and
> contribute to it's
> development, it would need to be pretty stable because we're
> going to be
> using it in medical systems management for O/R systems.
> Therefore, if bugs
> were to suddenly appear, we'd basically be screwed. Any help would be
> greatly appreciated.
>
> Jesse Kuhnert
> [EMAIL PROTECTED]
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
