In the source for the beans cdejb for com.web_tomorrow.cd, I can see a
number of alarming statements concerning JAWS in notes.txt:
(By the way, the deployment of this example is rather smooth and requires
very little tweaking. You just have to adjust the classpath for the
compilation and for executing the clientapps, which, in my case, made wrong
assumptions about the location of ejb.jar and jboss-client.jar.)
(1) " if you add a CMP field to a class after it has been deployed, you can
expect
problems. Merely restarting the server won't be enough: you may have to
re-install it. If you are running a number of projects on the same server
this
is going to be very inconvient."
(2) "Although hot deployment works well, if an error occurs during
deployment it is
possible that you will need to restart the jBoss server. This is
particularly
noticeable with `NoClassDefFound' errors; these arise if you package a Bean
without the supporting classes it needs."
(3) "jBoss CMP does field updating by recording the existing field values,
deleting
the row of the database, then writing the new row with the new values. This
means that if you create an object and set its ten (say) attributes, this
will
translate into at least 21 whole-row operations!"
(4) "The jBoss database is persistent, in that its data is retained even
when the
server is stopped. However, its persistence is managed in an odd way, by
writing out a script of SQL commands that will re-build the database. This
file
cann become extremely large. It's not obvious that this is a good way to do
this."
Have these, rather serious issues, already been addressed, or are they still
present in the 2.0-FINAL release?
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
