I'm running into an issue where a .NET client can see the WSDL via Web Reference but once the reference has been imported produces a "Invalid URI: The URI is empty" error message. There's no other description of the error. Because of this, the .NET framework is not able to generate a (C#) object off of this reference. Could this be an issue with the http/jsr181 endpoint(s)? I don't really know where to start to troubleshoot this issue. Any suggestions/advice would be appreciated. Thanks in advance.
-los gnodet wrote: > > Provider endpoints are only used when you want servicemix > to act as a client, i.e. send HTTP requests to an external > web service. A consumer endpoint is sufficient to > expose a jbi service on HTTP. > > On 12/19/06, moraleslos <[EMAIL PROTECTED]> wrote: >> >> Ok, I've seemed to deploy my new WS successfully. My http endpoint >> exposes a >> particular URI that points to my JSR181 endpoint. I can see the WSDL for >> my >> service at the specified locationURI. I have a stupid question. Is this >> service with one http consumer endpoint and one jsr181 endpoint useable >> as >> is, i.e. a client sees this service, invokes the service, and receives >> something back. Or will I need to write a "provider" http endpoint to >> send >> responses? Since the client will be written by someone else in another >> platform, I won't know if I've provided enough for the WS >> invocation/response. Thanks in advance. >> >> -los >> >> >> >> gnodet wrote: >> > >> > Yeah, exactly. >> > >> > On 12/18/06, moraleslos <[EMAIL PROTECTED]> wrote: >> >> >> >> I think I know where you're getting at so let me summarize. I >> currently >> >> have >> >> a jsr181 endpoint. I want to expose this as a WS so I think I have to >> >> use >> >> servicemix-http and link the http endpoint to the jsr181 endpoint. Am >> I >> >> close? >> >> >> >> -los >> >> >> >> >> >> >> >> gnodet wrote: >> >> > >> >> > WSDL for http endpoints can be retrieved if you point your >> >> > web browser to the URI where the service was deployed. >> >> > For example, if you deploy an http endpoint to >> >> > http://0.0.0.0:8192/MyService >> >> > you can browse to http://0.0.0.0:8192 and see the list of >> >> > available services and access their wsdls. >> >> > >> >> > For internal endpoints, the wsdls can be retrieved using >> >> > a jmx console (jconsole from jdk or mc4j or any other one). >> >> > >> >> > On 12/18/06, moraleslos <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> I think I've deployed my jsr181-annotated service appropriately. >> >> >> However, >> >> >> when working with a .NET client, where do I go to find the WSDL? >> I've >> >> >> used >> >> >> a target namespace for my WS like this: >> >> >> http://ws.test.music.com/music/service/MusicService >> >> >> >> >> >> How do I find this out? I've tried a variety of >> localhost:1099/.... >> >> but >> >> >> I >> >> >> can't seem to find the WSDL. Any suggestions? Thanks in advance. >> >> >> >> >> >> -los >> >> >> -- >> >> >> View this message in context: >> >> >> >> >> >> http://www.nabble.com/retrieve-WSDL-from-running-smx-tf2841762s12049.html#a7934623 >> >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> > >> >> > >> >> > -- >> >> > Cheers, >> >> > Guillaume Nodet >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/retrieve-WSDL-from-running-smx-tf2841762s12049.html#a7936305 >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> > -- >> > Cheers, >> > Guillaume Nodet >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/retrieve-WSDL-from-running-smx-tf2841762s12049.html#a7949682 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/retrieve-WSDL-from-running-smx-tf2841762s12049.html#a7956197 Sent from the ServiceMix - User mailing list archive at Nabble.com.
