Now that couldn't have been much more simpler. Thanks a lot! Kalle
On 3/24/06, Dan Diephouse <[EMAIL PROTECTED]> wrote: > Try this: > > XFireServletController.getRequest().getRemoteUser(); > > Cheers, > - Dan > > Kalle Korhonen wrote: > > >Thanks Dan, I thought about Invoker as well, but the current way of > >accessing MessageContext was good enough. Created XFIRE-317: @Resource > >for accessing MessageContext as an improvement request. > > > >Taking this a little bit further, if I keep my the httpClient proxy > >alive on the client (i.e. to use the same session) and I use container > >managed authentication on the server, is there a way to access > >HttpServletRequest's getRemoteUser() from the MessageContext (didn't > >look at the source yet)? I guess an alternative way of doing this > >would be to write a simple filter for this that would save the current > >name into some known location... (ThreadLocal heh heh - I suppose the > >current "MessageContext as a parameter" implementation was done > >exactly to avoid using ThreadLocal). > > > >Kalle > > > >On 3/23/06, Dan Diephouse <[EMAIL PROTECTED]> wrote: > > > > > >>The @Resource is probably a much better way. Could you open a JIRA issue > >>for this? Thanks! > >> > >>One option you do have is to write your own Invoker and pass along the > >>MessageContext whatever way you want to your service. > >> > >>- Dan > >> > >>Kalle Korhonen wrote: > >> > >> > >> > >>>Hello XFire users, > >>> > >>>I'm new to XFire, but this stuff rocks. Got basic authentication > >>>working with XFire using JSR181, and I'd need to know the username > >>>within the operation. The documentation says you can simply add > >>>MessageContext as a parameter to your operation, and indeed this seems > >>>to work but this forces me to add it to the interface as well(?). On > >>>the (Java) client, it looks a little ugly now that I'm reusing the > >>>same interface and passing in an additional null with each operation > >>>(that are user specific) but then "mysteriously" on the server I get > >>>an existing MessageContext object. Are the any chances/plans to change > >>>this to use @Resource annotation or some other undocumented way of > >>>doing this, or is this going to be it? > >>> > >>>Thanks for the project. It's so much cleaner after some Axis/WSDL hacking! > >>> > >>>Kalle > >>> > >>> > >>> > >>> > >>-- > >>Dan Diephouse > >>(616) 971-2053 > >>Envoi Solutions LLC > >>http://netzooid.com > >> > >> > >> > >> > > > -- > Dan Diephouse > (616) 971-2053 > Envoi Solutions LLC > http://netzooid.com > >
