Please join us at the new JavaWorld Q&A Forums. Your existing login will work there. The discussions here are now read-only.


JavaWorld >> Programming Theory & Practice

Pages: 1
gopid5
stranger


Reged: 05/09/08
Posts: 1
how to handle exception propagation in webservice
      #140877 - 05/09/08 03:20 PM


Hi ,
Is there a way to catch an exception thrown by Webservice server handler?

We have a situation where we need to handle the exception on the client side thrown by the server handler.
We are using Webspehere webservices created thru RAD 7 and clients are generated using axis 2 code generator tool. We generate WSDL from java class rather than Java from WSDL.

We have vague idea that we can use wsld fault mechanism but does not have much implementation knowledge on it.

Any ideas on this will be great help.

Thanks in advance..


Post Extras: Print Post   Remind Me!   Notify Moderator  
hiwa
Carpal Tunnel


Reged: 06/21/03
Posts: 7704
Loc: Japan
Re: how to handle exception propagation in webserv [Re: gopid5]
      #143231 - 05/11/08 06:28 AM

The Saint John Gospel:
In the beginning was the Word

The Web Gospel:
In the beginning was the Request

Web is a pull technology, not a push one. If you have a request at hand, i.e. a session is alive, you could do anything in the output and/or manipulation of the response.

--------------------
*stop cruelty* Annual number of euthanized cats&dogs: US 5M, JP 500K.*for our better karma*


Post Extras: Print Post   Remind Me!   Notify Moderator  
gabec_geo
stranger


Reged: 04/16/07
Posts: 2
Re: how to handle exception propagation in webserv [Re: gopid5]
      #183389 - 09/04/08 10:46 AM

Hello,

I believe that after so much time you have resolved your problem, but maybe another view will make it clearer.

You may alway use WS handlers to log what response message is to be sent back to the client. So if there is a invalid message (not serializable exception, ..), you will find it.

But still there is a server code what you have no control over it (transaction commiting, cleanup, ..). I spent a lot of time finding an incorrect transaction setting for DB access where WAS error log was not very helpful. All the code ran, but at the end the server threw an exception and rolled back. Maybe you should check if all operations may run in the same transaction.. may halp sometimes

gabec


Post Extras: Print Post   Remind Me!   Notify Moderator  
Pages: 1



Extra information
0 registered and 2 anonymous users are browsing this forum.

Moderator:   

Print Topic

Forum Permissions
      You cannot start new topics
      You cannot reply to topics
      HTML is disabled
      UBBCode is enabled

Rating:
Topic views: 6101

Rate this topic

Jump to

Contact us JavaWorld

Powered by UBB.threads™ 6.5.5