• Post Reply Bookmark Topic Watch Topic
  • New Topic

Removing Stateful Session Bean  RSS feed

 
Hasmitha Ramakrishnan
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a Stateful session bean deployed in a weblogic container.
Gave it a webservice wrapper using axis.
My client app is written in .net c#
Can someone please help me figure out how to remove this stateful session bean when Iam done?
I exposed the ejbRemove in the interface. Which means I can call ejbRemove() from my client app and I know that method is indeed being called. But when I monitor my beans it is still there.
I dont want to use a time out or NRU because of the app specs.
Can someone Please help me find a way to clean this up??
Thanks in advance!
-Hash
 
Marcos Maia
Ranch Hand
Posts: 977
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Hasmitha Ramakrishnan:
I have a Stateful session bean deployed in a weblogic container.
Gave it a webservice wrapper using axis.

WebLogic server, as far as I know, only give support for web services(synchronous or assynchronous) built on top of stateless session beans or a java class. I don't know wich behavior expect if u implement this using statefull session bean I think a better way to implement this is using parameters wrapped in a complex object soap tipe and simulate a statefull session, passing parameters for the stateless session bean.
Another way to do this is building your web service and adding a conversation support to it, conversations in weblogic web services are divided into three phases:
start
continue
finish
one of this solutions should solve u'r problem in a better and standard way.
Take a look at weblogic web services docs at:
http://edocs.bea.com/wls/docs81/webserv/index.html

I exposed the ejbRemove in the interface. Which means I can call ejbRemove() from my client app and I know that method is indeed being called. But when I monitor my beans it is still there.

You shoul'd not do this, it's really against the ejb spcs. the ejbRemove method is a bean method built to be called by the container only. You should use(if u wanna keep this solution) the remove method from the EJBObject Interface to remove the bean.
regards.
 
Hasmitha Ramakrishnan
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you for taking the time to reply
Now I know that webservices with Stateful is not standard. Iam going to try to find an explanation as to why they wont allow this (There should be a good reason, right?). I would not have used a stateful bean if I dint have to build a tree with the data I was getting from the DB and apply diff calculations on diff nodes with specific response time requirements
Thanks again!
PS: Does anyone have a quick dirtly solution just to get me by for a while?
 
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!