 | |
Preventing Escapes in Post
ASP.net Web Services microsoft.public.dotnet.framework.aspnet.webservices
 |
| | Thread Tools | Search this Thread | Display Modes |
#11
 
| |||
| |||
|
Re: Preventing Escapes in Post -
08-30-2007
, 12:55 AM
.|
From: "KBSTours" <kbstours (AT) kbstours (DOT) com References: <7B84F435-B90B-40F7-8DF8-77C419164289 (AT) microsoft (DOT) com OiPtxRA6HHA.4584 (AT) TK2MSFTNGP03 (DOT) phx.gbl |
<O0UuveE6HHA.1148 (AT) TK2MSFTNGP05 (DOT) phx.gbl>
<X#gO#$F6HHA.4200 (AT) TK2MSFTNGHUB02 (DOT) phx.gbl>
<91A8CA6E-D03E-4179-8CF2-6EA84BEB5D1F (AT) microsoft (DOT) com>
<JlIX0me6HHA.5608 (AT) TK2MSFTNGHUB02 (DOT) phx.gbl>
Quote:
|
In-Reply-To: <JlIX0me6HHA.5608 (AT) TK2MSFTNGHUB02 (DOT) phx.gbl Subject: Re: Preventing Escapes in Post Date: Wed, 29 Aug 2007 22:11:48 -0400 Lines: 226 Message-ID: <A9559244-C3D8-48B3-99AD-A3C02C6A96E6 (AT) microsoft (DOT) com MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Windows Mail 6.0.6000.16480 X-MS-CommunityGroup-PostID: {A9559244-C3D8-48B3-99AD-A3C02C6A96E6} X-MS-CommunityGroup-ThreadID: 8FF02BD5-84BB-4955-BB03-97C4F51154A0 X-MS-CommunityGroup-ParentID: ABC1F4AE-F1AE-4693-AECB-7ABB5A25C792 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16480 Newsgroups: microsoft.public.dotnet.framework.aspnet.webservic es NNTP-Posting-Host: ool-4353afab.dyn.optonline.net 67.83.175.171 Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP04.phx.gbl Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.dotnet.framework.aspnet.webservic es:1435 X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservic es Thanks Steven, I was actually looking for answer and you've given that to me. At least I do not need to look for more. I also during that time, given up and started developing by my own posting as I didn't see any chance. Thanks for the information. -- CTO www.kbstours.com "Steven Cheng[MSFT]" <stcheng (AT) online (DOT) microsoft.com> wrote in message news:JlIX0me6HHA.5608 (AT) TK2MSFTNGHUB02 (DOT) phx.gbl... Thanks for the reply, So based on your further description, I know that the java webservice actually expect a webservice SOAP message which contains an XML fragment (which is not escaped) as part of the SOAP body itself. I'm afraid this doesn't quite conform to XML webservice standard. Because for any method's data(parameters or return value) ,if it contains particular charaters, it should be escaped. For example, the SOAP body xml document is used to represent a request message of a method call, however, if your parameters data is a XML fragment and not escaped, how can we know which part of the xml document is the method body and which part are parameters data? Therefore, for the scenario here, I think it would be better to manually post the XML soap message through some network components such as HttpWebRequest as it can let you freely control the underlying tranfered message data. How do you think? Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- From: "KBSTours" <kbstours (AT) kbstours (DOT) com Hi Steven, The webservice (not the native .NET webservice) which is written in Java is expecting the string in XML format without being escaped. Its not my service, I am just trying to consume it. So how can I customize it in the proxy class? What are the basics? Are there any samples or guides? -- CTO www.kbstours.com "Steven Cheng[MSFT]" <stcheng (AT) online (DOT) microsoft.com> wrote in message news:X%23gO%23$F6HHA.4200 (AT) TK2MSFTNGHUB02 (DOT) phx.gbl... Thanks for John's input. Hello SevDer, I agree that the problem should be quite specific to the service and its requirement on the SOAP message format. Would you provide some further information on the service(such as the format and structure of the SOAP message it expects from client). Normally, for any string value inside XML document(include SOAP envelope), it have to escape those special characters so as to ensure the validity of the document. If the customzation requests for your scenario does be reasonable, we may look for some ways to customize the client proxy class. Please feel free to post here if there is anything we've missed. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscripti...ult.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscripti...t/default.aspx. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- From: "John Saunders [MVP]" <john.saunders at trizetto.com References: <7B84F435-B90B-40F7-8DF8-77C419164289 (AT) microsoft (DOT) com OiPtxRA6HHA.4584 (AT) TK2MSFTNGP03 (DOT) phx.gbl 7267F6E2-FD37-4E29-84F2-55937C3B6D13...soft (DOT) com Subject: Re: Preventing Escapes in Post Date: Sun, 26 Aug 2007 21:14:58 -0400 Lines: 58 Organization: The TriZetto Group, Inc. MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Message-ID: <O0UuveE6HHA.1148 (AT) TK2MSFTNGP05 (DOT) phx.gbl Newsgroups: microsoft.public.dotnet.framework.aspnet.webservic es NNTP-Posting-Host: pool-71-184-5-216.bstnma.east.verizon.net 71.184.5.216 Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP05.phx.gbl Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.dotnet.framework.aspnet.webservic es:1413 X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservic es "SevDer" <sevder (AT) newsgroup (DOT) nospam> wrote in message news:7267F6E2-FD37-4E29-84F2-55937C3B6D13 (AT) microsoft (DOT) com... Hello John, Thanks for the reply. I think you should check this again. I've learned that .NET actually escapes the inner XML to prevent bad XML forming on some cases. And as far as I learned this is the behavior of .NET not the way that I use. Additionally the otherway around problem is there too. For your webservice to work with other applications, you will need to escape all received inner XMLs as they (like Java) send it as nonescaped form. Also I added as web reference and I am trying to make the webreference to work not any other way. If I cannot make this working, then I will have to POST using regular HTTP Post and not use wsdl reference. And their WSDL defined method calls does not accept structured objects but simple and generic object which actually is simple XML. The bottom line is, I am just trying to learn if there is a way for NET to not to escape my request XML while sending over! I promise you that, as a general rule, .NET doesn't prevent people from using XML by escaping it. You are clearly using it in a way that other developers do not use it - they are succeeding and you are failing. Please post some code showing us how you are using XML. Among other things, your mention of "inner xml" is frightening. You are doing something very strange. Please look at some of the following links on Web Service basics. Overview of XML Web services: http://msdn2.microsoft.com/en-us/library/7bkzywba.aspx A walkthrough of building a basic XML Web service: http://msdn2.microsoft.com/en-us/library/7hs6sw69.aspx A walkthrough of building a basic client application: http://msdn2.microsoft.com/en-us/library/hk7y1596.aspx Serializing objects with XML web services http://msdn2.microsoft.com/en-us/library/564k8ys4.aspx -- John Saunders [MVP] |
|
« Previous Thread
|
Next Thread »
| Thread Tools | Search this Thread |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.