transport options?

2006-02-17 Thread Fernando.Matomira








I see BasicHandler has support for options. How do I pass
options to a transport in client-config.wsdd?

 

Thanks








AXIS-790 workaround -> bad envelope tag

2006-02-03 Thread Fernando.Matomira








I tried using the workaround attached to

 

https://issues.apache.org/jira/browse/AXIS-790

 

to allow proxy authentication while operating under Java Web
Start but the communication

fails with a “Bad envelope tag” error

 








wrapped/literal array results -> cast exception in client

2006-02-02 Thread Fernando.Matomira








With a client using Axis 1.3, when one calls a method that
is declared to return String[]

(confirmed by wsdl2java), the call fails with a
ClassCastException because what the deserializer is actually returning to the
proxy is an ArrayList.

 

 








ServiceFactory in Axis2?

2006-02-02 Thread Fernando.Matomira








What is the equivalent of
org.apache.axis.client.ServiceFactory in Axis2 so that it can be plugged into a
Spring-based client?

 

Thanks








RE: Axis not interoperable with JWSDP?

2006-01-31 Thread Fernando.Matomira








Thanks. Adding that parameter got the program
working through the WSDL.

 

However, now I make a call and I get the
following error when returning long[]:

 

Exception in thread
"AWT-EventQueue-0" deserialization error: 

java.lang.ClassCastException:
[J

    at 

com.sun.xml.rpc.encoding.ArraySerializerBase.deserialize(ArraySerializerBase.java:277)

    ...

 

CAUSE:

 

java.lang.ClassCastException:
[J

   
at 

com.sun.xml.rpc.encoding.ObjectArraySerializer.deserializeArrayInstance(ObjectArraySerializer.java:178)

    ...

 

 

 

The dynamically generated WSDL has this
type for the response:

 





type="impl:ArrayOf_xsd_long"/>



 









From: Anne Thomas
Manes [mailto:[EMAIL PROTECTED] 
Sent: Monday, January 30, 2006
6:05 PM
To: axis-user@ws.apache.org
Subject: Re: Axis not
interoperable with JWSDP?



 

Add this parameter to
your WSDD:

   

Anne



On 1/30/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]
> wrote:



I have
Axis 1.2 Final on the server, JWSDP 1.6 on the client.

 

When
I try to connect, I get the following error regarding the WSDL:

 

Exception in thread "main" unexpected array element
type: 

expected={http://www.w3.org/2001/XMLSchema}string , 

actual={http://schemas.xmlsoap.org/soap/encoding/}string


    at 

com.sun.xml.rpc.encoding.ArraySerializerBase.verifyArrayElementType(ArraySerializerBase.java:399)

 

 

Is
there any way to avoid this (eg., by upgrading the server to Axis 1.3 Final)?

 

Thanks





 








Axis not interoperable with JWSDP?

2006-01-30 Thread Fernando.Matomira








I have Axis 1.2 Final on the server, JWSDP 1.6 on the
client.

 

When I try to connect, I get the following error regarding
the WSDL:

 

Exception in thread
"main" unexpected array element type: 

expected={http://www.w3.org/2001/XMLSchema}string,


actual={http://schemas.xmlsoap.org/soap/encoding/}string

    at 

com.sun.xml.rpc.encoding.ArraySerializerBase.verifyArrayElementType(ArraySerializerBase.java:399)

 

 

Is there any way to avoid this (eg., by upgrading the server
to Axis 1.3 Final)?

 

Thanks








RE: No way to use webservice through proxy server

2006-01-30 Thread Fernando.Matomira
As a matter of fact, proxy does work if it doesn't require
authentication.
Once you set up the proxy to require authentication, it fails.
I am using Java Web Start. Apparently the problem is that Axis is not
using Sun's networking library in the proper was as to get the default
configuration. There seems to be no way of getting the proxy
authentication
info from the runtime (to configure Axis manually) because of security
reasons.

So, I am forced to abandon Axis and try with Sun's JAX-RPC reference
implementation.

-Original Message-
From: Mato Mira, Fernando (DIA CHE) 
Sent: Thursday, January 26, 2006 12:12 PM
To: axis-user@ws.apache.org
Subject: No way to use webservice through proxy server

Hello,

1. First, the connection was to a service via HTTPS, the proxy
apparently does all the crypto
and the client raises an exception because it can't understand a plain
text response.

2. To avoid this, I tried connecting via HTTP. Now it seems the proxy
removes the basic authentication header
sent by the client, as it gets an error "Authentication required" from
the server.

I imagine there's nothing Axis can do about 2, but what about fixing 1?
1 is the right way to connect anyway.

I am using 1.2 Final

Thanks



No way to use webservice through proxy server

2006-01-26 Thread Fernando.Matomira
Hello,

1. First, the connection was to a service via HTTPS, the proxy
apparently does all the crypto
and the client raises an exception because it can't understand a plain
text response.

2. To avoid this, I tried connecting via HTTP. Now it seems the proxy
removes the basic authentication header
sent by the client, as it gets an error "Authentication required" from
the server.

I imagine there's nothing Axis can do about 2, but what about fixing 1?
1 is the right way to connect anyway.

I am using 1.2 Final

Thanks