You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When one uses "Invoke SOAP Lite" (like we do in sample OSOAP001_GreetingsClient) Magic saves absolute pathnames for .wsdl location and the XSDs used for arguments and return value in the program source. The .wsdl location there is basically ok, because it's part of the project, the Xpa installation folder where the XSDs go is however not. The program (Invoke SOAP Lite) just won't work however if there is no access to these files (module directory) during runtime.
When one uses "Invoke SOAP Lite" (like we do in sample OSOAP001_GreetingsClient) Magic saves absolute pathnames for .wsdl location and the XSDs used for arguments and return value in the program source. The .wsdl location there is basically ok, because it's part of the project, the Xpa installation folder where the XSDs go is however not. The program (Invoke SOAP Lite) just won't work however if there is no access to these files (module directory) during runtime.
<Invoke FieldID3="5" FlowIsn="67"> <OperationType val="L"/> <TaskID comp="-1"/> <Lock val="N"/> <Arguments> <Argument> <Variable val="8"/> </Argument> <Argument> <Variable val="9"/> <Skip val="10"/> <Name val="in"/> </Argument> </Arguments> <Wait val="Y"/> <SyncData val="N"/> <ServiceName_LT val="Soap SOAPService Service"/> <SoapAction_LT val="||||UTF-8"/> <OperationName_LT val="C:\magic\xpa3.3\SoapClientModules\SOAPLITE\SOAPService_greetMe_In.xsd"/> <Namespace_LT val="C:\magic\xpa3.3\SoapClientModules\SOAPLITE\SOAPService_greetMe_Out.xsd"/> <ReturnCode_LT val="8"/> <FaultCode_LT val="10"/> <WSDL_URL val="C:\xpa\samples\XpaDemo\XpaDemo\external\Java\wsdl_first_https\src\main\config\hello_world.wsdl"/> <ReturnType val="13"/> <Convention val="D"/> <RetainFocus val="N"/> <Condition val="Y"/> <Modifier val="B"/> <Direction val="C"/> </Invoke>
Expected behavior
The installation / configuration should fix this
The text was updated successfully, but these errors were encountered: