Session IDs and robots

Hi All I'm currently working on a large webapp, powered by Struts, and I have a serious problem with making it SE-friendly. The problem is, I don't know how to make Struts to not attach session id (i.e. no encodeURL()) the URL returned to visitor, in case it's a robot (i.e. googlebot). In other

Re: Struts, Business Logic, DAOs

Jesse You're correct. I'm not sure how complex Paul's application is, but indeed, separating it's logic into such a layers is a good idea. Paul asked about examples - the best I know is RedHat's WAF. There is a powerful persistence layer, handling objects creation and manipulation, and domain objec

Re: Struts, Business Logic, DAOs

Hi I'm not sure if this follows the 'best practices' (for me it do) and what kind of RDBMS you're using, but the best place for such a logic is a database itself. Using stored procedures, you can code such a checking and validation on the table level, and avoid code overhead. Sergiusz --

Re: Clustering Application Scope Objects

Hi > For my purposes, I would let the database manage conflicts. Each application scope object would > be tied to the database, a change made on a specific application server would first update the > database. For example, the information from a table containing label/value pairs for product > c