Re: Does Axis interoperate with .NET's multiRef syntax?

Hi Blake, In .NET, I see: /q1:getInfoForNametns:TestObj id=id1 xsi:type=tns:TestObj instvara xsi:type=xsd:stringHello/partnerid instvarb xsi:type=xsd:stringGoodbye/password /tns:PartnerAuthentication Is this a copy and paste error or do the closing tags differ from the

Multiple import problem

Title: Multiple import problem Hi, I am using WSDL2Java tool (beta-2 version), trying to generate Java classes and run into problem when one of my imported xsd was already been imported in another xsd. Generally the structure is similar to this: MyWSDL. wsdl | +-- import comp.xsd |

Sorry if u have already answered this, but my mail went down and i've lost all yesterdays emails

Title: Sorry if u have already answered this, but my mail went down and i've lost all yesterdays emails I'm trying to expose an Stateless EJB as a Web Service with the following XSDD, it deploys okay, but I the generated WSDL file does not show the methods for the service. Does anyone have

Creating custom de/serializers

Hi all, If some one could throw some light on creating custom (de) serializers for a Class which does not follow Java Beans rules. thank you Vishal

Solving .NET desrialization problem by simple soap arrays

We are exposing our Java application as a web service using AXIS on Tomcat and trying to access it thru GUI build in .NET but are getting problems in deserialization of Collection classes. Would I be going in wrong direction in trying to solve this problem by creating custom

Another EJB Question

Title: Another EJB Question Hopefully a quick one.. I am correct in assuming that if I have expsoed a stateless session bean through axis, then the client only needs to call the method that I require of the e.g. getXML. They do not need to worry about using create etc, as this is handled

AXIS BUG ?

Hi all, I found several bugs in server sid generated WSDL ( invoked with the ?wsdl option in the URL...). Imade tests with several tools ( XML spy ( soap debugger plug-in SOAP:Net from www.soaptoolset.com)and i find this: AXIS generate WSDL with "wsdl:" namespace before almost element:

Identifier conversion WSDL- java

Hi, I have encountered a problem using axis wsdl2java conversion unfortunately the WSDL spec I have to use contains two field for user IDs as shown below message name='X' part name='userId' type='xsd:string'/ part name='user_id' type='xsd:anyType'/ /message unfortunately

Includes

Title: Includes Hi, We have elaborate set of XSDs generated by our own tool. Some of them live in the same namespace, but they don't have knowledge of content of each other except the file name. So the most natural way to connect them is not copy and paste one into another, but using

Re: Includes

AXIS probably doesn't yet support xml include. I would have hoped that we would have gotten it for free using xerces, but perhaps not. Could you send us an example that we can test? We DO support import but, as you pointed out in a previous note, it falls apart in certain cases. As I said,

RE: NullPointerException with Arrays

Hello, this is in response to your message to the axis-user group (I don't have the original message in my mail reader...). If you are using public attributes and the BeanSerializer, then this looks a lot like bug #9492 in the bugzilla database:

Re: Sorry if u have already answered this, but my mail went down and i'velost all yesterdays emails

For future reference, you can check what happened to emails for axis-user by looking in an archive. See the mailing lists link on the Axis home page. Glyn

Re: AXIS BUG ?

Thanks for your quick response, Maybe XML spy and SOAP:NEt aren't following the specs. but i think that we can add the name attribute in definitions element with service name as value ( i think that there is no effort to add it , maybe with an optional parameter in wsdl4j) I will send a note to

Re: Error of WSDL2Java

WSDL2Java doesn't support http://www.w3.org/2001/XMLSchema:schema. Since it doesn't support it, it assumes you will define it. Since you don't, it says it's not defined. JAX-RPC, the mapping spec we follow, doesn't provide a mapping from xsd:schema to Java. Does anyone have suggestions as to

Re: Error of WSDL2Java

However I could generate java code from this WSDL: http://ws.serviceobjects.net/gp/GeoPhone.asmx?WSDL Could you tell me what is the differences between these two WSDL files? Thanks The WDSL file: ?xml version=1.0 encoding=utf-8 ? - definitions xmlns:http=http://schemas.xmlsoap.org/wsdl/http/

Re: AXIS BUG ?

These are not bugs. See my comments inline between rjb.../rjb Russell Butek [EMAIL PROTECTED] Jean-Marc Taillant [EMAIL PROTECTED] on 05/29/2002 08:41:06 PM Please respond to [EMAIL PROTECTED] To:[EMAIL PROTECTED], [EMAIL PROTECTED] cc: Subject:AXIS BUG ? Hi all, I found several

Re: Error of WSDL2Java

Well, these two WSDL files are completely different. But in particular, the first WSDL has the line: s:element ref=s:schema / The second WSDL doesn't. Russell Butek [EMAIL PROTECTED] Anna Chen [EMAIL PROTECTED] on 05/29/2002 11:04:23 AM Please respond to [EMAIL PROTECTED] To:[EMAIL

RE: EJB Provider

Hey Christopher Try adding the following parameter to the service description parameter name=className value=uk.co.marketforce.transactional.creditclaims.CreditClaimXML / There was some problem when this was absent from the service description. This might solve your problem Hope this

Error of call.invoke()

What causes this error? Server was unable to process request. -- Object reference not set to an instance of an object. at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:134) at

RE: NullPointerException with Arrays

I am pasting the original message in the end of the reply. I believe my problem might be different as the JavaBean dosen't have any public attributes. -Original Message- From: Boris Magocsi [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 29, 2002 9:58 AM To: [EMAIL

RE: Includes

Title: RE: Includes Russell, Thank you for you reply. To test includes you just need to move definition to separate file within the same namespace and add include statement in the referencing one. But anyway I combined my testcase in one zip archive and attaching it to this memo. I also

Re: Does Axis interoperate with .NET's multiRef syntax?

Barbara, As you note, it is a paste error, should read: /q1:getInfoForNametns:TestObj id=id1 xsi:type=tns:TestObj instvara xsi:type=xsd:stringHello/instvara instvarb xsi:type=xsd:stringGoodbye/instvarb /tns:PartnerAuthentication So, the .NET frame work is producing well formed

AxisFault vs SOAP Fault

I am having trouble getting the fault code out of a SOAP message Environment: --- SunOS zima 5.8 Generic_111433-02 sun4u sparc SUNW,Sun-Blade-1000 java version 1.4.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92) Java HotSpot(TM) Client VM (build

Re: AxisFault vs SOAP Fault

The fault contents currently are not passed across the wire. Use AxisFault.getFaultCode() to get the fault code. Hope this helps. Rich Scheuerle XML Web Services Development 512-838-5115 (IBM TL 678-5115) Schwartz, Brenton [EMAIL PROTECTED] 05/29/2002 05:03 PM Please respond to

Re: Please Help-me - Basic install of Axis Beta2 on Resin 2.1.1 Web Server

Hi Scott Nichol, I'm still having problem with Axis and Resin. My environment is now with Windows 2000 server, Sun JDK 1.3.1, Resin 2.1.1 e Axis Beta2. I did this: 1. Unzip xml-axis-beta2.zip to e:\ (so Axis root is e:\xml-axis-beta2). 2. Unzip resin-2.1.1.zip to e:\ (so Resin root is

RE: AxisFault vs SOAP Fault

Thanks for the try, System.out.println(AxisFault.getFaultCode() ); prints the value Server which is the soap-env:faultcodeServer /soap-env:faultcode out of the soap message not the message several layers down which contains the actual e:errorCode4500/e:errorCode that I need access to. I

RE: AxisFault vs SOAP Fault

This may be related to the fact that axis does not adequately serializer/deserialize the contents of the fault. Did you try Axis.getFaultDetails ? Rich Scheuerle XML Web Services Development 512-838-5115 (IBM TL 678-5115) Schwartz, Brenton [EMAIL PROTECTED] 05/29/2002 05:23 PM Please