> Thanks for your comments and suggestions, especially on your day off! > > > Form (3) is more work, and while the server itself does not > directly > > support it, it can probably be done > > I am a little surprised that MLS doesn't support this > natively. Is there any plans to build a WS-* interface into > MLS.
I'm not the right person to comment on future product plans. However, I think it's safe to say that the people who pay attention to this will be reading this thread and will take your suggestions into account. > > One starting point might be the SOAP Router contributed by the > > community and found a ways down the page here: > > http://developer.marklogic.com/code/ > > That was certainly interesting to look at and got me > thinking; however, I need much more than what is available > from that contribution. Specifically, it would be nice to be able to: > > * Create a bunch of XQuery functions in a module and indicate > that they all should be exposed as a SOAP Web service > * Configure the binding and endpoint information in the MLS > administration UI > * Allow service consumers to access the module in such a way > that MLS would automatically generate the WSDL (e.g., by > pulling up a URL like > http://localhost/myGoodXQuery.xqy?wsdl) > * Allow service consumers to send messages to this endpoint > and have MLS receive and dispatch them to the appropriate > XQuery function. I understand your situation. Historically, natively supporting SOAP services has not been a priority across our customer base, which is why it's not currently in the product. I don't honestly know if that's changing or not - your email is one piece of evidence that is may be. Cheers ian _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
