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

Luca, 

Thanks for your reply. I'm pretty certain that I am using the SOAP binding,
and thus the int parameter argument, given that 

 a) AXIS cant generate code for http bindings, as I found out a couple days
ago 

	http://marc.theaimsgroup.com/?l=axis-user&m=112964700415670&w=2

 b) The generated class, GBSCTHolidayDatesSoap, is replete with methods such
as

	/**
	   * Get the date of New Year.
	   */
	public java.util.Calendar getNewYear(int year) throws
java.rmi.RemoteException;


When I traced into WSIFClientProxy.findMatchingOperation in the debugger:

	Line 396: The Method passed is successfully found in the iface

	Line 417: Finds Operation in opList called GetGuyFawkesNight

	
	Operation.toString() yields:

" Operation: name=GetGuyFawkesNight
	style=REQUEST_RESPONSE
	Input: name=null
	Message:
name={http://www.27seconds.com/Holidays/GBSCT/Dates/}GetGuyFawkesNightSoapIn
	Part: name=parameters
	
elementName={http://www.27seconds.com/Holidays/GBSCT/Dates/}GetGuyFawkesNigh
t
	Output: name=null
	Message:
name={http://www.27seconds.com/Holidays/GBSCT/Dates/}GetGuyFawkesNightSoapOu
t
	Part: name=parameters
	
elementName={http://www.27seconds.com/Holidays/GBSCT/Dates/}GetGuyFawkesNigh
tResponse "


As I understand things, the GetGuyFawkesNightSoapIn, which has the Part
'GetGuyFawkesNight', should mean that the following type is resolved from
the WSDL, and thus the int param

	<s:element name="GetGuyFawkesNight">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="1" maxOccurs="1" name="year" type="s:int"
/>
          </s:sequence>
        </s:complexType>
      </s:element>


However, the parameter lookup between lines 470-492 resolves nothing in the
typeMap and I trace on down to simple types, lines 494-529, and then pop out
the bottom where we consider to have not found a matching operation. 

Given this added detail, am I still doing something wrong, or is there some
other problem?

Let me know if there is any other information you might need to understand
this

Regards

J


-----Original Message-----
From: Luca Baldi [mailto:[email protected]] 
Sent: 20 October 2005 16:20
To: [email protected]
Subject: RE: WSIF Reports "Method nnnnn(param) was not found in portType'


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
 



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

-- 
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