I often do session handling this way. What I do is on login, return a token generated by the UUID class in java 5 and later. Then I force the users on subsequent calls to pass in the token or the invokation is rejected. Works great if you can control policy on both sides.
HTH, Robert On 9/21/07, tyju tiui <[EMAIL PROTECTED]> wrote: > > I guess I'll do this with the session though it seems wrong ... I can't > think of any other way to handle it. > > I'm still open to suggestions if anyone has a good idea to share :-) > > Thanks, > > Ty > > ----- Original Message ---- > From: tyju tiui <[EMAIL PROTECTED]> > To: axis-user@ws.apache.org > Sent: Friday, September 21, 2007 3:25:48 AM > Subject: Request Tracking > > > I'd like to assign a unique ID to each request as it comes in so that I > might track it all the way through to the outFlow. In other words I want to > give each request a tracking ID so I can go back in my logs and follow a > request's path all the way through my system. > > What do you guys and gals think the best way to do this might be? > > I've thought about doing something with a session variable, but that seems > to go against the stateless nature of WS in general. > > I also thought I might inject the unique ID into the request after I've > received it, but that also seems like a bad idea ... I'm sure there are a > million things that could potentially go wrong doing something like this. > > Your ideas are much appreciated. > > Thanks, > > Ty > > ________________________________ > Boardwalk for $500? In 2007? Ha! > Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! > Games. > > ________________________________ > Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
