Help with returning a C# object from a web service

[rbjorkquist]

This is my first attempt at writing/using web services, so any and all
comments will be greatly appreciated. With that said, I am also by no
means saying this is the correct either.

I have noticed that when returning a new TPastePart, created and
filled by the web service, that if the "PastePartI D" and "PastePart"
properties do not have "set" accessor methods, their respective data
is not returned, even though the object has contains that
information. So my solution, not one I like mind you, is to put in a
blank "set" method for each.

I have to main questions. First, why does this happen; and secondly,
what's the most appropriate way of doing this?

Thanks in advance,

Randel

//
*************** *************** *************** *************** ************
public class TPastePart{
//----------------------------------------------------------------------
private int FPastePartID;
private string FPastePart;
private string FPastePartNumbe r;
private string FPastePartDescr iption;

//----------------------------------------------------------------------
public TPastePart(){
FPastePartID = 0;

FPastePart = "";
FPastePartNumbe r = "";
FPastePartDescr iption = "";
}

//----------------------------------------------------------------------
public TPastePart(int PastePartID, string PastePartNumber ,
string PastePartDescri ption, string PastePart){

FPastePartID = PastePartID;

FPastePart = PastePart;
FPastePartNumbe r = PastePartNumber ;
FPastePartDescr iption = PastePartDescri ption;
}

//----------------------------------------------------------------------
public int PastePartID{
get{return(FPas tePartID);}
set{}
}

//----------------------------------------------------------------------
public string PastePart{
get{return(FPas tePart);}
set{}
}

//----------------------------------------------------------------------
public string PastePartNumber {
get{return(FPas tePartNumber);}

set{
FPastePartNumbe r = value;
FPastePart = FPastePartNumbe r + " " + FPastePartDescr iption;
}
}

//----------------------------------------------------------------------
public string PastePartDescri ption{
get{return(FPas tePartDescripti on);}

set{
FPastePartDescr iption = value;
FPastePart = FPastePartNumbe r + " " + FPastePartDescr iption;
}
}
}

//
*************** *************** *************** *************** ************
//***** WEB SERVICE
*************** *************** *************** *********
//
*************** *************** *************** *************** ************
//-----------------------------------------------------------------------
[WebMethod(Descr iption="Retriev e the information for the given paste
part ID.")]
public TPastePart PastePart_Get(i nt PastePartID){
TPastePart PastePart = null;
ConnectionStrin gSettings Cs =
ConfigurationMa nager.Connectio nStrings["ECS"];

SqlConnection SqlCon = new SqlConnection() ;
SqlCommand SqlCmd = new SqlCommand();
SqlDataReader SqlReader = null;

try{
SqlCmd.CommandT ext = "ccisp_PastePar t_Get";
SqlCmd.CommandT ype = CommandType.Sto redProcedure;
SqlCmd.Connecti on = SqlCon;
SqlCmd.Paramete rs.Add(new SqlParameter("@ RETURN_VALUE",
SqlDbType.Int,
4,

ParameterDirect ion.ReturnValue ,
true,
((System.Byte)( 10)),
((System.Byte)( 0)),
"",
DataRowVersion. Current,
null));

SqlCmd.Paramete rs.Add(new SqlParameter("@ PastePartID",
SqlDbType.Int,
4,
ParameterDirect ion.Input,
false,
((System.Byte)( 10)),
((System.Byte)( 0)),
"",
DataRowVersion. Current,
PastePartID));

SqlCon.Connecti onString = (string)Cs.Conn ectionString;
SqlCon.Open();
SqlReader = SqlCmd.ExecuteR eader();

if(SqlReader.Ha sRows){
SqlReader.Read( );

PastePart = new TPastePart(SqlR eader.GetInt32( 0), //
PastePartID
SqlReader.GetSt ring(1), //
PastePartNumber
SqlReader.GetSt ring(2), //
PastePartDescri ption
SqlReader.GetSt ring(3)); //PastePart
}//END IF-STATEMENT "if(SqlReader.H asRows)"
}//END TRY-BLOCK
catch(Exception E){
HandleWebExcept ion(E);
}//END CATCH-BLOCK
finally{
SqlCon.Close();
}//END FINALLY-BLOCK

return(PastePar t);
}

//
*************** *************** *************** *************** ************
//***** WEB SERVICE RESULTS
*************** *************** *************** *
//
*************** *************** *************** *************** ************

//WITH "set" ACCESSOR
METHOD********* *************** *************** *******
<TPastePart>
<PastePartID> 1</PastePartID>
<PastePart>46-141 7% Platinum Paste</PastePart>
<PastePartNumbe r>46-141</PastePartNumber >
<PastePartDescr iption>7% Platinum Paste</PastePartDescri ption>
<PasteViscosity ID>1</PasteViscosityI D>
</TPastePart>
//
*************** *************** *************** *************** ************

//WITH OUT "set" ACCESSOR METHOD
*************** *************** ***********
<TPastePart>
<PastePartNumbe r>46-141</PastePartNumber >
<PastePartDescr iption>7% Platinum Paste</PastePartDescri ption>
<PasteViscosity ID>1</PasteViscosityI D>
</TPastePart>
//
*************** *************** *************** *************** ************

[John Saunders [MVP]]

"rbjorkquis t" <rb*********@co ilcraft.comwrot e in message
news:11******** **************@ q5g2000prf.goog legroups.com...

This is my first attempt at writing/using web services, so any and all
comments will be greatly appreciated. With that said, I am also by no
means saying this is the correct either.

I have noticed that when returning a new TPastePart, created and
filled by the web service, that if the "PastePartI D" and "PastePart"
properties do not have "set" accessor methods, their respective data
is not returned, even though the object has contains that
information. So my solution, not one I like mind you, is to put in a
blank "set" method for each.

I have to main questions. First, why does this happen; and secondly,
what's the most appropriate way of doing this?

You've found it. Add the setter.

This is a requirement of XML serialization. You'd have to ask Microsoft why
they require it.
--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer

[rbjorkquist]

On Oct 17, 12:52 pm, "John Saunders [MVP]" <john.saunder s at
trizetto.comwro te:

"rbjorkquis t" <rbjorkqu...@co ilcraft.comwrot e in message

news:11******** **************@ q5g2000prf.goog legroups.com...

This is my first attempt at writing/using web services, so any and all
comments will be greatly appreciated. With that said, I am also by no
means saying this is the correct either.

I have noticed that when returning a new TPastePart, created and
filled by the web service, that if the "PastePartI D" and "PastePart"
properties do not have "set" accessor methods, their respective data
is not returned, even though the object has contains that
information. So my solution, not one I like mind you, is to put in a
blank "set" method for each.

I have to main questions. First, why does this happen; and secondly,
what's the most appropriate way of doing this?

You've found it. Add the setter.

This is a requirement of XML serialization. You'd have to ask Microsoft why
they require it.
--
---------------------------------------------------------------------------*-----
John Saunders | MVP - Windows Server System - Connected System Developer

Hey John,

Thanks for the quick response. But just to make sure I'm
understanding what you are saying. Just add a blank setter method,
like I'm doing is ok? There will be no ill side affects? And, why if
I leave it blank, does it know how to give me the rest of the data? I
mean, I'm not telling it or doing anything special. Actually, I'm not
doing anything.

Thanks again,

Randel

[John Saunders [MVP]]

"rbjorkquis t" <rb*********@co ilcraft.comwrot e in message
news:11******** *************@t 8g2000prg.googl egroups.com...
On Oct 17, 12:52 pm, "John Saunders [MVP]" <john.saunder s at
trizetto.comwro te:

"rbjorkquis t" <rbjorkqu...@co ilcraft.comwrot e in message

news:11******** **************@ q5g2000prf.goog legroups.com...

This is my first attempt at writing/using web services, so any and all
comments will be greatly appreciated. With that said, I am also by no
means saying this is the correct either.

I have noticed that when returning a new TPastePart, created and
filled by the web service, that if the "PastePartI D" and "PastePart"
properties do not have "set" accessor methods, their respective data
is not returned, even though the object has contains that
information. So my solution, not one I like mind you, is to put in a
blank "set" method for each.

I have to main questions. First, why does this happen; and secondly,
what's the most appropriate way of doing this?

You've found it. Add the setter.

This is a requirement of XML serialization. You'd have to ask Microsoft
why
they require it.
--
---------------------------------------------------------------------------*-----
John Saunders | MVP - Windows Server System - Connected System Developer

Hey John,

Thanks for the quick response. But just to make sure I'm
understanding what you are saying. Just add a blank setter method,
like I'm doing is ok? There will be no ill side affects? And, why if
I leave it blank, does it know how to give me the rest of the data? I
mean, I'm not telling it or doing anything special. Actually, I'm not
doing anything.
----------
Yes, just leave a blank setter. This is just a restriction of the
serializer. As long as you don't need to deserialize that type, you'll be ok
with a setter that does nothing.
--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer

[Spam Catcher]

rbjorkquist <rb*********@co ilcraft.comwrot e in
news:11******** *************@t 8g2000prg.googl egroups.com:

Thanks for the quick response. But just to make sure I'm
understanding what you are saying. Just add a blank setter method,
like I'm doing is ok? There will be no ill side affects? And, why if
I leave it blank, does it know how to give me the rest of the data? I
mean, I'm not telling it or doing anything special. Actually, I'm not
doing anything.

You can even set the set to private...

As long as you're not serializing the object BACK to the server, I believe
you can have a private settor.

BTW, were you a Delphi programmer previously?