Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / September 2004

Tip: Looking for answers? Try searching our database.

SOAPHeader

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Eric - 13 Jul 2004 11:24 GMT
Hi,

I have a WebService client. All the code is generated by VS.NET 2003.
The problem is that some attributes are not generated.
All the attributes in the base class are generated.
But the attribute in the inherited class RFCSending are not.

Is it not possible to use this class structure for a SOAP header?

Thanks
Eric

Definition:
----------------------------------------------------------------------------
------------------
public RFCSending RFCSendingValue;

[System.Web.Services.Protocols.SoapHeaderAttribute("RFCSendingValue",
Direction=System.Web.Services.Protocols.SoapHeaderDirection.In,
Required=true)]

----------------------------------------------------------------------------
------------------

RFCSending is defined like that:

----------------------------------------------------------------------------
------------------
[System.Xml.Serialization.XmlTypeAttribute(Namespace="http://www.xxx")]
[System.Xml.Serialization.XmlRootAttribute(Namespace="http://www.xxx",
IsNullable=false)]
public class RFCSending : sendingType {
   [System.Xml.Serialization.XmlAttributeAttribute("groupe-id")]
   public int groupeid;
}

[System.Xml.Serialization.XmlTypeAttribute(Namespace="http://www.xxx")]
[System.Xml.Serialization.XmlIncludeAttribute(typeof(EFCSending))]
[System.Xml.Serialization.XmlIncludeAttribute(typeof(RFCSending))]
public class sendingType : System.Web.Services.Protocols.SoapHeader {

       /// <remarks/>
       [System.Xml.Serialization.XmlAttributeAttribute("sending-date")]
       public System.DateTime sendingdate;
}
----------------------------------------------------------------------------
------------------
Elena Kharitidi - 02 Sep 2004 07:14 GMT
I am going to guess here that the 'groupeid' attribute is defined in the
schema with use="optional" and type="xs:int", the schema type "int" will be
mapped to CLR primitive type System.Int32, which is a ValueType, so after
an instance of RFCSending is deserialized there is no way to tell if the
groupeid=".." attribute was present in the instance. XmlSerializer employs
xxxSpecified pattern to determine if the satellite xxx member was set or
not. When reading an instance of RFCSending, the groupeidSpecified member
will be set to "true" if the xml instance had the groupeid=".." attribute,
otherwise the value of the groupeidSpecified will be false.  Unfortunately
this means that user is burdened with responsibility of setting the
groupeidSpecified to true if he/she want is to be serialized:

    MyProxy x = new MyProxy();
    x.RFCSendingValue = new RFCSending();
    x.RFCSendingValue.groupeid = 555;
    x.RFCSendingValue. groupeidSpecified = true;

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.