Thomas,

That�s a matter of how the wsdl is generated. The "mobile", or better, the
interface part of the wsdl is captured by
the <portType/>. The immobile part, rather, the instance of the web service
running on a particular machine
is captured by the <binding/>.

Currently there is no modular way to separate both informations in distinct,
reusable files. But you could easily change
the constructor of the .Net generated stub classes ... the target url is set
there. 

CGJ

-----Urspr�ngliche Nachricht-----
Von: Thomas Phan [mailto:[EMAIL PROTECTED]] 
Gesendet: Mittwoch, 12. Juni 2002 15:47
An: [EMAIL PROTECTED]
Betreff: Re: AW: [JBoss-user] JBoss.net: AXIS engine could not find a target
service


Hi Dr Jung,

FYI, I got my web service working :D

The reason why it didn't work was because I put my methods in the local EJB
interface (instead of the remote one). It was a careless mistake!

I've one more question about location transparency: Currently, we specify
our web service server, say http://localhost:8080, in the .NET client. If
we'd like to switch the server service to another server, say
http://net.jboss.org:8080, we need to re-add the web reference, and
re-complie the client program. Is there a way to change the server's (or a
directory server, similar to the RMI registry) location anytime during the
client's run-time?

Thanks

Thomas

----- Original Message -----
From: "Thomas Phan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 12, 2002 4:06 AM
Subject: Re: AW: [JBoss-user] JBoss.net: AXIS engine could not find a target
service


> Hi Dr Jung,
>
> I got my web services deployed successfully. The problem was due to my 
> web-service.xml, and my jndi setting, sorry. Thanks for your lead :)
>
> ---
> Now, http://localhost:8080/axis/services/Region?wsdl gives:
>
>   <?xml version="1.0" encoding="UTF-8" ?>
> - <wsdl:definitions 
> targetNamespace="http://localhost:8080/axis/services/Region";
> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:intf="http://localhost:8080/axis/services/Region";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> xmlns:impl="http://localhost:8080/axis/services/Region-impl";
> xmlns="http://schemas.xmlsoap.org/wsdl/";>
>   <wsdl:portType name="Region" />
> - <wsdl:binding name="RegionSoapBinding" type="intf:Region">
>   <wsdlsoap:binding style="rpc" 
> transport="http://schemas.xmlsoap.org/soap/http"; />
>   </wsdl:binding>
> - <wsdl:service name="RegionService">
> - <wsdl:port name="Region" binding="intf:RegionSoapBinding">
>   <wsdlsoap:address 
> location="http://localhost:8080/axis/services/Region";
/>
>   </wsdl:port>
>   </wsdl:service>
>   </wsdl:definitions>
>
> and http://localhost:8080/axis/services/Hello?wsdl gives:
>
>   <?xml version="1.0" encoding="UTF-8" ?>
> - <wsdl:definitions 
> targetNamespace="http://localhost:8080/axis/services/Hello";
> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:intf="http://localhost:8080/axis/services/Hello";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> xmlns:impl="http://localhost:8080/axis/services/Hello-impl";
> xmlns="http://schemas.xmlsoap.org/wsdl/";>
>   <wsdl:portType name="Hello" />
> - <wsdl:binding name="HelloSoapBinding" type="intf:Hello">
>   <wsdlsoap:binding style="rpc" 
> transport="http://schemas.xmlsoap.org/soap/http"; />
>   </wsdl:binding>
> - <wsdl:service name="HelloService">
> - <wsdl:port name="Hello" binding="intf:HelloSoapBinding">
>   <wsdlsoap:address 
> location="http://localhost:8080/axis/services/Hello";
/>
>   </wsdl:port>
>   </wsdl:service>
>   </wsdl:definitions>
>
> These WSDLs look completely different from the one generated using the 
> command line java2wsdl, any idea?
>
> And the .NET client gets the below exception, while I use 
> wsdlsoap:address location=http://localhost:8080/axis/services/Region
>
> ************** Exception Text **************
> System.Web.Services.Protocols.SoapException: Method not found Method 
> name = getRegion Service name = Region
>    at
>
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient
> Message message, WebResponse response, Stream responseStream)
>    at 
> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters)
>    at esb.RegionReference.RegionBeanService.getRegion(Int32 in0) in
> D:\dev\esb\Web References\RegionReference\Reference.cs:line 78
>    at esb.RegionForm.LoadButton_Click(Object sender, EventArgs e) in
> d:\dev\esb\regionform.cs:line 204
>    at System.Windows.Forms.Control.OnClick(EventArgs e)
>    at System.Windows.Forms.Button.OnClick(EventArgs e)
>    at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
>    at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
> button, Int32 clicks)
>    at System.Windows.Forms.Control.WndProc(Message& m)
>    at System.Windows.Forms.ButtonBase.WndProc(Message& m)
>    at System.Windows.Forms.Button.WndProc(Message& m)
>    at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
>    at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
>    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
> IntPtr wparam, IntPtr lparam)
>
> Thanks
>


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/

_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to