DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12428>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12428 request.getUserPrincipal(): Misinterpretation of specification? ------- Additional Comments From [EMAIL PROTECTED] 2003-09-29 03:16 ------- This works, but only in the context of the WEB container. If my WEB application calls down to my entity beans, I am out of luck. I don't know of a way to pass this "context" down to the entity beans without having to implicitly pass a user parameter to ALL the functions which would normally get a principal from the context. By the way, this is happening with JBOSS 3.2.2RC3 which has TomCat version 4.1 bundled with it (I am not sure which one). In my application, additional features become available when user becomes a member. Thus all of my code is based on: a) Do I have a principal, no? then GUEST access otherwise b) b) If role X is enabled, allow functions X1...Xn Not having principal in the public pages, does not allow me to check the role. I noticed that I am not the only one who is having an issue with the way this works. Is there a way to make a parameter, that when set, would pass the principal to the public pages. If the parameter is not set, then don't pass the principal as it's now? Since the spec is so ambiguous, it makes migration to TomCat/JBOSS combo from Weblogic, Orion or other app servers difficult. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
