from:"CREMENESCU FLORIN"

PLEASE unsubscribe me

2005-06-28 Thread CREMENESCU FLORIN


 Hi, 
 
 Could someone managing the list unsubscribe me ? The automatic unsubscribe
mecanism does not function for me ! At the week I'll be in holiday, and I
have to put an automatic answer to my mailbox : every message I receive from
the axis list will generate a new mail to the list. 
 
Thank you for your understanding. 

 Florin


 -Message d'origine-
 De:   CREMENESCU FLORIN [SMTP:[EMAIL PROTECTED]
 Date: lundi 27 juin 2005 09:42
 À:'axis-user@ws.apache.org'
 Objet:Please unsubscribe me
 
 
  Hi, 
 
  I'm trying to unsubscribe from the axis list, but I found this
 impossible.
 Could someone remove my address [EMAIL PROTECTED] from this list ?  
 Thank you, 
   Florin
 
  PS Here are my subscribe request and the unsubscribe answer from your
 list
 manager program (you can see that it's the same address) : 
 
 SUBSCRIBE MESSAGE : 
 
 Hi! This is the ezmlm program. I'm managing the
 axis-dev@ws.apache.org mailing list.
 
 Acknowledgment: I have added the address
 
[EMAIL PROTECTED]
 
 to the axis-dev mailing list.
 
 Welcome to [EMAIL PROTECTED]
 
 Please save this message so that you know the address you are
 subscribed under, in case you later want to unsubscribe or change your
 subscription address.
 
 To unsubscribe, send a message to:
 
 [EMAIL PROTECTED]
 
 
 --- Administrative commands for the axis-dev list ---
 
 I can handle administrative requests automatically. Please
 do not send them to the list address! Instead, send
 your message to the correct command address:
 
 To subscribe to the list, send a message to:
[EMAIL PROTECTED]
 
 To remove your address from the list, send a message to:
[EMAIL PROTECTED]
 
 Send mail to the following for info and FAQ for this list:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
 
 To get messages 123 through 145 (a maximum of 100 per request), mail:
[EMAIL PROTECTED]
 
 To get an index with subject and author for messages 123-456 , mail:
[EMAIL PROTECTED]
 
 They are always returned as sets of 100, max 2000 per request,
 so you'll actually get 100-499.
 
 To receive all messages with the same subject as message 12345,
 send an empty message to:
[EMAIL PROTECTED]
 
 The messages do not really need to be empty, but I will ignore
 their content. Only the ADDRESS you send to is important.
 
 You can start a subscription for an alternate address,
 for example [EMAIL PROTECTED], just add a hyphen and your
 address (with '=' instead of '@') after the command word:
 [EMAIL PROTECTED]
 
 To stop subscription for this address, mail:
 [EMAIL PROTECTED]
 
 In both cases, I'll send a confirmation message to that address. When
 you receive it, simply reply to it to complete your subscription.
 
 If despite following these instructions, you do not get the
 desired results, please contact my owner at
 [EMAIL PROTECTED] Please be patient, my owner is a
 lot slower than I am ;-)
 
 --- Enclosed is a copy of the request I received.
 
 Return-Path: [EMAIL PROTECTED]
 Received: (qmail 7396 invoked by uid 99); 29 Mar 2005 15:42:23 -
 X-ASF-Spam-Status: No, hits=0.0 required=10.0
   tests=
 X-Spam-Check-By: apache.org
 Received-SPF: pass (hermes.apache.org: local policy)
 Received: from mailhost2.cdn.fr (HELO net191rms002.cdn.fr) (194.2.239.194)
   by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 29 Mar 2005 07:42:21 -0800
 Received: from net188fls002.cdn.fr (unverified) by net191rms002.cdn.fr
  (Content Technologies SMTPRS 4.3.17) with ESMTP id
 [EMAIL PROTECTED] for
 [EMAIL PROTECTED]
 pa
 che.org;
  Tue, 29 Mar 2005 17:40:36 +0200
 Received: from sec014mes052.cdn (unverified) by net188fls002.cdn.fr 
 (Content Technologies SMTPRS 4.3.17) with ESMTP id 
 [EMAIL PROTECTED] for 
  
 [EMAIL PROTECTED]
 pa
 che.org
; Tue, 29 Mar 2005 17:42:18 +0200
 Received: by sec014mes052.cdn with Internet Mail Service (5.5.2657.72) id
   HPN5CKAM; Tue, 29 Mar 2005 17:42:20 +0200
 Message-ID: [EMAIL PROTECTED]
 From: CREMENESCU FLORIN [EMAIL PROTECTED]
 To:
 '[EMAIL PROTECTED]
 ap
 ache.org'
  
 [EMAIL PROTECTED]
 pa
 che.org
 Subject: RE: confirm subscribe to axis-dev@ws.apache.org
 Date: Tue, 29 Mar 2005 17:35:49 +0200
 MIME-Version: 1.0
 X-Mailer: Internet Mail Service (5.5.2657.72)
 Content-Type: text/plain; charset=iso-8859-1
 Content-Transfer-Encoding: quoted-printable
 X-Virus-Checked: Checked
 
 
 
  -Message d'origine-
  De: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]
  Date:   mardi 29 mars 2005 17:42
  =C0:[EMAIL PROTECTED]
  Objet:  confirm subscribe to axis-dev@ws.apache.org
 =20
  Hi! This is the ezmlm program. I'm managing the
  axis-dev@ws.apache.org mailing list.
 =20
  To confirm that you would like
 =20
 [EMAIL PROTECTED]
 =20
  added to the axis-dev mailing list, please send
  an empty reply to this address:
 =20
  =20
 
 [EMAIL PROTECTED]
 .ap
  ache.org
 =20
  Usually, this happens when you just hit the reply button.
  If this does not work, simply copy the address and paste

Please unsubscribe me

2005-06-27 Thread CREMENESCU FLORIN


 Hi, 

 I'm trying to unsubscribe from the axis list, but I found this impossible.
Could someone remove my address [EMAIL PROTECTED] from this list ? 

Thank you, 
  Florin

 PS Here are my subscribe request and the unsubscribe answer from your list
manager program (you can see that it's the same address) : 

SUBSCRIBE MESSAGE : 

Hi! This is the ezmlm program. I'm managing the
axis-dev@ws.apache.org mailing list.

Acknowledgment: I have added the address

   [EMAIL PROTECTED]

to the axis-dev mailing list.

Welcome to [EMAIL PROTECTED]

Please save this message so that you know the address you are
subscribed under, in case you later want to unsubscribe or change your
subscription address.

To unsubscribe, send a message to:

[EMAIL PROTECTED]


--- Administrative commands for the axis-dev list ---

I can handle administrative requests automatically. Please
do not send them to the list address! Instead, send
your message to the correct command address:

To subscribe to the list, send a message to:
   [EMAIL PROTECTED]

To remove your address from the list, send a message to:
   [EMAIL PROTECTED]

Send mail to the following for info and FAQ for this list:
   [EMAIL PROTECTED]
   [EMAIL PROTECTED]

To get messages 123 through 145 (a maximum of 100 per request), mail:
   [EMAIL PROTECTED]

To get an index with subject and author for messages 123-456 , mail:
   [EMAIL PROTECTED]

They are always returned as sets of 100, max 2000 per request,
so you'll actually get 100-499.

To receive all messages with the same subject as message 12345,
send an empty message to:
   [EMAIL PROTECTED]

The messages do not really need to be empty, but I will ignore
their content. Only the ADDRESS you send to is important.

You can start a subscription for an alternate address,
for example [EMAIL PROTECTED], just add a hyphen and your
address (with '=' instead of '@') after the command word:
[EMAIL PROTECTED]

To stop subscription for this address, mail:
[EMAIL PROTECTED]

In both cases, I'll send a confirmation message to that address. When
you receive it, simply reply to it to complete your subscription.

If despite following these instructions, you do not get the
desired results, please contact my owner at
[EMAIL PROTECTED] Please be patient, my owner is a
lot slower than I am ;-)

--- Enclosed is a copy of the request I received.

Return-Path: [EMAIL PROTECTED]
Received: (qmail 7396 invoked by uid 99); 29 Mar 2005 15:42:23 -
X-ASF-Spam-Status: No, hits=0.0 required=10.0
tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from mailhost2.cdn.fr (HELO net191rms002.cdn.fr) (194.2.239.194)
  by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 29 Mar 2005 07:42:21 -0800
Received: from net188fls002.cdn.fr (unverified) by net191rms002.cdn.fr
 (Content Technologies SMTPRS 4.3.17) with ESMTP id
[EMAIL PROTECTED] for
[EMAIL PROTECTED]
che.org;
 Tue, 29 Mar 2005 17:40:36 +0200
Received: from sec014mes052.cdn (unverified) by net188fls002.cdn.fr 
(Content Technologies SMTPRS 4.3.17) with ESMTP id 
[EMAIL PROTECTED] for 
 
[EMAIL PROTECTED]
che.org
   ; Tue, 29 Mar 2005 17:42:18 +0200
Received: by sec014mes052.cdn with Internet Mail Service (5.5.2657.72) id 
HPN5CKAM; Tue, 29 Mar 2005 17:42:20 +0200
Message-ID: [EMAIL PROTECTED]
From: CREMENESCU FLORIN [EMAIL PROTECTED]
To:
'[EMAIL PROTECTED]
ache.org'
 
[EMAIL PROTECTED]
che.org
Subject: RE: confirm subscribe to axis-dev@ws.apache.org
Date: Tue, 29 Mar 2005 17:35:49 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked



 -Message d'origine-
 De:   [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]
 Date: mardi 29 mars 2005 17:42
 =C0:  [EMAIL PROTECTED]
 Objet:confirm subscribe to axis-dev@ws.apache.org
=20
 Hi! This is the ezmlm program. I'm managing the
 axis-dev@ws.apache.org mailing list.
=20
 To confirm that you would like
=20
[EMAIL PROTECTED]
=20
 added to the axis-dev mailing list, please send
 an empty reply to this address:
=20
 =20
 [EMAIL PROTECTED]
.ap
 ache.org
=20
 Usually, this happens when you just hit the reply button.
 If this does not work, simply copy the address and paste it into
 the To: field of a new message.
=20
 This confirmation serves two purposes. First, it verifies that I am able
 to get mail through to you. Second, it protects you in case someone
 forges a subscription request in your name.
=20
=20
 --- Administrative commands for the axis-dev list ---
=20
 I can handle administrative requests automatically. Please
 do not send them to the list address! Instead, send
 your message to the correct command address:
=20
 To subscribe to the list, send a message to:
[EMAIL PROTECTED]
=20
 To remove your address from the list, send a message to:
[EMAIL PROTECTED]
=20
 Send mail to the following for info and FAQ for this list:
[EMAIL PROTECTED

RE: Howto not mess up response when using Call.setHandler

2005-04-01 Thread CREMENESCU FLORIN

Hi, 

 Verify that your handler class is in your classpath and that it has a
public empty constructor. If this is true, try to put a breakpoint in the
axis code HandlerChainImpl class to see why it cannot instantiate your
handler : 
  private Handler newHandler(HandlerInfo handlerInfo) {
try {
Handler handler =  // -- breakpoint here
(Handler) handlerInfo.getHandlerClass().newInstance();
handler.init(handlerInfo);
return handler;
} catch (Exception ex) {
String messageText = Messages.getMessage(NoJAXRPCHandler00,
handlerInfo.getHandlerClass().toString());
throw new JAXRPCException(messageText, ex);
}
}

Regards, 
  Florin


 -Message d'origine-
 De:   Morten Olsen [SMTP:[EMAIL PROTECTED]
 Date: vendredi 1 avril 2005 09:29
 À:axis-user@ws.apache.org
 Objet:RE: Howto not mess up response when using Call.setHandler
 
 Hi again,
 
  
 
 Thanks Florin for your answer. When using your code as is, without
 changing the endpoint (sticking with piPort) it works, but my handler is
 not called.
 
  
 
 I'm quite new to Axis, but I figured out to put my own service name as the
 end point in your code. When doing this I get the exception shown below. I
 don't know why, so any explanation or advice will be highly appreciated.
 
  
 
 Bests,
 
 Morten
 
  
 
 AxisFault
 
  faultCode:
 {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 
  faultSubcode: 
 
  faultString: javax.xml.rpc.JAXRPCException: Unable to create handler of
 type class dk.unwire.udps.io.ws.client.WsseClientHandler
 
  faultActor: 
 
  faultNode: 
 
  faultDetail: 
 
   {http://xml.apache.org/axis/}stackTrace:
 javax.xml.rpc.JAXRPCException: Unable to create handler of type class
 dk.unwire.udps.io.ws.client.WsseClientHandler
 
   at
 org.apache.axis.handlers.HandlerChainImpl.newHandler(HandlerChainImpl.java
 :183)
 
   at
 org.apache.axis.handlers.HandlerChainImpl.lt;initgt;(HandlerChainImpl.ja
 va:101)
 
   at
 org.apache.axis.handlers.HandlerInfoChainFactory.createHandlerChain(Handle
 rInfoChainFactory.java:80)
 
   at
 org.apache.axis.client.AxisClient.invokeJAXRPCHandlers(AxisClient.java:262
 )
 
   at org.apache.axis.client.AxisClient.invoke(AxisClient.java:170)
 
   at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
 
   at org.apache.axis.client.Call.invoke(Call.java:2553)
 
   at org.apache.axis.client.Call.invoke(Call.java:2248)
 
   at org.apache.axis.client.Call.invoke(Call.java:2171)
 
   at org.apache.axis.client.Call.invoke(Call.java:1691)
 
   at
 dk.unwire.udps.io.ws.client.ProfileSoapBindingStub.newProfile(ProfileSoapB
 indingStub.java:190)
 
   at
 dk.unwire.udps.io.ws.client.WSClientProfileFactory.newProfile(WSClientProf
 ileFactory.java:198)
 
   at WSTest.main(WSTest.java:38)
 
  
 
  
 
 javax.xml.rpc.JAXRPCException: Unable to create handler of type class
 dk.unwire.udps.io.ws.client.WsseClientHandler
 
   at org.apache.axis.AxisFault.makeFault(AxisFault.java:129)
 
   at org.apache.axis.client.AxisClient.invoke(AxisClient.java:210)
 
   at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
 
   at org.apache.axis.client.Call.invoke(Call.java:2553)
 
   at org.apache.axis.client.Call.invoke(Call.java:2248)
 
   at org.apache.axis.client.Call.invoke(Call.java:2171)
 
   at org.apache.axis.client.Call.invoke(Call.java:1691)
 
   at
 dk.unwire.udps.io.ws.client.ProfileSoapBindingStub.newProfile(ProfileSoapB
 indingStub.java:190)
 
   at
 dk.unwire.udps.io.ws.client.WSClientProfileFactory.newProfile(WSClientProf
 ileFactory.java:198)
 
   at WSTest.main(WSTest.java:38)
 
 Caused by: javax.xml.rpc.JAXRPCException: Unable to create handler of type
 class dk.unwire.udps.io.ws.client.WsseClientHandler
 
   at
 org.apache.axis.handlers.HandlerChainImpl.newHandler(HandlerChainImpl.java
 :183)
 
   at
 org.apache.axis.handlers.HandlerChainImpl.init(HandlerChainImpl.java:101
 )
 
   at
 org.apache.axis.handlers.HandlerInfoChainFactory.createHandlerChain(Handle
 rInfoChainFactory.java:80)
 
   at
 org.apache.axis.client.AxisClient.invokeJAXRPCHandlers(AxisClient.java:262
 )
 
   at org.apache.axis.client.AxisClient.invoke(AxisClient.java:170)
 
   ... 8 more
 
  
 
  
 
   _  
 
  
 
 Hi, 
  
  You havent't included the stacktrace, but I had also problems in defining
 a
 handler. The winning code for me was : 
ArrayList handlersInfo=new ArrayList();
 
HandlerInfo hInfo=new
 HandlerInfo(SOAPLogHandler.class,null,
 null);
handlersInfo.add(hInfo);
  
 _call.getService().getHandlerRegistry().setHandlerChain(new
 QName(piPort), handlersInfo);
  
  
  Cheers,
 Florin Cremenescu
  
  
  
  -Message d'origine-
  De:   Morten Olsen [SMTP:[EMAIL PROTECTED]
  Date:

RE: Howto not mess up response when using Call.setHandler

2005-03-30 Thread CREMENESCU FLORIN

Hi, 

 You havent't included the stacktrace, but I had also problems in defining a
handler. The winning code for me was : 
ArrayList handlersInfo=new ArrayList(); 
HandlerInfo hInfo=new HandlerInfo(SOAPLogHandler.class,null,
null);
handlersInfo.add(hInfo);
_call.getService().getHandlerRegistry().setHandlerChain(new
QName(piPort), handlersInfo);


 Cheers,
Florin Cremenescu

 

 -Message d'origine-
 De:   Morten Olsen [SMTP:[EMAIL PROTECTED]
 Date: mercredi 30 mars 2005 09:57
 À:axis-user@ws.apache.org
 Objet:Howto not mess up response when using Call.setHandler
 
 Hi all,
 
  
 
 I'm trying to implement authentication in my web service. I've changed my
 client to include security information in the message by following an
 example from http://axis-wsse.sourceforge.net/. Essentially, the client
 sets up a handler on the call which appends the security information. I
 haven't changed the server side of things yet, as I wanted to see the
 client work first.
 
  
 
 When I run my client without setting up the handler everything is fine -
 and it gets a result back from the server that it can deserialize and
 write out. 
 
  
 
 When I setup the handler, I can see (with tcpmon) that the security
 information is added in the client's message and that the server (ignores
 it and) returns a message like in the above case. Unfortunately I'm
 getting the below exception when the client gets back the message from the
 server.
 
  
 
 I'm suspecting that setting up the handler for the request message somehow
 messes up the handling of the response. The handler is setup with
 Call.setHandler(request, response) which takes both a handler for the
 request and the response. A just set the response handler to null - as
 this is done in the example I've copied. Does anyone know if this is the
 correct way, to set up the handler?
 
  
 
 Best,
 
 Morten
 
  
 
  
 
 - Exception:
 
 org.xml.sax.SAXException: Deserializing parameter 'newProfileReturn':
 could not find deserializer for type
 {http://encoding.ws.io.udps.unwire.dk}SerializableProfile
 
   at
 org.apache.axis.message.RPCHandler.onStartChild(RPCHandler.java:302)
 
   at
 org.apache.axis.encoding.DeserializationContextImpl.startElement(Deseriali
 zationContextImpl.java:963)
 
   at
 org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:19
 8)
 
   at
 org.apache.axis.message.MessageElement.publishToHandler(MessageElement.jav
 a:722)
 
   at
 org.apache.axis.message.RPCElement.deserialize(RPCElement.java:233)
 
   at org.apache.axis.message.RPCElement.getParams(RPCElement.java:347)
 
   at org.apache.axis.client.Call.invoke(Call.java:2272)
 
   at org.apache.axis.client.Call.invoke(Call.java:2171)
 
   at org.apache.axis.client.Call.invoke(Call.java:1691)
 
   at
 dk.unwire.udps.io.ws.client.ProfileSoapBindingStub.newProfile(ProfileSoapB
 indingStub.java:182)
 
   at
 dk.unwire.udps.io.ws.client.WSClientProfileFactory.newProfile(WSClientProf
 ileFactory.java:198)
 
   at WSTest.main(WSTest.java:38)
 
 - There was an error invoking the web service
 
 AxisFault
 
  faultCode:
 {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 
  faultSubcode: 
 
  faultString: org.xml.sax.SAXException: Deserializing parameter
 apos;newProfileReturnapos;:  could not find deserializer for type
 {http://encoding.ws.io.udps.unwire.dk}SerializableProfile
 
  faultActor: 
 
  faultNode: 
 
  faultDetail: 
 
   {http://xml.apache.org/axis/}stackTrace: org.xml.sax.SAXException:
 Deserializing parameter 'newProfileReturn':  could not find deserializer
 for type {http://encoding.ws.io.udps.unwire.dk}SerializableProfile
 
   at
 org.apache.axis.message.RPCHandler.onStartChild(RPCHandler.java:302)
 
   at
 org.apache.axis.encoding.DeserializationContextImpl.startElement(Deseriali
 zationContextImpl.java:963)
 
   at
 org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:19
 8)
 
   at
 org.apache.axis.message.MessageElement.publishToHandler(MessageElement.jav
 a:722)
 
   at
 org.apache.axis.message.RPCElement.deserialize(RPCElement.java:233)
 
   at org.apache.axis.message.RPCElement.getParams(RPCElement.java:347)
 
   at org.apache.axis.client.Call.invoke(Call.java:2272)
 
   at org.apache.axis.client.Call.invoke(Call.java:2171)
 
   at org.apache.axis.client.Call.invoke(Call.java:1691)
 
   at
 dk.unwire.udps.io.ws.client.ProfileSoapBindingStub.newProfile(ProfileSoapB
 indingStub.java:182)
 
   at
 dk.unwire.udps.io.ws.client.WSClientProfileFactory.newProfile(WSClientProf
 ileFactory.java:198)
 
   at WSTest.main(WSTest.java:38)
 
  
 
  
 
 org.xml.sax.SAXException: Deserializing parameter 'newProfileReturn':
 could not find deserializer for type
 {http://encoding.ws.io.udps.unwire.dk}SerializableProfile
 
   at

Problems using axis 1.1 and 1.2 with attachments

2005-03-29 Thread CREMENESCU FLORIN

Hello, 

 
I am trying to use Axis as a client for a web service with attachments. I
have several problems, but I'm not sure that they are due to axis bugs, so I
ask you for advice. 


Skim of the wsdl service description : 

The service returns general information in a classic SOAP message plus an
attached document. The attached document is referenced from the general
information by the REP field (the entire wsdl can be found at the end of the
message). 
The output message has the form : 
wsdl:message name=piReponse
wsdl:part type=pi:REP_PROTECTEL_IBDF name=REP_PROTECTEL_IBDF/
wsdl:part type=xsd:string name=attch/
/wsdl:message

The binding has the form : 
wsdl:output
mime:multipartRelated
mime:part
soap:body use=encoded
namespace=http://mynamespace;
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/
/mime:part
mime:part
mime:content part=attch type=text/xml/
/mime:part
/mime:multipartRelated
/wsdl:output

Somewhere in the REP_PROTECTEL_IBDF element there is an element REP
containing : 

xsd:complexType name=REP
xsd:attribute name=href type=xsd:anyURI/
xsd:attribute name=ID type=xsd:ID/
/xsd:complexType

This element points to the attached document. 

Questions : do you see something unusual with this specification ? Are there
any reasons to encounter problems with wsdl2java and axis ? Does wsdl2java
take into account attachments ? 

First problem :  Null pointer exception with axis 1.1, but ok with axis 1.2
RC2
We have succeeded to call the service and get the attachment using
axis 1.2RC2 but not with axis 1.1. In axis 1.1 we get the following
NullPointerException : 

java.lang.NullPointerException
at java.io.FilterInputStream.available(FilterInputStream.java:146)
at
org.apache.xerces.impl.XMLEntityManager$RewindableInputStream.available(XMLE
ntityManager.java:2644)
at
sun.nio.cs.StreamDecoder$CharsetSD.inReady(StreamDecoder.java:487)
at
sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:448)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:182)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at
org.apache.xerces.impl.XMLEntityScanner.load(XMLEntityScanner.java:1740)
at
org.apache.xerces.impl.XMLEntityScanner.skipSpaces(XMLEntityScanner.java:125
9)
at
org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLD
ocumentScannerImpl.java:756)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocume
ntFragmentScannerImpl.java:338)
at
org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:8
28)
at
org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:7
58)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:148)
at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:117
8)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at
org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationCon
textImpl.java:242)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:538)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:376)
at org.apache.axis.client.Call.invokeEngine(Call.java:2583)
at org.apache.axis.client.Call.invoke(Call.java:2553)
at org.apache.axis.client.Call.invoke(Call.java:2248)
at org.apache.axis.client.Call.invoke(Call.java:2171)
at org.apache.axis.client.Call.invoke(Call.java:1691)

Analyzing this problem we have found that the
MultiPartRelatedInputStream  in 1.2 has its definition of the method
available() : 
public int available() throws java.io.IOException {
return (closed || eos) ? 0 : soapStream.available();
}
This does not exist in axis 1.1 so the super method is used. But the
super class is initialized with a super(null) in the constructor, so
NullPointerException. 

Questions : Is it normal that the attachment part does not fonction
correctly in 1.1 or am I doing something wrong ? Are there other people
using attachments with axis ? I would like to use axis 1.1, what
possibilities I have to correct the problem (beyond patching axis) ? Is axis
1.2 RC 2-3 stable enough to use it in a production mode ? Do you know the
release date of axis 1.2 ? 



Second problem : Wsdl2java generator

  It seems to me that the WSDL2Java generator does not treat the
attachments. The generated code of the REP class no place attribute to put
the attachment. Is this a bug or the declaration of the REP element is wrong
? 

 Also, the deserializer used for the REP object is generated as the
BeanDeserializer (so I get a class cast exception when axis tries to put the
AttachmentPart object in the object containing REP). I wrote a new
deserializer which

PLEASE unsubscribe me

Please unsubscribe me

RE: Howto not mess up response when using Call.setHandler

RE: Howto not mess up response when using Call.setHandler

Problems using axis 1.1 and 1.2 with attachments

5 matches

Site Navigation

Mail list logo

Footer information