RE: Dot-Net's "wsdl.exe" and Non-Nullable Value Types

Please see the following for recommendations:   Interoperability Notes on Apache Axis 1.1 and [Microsoft .NET Framework] 1.0/1.1 FAQ http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/DotNetInterop     From: Erik Klein [mailto:[EMAIL PROTECTED] Sent: Friday, May 07

RE: Dot-Net's "wsdl.exe" and Non-Nullable Value Types

Please see the following for recommendations:   Interoperability Notes on Apache Axis 1.1 and [Microsoft .NET Framework] 1.0/1.1 FAQ http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/DotNetInterop     From: Erik Klein [mailto:[EMAIL PROTECTED] Sent: Friday, May 07

RE: Axis, JMS and SOAP issue.

Hello, --- What we are trying to do: We are trying to call JMS using a java bean running in axis running in tomcat. We are trying to create the jms socket within axis. We are getting a 42 Invocation Error. This seems to be very generic error. --- --- What we are using: 1) Apache Axis 1.1 2)

Web Service Security

In regards to security, what is any is the "standard", if any, that everyone is moving towards such that security will work across .Net, Axis, and et. al? As a follow up, where is Axis in regards to that standard. Ross

RE: WSDL autogeneration - xmlns="" in service response

Are you using Doc/Literal or RPC/Encoded? If you are using Doc/Literal, then the namespace comes from the targetNamespace of the definition that describes the element in the section. If you are using RPC/Encoded, then the namespace comes from the namespace attribute in the WSDL binding/opera

RE: WSDL autogeneration - xmlns="" in service response

Are you using Doc/Literal or RPC/Encoded? If you are using Doc/Literal, then the namespace comes from the targetNamespace of the definition that describes the element in the section. If you are using RPC/Encoded, then the namespace comes from the namespace attribute in the WSDL binding/opera

RE: Why use WSDL?

Yes. Convert collections to arrays or arrays within an array. There's some discussion within the W3C WSDL group to define some recommended schema examples. See the attached email. Anne -Original Message- From: Dorner Thomas [mailto:[EMAIL PROTECTED] Sent: Friday, May 07, 2004 7:57 AM T

RE: Why use WSDL?

Yes. Convert collections to arrays or arrays within an array. There's some discussion within the W3C WSDL group to define some recommended schema examples. See the attached email. Anne -Original Message- From: Dorner Thomas [mailto:[EMAIL PROTECTED] Sent: Friday, May 07, 2004 7:57 AM T

Re: WSDL autogeneration - xmlns="" in service response

I had exactly the same problem. To fix it add elementFormDefault="qualified" to the schema element in your wsdl, and then rerun wsdl2java. On Friday 07 May 2004 6:38 am, Satrusalya, Prassana wrote: > In my response axis sends back the response the following way. Notice the ' > xmlns="" ' . .NET

possible logic error in RPCHandler

In this code snippet from org.apache.axis.message.RPCHandler, around line 260 in the axis-1.2 beta sources, if(null != destClass && dser == null && destClass.isAssignableFrom( org.w3c.dom.Element.class )){ //If a DOM element is expected, as last resort always allow di

WSDL autogeneration - xmlns="" in service response

In my response axis sends back the response the following way. Notice the ' xmlns="" ' . .NET does not like it. My WSDL is generated on the fly and I am using Simple types. Any idea how to avoid this. - http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xml

Dot-Net's "wsdl.exe" and Non-Nullable Value Types

I have built a webservice using Apache Axis 1.1 that is implemented as RPC / Encoded for no reason other than the fact that I have Custom Exceptions thrown from my Interface and Java2WSDL does not like this.  I also attempted to use Axis 1.2 Beta to resolve this problem but ran into additional prob

Re: Serializing dates using the local timezone to improve interoperability

[EMAIL PROTECTED] wrote: At the moment Axis canonicalises all dates to the UTC timezone in SOAP messages. In and of itself this is of course perfectly correct, and you would expect it to simplify things. However for us it is having the inverse effect -- you see for the years 1969 to 1972 both Ir

WSDL in Server-config.wsdd problem

Hi I am providing the location of WSDL in server-config.wsdd as: /WS.wsdl It does not let me see wsdl when I use the URL : http://trs-ut.abc.com/learnnet/services/TestWS?wsdl But I can make a call like the foll

Re: Why use WSDL?

Anne, While working with Axis 1.2 Beta I found that axis itself handles ArrayList. That is it automatically converts the ArrayList in the form of an array in the generated WSDL. Am I correct? Jagannath Anne Thomas Manes wrote: Sorry -- what I meant to say ... First rule of interoperabi

Client Authentication SSL

Hi, I am trying to authenticate my web services client. I have server authentication working using the System.setProperty method to set the clients trusted certificates, now I want to set the clients keystore. I am using the following set property... System.setProperty("javax.net.ssl.trustStore",

Serializing dates using the local timezone to improve interoperability

Hi, At the moment Axis canonicalises all dates to the UTC timezone in SOAP messages. In and of itself this is of course perfectly correct, and you would expect it to simplify things. However for us it is having the inverse effect -- you see for the years 1969 to 1972 both Ireland and Britain (an

AW: Why use WSDL?

OkOKO, one moment, do i understand it? You say i should not use Hashmaps or Hashtables for SOAPConnections? I shall use Arrays - for this I should use 2 Dimensional Arrays or Array in Array? Can u explain more detailed please Thanks Tomi -Ursprüngliche Nachricht- Von: Galbreat

RE: Why use WSDL?

You mean to say to DO expose collections AS arrays? -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Friday, May 07, 2004 7:50 AM To: [EMAIL PROTECTED] Subject: RE: Why use WSDL? Sorry -- what I meant to say ... First rule of interoperability -- do NOT expose c

RE: Why use WSDL?

Sorry -- what I meant to say ... First rule of interoperability -- do NOT expose collections (List, Map, etc) through your interface. Anne -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Friday, May 07, 2004 7:40 AM To: [EMAIL PROTECTED] Subject: RE: Why use

RE: Why use WSDL?

Sorry -- what I meant to say ... First rule of interoperability -- do NOT expose collections (List, Map, etc) through your interface. Anne -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Friday, May 07, 2004 7:40 AM To: [EMAIL PROTECTED] Subject: RE: Why use

RE: Why use WSDL?

Turn your hashmap into an array. First rule of interoperability -- do expose collections (List, Map, etc) through your interface. Anne -Original Message- From: Dorner Thomas [mailto:[EMAIL PROTECTED] Sent: Friday, May 07, 2004 2:54 AM To: '[EMAIL PROTECTED]' Subject: AW: Why use WSDL?

RE: Why use WSDL?

Turn your hashmap into an array. First rule of interoperability -- do expose collections (List, Map, etc) through your interface. Anne -Original Message- From: Dorner Thomas [mailto:[EMAIL PROTECTED] Sent: Friday, May 07, 2004 2:54 AM To: '[EMAIL PROTECTED]' Subject: AW: Why use WSDL?

Re: Character encoding woes

Thanks for your reply but unfortunately it didn't do the trick. Tried both to invoke it when starting and in code with System.setProperty("file.encoding", "ISO-8859-1"); Regards Kjetil På 6. mai. 2004 kl. 18.29 skrev Samir Shaikh: Try to pass the options when the jvm is invoked. -Dfile.encoding