RE: WSIF Reports "Method nnnnn(param) was not found in portType'

"Luca Baldi" <[email protected]> Thu, 20 Oct 2005 16:19:42 +0100
Newsgroups gmane.comp.apache.webservices.wsif.user
Message-ID <ABC231AADE3CE44495F858C2A7782519152E6F@MANEXCHANGE.i-documentsystems.com>
Hi Jerome.
From what I can see, the problem is that you're not using the SOAP port,
but one of the two Http ports. In fact, both for the HttpGet and
HttpPost, the operation GetGuyFawkesNight in their portType takes a
string as parameter, not an integer.
Just make sure that you pick the right port ( and therefore the right
endpoint ), and you're away !!
Hope this helps

Luca

-----Original Message-----
From: Jerome Pimmel [mailto:jerome-EF30JahWjHNvBvnq28/[email protected]] 
Sent: 20 October 2005 16:01
To: [email protected]
Subject: WSIF Reports "Method nnnnn(param) was not found in portType'

All

Have been working with WSIF 2.0.1_IB3 and WSDL4J-20030807 and have been
successfully executing calls to web services. Our implementation which
invokes WSIF uses Axis (1.3) to generate interface stub classes/types
for a
WSDL. For our purposes we cannot use dynamic invocation.

We recently tested against the following service 

	
http://www.holidaywebservice.com/Holidays/servicesAvailable_GBSCTHoliday
Date
s.aspx

And in the course of executing the call the WSIF throws the following
exception

org.apache.wsif.WSIFException: Method getGuyFawkesNight(int) was not
found
in portType
{http://www.27seconds.com/Holidays/GBSCT/Dates/}GBSCTHolidayDatesSoap
	at
org.apache.wsif.base.WSIFClientProxy.findMatchingOperation(WSIFClientPro
xy.j
ava:562)
	at
org.apache.wsif.base.WSIFClientProxy.invoke(WSIFClientProxy.java:205)
	at $Proxy0.getGuyFawkesNight(Unknown Source)
	... 

I searched the net high and low to find what the cause of this may be
and I
am unable to find my answer. What is confusing is that many other
services,
some having lots of complex types and generated code, all seem to work
fine.
None exhibit this problem.

Would anyone perhaps have some insights into possibly why?

Regards

Jerome

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.12.4/143 - Release Date:
19/10/2005