Subject: SOAP Errors - msg#00021

Previous Message by Date: click to view message preview

SOAP Listeners

Just a general question about SOAP Listeners for all of you. I have written a JAVA SOAP Listener to handle SOAP requests for my web service. I just wondered what the general practice is for listeners. Is it common to write your own listener or are there off the shelf packaged listeners available? What is the recommendation? If you wrote your own listener, what platforms/languages are you using? thanks, Appreciate any input you can provide. You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com.

Next Message by Date: click to view message preview

Re: customized encoding and SOAP interoperability

Customized encoding means you have compromised SOAP interoperability. Is there any reason not to expect so? To foster interoperability you may document well your encoding methods, have readily available implementation and be ready to share it with business partners. Soumen Sarkar. -----Original Message----- From: Neela Lakshminarayan [mailto:lneelaka@xxxxxxxxx] Sent: Thursday, November 14, 2002 4:44 AM To: SOAP@xxxxxxxxxxxxxxxxxxx Subject: [SOAP] customized encoding and SOAP interoperability We have a client communitcating with a Java Servlet through SOAP messages. The SOAP implementation is our own but it does conform to the SOAP specification. Since our response can be very verbose, we decided to compress our messages. For certain reasons, we are unable to use the standard encoding methods such as gZip, deflate, compress etc. We have a customized encoding. We don't like deviating from standards but in this case we had to. My question is - by using a customized encoding, have we terribly compromised SOAP interoperability? Is customized encoding a terrible thing to do? Currently we don't care about being interoperable with other SOAP toolkits - but the requirement might change in the future. Thanks, Neela You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com.

Previous Message by Thread: click to view message preview

SOAP Listeners

Just a general question about SOAP Listeners for all of you. I have written a JAVA SOAP Listener to handle SOAP requests for my web service. I just wondered what the general practice is for listeners. Is it common to write your own listener or are there off the shelf packaged listeners available? What is the recommendation? If you wrote your own listener, what platforms/languages are you using? thanks, Appreciate any input you can provide. You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com.

Next Message by Thread: click to view message preview

Re: SOAP Errors

I think it is advisable that security protocol failures are silently discarded so as not to provide a potential intruder of useful information/feedback. However, it is useful to send an out of band message to the administrator of the security infrastructure of the failure so that an audit trail is produced. Marty -----Original Message----- From: Discussion of implementing SOAP applications today [mailto:SOAP@xxxxxxxxxxxxxxxxxxx]On Behalf Of Paul Faulkner Sent: Thursday, November 14, 2002 12:24 PM To: SOAP@xxxxxxxxxxxxxxxxxxx Subject: [SOAP] SOAP Errors What is the SOAP standard for handling errors. Let say I implement PKI security for my SOAP Web Service and someone sends a message that fails security. Do I reply with an error letting them know this or simply discard the message? Obviously both have merits and pitfalls. The biggest concern I have is someone flooding my webservice with invalid requests and having to reply to each request. What is the industry standard for these situations? You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com.