Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / JavaBeans / June 2004

Tip: Looking for answers? Try searching our database.

Store data per web service client even in a J2EE stateless session bean, possible?

Thread view: 
Merten Schumann - 03 Jun 2004 15:28 GMT
Hello,

doing my first steps in J2EE, coming from WebMethods GLUE ...

Is it possible to identify in a stateless session bean on the web server the
web service client?

I need to store some data PER client. When the same client comes back to any
session bean instance I want to find the data exactly for this client.
I know this is not what stateless session beans are considered for.
Anyway, I would really need it.

Is there a way to certainly identify the web service client? It's
HTTPSessionObject or so which should stay the same as long as the HTTP
session is alive?

Thanx
  Merten
Merten Schumann - 07 Jun 2004 13:30 GMT
Hm, no answer.
I found that WebSphere and JBoss support implementing web services as
stateful session beans.
Would be nice to have that supported in Sun's reference implementation and
in J2EE at all.

> Hello,
>
[quoted text clipped - 14 lines]
> Thanx
>    Merten


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.