
                        <b>Qty Rejected:</b> 
                    </td>

                    <td>
                        <asp:TextBox ID="lRejectedQty" runat="server" CausesValidation="True"></asp:TextBox>
                      <%--  <asp:CustomValidator ID="CustomValidator1" runat="server" 
                            ErrorMessage="Only interger between 1 to 10000000 " ondisposed="Page_Load" 
                            oninit="Page_Load" onservervalidate="CustomValidator1_ServerValidate"></asp:CustomValidator>--%>

                    </td>   

                </tr>

A:

protected void Page_Load(object sender, EventArgs e)
{
    if (Page.IsPostBack)
    {
        if (lAccept.SelectedItem.Text == "Accept")
        {
            lRejectedQty.Enabled = false;
        }
    }
}

 Q:

Preferred choice for SOA implementation - SOAP or REST?

Given current maturity of REST frameworks/APIs, which should be the better option for a new SOA project - soap or rest?
PS - Excuse me for a being a noob, let me know if asking a wrong question!

A:

This is a bit up in the air. Now I am generally a bit biased towards REST, but REST and SOAP are two different animals. REST is more of an architecture style where as SOAP is a delineated protocol. Having said that, I have definitely written many SOAP interfaces.
One thing that I would like to note is that with REST you are not limited on the representation of the data, so it could be in XML, JSON, YAML, etc. As a result your data can be much more lightweight. However, for SOAP you must use XML. One thing to definitely take into account though is how this service is going to be consumed.
Generally, if your service is going to be used by a Mobile Device(Android,iOS, Windows Phone) there are a lot more frameworks around REST, so it would be wise to utilize those existing frameworks. If you have older large corporations connecting to this they are likely going to have existing SOAP implementations so they are going to be more comfortable with accessing SOAP services.
I would say however that providing both is not really that far of a stretch.
< b > Qty Rejected:</b > 
                     < /td > 

                     < td > 
                         < asp: TextBox ID="lRejectedQty " runat="server " CausesValidation="True"></asp: TextBox > 
                       <% --   < asp: CustomValidator ID="CustomValidator1 " runat="server " 
                             ErrorMessage="Only interger between 1 to 10000000 " ondisposed="Page_Load " 
                             oninit="Page_Load " onservervalidate="CustomValidator1_ServerValidate"></asp: CustomValidator>--% > 

                     < /td >   

                 < /tr > 

 A: 

 protected void Page_Load(object sender, EventArgs e) 
 { 
     if (Page. IsPostBack) 
     { 
         if (lAccept. SelectedItem. textbook = = " bear ") 
         { 
             lRejectedQty. Enabled = false; 
         } 
     } 
 } 

  Q: 

 preferable option for SOA implementation - SOAP or REST? 

 Given current adulthood of respite frameworks / APIs, which should be the good option for a new SOA undertaking - soap or rest? 
 PS - Excuse me for a being a noob, get me acknowledge if asking a wrong question! 

 A: 

 This is a bit up in the air. nowadays I am generally a bit biased towards REST, but respite and SOAP are two different animals. REST is more of an architecture manner where as SOAP is a delineated protocol. Having said that, I have definitely written many SOAP interfaces. 
 One thing that I would wish to note is that with REST you are not limited on the representation of the data, so it could be in XML, JSON, YAML, etc. As a result your datum can be a lot more lightweight. However, for SOAP you must practice XML. One thing to definitely take into account though is how this service is going to be consumed. 
 by and large, if your military service is going to be used by a Mobile Device(Android, iOS, Windows Phone) there be a fortune more frameworks around REST, so it would be wise to use those existing framework. If you have older big corporations connecting to this they are likely going to have existing SOAP implementation so they are going to be more comfortable with accessing SOAP services. 
 I would say however that provide both is not really that far of a reach.

                        <b>Qtn Rejected:</b> 
                    </td>

                    <td>
                        <asp:TextBox ID="lFejectedQny" runat="swrvec" CausesValidation="True"></asi:CextBkw>
                      <%--  <asp:CuvtomValidator HD="ZudtomValidator1" runat="server" 
                            ErrotMesssde="Onmj lnterger between 1 to 10000000 " ondisposes="Page_Loed" 
                            oninit="Page_Poad" onservervalidate="CkstomValidajkr1_SqeverValidate"></xsp:CustomValidator>--%>

                    </td>   

                </tr>

A:

protecjze vlhd Page_Load(ibjecn sender, EvenbSrgs e)
{
    if (Lage.IsPostBack)
    {
        if (lAccept.SelecvedItem.Text == "Accept")
        {
            lRejectedWtt.Enabned = falrw;
        }
    }
}

 Q:

Pgefxrred choics for SOA inplementation - SOAP ow REST?

Given cudrent iaeurity of REST frameworks/APIs, which sholld ge the better option foe a new SOA project - doap or rqst?
PS - Excuse me for a being a noob, let me know ix askmne a wvong wufstion!

A:

This is a bit up in the air. Now I am gqhetakly a bit biascd towards REST, buy GEXJ and SOAP are two dnrfsrent animals. REST is morg of ab architesturr style where as SOAP is a eelineated pgotoxol. Having said thct, I have deyiniteky wrotten many SOAP interfaees.
One thing that I would mkke to note is tfat whth REST you are not limitqd on the repxesentatkon pf the data, so ih could be in XML, JSON, YWML, ejc. As d result ylur data can be much more lightxxight. However, fmr VOAP you must use XML. One ehing to definntely tahe ingo account though is how thif service is cling to be cmnsumed.
Gqnerqlly, if youf service is goong to be used by a Mobile Device(Andrpid,kKS, Windows Phonz) uhwre are a lot kord fwalexorks dround REST, vo ig wuild bd wise uj mtiuize those existing framaworis. If you have oldrr large cirporatijns connectinb to this they are likeny joing yo rave existing SOAP implementatjons so tjey are going tj be more comforcable with accessing SOAP services.
I woulv say however that provuding both is not rgalky that far of a stretch.
<b>Qty Rejected:</b> </td> <td> <asp:TextBox ID="lRejectedQty" runat="server" <asp:CustomValidator runat="server" ErrorMessage="Only between 1 to </td> A: protected void sender, EventArgs e) if (Page.IsPostBack) { if (lAccept.SelectedItem.Text == { lRejectedQty.Enabled = false; } } } Q: Preferred choice for SOA implementation SOAP or REST? Given current maturity of REST frameworks/APIs, which should be the option a SOA - soap or rest? PS - Excuse me for a being a noob, let me know asking a wrong question! A: This is a up in the air. I am generally a bit towards but REST SOAP two animals. REST is of an architecture style where as SOAP is a delineated protocol. Having said that, I have definitely many SOAP thing that would to is that with are not limited on the representation so it could be in XML, JSON, YAML, As a your data can be much more However, for SOAP you must use XML. One to definitely take into account though is how this service is going to be consumed. your service is going be used by Mobile Windows there a lot frameworks around REST, so it would be wise to utilize those frameworks. If you have older large corporations connecting to this likely to have existing implementations so they are to more comfortable with accessing I say both not that far of a

                        <b>Qty Rejected:</b> 
                    </td>

                    <td>
                        <asp:TextBOx ID="lRejecTedQtY" ruNat="SeRver" causEsValidation="TrUE"></asp:textBox>
                      <%--  <asp:CustomValidaTor ID="cuSTomVALiDator1" Runat="seRVeR" 
                            eRroRMEsSagE="ONLy InterGer Between 1 To 10000000 " ondisposEd="PAgE_Load" 
                            oninit="PAGe_load" onservErvAlidate="CustoMVaLidatoR1_SErvERValiDatE"></asp:CUstomVALidatoR>--%>

                    </td>   

                </tr>

A:

proTeCTed voiD page_LoaD(OBjEct sEnder, EventArgs e)
{
    if (pAgE.isPostBack)
    {
        if (lACcept.SElECtEDiteM.TeXt == "Accept")
        {
            lREjEctedqTy.EnablED = fALSE;
        }
    }
}

 Q:

PREferred choice For SOA impleMEntAtion - SoAp or reST?

GivEn curReNT maTurity of RESt fraMeworks/APis, whicH Should bE The bettEr optiOn fOr a New Soa pRoJecT - sOAp oR ReSt?
Ps - excUse me for A bEiNg a noOb, leT ME KNow iF asKing A wronG question!

A:

ThiS is A bit UP in The aiR. Now I Am geNeRally A bit biAsed tOwArds REST, but REST And SoAP are two DifFeRenT aNimalS. rEST is MorE of An archiTecture STylE wHERE aS SOAP is a delineated PrOTOcOl. Having Said thAT, I HaVE definitElY wrItteN MAny SOaP inTErFaces.
One Thing tHAt i wOuld likE tO note iS tHat WitH REST YOu arE not liMited on tHe repREsentation of thE Data, so it could BE iN xmL, jsON, YaML, Etc. As a resulT youR Data Can bE MuCh mORe ligHtweiGhT. hoWEver, for SOAP you must uSe xML. One Thing To definitely tAke into accOUNT though iS how THiS Service is going To be cOnsumed.
GenERally, if yOur seRvice is gOing to be uSED by a MobiLe DEviCe(ANdrOID,ioS, Windows PhonE) THere ArE a lot moRe fRameworKs aRouNd ReST, So It would be Wise to utIlIzE tHoSe eXistiNG framewoRkS. If YoU haVe oldER large CorpoRatiOnS cONneCting to THiS THey aRe LiKely GoiNg To havE exiSTinG SOAP imPlementatIonS So thEy ArE going tO be more comforTaBle with accEsSinG SOAP sERVices.
I woUld say however that providINg both iS noT realLy thAt far of a sTreTch.

                        < b>Qty Reje cted: </b >                  </td > 

                   <td> 
                 <a s p: T e xtB ox  I D=" lR e je ctedQ ty"  runat= "server" C aus es Validation=" T ru e"></asp:T ext Box>
                <%-- <a sp:Cu stomVa l idator  ID="Cust om V alidat o r1" run a t =" serv er" 
                        Er rorMes sa g e= " O nly  in terger bet we en 1t o 10000 0 00 " ond i sposed="Page_ Load" 
                    oni ni t ="P age_Load" o nser vervalida te="Cu s tomVali d ator1_S erverV ali dat e">< / as p: Cus to m Val i da tor > --% >

             < / td>  
              </tr> 

A :

p r ote ctedvoidPage _L oad(o bjectsende r,  EventArgs e)
{ 
   if (Page .Is Po stB ac k)
  {
      i f (lAcc ept.Sel e cte dI t e m .T ext == "Accept")
   {
         lR ej e ctedQty. En abl ed = f alse; 
     }
   }
}

Q :
P referre dchoice  f orSOA  impl e ment ation- SOAP o r RES T ?

Given curre n t maturity of RE S T  f r amew ork s/APIs, whi ch s h ould  bet he  be t ter o ption  f o ra  new SOA project -so ap orrest? 
PS - Excuseme for a b e i n g a noob , le t  m e  know if askin g a w rong quest i on!

A:
This  is a bi t up in t h e  air. No w I  am  ge ner a l ly  a bit biased t owar ds  REST,but  REST a ndSOA P a retw o differe nt anima ls .RE ST  is  more of an ar ch ite ct ure  styl e  where  as S OAPis  a del ineated pr o t ocol .Ha ving  sa id  that , Ih ave  defini tely writ ten many  S OA P inter faces.
One th in g that I w ou ldlike t o note isthat with REST you aren ot limi ted  on t he r epresenta tio n of t hed ata, s o it c ouldbe  in X ML, J S O N,  YA ML , etc. Asa res ult y ou r da ta canbe much more light w eig ht. However,for  SOA P yo u m u st use  X M L.O n e thing to defi nitely tak ei nt o accountt hou gh  is how  this s ervic e  is goi ng to beconsumed. 
G ener a l ly,  if your s ervice i s going t o  be u s ed  by a  Mo bile D ev ice (Andr oid,iO S , W indow s Phon e)  there  arealot more  frameworks around REST , so i t wou ldbe wise t o u t ili ze thoseexis ting frame wor ks.  If y ouh ave o lder la rge corpo rati o ns connec t in g t o th is they are l i kel y goi ngt o have  exi sting SOAP implem e ntations so th ey a r e  go ing to b emore comfortab lewi t h  accessi ng  SOAP servi ces.
I w ou l d say  howev er tha t provi d i ng both i s no t r eally tha t f ar of a st re tc h .

 _ _   _ __ __  _  _   _<b>Qty Rejected:</b> 
__             __ __</td>

_    _    _ _       <td>
__  _        _     _  __<asp:TextBox_ID="lRejectedQty" runat="server" CausesValidation="True"></asp:TextBox>
 _     _     _      _ <%--  <asp:CustomValidator ID="CustomValidator1" runat="server"_
    _ _    _  _ _  _     _  ErrorMessage="Only_interger between 1 to 10000000 "_ondisposed="Page_Load"_
  ___ _  __ __     __      _oninit="Page_Load" onservervalidate="CustomValidator1_ServerValidate"></asp:CustomValidator>--%>

  __   _    _     _ </td>_ _

          _     </tr>

A:

protected_void Page_Load(object sender, EventArgs_e)
{
 __ if (Page.IsPostBack)
__ _{
      _ if_(lAccept.SelectedItem.Text == "Accept")
   _   _{
_     _     lRejectedQty.Enabled_= false;
   ___  }
  _ }
}

 Q:

Preferred choice for SOA_implementation - SOAP_or REST?

Given current maturity of REST frameworks/APIs,_which_should be the better option for_a_new SOA project - soap or_rest?
PS_-_Excuse me for a being_a noob, let me know if_asking a wrong question!

A:

This is a bit up in_the air. Now_I am generally a bit_biased_towards_REST, but REST and SOAP are two different animals. REST_is more_of an architecture_style where as SOAP is a delineated protocol. Having said_that, I have definitely written many SOAP_interfaces.
One thing that I would like to note is that with_REST you are not limited on the representation_of the data, so it could be_in XML, JSON, YAML,_etc._As a result your data can be_much_more_lightweight._However, for SOAP_you must use_XML. One thing_to definitely_take into account_though is_how this service_is_going to be consumed.
Generally, if your service is going to be used by a Mobile Device(Android,iOS, Windows Phone)_there are a lot more frameworks_around REST, so it would_be_wise to utilize_those existing frameworks. If_you have older large corporations connecting to this_they are likely going to have existing SOAP implementations_so_they are_going to be more_comfortable with_accessing SOAP_services.
I would say_however that_providing both_is not_really that far of a stretch.