The WSDL info is stored in the filter itself.

As for the ns0 and ns1.  Those are because the WSDL defines 2 different 
namespaces when referencing the elements. The method/operation is defined in 
one namespace/schema while the elements/attributes are defined in a different 
namespace/schema.   
   xmlns:ns0="http://xml.netbeans.org/schema/schemaOceaneITSM.xsd";   
   xmlns:ns1="http://j2ee.netbeans.org/wsdl/ItsmEndpointBpel/wsITSM2Oceane";   

Since it works from SoapUI compare the 2 and see what the difference is.

Fred

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Marek B.
Sent: Thursday, August 25, 2011 9:19 AM
To: arslist@ARSLIST.ORG
Subject: Web service method invoking

** Hi,

I'm having problem with consuming a web service from a filter.
This is a weird situation: one of many methods from a service is giving an 
error:


javax.jbi.messaging.MessagingException: HTTPBC-E00701: Failed to locate the 
operation in the requested endpoint 
http://j2ee.netbeans.org/wsdl/ItsmEndpointBpel/wsITSM2Oceane,wsITSM2OceaneService,wsITSM2OceanePort,Consumer
 that matches the message signature


The others methods work fine.
Additionally this method can be succesfully consumed from other web service 
clients (SoapUI).

I did a test saving wsdl to a file and referencing that file instead of an url. 
This once worked, but when I went back to the url the problem has returned.
Switching back again to a wsdl or xml file doesn't help.

My question is if there is a place where ARS placing or cashing wsdl 
definitions which can be flushed?
Any other help would be appreciated.

Here is the captured soap message.
Is this message generated correctly?
Note ns1 and ns0 tags. Shouldn't be the same type?

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soapenv:Body>
<ns1:Inform xmlns:ns0="http://xml.netbeans.org/schema/schemaOceaneITSM.xsd"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:ns1="http://j2ee.netbeans.org/wsdl/ItsmEndpointBpel/wsITSM2Oceane";>
    <ns0:system_managerticketid>somedata</ns0:system_managerticketid>
    <ns0:timestamp>2011-08-25T15:02:20+02:00</ns0:timestamp>
    <ns0:ticket_natureid>somedata</ns0:ticket_natureid>
    <ns0:ticket_typeid>somedata</ns0:ticket_typeid>
    <ns0:ticket_startdate>2011-08-25T15:20:49+02:00</ns0:ticket_startdate>
    <ns0:ticket_description>somedata</ns0:ticket_description>
    
<ns0:ticket_expectedrestorationdate>2011-08-25T21:51:21+02:00</ns0:ticket_expectedrestorationdate>
    
<ns0:ticket_initialrestorationdate>2011-08-25T21:51:21+02:00</ns0:ticket_initialrestorationdate>
    <ns0:service_typeid>somedata</ns0:service_typeid>
    <ns0:service_value>somedata</ns0:service_value>
    <ns0:system_agentgroup>somedata</ns0:system_agentgroup>
</ns1:Inform></soapenv:Body></soapenv:Envelope>

ARS - 7.6.03

thanks,
Marek

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to