You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Lenhart Stefan <St...@rbu.de> on 2002/04/04 10:11:21 UTC

URL and port

Hi everybody!

I'm quite confused about the URL I have to use for the invoke method of the
Call class. In the examples I've found, only the value found in the
<soap:address location=.....> tag of the corresponding WSDL file is used. 

However, when I try this for my own sample WebService, I get a SOAP Fault:
"Missing port information". I tried to add the port Tomcat displays when I
point my browser to the service's URL, i.e. using the URL
"http://localhost:8080/sample/service/PORTNAME_AS_STATED_BY_TOMCAT". It
doesn't work this way either, I'm getting another SOAP Fault: "Internal
server error", but this could be a problem with the service itself, although
it worked fine when I invoked it's methods directly.

Anyway, the big question for me is: Do I have to add the port name to the
URL object in Call.invoke(url, "") or not? If so, why must I and the guys
doing these example service don't have to?

I'm grateful for any hints.
Thanks a lot in advance!

 
Mit freundlichen Gruessen

Stefan Lenhart

R. Boeker Consulting GmbH
Ein Unternehmen der R. Boeker Unternehmensgruppe AG
RBU AG Zweigniederlassung Frankfurt
Mergenthalerallee 77
D-65760 Eschborn

Tel.:	 +49 (61 96) 4 70-883
Fax.:	 +49 (61 96) 4 70-8 90
E-Mail:	 mailto:StefanLenhart@rbu.de
Internet: http://www.rbu.de

Diese eMail enthält möglicherweise vertrauliche und/oder rechtlich
geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese eMail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten diese eMail. Das unerlaubte Kopieren sowie die
unbefugte Weitergabe dieser eMail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.