Re: HOW TO: get axis2 client tcp to find Addressing module

[Martin Gainty]

Title: HOW TO: get axis2 client tcp to find Addressing module

Robert-   Does WinFX have TLS debug support such as what is supported in Axis? As this inquiry is not supporting Axis solutions this is prob O/T ..accordingly I ask list members where should this be posted? Martin -- ********************************************************************* This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed.  If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy.  Thank you.     ----- Original Message ----- From: DeRemer, Bob To: axis-user@ws.apache.org ; Martin Gainty Sent: Tuesday, May 23, 2006 7:49 PM Subject: RE: HOW TO: get axis2 client tcp to find Addressing module I actually got that via WSDL2Java -uri.  That's what generated my java proxy code for calling my service.  The service is very simple:   interface IService {     string MyOperation(string s); }   I believe the problem is in the tcp transport settings.  My guess [but I have to dig into it] is that the WinFX defaults for tcp and the axis2 defaults are probably not in sync.   Thanks for the suggestion, however! From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 23, 2006 5:30 PM To: axis-user@ws.apache.org Subject: Re: HOW TO: get axis2 client tcp to find Addressing module Robert It looks like you're going to need the WSDL the service generates so you may understand supported operations and parameters of the webservice Anyone else ? Martin -- ********************************************************************* This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed.  If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy.  Thank you.     ----- Original Message ----- From: DeRemer, Bob To: axis-user@ws.apache.org Sent: Tuesday, May 23, 2006 4:54 PM Subject: RE: HOW TO: get axis2 client tcp to find Addressing module I was able to get this working by pointing the ConfigurationContext.createConfigurationContextFromFileSystem at the apache installation's axis 2 location.  I am now struggling with getting the actual tcp connection established.  The WinFX side is throwing an exception [see below].  I'm currently tracing the call using the NET trace tools.  If anyone has [successfully] written an axis2 client to a WinFX service using the TCP transport and has any suggestions, I'd appreciate it.   Thanks, Bob   exception: Expected record type 'Version', found '60' From: DeRemer, Bob [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 23, 2006 2:40 PM To: axis-user@ws.apache.org Subject: HOW TO: get axis2 client tcp to find Addressing module I'm trying to write a simple java client in axis2 that uses tcp transport to talk to my .NET WinFX service.  I'm currently using the AXIOM approach vs the wsdl-gen'd proxy code.  In the AXIOM case, I get an exception when trying to engageModule.  I'm looking for some example that shows what I need to do in code to specify the configurationContext - so it knows where the addressing.mar is, but haven't been able to find any good example.  The sample code in the std source download doesn't appear to do anything to set this - as if the java console client just knows where the Axis repository is. Thanks in advance for any help, Bob DeRemer Sr. Software Architect   SAP Labs, LLC 350 Eagleview Blvd Exton, PA  19341  USA T1  +1.610.903.8000 x 136 T2  +1.717.505.7923 M   +1.717.424.9595 E    [EMAIL PROTECTED]