WSE Pop Quiz 2

What happens if you create a vanilla ASMX service that accepts an EndpointReference as an argument? e.g.

// SoapDocument* attrs elided for brevity
// and yes, I started out with wsdl
public class MyWebService : WebService
{
  [WebMethod]  
  public void Accept(EndpointReference e)
  {
    // whatever
  }
}

Try it out. Suggest work arounds in comments if you don't mind. Try them out as well. Let me know how it goes. I came up with a solution, but I wasn't blown away by its beauty or anything. I just thought the reasons for coming up with a work-around were interesting. I'll post it later.

Comments

[JosephCooney]

Passing a string as an argument and constructing a URI from the string, and then an EndPointReference from the URI was the best thing I could think of in my lunch break. XmlElement has a default constructor (and thus can be xml serialized), and is also one of the possible arguements when constructing an EndPointReference - could you use one of those too? All of my playing around with WSE has been with EndPointReferences created from URIs so I'm not aware of what the issues would be when using an XmlElement....ofc I'm not smarter than Don Box so..... (http://integralpath.blogs.com/thinkingoutloud/2004/07/don_box_on_tran.html)