Yeah, that's why I stated '...if you're using JSP/Servlets...' There is no simple 'push' model for accessing EJBs. The most lightweight I can think of is connecting to the JNDI implementation on the server. Since each app server uses an impl. of their own, it's going to be difficult to track it this way. I mentioned JSP/Servlets because if the transport is some kind of Web Service, all will be available there.
Juan Pablo Lorandi Chief Software Architect Code Foundry Ltd. [EMAIL PROTECTED] Barberstown, Straffan, Co. Kildare, Ireland. Tel: +353-1-6012050 Fax: +353-1-6012051 Mobile: +353-86-2157900 www.codefoundry.com > -----Original Message----- > From: Dash Sam [mailto:[EMAIL PROTECTED]] > Sent: Sunday, November 17, 2002 4:23 PM > To: Juan Pablo Lorandi > Subject: Re: client info > > > > --- Juan Pablo Lorandi <[EMAIL PROTECTED]> wrote: > > Of course, if you're using JSP/Servlets, you can fiddle > > around several methods of HTTPServletRequest that will > > provide the info you need. > > There's a snoop.jsp page that comes with many appservers > > that demonstrates this functionality > > So you will have to "push" the information to your EJB beans, > rather than use code in the beans to "pull" it. > > For example, your web-tier will look at the HTTP headers, > get the IP address, and then pass it on to your EJB bean > in a method call. > > If you have no web-tier, for example you have an applet > that is a client, then it will have to provide the IP address. > > -- Sam > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Web Hosting - Let the expert host your site http://webhosting.yahoo.com =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
