2007/2/28, Christopher Schultz <[EMAIL PROTECTED]>:
How is it that you have code that needs request-specific information, but no access to the request? Are you forced into this situation by other components (through a callback mechanism or something like that)? Or, is this the result of poor planning?
well, the code has been designed to run into jboss. In a clustered configuration the request was not available in the Business tier. The Jboss SecurityAssociations classes where doing the job of propagating the principal to the BT. Now we deployed the same code in tomcat, where a subset of the classes have been included from those componing the BT. Hence, we are developing the same application for both the environments and we'd like to mantain the classes as general as possible. Think of a log4j utility that must be called from either the WT and the BT. We don't want to introduce a new version of the log helper (we don't want to make things too complicated). We want to build the some code and it works wether deployed in tomcat or jboss. We are there at 99%, I still need the user principal but I can solve using the ThreadLocal. And a Valve, maybe... -- TREMALNAIK --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
