Dear Adrian,

Do not let the words 'Chief' and 'Scientist' cloud your judgement. It is not by 
posts like this that EJB has a bad reputation. It is by poor documentation 
cumbersome configuration and contradictory advice in the forums.
Having done a good deal of searches on these forums, read wikis and docs that 
it took me two days to finally find a solution to the 'read-only' - 
'commit-option' combo.
I found all kind of things, including one JBoss employee giving the definitive 
solution: use 'clean-read-ahead-on-load'.
You are saying that 'read-only' should be only used with commit option 'A'. So 
how come it is possible at all to use 'read-only with other commit options? 
Shouldn't we get an error message during start-up? How about at least a warning 
message? If this is too hard for a scientist or a chief, how about including 
this in the docs? May be in the 'commit-option', or 'read-only' section?
It is very easy to be arrogant and tell other how stupid they are. It is more 
constructive to help and improve ourselves.
Cheers,

GRT

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870691#3870691

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870691


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to