all groups > dotnet web services enhancements > december 2005 >
You're in the

dotnet web services enhancements

group:

VBA access to WSE web service?


VBA access to WSE web service? Bradley Plett
12/12/2005 9:48:34 AM
dotnet web services enhancements:
I have built a web service using WSE that uses "soap.tcp" as the
transport. Is it possible to access this web service from VBA using
the standard soap client (SoapClient30) (i.e. the stuff that's
included with the "Web Service References Tool")? If so, how?

When I use the "Web Service References Tool" to generate the code to
access the web service, it generates the following:
--------------------------------------------------
Private sc_ClientComponentServic As SoapClient30
Private Const c_WSDL_URL As String = "http://localhost/myapp.wsdl"
Private Const c_SERVICE As String = "ServiceName"
Private Const c_PORT As String = "ServicePort"
Private Const c_SERVICE_NAMESPACE As String = "http://tempuri.org/"
..
..
..
Set sc_ClientComponentServic = New SoapClient30
sc_ClientComponentServic.MSSoapInit2 c_WSDL_URL, str_WSML, c_SERVICE,
c_PORT, c_SERVICE_NAMESPACE
--------------------------------------------------
My web service is at "soap.tcp://localhost:8081/myapp", and that
endponit works just fine when calling from a WSE client. However, I
can't get VBA (in this case hosted in Access) to talk to it. I've
tried changing the c_WSDL_URL to "soap.tcp", but then I get an error
saying "the specified protocol is unknown."

Any help would be appreciated!

Thanks!
RE: VBA access to WSE web service? stcheng NO[at]SPAM online.microsoft.com
12/13/2005 2:31:14 AM
------=_NextPart_0001_76F39FE7
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi Bradley,

Welcome to webservice newsgroup.
Regarding on the calling WSE protected XML Webservice through Office
WebService toolkit question, based on my understanding, this is not
supported due to the limitation of the Office webservice toolkit ....
First, the Tcp tranport channel is specific to the WSE components while
most of the webservice components only support HTTP as the transport
layer......
Also, even office toolkit support HTTP, since the WSE component protect the
xml webservice's SOAP message by apply encryping/signing policy, this is
also what office toolkit can not do so far. So I think we can only call
normal xml webservice over http directly through office webservice toolkit
currently...

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
From: Bradley Plett <plettb@newsgroup.nospam>
Subject: VBA access to WSE web service?
Date: Mon, 12 Dec 2005 09:48:34 -0700
Message-ID: <vo9rp1tqtsv0pm1ep54tg9tp92s2gu5mi1@4ax.com>
X-Newsreader: Forte Agent 3.1/32.783
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: microsoft.public.dotnet.framework.webservices.enhancements
NNTP-Posting-Host: s010600062595c433.cg.shawcable.net 68.144.91.204
Lines: 1
Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl
microsoft.public.dotnet.framework.webservices.enhancements:7916
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices.enhancements

I have built a web service using WSE that uses "soap.tcp" as the
transport. Is it possible to access this web service from VBA using
the standard soap client (SoapClient30) (i.e. the stuff that's
included with the "Web Service References Tool")? If so, how?

When I use the "Web Service References Tool" to generate the code to
access the web service, it generates the following:
--------------------------------------------------
Private sc_ClientComponentServic As SoapClient30
Private Const c_WSDL_URL As String = "http://localhost/myapp.wsdl"
Private Const c_SERVICE As String = "ServiceName"
Private Const c_PORT As String = "ServicePort"
AddThis Social Bookmark Button