Hi, Would be legitimate to reuse Call object after invoke method call in the same thread re-setting endpoint, operation, transportProperty (what else?) without reinitializing the object?
Should Call object be re-initialized for use (invoke) with another endpoint? What about such a reuse Call object after unsuccessful (throwing exception) invoke ? Best regards, Leonid Adrian Dick wrote: > > > Hi, > > I'm posting this back to the mailing list, so others can participate. > > > > For simple XSD types, simply choose the appropriate getElementAs method > (eg: getElementAsString for xsd:string) > For arrays of simple XSD types use getBasicArray > For complex types, use getCmplxObject and getCmplxArray -- I strongly > recommend looking at a WSDL2Ws generated example to understand how these > should be used. > > Regards, > Adrian > _______________________________________ > Adrian Dick ([EMAIL PROTECTED]) > > > > > Hi Adrian, > > Thanks for the quick response - > > i have a scenario when in wsdl file of the service > <message name="MyMessage" > <part element=<some schema>:<type> name="MyResponse" /> > > </message> > > > What CAll::getElementAs should i use after Call::checkMessage>? > > Best regards, > Leonid > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Fw%3A-What-is-the-best-AXIS-C%2B%2B-practice-to-implement-request-response-MEP-tf2152796.html#a5950389 Sent from the Axis - C++ - User forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
