What were the problems you had with the last version of Castor you
tried? (I believe a new version is now available).
Reinhard pointed out a potential problem with Digester - we have to
write out the instance data when preferences are updated.
I wish I understood what exactly the problem is. We have run this under
load in our QA environment with no problems but it hangs up in
production with a fairly light load.
Ralph
Carsten Ziegeler wrote:
Ralph Goers wrote:
Thanks for the info. Do you think we should rewrite this using Digester
instead of Castor?
I never really liked Castor; at the time when we started with the
portal Digester was not usable for us as there were some problems
with complex types like lists and maps (at least as far as i remember).
But if Digester meets your needs, I think it makes sense to give it a try.
Carsten
