You'd have to put JMS classes on the client, you'd have to worry about transports (perhaps socket is not an option because of firewalls), and the information would be asynchronic, which also means you'd still would have to associate a JNDI session with the info that comes from JMS. That option would be (1), the client willingly pushes the info into the server. But I don't perceive it as trivial unless the requirements are disclosed further.
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: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED]] On Behalf Of Saminathan > Balasundaram > Sent: Tuesday, November 19, 2002 11:10 AM > To: [EMAIL PROTECTED] > Subject: Re: client info > > > Can this thing not possible by some simple way like > using JMS Q's? > > Regards > Saminathan. > ----- Original Message ----- > From: Juan Pablo Lorandi <[EMAIL PROTECTED]> > Date: Tuesday, November 19, 2002 3:25 am > Subject: Re: client info > > > 1) push it from the client. > > 2) Use Web Services as transport (since they're mounted on top of > > Servlets/JSP you'll be able to get that info from the client). > > 3) Write your own JNDI implementation. > > > > For all solutions but 1 (the client willingly reveals the info), > > there'salways the possibility to fail, for proxies/firewalls might > > conceal the IP info(and in many cases the "real" IP is not a public > > IP). > > > > HTH, > > > > 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: Metrona D'souza [mailto:[EMAIL PROTECTED]] > > > Sent: Monday, November 18, 2002 4:59 AM > > > To: Juan Pablo Lorandi > > > Subject: Re: Re: client info > > > > > > > > > Well its true that if we were using either JSP/Servlets we could > > > fiddle around get such info.. but the fact is our client > is a destop > > > swing client and the middle tier is EJB ..in such a setup > what would > > > be the idle way to get client info.. > > > > > > thanks > > > > > > ----- Original Message ----- > > > From: Juan Pablo Lorandi <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Monday, November 18, 2002 4:16 AM > > > Subject: Re: client info > > > > > > > > > > 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". > > > > > > > > > > > ============================================================== > ========== > === > > 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". > > > > > > ============================================================== > ============= > 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". > > =========================================================================== 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".
