locked
Web Service approach RRS feed

  • Question

  • Hello
    I am .NET 1.1 Web service developer.
    On a new project I am interfacing with a java programmer.

    He has presented me with a question I don't understand. 

    "Are we planning to implement XML based approach on the interface or are we planning to use object based and will have specific methods exposed for each function?"

    I don't understand what he means because all I know is an XML based approach.
    He believes .NET 2.0 and greater affords me a different approach?  Does it?  All I understand is XML in and XML out !  Have not coded in 2.0 or 3.5...
    What does he mean (in .NET speak) about an object based approach?  He speaks java and doesn't get .NET!

    If there is a difference is there some simple .NET code I can review to help me?

    Thanks for any clarification 
    Wednesday, September 2, 2009 5:31 PM

All replies


  • A couple guesses
    - He might be talking about WCF data contract serialization: http://msdn.microsoft.com/en-us/library/ms731073.aspx (still just XML)

    - Small chance he is talking about REST http://blog.donnfelker.com/post/How-To-Implement-a-simple-REST-Services-in-WCF-35-Part-1.aspx Again though still XML.


    Tim
    Wednesday, September 2, 2009 7:13 PM
  • When we talk about service oriented integration, we have either document based integration or RPC based integration.
    Now about your query:--
    If you create objects instead of plain XML, there may be chances that you are exposing language centric objects like Datasets in .Net to the outer world.In this case, Java programs will not be able to consume this .Net webservice as they do'n't know what is dataset.
     
    So better go for XML based integration with language independent and application independent data sharing.
    Hope this helps.

    Cheers
    TA123
    ---------------------------------------------------------
    Please mark this as answer if this helps you

    Thursday, September 3, 2009 4:02 PM