Paul,
Try using the code generated by the WSDL2Java tool as a starting point for your adhoc approach. -- Tom Jordahl -----Original Message----- From: Paul Baker [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 17, 2002 6:22 PM To: [EMAIL PROTECTED] Subject: RE: axis beta 1 and document style, best approach? Tom, thanks for the response. So Axis will build the proper envelope to deal with .Net document style? Actually I've been avoiding the stub approach, but that may have to be my backup plan. I'm trying to build an adhoc approach of getting data into my app. I have been trying to enable calling services on the fly. The requirement to compile code before using a service would kill my adhoc functionality. I'd like to be flexible enough to pull data from services that I don't know about at compile time. The sample .Net services I've been working with encode schema in the response. Which enables my code to create my application data structure schema on the fly and populate it with data values. I was expecting .Net to always supply me schema in the response. Could be expecting schema in the response is not a safe assumption? Are there any options without using stubs to get axis to deal with the .Net schema? I really don't want try to write the number of translations that will be necesary to be even close to 100% compatible. Regards, Paul -----Original Message----- From: Tom Jordahl [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 17, 2002 5:18 PM To: '[EMAIL PROTECTED]' Subject: RE: axis beta 1 and document style, best approach? Have you tried WSDL2Java on the WSDL generated by .NET and use the resulting stub code to invoke the service? -- Tom Jordahl Macromedia -----Original Message----- From: Paul Baker [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 17, 2002 12:33 PM To: [EMAIL PROTECTED] Subject: axis beta 1 and document style, best approach? Hello, Looking for a better approach for my java client to deal with a .Net service. Doesn't seem to be any examples, or even vague references, that deal with document style soap envelopes in the Axis beta 1 documentation. I'm new to axis, so I suspect I may be missing the point and doing things the hard way. To get some data into my client...I make up my own document style envelope and build a SOAPEnvelope object, by using the SOAPEnvelope contructor method that accepts an inputstream. I use the call.invoke(customEnv) method, which returns a soap envelope object. Then I end up parsing the response envelope on my own using DOM, and finally place the data into my client application data format. Theres must be an easier way, right? My approach works, but theres more of my own code doing the plumbing chores than I'd like. Regards, Paul
