You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by "Michael J. Hudson" <mh...@blueprinttech.com> on 2001/08/11 00:19:04 UTC
After a Generated SOAP Fault, the Call object is DEAD.
After invoking the Call object... and the response generates a fault,
it doesn't seem like I can use the same Call object again to call
any other methods.
I get a "service '' unknown" error for every method I try to call AFTER
I've generated one fault.
I'm using Apache SOAP 2.2 and it's hitting a stateful session bean.
Any ideas?
-------------------------------------
Michael J. Hudson
Software/Framework Engineer
mhudson@blueprinttech.com
cell-phone: 703.362.8039
voice-mail: 703.827.0638 ext. 4786
fax: 703.734.0987
Blueprint Technologies
"Great software starts with great architecture"
http://www.blueprinttech.com
Re: [Solution] After a Generated SOAP Fault, the Call object is DEAD.
Posted by "Michael J. Hudson" <mh...@blueprinttech.com>.
I figured out what's happening...
for some reason, Apache SOAP blows away the FULL target-object-URI when
a fault occurs. When I say "FULL"... I mean the one that holds the
session ID for contacting stateful session beans and the like.
THUS, subsequent invokations of methods on the Call object AFTER a
fault causes "service '' unknown" errors... cause that URI is null.
So... as long as I retrieve the FULL target-object-URI after this
first contact with my bean... and then refresh the Call object's
target-object-URI with this value after a fault... then everything
is fine.
Does anybody know if they've fixed this in any of their nightly builds,
or if they otherwise know about this bug??
--------------------"Michael J. Hudson" wrote:
>
> After invoking the Call object... and the response generates a fault,
> it doesn't seem like I can use the same Call object again to call
> any other methods.
>
> I get a "service '' unknown" error for every method I try to call AFTER
> I've generated one fault.
>
> I'm using Apache SOAP 2.2 and it's hitting a stateful session bean.
>
> Any ideas?
>
> -------------------------------------
> Michael J. Hudson
> Software/Framework Engineer
> mhudson@blueprinttech.com
>
> cell-phone: 703.362.8039
> voice-mail: 703.827.0638 ext. 4786
> fax: 703.734.0987
>
> Blueprint Technologies
> "Great software starts with great architecture"
> http://www.blueprinttech.com
Re: [Solution] After a Generated SOAP Fault, the Call object is DEAD.
Posted by "Michael J. Hudson" <mh...@blueprinttech.com>.
I figured out what's happening...
for some reason, Apache SOAP blows away the FULL target-object-URI when
a fault occurs. When I say "FULL"... I mean the one that holds the
session ID for contacting stateful session beans and the like.
THUS, subsequent invokations of methods on the Call object AFTER a
fault causes "service '' unknown" errors... cause that URI is null.
So... as long as I retrieve the FULL target-object-URI after this
first contact with my bean... and then refresh the Call object's
target-object-URI with this value after a fault... then everything
is fine.
Does anybody know if they've fixed this in any of their nightly builds,
or if they otherwise know about this bug??
--------------------"Michael J. Hudson" wrote:
>
> After invoking the Call object... and the response generates a fault,
> it doesn't seem like I can use the same Call object again to call
> any other methods.
>
> I get a "service '' unknown" error for every method I try to call AFTER
> I've generated one fault.
>
> I'm using Apache SOAP 2.2 and it's hitting a stateful session bean.
>
> Any ideas?
>
> -------------------------------------
> Michael J. Hudson
> Software/Framework Engineer
> mhudson@blueprinttech.com
>
> cell-phone: 703.362.8039
> voice-mail: 703.827.0638 ext. 4786
> fax: 703.734.0987
>
> Blueprint Technologies
> "Great software starts with great architecture"
> http://www.blueprinttech.com