AW: Deserialization: NumberFormatException: Invalid date/time

2005-09-14 Thread Christian Kunert 









Hello Xinjun,

 

the problem is, that the
exception is thrown by axis during the parsing/ deserialization process. My client
code does not use this field explicitly. The Return Type is the
java.util.Calendar Interface and set by axis. I think this type is okay. Normally
it works.

 

Regads,

Christian

 

-Ursprüngliche Nachricht-
Von: #CHEN XINJUN#
[mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 14. September
2005 08:43
An: axis-user@ws.apache.org
Betreff: RE: Deserialization:
NumberFormatException: Invalid date/time

 

One
suggestion,  setReturnType in your client code explicitly. If it can pass,
there should be no problem. 

 

Regards,


Xinjun

 







From:
Christian Kunert [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 13, 2005
8:00 PM
To: axis-user@ws.apache.org
Subject: Deserialization:
NumberFormatException: Invalid date/time

Hello,

 

i have a problem with the
deserialization of a dateTime field. The WSDL defines the field as follows:

 

<xs:element name="DateModified" type="xs:dateTime" nillable="true" minOccurs="0"
/>

 

This field could be part
of SOAP Response and it is possible that this field is not set. In this case I
get a SOAP Response containing:

 



 

And now to the problem. I
always get a NumberFormatException: invalid dateTime during the
derserialization prozess.

 

Any Ideas? I’m
using Axis 1.2-RC but i can reproduce the problem with axis 1.2(.x). 

Axis 1.1 crashes with a
NullPointerException

 

 

Thanks!,

Christian

 

 

{http://xml.apache.org/axis/}stackTrace:java.lang.NumberFormatException: Invalid date/time

  at
org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeserializer.java:178)

  at
org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:502)

  at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083)

  at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:171)

  at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1140)

  at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:238)

  at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:386)

  at
org.apache.axis.client.Call.invoke(Call.java:2402)

  at
org.apache.axis.client.Call.invoke(Call.java:2301)

  at
org.apache.axis.client.Call.invoke(Call.java:1758)

 

 

Deserialization: NumberFormatException: Invalid date/time

2005-09-13 Thread Christian Kunert 








Hello,

 

i have a problem with the deserialization of a dateTime
field. The WSDL defines the field as follows:

 



 

This field could be part of SOAP Response and it is
possible that this field is not set. In this case I get a SOAP Response
containing:

 



 

And now to the problem. I always get a NumberFormatException:
invalid dateTime during the derserialization prozess.

 

Any Ideas? I’m using Axis 1.2-RC but i can
reproduce the problem with axis 1.2(.x). 

Axis 1.1 crashes with a NullPointerException

 

 

Thanks!,

Christian

 

 

{http://xml.apache.org/axis/}stackTrace:java.lang.NumberFormatException: Invalid date/time

  at org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeserializer.java:178)

  at org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:502)

  at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083)

  at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:171)

  at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1140)

  at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:238)

  at org.apache.axis.message.RPCElement.getParams(RPCElement.java:386)

  at org.apache.axis.client.Call.invoke(Call.java:2402)

  at org.apache.axis.client.Call.invoke(Call.java:2301)

  at org.apache.axis.client.Call.invoke(Call.java:1758)

 

 

AW: Error on Client or Service Side ?

2005-06-29 Thread Christian Kunert 
I think this exception is thrown when the deployment description (wsdd) doesn't 
corresponding to the wsdl description. The client sends a request which is 
different to the expected request. 

I had the same problem too. I solved the problem by deploying the service with 
the actual wsdd file on the server. So ru wsdl2java again an deploy the 
deploy.wsdd.

Christian


-Ursprüngliche Nachricht-
Von: Kumar [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 29. Juni 2005 16:27
An: axis-user@ws.apache.org
Betreff: Error on Client or Service Side ?

Hi All,

I have below request and response soap messages. Now, I get an axis
fault when I request the service but  I dont see any error or log
messages generated on the server side when I make the request. Is
there a problem  on the client side itself or on the service side. Can
anyone please clarify what the axis fault means in this context .



request soap message from client
--
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  http://ws.amex.com/wsdl/api";> 
 http://ws.amex.com/schema/api";>
a
b 
   
 
   
   




axis fault as viewed in tcpmontor response window
--
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
   
  
 soapenv:Server.userException
 org.xml.sax.SAXException: SimpleDeserializer
encountered a child element, which is NOT expected, in something it
was trying to deserialize.
 
http://xml.apache.org/axis/";>org.xml.sax.SAXException:
SimpleDeserializer encountered a child element, which is NOT expected,
in something it was trying to deserialize.  at
org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeserializer.java:143)
   at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1031)
  at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1140)
   at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:347) at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:386)   at
org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:148) 
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:319)   
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) 
at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:450)  at
org.apache.axis.server.AxisServer.invoke(AxisServer.java:285)   at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:653) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:301)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
 at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
   at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
 at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
   at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
 at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
 at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:983)
   at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:564)
   at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119) 
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)
  at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at
com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:116)
 at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
 at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334

AW: AW: WSDL2Java Bug?

2005-06-22 Thread Christian Kunert 









Okay.. i have no other ideas, sorry, but it sounds like a namespace problem.


 

Good luck,

christian

 

 

-Ursprüngliche
Nachricht-
Von: Antonio Ruiz Martínez
[mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 22. Juni 2005
21:31
An: axis-user@ws.apache.org
Betreff: Re: AW: WSDL2Java Bug?

 

Hello!

Christian Kunert wrote:



..The paramter Signatur of method " validaSig " is not defined anywhere.   

But it imported from
xmldsig, with 



"http://www.w3.org/2000/09/xmldsig#" schemaLocation="http://ea.carm.es/schemas/funcionales/efirma/xmldsig-core-schema.xsd"/> Regards,Antonio. 

 -Ursprüngliche Nachricht-Von: Antonio Ruiz Martínez [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 22. Juni 2005 21:13An: axis-user@ws.apache.orgBetreff: Re: WSDL2Java Bug? Hello! Sorry I forgot attach the wsld, here is: "http://schemas.xmlsoap.org/wsdl/" xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/" xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:ns0="http://ea.carm.es/schemas/basicos/seguridad/certificados/respuestaCertificado.xsd" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.xsd" xmlns:s1="http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" targetNamespace="http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl">            "http://www.w3.org/2000/09/xmldsig#" schemaLocation="http://ea.carm.es/schemas/funcionales/efirma/xmldsig-core-schema.xsd"/>                                                        transport="http://schemas.xmlsoap.org/soap/http"/>        soapAction="http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl/validaSig" style="document"/>                                            location="http://miip:80/servicios/basicos/seguridad/certificados/ValidaCertificadoWS.jws"/>         Regards,AntonioAntonio Ruiz Martínez wrote:   

Hello!    I have a problem with Axis 1.2.1. I thing that it is a bug because the wsdl is very simple and I think is correct. Here is the error:java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy true -t -p validate simple.wsdljava.io.IOException: Type {http://www.w3.org/2000/09/xmldsig#}Reference is referenced but not defined.   at org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:665)   at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545)   at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTablejava:518)     at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)     at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)   at java.lang.Thread.run(Unknown Source) Could you tell me how I can solve it, please?Regards,Antonio. 

    






-- --Antonio Ruiz MartínezFaculty of Computer Science-University of Murcia30071 Murcia - Spaine-mail: [EMAIL PROTECTED] or arm [at] dif [dot] um [dot] es--

AW: WSDL2Java Bug?

2005-06-22 Thread Christian Kunert 
..The paramter Signatur of method " validaSig " is not defined anywhere.


-Ursprüngliche Nachricht-
Von: Antonio Ruiz Martínez [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 22. Juni 2005 21:13
An: axis-user@ws.apache.org
Betreff: Re: WSDL2Java Bug?

Hello!

Sorry I forgot attach the wsld, here is:

http://schemas.xmlsoap.org/wsdl/"; 
xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/"; 
xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/"; 
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; 
xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/"; 
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; 
xmlns:ns0="http://ea.carm.es/schemas/basicos/seguridad/certificados/respuestaCertificado.xsd";
 
xmlns:s="http://www.w3.org/2001/XMLSchema"; 
xmlns:s0="http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.xsd";
 
xmlns:s1="http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl";
 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; 
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"; 
targetNamespace="http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl";>


http://www.w3.org/2000/09/xmldsig#"; 
schemaLocation="http://ea.carm.es/schemas/funcionales/efirma/xmldsig-core-schema.xsd"/>















http://schemas.xmlsoap.org/soap/http"/>

http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl/validaSig";
 
style="document"/>










http://miip:80/servicios/basicos/seguridad/certificados/ValidaCertificadoWS.jws"/>




Regards,
Antonio
Antonio Ruiz Martínez wrote:

> Hello!
>
>I have a problem with Axis 1.2.1. I thing that it is a bug because 
> the wsdl is very simple and I think is correct.
>
> Here is the error:
> java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy 
> true -t -p validate simple.wsdl
> java.io.IOException: Type 
> {http://www.w3.org/2000/09/xmldsig#}Reference is referenced but not 
> defined.
>at 
> org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol
> Table.java:665)
>at 
> org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545)
>at 
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518) 
>
>at 
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495) 
>
>at 
> org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
>at java.lang.Thread.run(Unknown Source)
>
> Could you tell me how I can solve it, please?
> Regards,
> Antonio.
>


-- 
--
Antonio Ruiz Martínez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
e-mail: [EMAIL PROTECTED] or arm [at] dif [dot] um [dot] es
--

AW: WSDL2Java Bug?

2005-06-22 Thread Christian Kunert 
I got the same exception when i use polymorphism. 
I definded an interface and used it as a method parameter. The wsdl creation 
with java2wsdl succeeded but wsdl2java failed. 

Do you use interfaces too?

Christian



-Ursprüngliche Nachricht-
Von: Antonio Ruiz Martínez [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 22. Juni 2005 21:02
An: axis-user@ws.apache.org
Betreff: WSDL2Java Bug?

Hello!

I have a problem with Axis 1.2.1. I thing that it is a bug because 
the wsdl is very simple and I think is correct.

Here is the error:
java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy true 
-t -p validate simple.wsdl
java.io.IOException: Type {http://www.w3.org/2000/09/xmldsig#}Reference 
is referenced but not defined.
at 
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol
Table.java:665)
at 
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545)
at 
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518)
at 
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Unknown Source)

Could you tell me how I can solve it, please?
Regards,
Antonio.

-- 
--
Antonio Ruiz Martínez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
e-mail: [EMAIL PROTECTED] or arm [at] dif [dot] um [dot] es
--

The requested method POST is not allowed for the URL - (405)Method Not Allowed

2005-06-22 Thread Christian Kunert 








Hi there,

 

i have troubles using a service with AXIS. I got  a
 “faultString:
(405)Method Not Allowed” 
Exception when i run my client. 

I got this additional message The requested method POST
is not allowed for the URL /index.html.
  

 

How can I change the request to GET?

I thought POST is the common request, isn’t it?

 

Thanks for any help,

Christian

Creating a java-WebService based on Interfaces?

2005-06-21 Thread Christian Kunert 








Hello,

 

in the past i wrote some POJO’s, define the
interface and runs java2wsdl to create the wsdl file. But there is always the
problem, that a specific implementation defines the entity. Is it possible to
define an interface for each entity to decouple the definition form the
implementation?

How does Axis knows the ‘right’
implementation, when the client invokes the method?

 

I hope you know what I mean :-)

Thanks for help!

 

 

 

I imagine something like this:

 

the webservice interface:

 

public interface MyService{

    createCustomer
(ICustomer customer);

}

 

 

 

the classes:

 

Public interface ICustomer {

 

    Pubic
String getName();

}

 

public class CustomerImplA implements ICustomer {

 

    public
String getName {

    //
do some specific stuff

}

}

 

public class CustomerImplB implements ICustomer {

 

// this is only an internal class, the class shouldn’t
be published via WSDL 

 

    public
String getName {

    //
do some specific stuff

}

}

 

 

 

 

client authorization with pkcs12

2005-06-03 Thread Christian Kunert 








Hello,

 

I have the following problem:

 

i wrote an axis client for an external service. I got
a p12 file to authorize me but I get an Exception:

 

AxisFault

 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException

 faultSubcode: 

 faultString: java.net.SocketException:
Default SSL context init failed: Invalid keystore format

 faultActor: 

 faultNode: 

 faultDetail:
 

 

Here is my code:

 

this.binding = (SoapBindingStub) this.locator.getSoapPort();

 

String file = this.getClass().getResource("xyz.p12").getFile();

this.binding.setUsername( “username” ); 

this.binding.setPassword(“password” ); 

System.setProperty("javax.net.ssl.keyStore",file);

System.setProperty("javax.net.ssl.trustStore",file);

 

 

I thin i’m on the wrong way.. 

Any advices?

 

 

 

___
Produktion und Entwicklung
NEXNET GmbH
Am Borsigturm 12

13507 Berlin

Tel.:
+49 30 726297 411
Mail: [EMAIL PROTECTED]

 

org.xml.sax.SAXException: Bad envelope tag: html - What does it mean?

2005-06-02 Thread Christian Kunert 








Hello,

 

i tested a Service which works fine yesterday but now
i get an AxisFault. 

 

AxisFault

 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException

 faultSubcode:

 faultString: org.xml.sax.SAXException: Bad
envelope tag:  html

 faultActor:

 faultNode:

 faultDetail:

 

Any Ideas?

There are no changes at the wsdl file.

 

 

___
Produktion und Entwicklung
NEXNET GmbH
Am Borsigturm 12

13507 Berlin

Tel.:
+49 30 726297 411
Mail: [EMAIL PROTECTED]

 

AW: Client authenticaion using certificates

2005-06-01 Thread Christian Kunert 
Hello Ephemeris,

thanks for your answer. I found a nice description at 
http://www-106.ibm.com/developerworks/webservices/library/ws-sec1.html .

That's the same way you told me :-) --> server configuration and keystore 
property.

Tanks!

-Ursprüngliche Nachricht-
Von: Ephemeris Lappis [mailto:[EMAIL PROTECTED] 
Gesendet: Dienstag, 31. Mai 2005 20:23
An: axis-user@ws.apache.org
Betreff: RE: Client authenticaion using certificates

If your server application is a J2EE web application, just configure your
application server security service (the realm in Tomcat for example), to
handle your client certificates, and just use the principal and roles in
your web service server code.
For the client code, i suppose you have to set up your HTTPS connection with
the right keystore and ssl factory... In my opinion, your web service client
code should not be aware of this security aspects, as it just use the
endpoint URL to address requests, with no security or network knowledge...
--
Ephemeris Lappis

>>> -Original Message-
>>> From: Christian Kunert [mailto:[EMAIL PROTECTED]
>>> Sent: Tuesday, May 31, 2005 4:56 PM
>>> To: axis-user@ws.apache.org
>>> Subject: Client authenticaion using certificates
>>>
>>>
>>> Hello everybody,
>>>
>>> I'm trying to create a client which uses certificate authentication. I
>>> have a cert-file but I really don't know how the use it. Sorry, but I'm
>>> a axis-newbie  :-)
>>> Should anybody show me a little workaround how to authenticate with this
>>> certificate?
>>>
>>> Christian
>>> Thanks!
>>>

Client authenticaion using certificates

2005-05-31 Thread Christian Kunert 
Hello everybody,

I'm trying to create a client which uses certificate authentication. I
have a cert-file but I really don't know how the use it. Sorry, but I'm
a axis-newbie  :-)
Should anybody show me a little workaround how to authenticate with this
certificate?

Christian
Thanks!

how to get the HTTP response code to avoid AxisFault "401 (Unauthorized)" Messages?

2005-05-31 Thread Christian Kunert 








Hello everybody,

 

I’m using Axis 1.2 in a little Web Service
project. The web service requires authentication with a username and a
password. 

The client set the values as follows:

 

ServiceLocator locator =
new ServiceLocator();

BindingStub  binding
= (BindingStub)locator.getPort();

   
binding.setUsername("username"); 

   
binding.setPassword("password"); 

 

and the client calls the service with:

 

   
binding.mehtodToCall();

 

 

This works really fine. But Sometimes it is possible
that username and password has changed. In this case i got an AxisFault Message
“401 (Unauthorized)”.

And now my question. Is it possible to get the http
response code before any exception is thrown on the client side?

May be:

 

ServiceLocator locator =
new ServiceLocator();

BindingStub  binding = (BindingStub)locator.getPort();

   
binding.setUsername("username"); 

   
binding.setPassword("password"); 

 

   
if (   methodToGetHTTPResponseCode() != 200 
){  // OK

 

   
// new authentication

}  


 

 

Thanks for your help!

 

Christian Kunert

   


 

 

___
Produktion und Entwicklung
NEXNET GmbH
Am Borsigturm 12

13507 Berlin

Tel.:
+49 30 726297 411
Mail: [EMAIL PROTECTED]