date:20060627

Hi all,

is it possible to use MTOM from a handler? In other words, can a handler
send a request (say, for a file) to a web service? It seems to me that
the problem is the handler endpoint generated by Axis2, needed to
receive the response, which is wrong.



Thanks in advance,
Michele

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] MTOM question


Hi Michele,
This whole scenario is not very clear to me. Ofcourse a handler can
invoke a web service call but I don't understand the part It seems to
me that the problem is the handler endpoint generated by Axis2

Ajith

On 6/27/06, Michele Mazzucco [EMAIL PROTECTED] wrote:

Hi all,

is it possible to use MTOM from a handler? In other words, can a handler
send a request (say, for a file) to a web service? It seems to me that
the problem is the handler endpoint generated by Axis2, needed to
receive the response, which is wrong.



Thanks in advance,
Michele

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Ajith Ranabahu

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] MTOM question

Hi Ajith ,

I'll try to clarify my scenario:
service A.a() sends a request to B.foo(). The message is intercepted by
a handler (on the B side) before it hits the target. If needed the
handler sends a message to a service C.c() to get a file. After getting
a file it allow the message sent by A to pass through. After executing
the request, the response is intercepted again and redirected to service
A.b().

Ajith Ranabahu wrote:
 Hi Michele,
 This whole scenario is not very clear to me. Of course a handler can
 invoke a web service call but I don't understand the part It seems to
 me that the problem is the handler endpoint generated by Axis2
 
What I mean is that to receive the file from C.c(), the handler needs an
address, doesn't it?, but the one provided by Axis2 (I guess replyTo())
is wrong. How can the handler receive the response from service C.c()

Hope this clarifies your doubts,
Michele

 Ajith
 
 On 6/27/06, Michele Mazzucco [EMAIL PROTECTED] wrote:
 Hi all,

 is it possible to use MTOM from a handler? In other words, can a handler
 send a request (say, for a file) to a web service? It seems to me that
 the problem is the handler endpoint generated by Axis2, needed to
 receive the response, which is wrong.



 Thanks in advance,
 Michele

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] MTOM question

2006-06-27 Thread Saminda Abeyruwan

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Aha, it has the typical semantics of  Synapse pass through scenario.

Saminda

Michele Mazzucco wrote:
 Hi Ajith ,
 
 I'll try to clarify my scenario:
 service A.a() sends a request to B.foo(). The message is intercepted by
 a handler (on the B side) before it hits the target. If needed the
 handler sends a message to a service C.c() to get a file. After getting
 a file it allow the message sent by A to pass through. After executing
 the request, the response is intercepted again and redirected to service
 A.b().
 
 Ajith Ranabahu wrote:
 
Hi Michele,
This whole scenario is not very clear to me. Of course a handler can
invoke a web service call but I don't understand the part It seems to
me that the problem is the handler endpoint generated by Axis2

 
 What I mean is that to receive the file from C.c(), the handler needs an
 address, doesn't it?, but the one provided by Axis2 (I guess replyTo())
 is wrong. How can the handler receive the response from service C.c()
 
 Hope this clarifies your doubts,
 Michele
 
 
Ajith

On 6/27/06, Michele Mazzucco [EMAIL PROTECTED] wrote:

Hi all,

is it possible to use MTOM from a handler? In other words, can a handler
send a request (say, for a file) to a web service? It seems to me that
the problem is the handler endpoint generated by Axis2, needed to
receive the response, which is wrong.



Thanks in advance,
Michele

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEoRFeYmklbLuW6wYRAnA5AJ0QsEyXf0urW+ngy3wNx6L64dDq9ACgjK2u
0l0zCTT8pDhGv7KAf7L/eSY=
=85qQ
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] MTOM question

Saminda,

I don't know how Synapse works, however I add some informations at any
stage.

Michele

Saminda Abeyruwan wrote:
 Aha, it has the typical semantics of  Synapse pass through scenario.
 
 Saminda
 
 Michele Mazzucco wrote:
 Hi Ajith ,

 I'll try to clarify my scenario:
 service A.a() sends a request to B.foo(). The message is intercepted by
 a handler (on the B side) before it hits the target. If needed the
 handler sends a message to a service C.c() to get a file. After getting
 a file it allow the message sent by A to pass through. After executing
 the request, the response is intercepted again and redirected to service
 A.b().

 Ajith Ranabahu wrote:

 Hi Michele,
 This whole scenario is not very clear to me. Of course a handler can
 invoke a web service call but I don't understand the part It seems to
 me that the problem is the handler endpoint generated by Axis2

 What I mean is that to receive the file from C.c(), the handler needs an
 address, doesn't it?, but the one provided by Axis2 (I guess replyTo())
 is wrong. How can the handler receive the response from service C.c()

 Hope this clarifies your doubts,
 Michele


 Ajith

 On 6/27/06, Michele Mazzucco [EMAIL PROTECTED] wrote:

 Hi all,

 is it possible to use MTOM from a handler? In other words, can a handler
 send a request (say, for a file) to a web service? It seems to me that
 the problem is the handler endpoint generated by Axis2, needed to
 receive the response, which is wrong.



 Thanks in advance,
 Michele

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis 1.2.1] Adding Attachment

Hi all. I use Axis 1.2.1; i have generated some Web service clients by using 
the wsdl2java tool. Well i need now to add some attachments to the Call..how 
can i do? I have seen the Locator class and other classes but i'm not able to 
understand how to set the attachments... i have seen that in the stub class 
usually there is this a similar code:

if (super.cachedEndpoint == null) {
  throw new org.apache.axis.NoEndPointException();
}
org.apache.axis.client.Call _call = createCall();
_call.setOperation(_operations[0]);
_call.setEncodingStyle(null);
_call.setProperty(org.apache.axis.client.Call.SEND_TYPE_ATTR, 
Boolean.FALSE);
_call.setProperty(org.apache.axis.AxisEngine.PROP_DOMULTIREFS,
  Boolean.FALSE);
_call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS);
_call.setOperationName(new javax.xml.namespace.QName(
http://siporservice.sipor.it/;, execute));

setRequestHeaders(_call);
setAttachments(_call);

but how can i specify the Attachment to the _call object? How can this code 
undertand what files to add?

Thanks to all.
Angelo.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: passing objects of subtypes

2006-06-27 Thread Martin Gainty


Joshua-

I sent you the wsdl for Vehicle BaseType, Car SubType and Motorcycle subtype 
on sunday

Did you not receive it?
Please confirm,

Martin



From: Joshua Fox [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
CC: Martin Gainty [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: passing objects of subtypes
Date: Sun, 25 Jun 2006 17:06:04 +0300
MIME-Version: 1.0
Received: from mail.apache.org ([209.237.227.199]) by 
bay0-mc10-f3.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Sun, 
25 Jun 2006 07:06:34 -0700

Received: (qmail 85222 invoked by uid 500); 25 Jun 2006 14:06:26 -
Received: (qmail 85211 invoked by uid 99); 25 Jun 2006 14:06:26 -
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)by 
apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Jun 2006 07:06:26 -0700
Received: pass (asf.osuosl.org: domain of [EMAIL PROTECTED] designates 
64.233.162.201 as permitted sender)
Received: from [64.233.162.201] (HELO nz-out-0102.google.com) 
(64.233.162.201)by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Jun 
2006 07:06:25 -0700
Received: by nz-out-0102.google.com with SMTP id 12so1148637nzpfor 
axis-user@ws.apache.org; Sun, 25 Jun 2006 07:06:04 -0700 (PDT)
Received: by 10.36.77.2 with SMTP id z2mr5285859nza;Sun, 25 Jun 
2006 07:06:04 -0700 (PDT)

Received: by 10.36.37.14 with HTTP; Sun, 25 Jun 2006 07:06:04 -0700 (PDT)
X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlKtU9j2Z7TuGo=
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Precedence: bulk
list-help: mailto:[EMAIL PROTECTED]
list-unsubscribe: mailto:[EMAIL PROTECTED]
List-Post: mailto:axis-user@ws.apache.org
List-Id: axis-user.ws.apache.org
Delivered-To: mailing list axis-user@ws.apache.org
X-ASF-Spam-Status: No, hits=0.5 
required=10.0tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS

X-Spam-Check-By: apache.org
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;s=beta; 
d=gmail.com;
h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; 
   
b=seI7S5bR4YNrvZB+SgLPkWMTX7KD4Tv9ljGUnUjHEHXZSBuwD2XlG3DQpdfq9XykQGlcFCuXFoZpLuNbN4Pesmn2fhXR/So7C8Z27VCUdCAMm66PjeE0yZN1rsSR7OJHmg68JQj7nu9xaWlbTgOAZp7yWP3gFx5CM8/FQXnMEVE=
References: [EMAIL PROTECTED] 
[EMAIL PROTECTED]

X-Virus-Checked: Checked by ClamAV on apache.org
Return-Path: [EMAIL PROTECTED]
X-OriginalArrivalTime: 25 Jun 2006 14:06:34.0893 (UTC) 
FILETIME=[915113D0:01C69860]


I'm looking for the ability to pass an object of runtime type Car when the
declared parameter or return type is the superclass Vehicle. For this to
happen, the serializer must pass runtime type information in our
document-literal SOAP (an xsi:type attribute in the root element) saying
that the serialized object is a Car.

In .NET, you do this with
http://www.topxml.com/xmlserializer/xmlincludeattribute.asp

This article mentions how to do it with WebSphere tools
http://www-128.ibm.com/developerworks/websphere/techjournal/0401_brown/brown.html
but this seems non-standard.

There must be some standard way of doing it in Axis.

Thanks,


Joshua




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

SOAPAction is just a hint. You may notice that the WSDD doesn't reference the SOAPAction parameter. Axis uses the WSDD (not the WSDL) to figure out how to dispatch the request. If the information isn't in there, Axis can't figure it out.
AnneOn 6/26/06, Doug B [EMAIL PROTECTED] wrote:
Hmmm... so it turns out the options he can specify in his JBoss environment correspond to those on the java2wsdl tool. -T, -A, -y, -u. To me, that should mean they're relevant only to the server side. Yet specifying SOAPAction: OPERATION (-A), doesn't seem to resolve the problem. Furthermore, such options aren't even available on wsdl2java, which is all it seems he should need to be using in this case. (That's another issue, why he can't get an actual service deployed just from wsdl2java artifacts and why he's having to go down this java2wsdl path at all (using the code originally generated from wsdl2java)).
Don't get me wrong, I believe that the wsdd option is the solution (or altering the WSDL to use the operation name as the request element name), I just want to understand why some of Axis seems to understand that the SOAPAction field might need to contain the operation name, but some of it doesn't.
Thanks again for your patient instruction.DougOn 6/26/06,
Doug B [EMAIL PROTECTED] wrote:
I'm also discovering that my Axis customer is having to do some intermediate step where he generates code from our WSDL but can't find any deployable artifacts until he takes some other steps, at which point he has to re-specify several options, including... style, encoding, SOAP Action. So far, none of those were set correctly and his ?wsdl didn't even match the contract WSDL in those crucial parameters. Will be testing soon with hopefully the correct values specified there.
(I have no details at all on my .NET customer's environment, so it's also possible he had to do some tweaking himself.)DougOn 6/26/06,

Anne Thomas Manes
[EMAIL PROTECTED] wrote:

Not quite. Axis does not assume that you are using wrapped. Axis is reading the Qname of the incoming SOAP body and trying to map it to a known operation. Because you have not explicitly specified that the incoming doi:SuccessfulCompletionRequest QName maps to the method SuccessfulCompletionOperation, Axis doesn't know how to handle the request and returns an error of No such operation.
You haven't supplied any information about the .NET environment, so I can't tell you why it miraculously worked.Anne
On 6/26/06, Doug B
[EMAIL PROTECTED] wrote:

Thanks again (you too, Jeff). I'm starting to understand, but bear with me. Your article was helpful, but I'm still left wondering about a few things.
Namely, I'd have to change my WSDL to support wrapped, whether or not I'm going to actually use it on either side, right? I have to use particular naming conventions. And Axis seems to be assuming that I've done so. Again, strangely enough, my .NET customer's environment did not make this assumption.
Or is Axis' operation name expectation completely unrelated to the wrapped convention? Maybe that's the real issue, and *that* seems like something the WS-I would need to address. i.e. whether a request element name should match its operation name to be able to be easily looked up.
Doug

RE: [Axis 1.2.1] Adding Attachment

2006-06-27 Thread Qinjian Jian


Do something like this: 

String filePath=C:\\temp\\example.txt;
DataHandler dh = new DataHandler(new FileDataSource(filePath));
AttachmentPart part = new
org.apache.axis.attachments.AttachmentPart();
part.setDataHandler(dh);
call.addAttachmentPart(part);

Hope this helps

Thanks
 
Tim Jian
Momentum systems, Inc.
-Original Message-
From: Angelo Immediata [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 27, 2006 7:22 AM
To: Axis Axis
Subject: [Axis 1.2.1] Adding Attachment

Hi all. I use Axis 1.2.1; i have generated some Web service clients by
using the wsdl2java tool. Well i need now to add some attachments to the
Call..how can i do? I have seen the Locator class and other classes but
i'm not able to understand how to set the attachments... i have seen
that in the stub class usually there is this a similar code:

if (super.cachedEndpoint == null) {
  throw new org.apache.axis.NoEndPointException();
}
org.apache.axis.client.Call _call = createCall();
_call.setOperation(_operations[0]);
_call.setEncodingStyle(null);
_call.setProperty(org.apache.axis.client.Call.SEND_TYPE_ATTR,
Boolean.FALSE);
_call.setProperty(org.apache.axis.AxisEngine.PROP_DOMULTIREFS,
  Boolean.FALSE);
 
_call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS
);
_call.setOperationName(new javax.xml.namespace.QName(
http://siporservice.sipor.it/;, execute));

setRequestHeaders(_call);
setAttachments(_call);

but how can i specify the Attachment to the _call object? How can this
code undertand what files to add?

Thanks to all.
Angelo.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




NOTICE: This message (including any attachments) from Momentum Systems, Inc. 
contains information that is PRIVILEGED and CONFIDENTIAL.  If you are not an 
intended recipient, you are hereby notified that any dissemination of this 
message is strictly prohibited.  If you have received this message in error, 
please do not read, copy or forward this message.  Please permanently delete 
all copies and any attachments and notify the sender immediately by reply email 
or by calling our Office at 703.740.9300.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Axis 1.2.1] Adding Attachment

Hi.
First of all thanks for your help.
I have done in this way and it works...but for doing this i must change the 
java classes generated by wsdl2java...i'ld like to know if there is a way to 
avoid this modifications.
Thanks to all,
 Angelo.

-- Initial Header ---

From  : Qinjian Jian [EMAIL PROTECTED]
To  : axis-user@ws.apache.org
Cc  :
Date  : Tue, 27 Jun 2006 09:16:48 -0400
Subject : RE: [Axis 1.2.1] Adding Attachment








 Do something like this:

 String filePath=C:\\temp\\example.txt;
 DataHandler dh = new DataHandler(new FileDataSource(filePath));
 AttachmentPart part = new
 org.apache.axis.attachments.AttachmentPart();
 part.setDataHandler(dh);
 call.addAttachmentPart(part);

 Hope this helps

 Thanks

 Tim Jian
 Momentum systems, Inc.
 -Original Message-
 From: Angelo Immediata [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, June 27, 2006 7:22 AM
 To: Axis Axis
 Subject: [Axis 1.2.1] Adding Attachment

 Hi all. I use Axis 1.2.1; i have generated some Web service clients by
 using the wsdl2java tool. Well i need now to add some attachments to the
 Call..how can i do? I have seen the Locator class and other classes but
 i'm not able to understand how to set the attachments... i have seen
 that in the stub class usually there is this a similar code:

 if (super.cachedEndpoint == null) {
   throw new org.apache.axis.NoEndPointException();
 }
 org.apache.axis.client.Call _call = createCall();
 _call.setOperation(_operations[0]);
 _call.setEncodingStyle(null);
 _call.setProperty(org.apache.axis.client.Call.SEND_TYPE_ATTR,
 Boolean.FALSE);
 _call.setProperty(org.apache.axis.AxisEngine.PROP_DOMULTIREFS,
   Boolean.FALSE);

 _call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS
 );
 _call.setOperationName(new javax.xml.namespace.QName(
 http://siporservice.sipor.it/;, execute));

 setRequestHeaders(_call);
 setAttachments(_call);

 but how can i specify the Attachment to the _call object? How can this
 code undertand what files to add?

 Thanks to all.
 Angelo.



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




 NOTICE: This message (including any attachments) from Momentum Systems, Inc. 
 contains information that is PRIVILEGED and CONFIDENTIAL.  If you are not an 
 intended recipient, you are hereby notified that any dissemination of this 
 message is strictly prohibited.  If you have received this message in error, 
 please do not read, copy or forward this message.  Please permanently delete 
 all copies and any attachments and notify the sender immediately by reply 
 email or by calling our Office at 703.740.9300.

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Services.xml, RPCMessageReceiver, and Inheritance

2006-06-27 Thread Paul Truax









Im using
the RPCMessageReceiver. My class structure is as follows:



Main
Service Class: HelloService

Method to
expose: public Thing[] helloThere(String firstName, String lastName, String
middleName)



The
Thing Class extends ExtendedClass and

has 2 member
variables: private String firstName;

  private
String lastName;



ExtendedClass
has 1 member variable of middleName



When I put my
services.xml descriptor together to expose the HelloService, the extended class
and its variables do not show up Can I formulate my services.xml file to
tell access to follow the inheritance hierarchy?



Here is my
current services.xml file:







service

 parameter name=ServiceClass locked=falsecom.choicepoint.test.HelloService/parameter

 operation name=helloThere

 messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/

 /operation 

/service









Any help you
could give me would be greatly appreciated!

Sincerely,

Paul Truax

Re: No such operation

Interesting. So does the java2wsdl -A option do anything at all? Sorry if I'm just being thick here, but something just doesn't seem right when the only artifact required for defining an interface, the WSDL, is ignored. If the interface says the operation is named Operation, why is Axis expecting it to be named Request?
Again, I'm not disputing what you're saying, I just don't understand something about why it is so. Is Axis not actually able to define the service from the WSDL but only from the Java code generated from the WSDL? Even if Axis uses only the WSDD at deployment time, why is not not reflecting what was in the WSDL? I must be missing something obvious here, so feel free to give up on me whenever you want :-)
DougOn 6/27/06, Anne Thomas Manes [EMAIL PROTECTED] wrote:
SOAPAction is just a hint. You may notice that the WSDD doesn't reference the SOAPAction parameter. Axis uses the WSDD (not the WSDL) to figure out how to dispatch the request. If the information isn't in there, Axis can't figure it out.
AnneOn 6/26/06, Doug B
[EMAIL PROTECTED] wrote:
Hmmm... so it turns out the options he can specify in his JBoss environment correspond to those on the java2wsdl tool. -T, -A, -y, -u. To me, that should mean they're relevant only to the server side. Yet specifying SOAPAction: OPERATION (-A), doesn't seem to resolve the problem. Furthermore, such options aren't even available on wsdl2java, which is all it seems he should need to be using in this case. (That's another issue, why he can't get an actual service deployed just from wsdl2java artifacts and why he's having to go down this java2wsdl path at all (using the code originally generated from wsdl2java)).
Don't get me wrong, I believe that the wsdd option is the solution (or altering the WSDL to use the operation name as the request element name), I just want to understand why some of Axis seems to understand that the SOAPAction field might need to contain the operation name, but some of it doesn't.
Thanks again for your patient instruction.DougOn 6/26/06,
Doug B [EMAIL PROTECTED] wrote:
I'm also discovering that my Axis customer is having to do some intermediate step where he generates code from our WSDL but can't find any deployable artifacts until he takes some other steps, at which point he has to re-specify several options, including... style, encoding, SOAP Action. So far, none of those were set correctly and his ?wsdl didn't even match the contract WSDL in those crucial parameters. Will be testing soon with hopefully the correct values specified there.
(I have no details at all on my .NET customer's environment, so it's also possible he had to do some tweaking himself.)DougOn 6/26/06,

Anne Thomas Manes
[EMAIL PROTECTED] wrote:

Re: [Axis2] Flash Connectivity Problems

2006-06-27 Thread Luke DeWitt


Hello again,

I'm sorry, I may have missed something when I sent my last message, and I am 
hitting an error. I am very new to Axis so I am not sure what exactely I 
should be looking for in these logs.


Here is a bit more information:
In Flash I get the message - Error opening URL 
http://localhost:8080/axis2/services/version?wsdl;


In TDIMon I get:

669.74180154 Flash.exe:3080 85F8B1F8 IRP_MJ_CREATE TCP:0.0.0.0:0  SUCCESS 
Address Open
669.74186412 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1126 
SUCCESS Error Event
669.74187753 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1126 
SUCCESS Disconnect Event
669.74188926 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1126 
SUCCESS Receive Event
669.74190100 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1126 
SUCCESS Expedited Receive Event
669.74191189 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1126 
SUCCESS Chained Receive Event
669.74192307 Flash.exe:3080 85F8B1F8 TDI_QUERY_INFORMATION TCP:0.0.0.0:1126 
SUCCESS Query Address
669.74194514 Flash.exe:3080 85F8B1F8 TDI_QUERY_INFORMATION TCP:0.0.0.0:1126 
SUCCESS Query Address
669.74750338 Flash.exe:3080 85FCE4A8 IRP_MJ_CREATE TCP:Connection obj 
SUCCESS Context:0x854D6E50
669.74752489 Flash.exe:3080 85FCE4A8 TDI_ASSOCIATE_ADDRESS TCP:Connection 
obj  SUCCESS TCP:0.0.0.0:1126
669.74754249 Flash.exe:3080 85FCE4A8 TDI_CONNECT TCP:0.0.0.0:1126 
127.0.0.1:8080 SUCCESS-3555
669.74759641 tomcat5.exe:3932 854CBF90 TDI_EVENT_CONNECT TCP:0.0.0.0:8080 
127.0.0.1:1126 MORE_PROCESSING_REQUIRED
669.74760815 tomcat5.exe:3932 85309578 TDI_ACCEPT TCP:0.0.0.0:8080 
127.0.0.1:1126 SUCCESS-3556
669.74770089 tomcat5.exe:3932 861E1E98 IRP_MJ_CREATE TCP:Connection obj 
SUCCESS Context:0x85FB95E0
669.74771738 tomcat5.exe:3932 861E1E98 TDI_ASSOCIATE_ADDRESS TCP:Connection 
obj  SUCCESS TCP:0.0.0.0:8080
669.74784505 tomcat5.exe:3932 85309578 IRP_MJ_DEVICE_CONTROL 
TCP:0.0.0.0:8080 127.0.0.1:1126 SUCCESS IOCTL_TCP_SET_INFORMATION_EX
669.74801350 Flash.exe:3080 85FCE4A8 IRP_MJ_DEVICE_CONTROL TCP:0.0.0.0:1126 
127.0.0.1:8080 SUCCESS IOCTL_TCP_SET_INFORMATION_EX
669.74805429 Flash.exe:3080 85FCE4A8 TDI_SEND TCP:0.0.0.0:1126 
127.0.0.1:8080 SUCCESS-3563 Length:208
669.74807580 tomcat5.exe:3932 854CBF90 TDI_EVENT_RECEIVE TCP:0.0.0.0:8080 
127.0.0.1:1126 SUCCESS Length:208 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.76955814 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080 
127.0.0.1:1126 SUCCESS-3568 Length:3271
669.76960591 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126 
127.0.0.1:8080 MORE_PROCESSING_REQUIRED Length:1460 Flags: LOOKAHEAD 
DISPATCH
669.76961765 Flash.exe:3080 85FCE4A8 TDI_RECEIVE TCP:0.0.0.0:1126 
127.0.0.1:8080 SUCCESS
669.76970872 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080 
127.0.0.1:1126 SUCCESS-3571 Length:5
669.76972129 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126 
127.0.0.1:8080 SUCCESS Length:5 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.87226393 Flash.exe:3080 85FCE4A8 TDI_SEND TCP:0.0.0.0:1126 
127.0.0.1:8080 SUCCESS-3574 Length:570
669.87230779 tomcat5.exe:3932 854CBF90 TDI_EVENT_RECEIVE TCP:0.0.0.0:8080 
127.0.0.1:1126 SUCCESS Length:570 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.90076309 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080 
127.0.0.1:1126 SUCCESS-3577 Length:461
669.90081114 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126 
127.0.0.1:8080 SUCCESS Length:461 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.90093350 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080 
127.0.0.1:1126 SUCCESS-3580 Length:92
669.90094775 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126 
127.0.0.1:8080 SUCCESS Length:92 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.90126762 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080 
127.0.0.1:1126 SUCCESS-3585 Length:2297
669.90128466 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126 
127.0.0.1:8080 MORE_PROCESSING_REQUIRED Length:1460 Flags: LOOKAHEAD 
DISPATCH
669.90129500 Flash.exe:3080 85FCE4A8 TDI_RECEIVE TCP:0.0.0.0:1126 
127.0.0.1:8080 SUCCESS
669.90137322 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080 
127.0.0.1:1126 SUCCESS-3588 Length:56
669.90138635 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126 
127.0.0.1:8080 SUCCESS Length:56 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.90144530 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080 
127.0.0.1:1126 SUCCESS-3591 Length:5
669.90146401 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126 
127.0.0.1:8080 SUCCESS Length:5 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.90160258 tomcat5.exe:3932 85309578 TDI_DISCONNECT TCP:0.0.0.0:8080 
127.0.0.1:1126 SUCCESS-3594 RELEASE
669.90161850 Flash.exe:3080 85F8B1F8 TDI_EVENT_DISCONNECT TCP:0.0.0.0:1126 
127.0.0.1:8080 SUCCESS RELEASE
669.91214470 Flash.exe:3080 85FCE4A8 TDI_DISCONNECT TCP:0.0.0.0:1126 
SUCCESS-3600 ABORT
669.91218213 tomcat5.exe:3932 854CBF90 TDI_EVENT_DISCONNECT TCP:0.0.0.0:8080 
SUCCESS ABORT
669.91222153

[Axis2] Handler unexpected behaviour

Hi all,

from my previous posts I understood handlers are 'application scope',
that is they maintain a state across different client invocations.
I have a handler intercepting both incoming and outgoing messages and
unfortunately I realized that instance fields are 'reset' (see logs
below). Is there any reason for this counter intuitive behavior?


// Request
DEBUG ncl.qosp.modules.node.NodeDispatcher:findService - Trying to find
the target service...
INFO  ncl.qosp.modules.node.NodeDispatcher:findService - Required
service [MyService]


// Response
DEBUG ncl.qosp.modules.node.NodeDispatcher:createResponseHeader - node
[10.8.149.156:18080], service [null],


while if I declare the fields as 'static' it works fine.



Thanks,
Michele

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: passing objects of subtypes

2006-06-27 Thread Joshua Fox

Thanks, yes. It was valuable to me in learning how to do this and building the WSDL shown in my last message.

Joshua
On 6/27/06, Martin Gainty [EMAIL PROTECTED] wrote:
Joshua-I sent you the wsdl for Vehicle BaseType, Car SubType and Motorcycle subtypeon sunday
Did you not receive it?Please confirm,Martin

Re: [Axis2] Flash Connectivity Problems


Hi,

From this log we do get the details of some communication between

Flash and Axis but not what was passed in between. With TCPMon you can
actually see what's being passed (if there is any)
But from the looks of it, I feel that the service may not be properly
deployed. Did you try the URL in the browser ? it should pop up the
WSDL file.

Ajith

On 6/27/06, Luke DeWitt [EMAIL PROTECTED] wrote:

Hello again,

I'm sorry, I may have missed something when I sent my last message, and I am
hitting an error. I am very new to Axis so I am not sure what exactely I
should be looking for in these logs.

Here is a bit more information:
In Flash I get the message - Error opening URL
http://localhost:8080/axis2/services/version?wsdl;

In TDIMon I get:

669.74180154 Flash.exe:3080 85F8B1F8 IRP_MJ_CREATE TCP:0.0.0.0:0  SUCCESS
Address Open
669.74186412 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1126
SUCCESS Error Event
669.74187753 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1126
SUCCESS Disconnect Event
669.74188926 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1126
SUCCESS Receive Event
669.74190100 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1126
SUCCESS Expedited Receive Event
669.74191189 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1126
SUCCESS Chained Receive Event
669.74192307 Flash.exe:3080 85F8B1F8 TDI_QUERY_INFORMATION TCP:0.0.0.0:1126
SUCCESS Query Address
669.74194514 Flash.exe:3080 85F8B1F8 TDI_QUERY_INFORMATION TCP:0.0.0.0:1126
SUCCESS Query Address
669.74750338 Flash.exe:3080 85FCE4A8 IRP_MJ_CREATE TCP:Connection obj
SUCCESS Context:0x854D6E50
669.74752489 Flash.exe:3080 85FCE4A8 TDI_ASSOCIATE_ADDRESS TCP:Connection
obj  SUCCESS TCP:0.0.0.0:1126
669.74754249 Flash.exe:3080 85FCE4A8 TDI_CONNECT TCP:0.0.0.0:1126
127.0.0.1:8080 SUCCESS-3555
669.74759641 tomcat5.exe:3932 854CBF90 TDI_EVENT_CONNECT TCP:0.0.0.0:8080
127.0.0.1:1126 MORE_PROCESSING_REQUIRED
669.74760815 tomcat5.exe:3932 85309578 TDI_ACCEPT TCP:0.0.0.0:8080
127.0.0.1:1126 SUCCESS-3556
669.74770089 tomcat5.exe:3932 861E1E98 IRP_MJ_CREATE TCP:Connection obj
SUCCESS Context:0x85FB95E0
669.74771738 tomcat5.exe:3932 861E1E98 TDI_ASSOCIATE_ADDRESS TCP:Connection
obj  SUCCESS TCP:0.0.0.0:8080
669.74784505 tomcat5.exe:3932 85309578 IRP_MJ_DEVICE_CONTROL
TCP:0.0.0.0:8080 127.0.0.1:1126 SUCCESS IOCTL_TCP_SET_INFORMATION_EX
669.74801350 Flash.exe:3080 85FCE4A8 IRP_MJ_DEVICE_CONTROL TCP:0.0.0.0:1126
127.0.0.1:8080 SUCCESS IOCTL_TCP_SET_INFORMATION_EX
669.74805429 Flash.exe:3080 85FCE4A8 TDI_SEND TCP:0.0.0.0:1126
127.0.0.1:8080 SUCCESS-3563 Length:208
669.74807580 tomcat5.exe:3932 854CBF90 TDI_EVENT_RECEIVE TCP:0.0.0.0:8080
127.0.0.1:1126 SUCCESS Length:208 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.76955814 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080
127.0.0.1:1126 SUCCESS-3568 Length:3271
669.76960591 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126
127.0.0.1:8080 MORE_PROCESSING_REQUIRED Length:1460 Flags: LOOKAHEAD
DISPATCH
669.76961765 Flash.exe:3080 85FCE4A8 TDI_RECEIVE TCP:0.0.0.0:1126
127.0.0.1:8080 SUCCESS
669.76970872 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080
127.0.0.1:1126 SUCCESS-3571 Length:5
669.76972129 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126
127.0.0.1:8080 SUCCESS Length:5 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.87226393 Flash.exe:3080 85FCE4A8 TDI_SEND TCP:0.0.0.0:1126
127.0.0.1:8080 SUCCESS-3574 Length:570
669.87230779 tomcat5.exe:3932 854CBF90 TDI_EVENT_RECEIVE TCP:0.0.0.0:8080
127.0.0.1:1126 SUCCESS Length:570 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.90076309 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080
127.0.0.1:1126 SUCCESS-3577 Length:461
669.90081114 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126
127.0.0.1:8080 SUCCESS Length:461 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.90093350 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080
127.0.0.1:1126 SUCCESS-3580 Length:92
669.90094775 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126
127.0.0.1:8080 SUCCESS Length:92 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.90126762 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080
127.0.0.1:1126 SUCCESS-3585 Length:2297
669.90128466 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126
127.0.0.1:8080 MORE_PROCESSING_REQUIRED Length:1460 Flags: LOOKAHEAD
DISPATCH
669.90129500 Flash.exe:3080 85FCE4A8 TDI_RECEIVE TCP:0.0.0.0:1126
127.0.0.1:8080 SUCCESS
669.90137322 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080
127.0.0.1:1126 SUCCESS-3588 Length:56
669.90138635 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126
127.0.0.1:8080 SUCCESS Length:56 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.90144530 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080
127.0.0.1:1126 SUCCESS-3591 Length:5
669.90146401 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE TCP:0.0.0.0:1126
127.0.0.1:8080 SUCCESS Length:5 Flags: ENTIRE_MESSAGE LOOKAHEAD DISPATCH
669.90160258 tomcat5.exe:3932 85309578 TDI_DISCONNECT

Re: [Axis2] Handler unexpected behaviour


Hi


from my previous posts I understood handlers are 'application scope',
that is they maintain a state across different client invocations.


Actually handlers are supposed to be stateless! They should not
maintain anything by themselves, rather they should be using the
appropriate context  to store anything required.


I have a handler intercepting both incoming and outgoing messages and
unfortunately I realized that instance fields are 'reset' (see logs
below). Is there any reason for this counter intuitive behavior?



So what I seem to understand is your handler implementation may not
have been done in the recommended way.Have a look at this article [1]
by Deepal which explains how the handlers work.



--
Ajith Ranabahu

[1] http://www.developer.com/services/article.php/3529321

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] rest question

2006-06-27 Thread Anamitra . Bhattacharyya


Hi
As per the axis2 doc it seems that if I want to do a POST rest service -
the only way axis runtime would detect which method to delegate the call to
is from the name of the top level element in the http message body XML -
right?
I have a service whose method definition is like

public OMElement dothis(OMElelemt payload)

When I do the SOAP client  invoke I send the soap action as urn:dothis and
my payload top element does not match the method name - This works fine
with axis2.

But now if I have to do REST call and not have the root element as method
name - how can I acheive that using rest? [I presume soap action is not
going to work here or is it?]

thanks
Anamitra


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Flash Connectivity Problems

2006-06-27 Thread Luke DeWitt

Well I can use (pretty much) the EXACT same code to call other webservices 
online and I get exactely what I am looking for, it's just this single 
webservice that I have currently deployed in Axis2 that doesn't work. That's 
why I was wondering if there was any sort of security setting, though it 
doesn't make too much sense that the same webservice would work in my WS 
Analyzer program, and not in Flash.


--LD

- Original Message - 
From: Ajith Ranabahu [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Tuesday, June 27, 2006 11:45 AM
Subject: Re: [Axis2] Flash Connectivity Problems



Hmmm...
Strange indeed. Could this be a problem with the Flash code ?(I'm zero
about Web services in Action script)

Ajith

On 6/27/06, Luke DeWitt [EMAIL PROTECTED] wrote:

Hi,

I have tried the URL in the browser, and it does come up with the XML 
File.
The Web Service I am currently trying to use is the default one that 
comes

with Axis2 when I first deployed it, the 'version?WSDL'. I am just trying
this one because the webservice I will be using is not completed yet. I
really can't understand why it works for webservices which can be found
online, but not with ones I have running in Tomcat.

Thanks,
--LD

- Original Message -
From: Ajith Ranabahu [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, June 27, 2006 11:36 AM
Subject: Re: [Axis2] Flash Connectivity Problems


 Hi,
 From this log we do get the details of some communication between
 Flash and Axis but not what was passed in between. With TCPMon you can
 actually see what's being passed (if there is any)
 But from the looks of it, I feel that the service may not be properly
 deployed. Did you try the URL in the browser ? it should pop up the
 WSDL file.

 Ajith

 On 6/27/06, Luke DeWitt [EMAIL PROTECTED] wrote:
 Hello again,

 I'm sorry, I may have missed something when I sent my last message, 
 and I

 am
 hitting an error. I am very new to Axis so I am not sure what exactely 
 I

 should be looking for in these logs.

 Here is a bit more information:
 In Flash I get the message - Error opening URL
 http://localhost:8080/axis2/services/version?wsdl;

 In TDIMon I get:

 669.74180154 Flash.exe:3080 85F8B1F8 IRP_MJ_CREATE TCP:0.0.0.0:0 
 SUCCESS

 Address Open
 669.74186412 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
 TCP:0.0.0.0:1126
 SUCCESS Error Event
 669.74187753 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
 TCP:0.0.0.0:1126
 SUCCESS Disconnect Event
 669.74188926 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
 TCP:0.0.0.0:1126
 SUCCESS Receive Event
 669.74190100 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
 TCP:0.0.0.0:1126
 SUCCESS Expedited Receive Event
 669.74191189 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
 TCP:0.0.0.0:1126
 SUCCESS Chained Receive Event
 669.74192307 Flash.exe:3080 85F8B1F8 TDI_QUERY_INFORMATION
 TCP:0.0.0.0:1126
 SUCCESS Query Address
 669.74194514 Flash.exe:3080 85F8B1F8 TDI_QUERY_INFORMATION
 TCP:0.0.0.0:1126
 SUCCESS Query Address
 669.74750338 Flash.exe:3080 85FCE4A8 IRP_MJ_CREATE TCP:Connection obj
 SUCCESS Context:0x854D6E50
 669.74752489 Flash.exe:3080 85FCE4A8 TDI_ASSOCIATE_ADDRESS 
 TCP:Connection

 obj  SUCCESS TCP:0.0.0.0:1126
 669.74754249 Flash.exe:3080 85FCE4A8 TDI_CONNECT TCP:0.0.0.0:1126
 127.0.0.1:8080 SUCCESS-3555
 669.74759641 tomcat5.exe:3932 854CBF90 TDI_EVENT_CONNECT 
 TCP:0.0.0.0:8080

 127.0.0.1:1126 MORE_PROCESSING_REQUIRED
 669.74760815 tomcat5.exe:3932 85309578 TDI_ACCEPT TCP:0.0.0.0:8080
 127.0.0.1:1126 SUCCESS-3556
 669.74770089 tomcat5.exe:3932 861E1E98 IRP_MJ_CREATE TCP:Connection 
 obj

 SUCCESS Context:0x85FB95E0
 669.74771738 tomcat5.exe:3932 861E1E98 TDI_ASSOCIATE_ADDRESS
 TCP:Connection
 obj  SUCCESS TCP:0.0.0.0:8080
 669.74784505 tomcat5.exe:3932 85309578 IRP_MJ_DEVICE_CONTROL
 TCP:0.0.0.0:8080 127.0.0.1:1126 SUCCESS IOCTL_TCP_SET_INFORMATION_EX
 669.74801350 Flash.exe:3080 85FCE4A8 IRP_MJ_DEVICE_CONTROL
 TCP:0.0.0.0:1126
 127.0.0.1:8080 SUCCESS IOCTL_TCP_SET_INFORMATION_EX
 669.74805429 Flash.exe:3080 85FCE4A8 TDI_SEND TCP:0.0.0.0:1126
 127.0.0.1:8080 SUCCESS-3563 Length:208
 669.74807580 tomcat5.exe:3932 854CBF90 TDI_EVENT_RECEIVE 
 TCP:0.0.0.0:8080

 127.0.0.1:1126 SUCCESS Length:208 Flags: ENTIRE_MESSAGE LOOKAHEAD
 DISPATCH
 669.76955814 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080
 127.0.0.1:1126 SUCCESS-3568 Length:3271
 669.76960591 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE 
 TCP:0.0.0.0:1126

 127.0.0.1:8080 MORE_PROCESSING_REQUIRED Length:1460 Flags: LOOKAHEAD
 DISPATCH
 669.76961765 Flash.exe:3080 85FCE4A8 TDI_RECEIVE TCP:0.0.0.0:1126
 127.0.0.1:8080 SUCCESS
 669.76970872 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080
 127.0.0.1:1126 SUCCESS-3571 Length:5
 669.76972129 Flash.exe:3080 85F8B1F8 TDI_EVENT_RECEIVE 
 TCP:0.0.0.0:1126
 127.0.0.1:8080 SUCCESS Length:5 Flags: ENTIRE_MESSAGE LOOKAHEAD 
 DISPATCH

 669.87226393 Flash.exe:3080 85FCE4A8 TDI_SEND TCP:0.0.0.0:1126
 127.0.0.1:8080 SUCCESS-3574 Length:570
 669.87230779 tomcat5.exe:3932

Re: [Axis2] Flash Connectivity Problems


Hi,
ok here is a small thing to try out.
Goto  http://tools.wso2.net/tryit/tungsten/1.0/. there are 10 tungsten
instances running (Tungsten is based on Axis2 with lot of additions
but still it is a full blown Axis2 server) each tungsten server has
the version service up and running.
point the flash code to one of the tungsten version services and try
it out. If that works we can safely assume that it is not a problem
with Axis2 in general but probably something particular to your Axis2
instance.

Ajith


On 6/27/06, Luke DeWitt [EMAIL PROTECTED] wrote:

Well I can use (pretty much) the EXACT same code to call other webservices
online and I get exactely what I am looking for, it's just this single
webservice that I have currently deployed in Axis2 that doesn't work. That's
why I was wondering if there was any sort of security setting, though it
doesn't make too much sense that the same webservice would work in my WS
Analyzer program, and not in Flash.

--LD

- Original Message -
From: Ajith Ranabahu [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, June 27, 2006 11:45 AM
Subject: Re: [Axis2] Flash Connectivity Problems


 Hmmm...
 Strange indeed. Could this be a problem with the Flash code ?(I'm zero
 about Web services in Action script)

 Ajith

 On 6/27/06, Luke DeWitt [EMAIL PROTECTED] wrote:
 Hi,

 I have tried the URL in the browser, and it does come up with the XML
 File.
 The Web Service I am currently trying to use is the default one that
 comes
 with Axis2 when I first deployed it, the 'version?WSDL'. I am just trying
 this one because the webservice I will be using is not completed yet. I
 really can't understand why it works for webservices which can be found
 online, but not with ones I have running in Tomcat.

 Thanks,
 --LD

 - Original Message -
 From: Ajith Ranabahu [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Tuesday, June 27, 2006 11:36 AM
 Subject: Re: [Axis2] Flash Connectivity Problems


  Hi,
  From this log we do get the details of some communication between
  Flash and Axis but not what was passed in between. With TCPMon you can
  actually see what's being passed (if there is any)
  But from the looks of it, I feel that the service may not be properly
  deployed. Did you try the URL in the browser ? it should pop up the
  WSDL file.
 
  Ajith
 
  On 6/27/06, Luke DeWitt [EMAIL PROTECTED] wrote:
  Hello again,
 
  I'm sorry, I may have missed something when I sent my last message,
  and I
  am
  hitting an error. I am very new to Axis so I am not sure what exactely
  I
  should be looking for in these logs.
 
  Here is a bit more information:
  In Flash I get the message - Error opening URL
  http://localhost:8080/axis2/services/version?wsdl;
 
  In TDIMon I get:
 
  669.74180154 Flash.exe:3080 85F8B1F8 IRP_MJ_CREATE TCP:0.0.0.0:0
  SUCCESS
  Address Open
  669.74186412 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
  TCP:0.0.0.0:1126
  SUCCESS Error Event
  669.74187753 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
  TCP:0.0.0.0:1126
  SUCCESS Disconnect Event
  669.74188926 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
  TCP:0.0.0.0:1126
  SUCCESS Receive Event
  669.74190100 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
  TCP:0.0.0.0:1126
  SUCCESS Expedited Receive Event
  669.74191189 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
  TCP:0.0.0.0:1126
  SUCCESS Chained Receive Event
  669.74192307 Flash.exe:3080 85F8B1F8 TDI_QUERY_INFORMATION
  TCP:0.0.0.0:1126
  SUCCESS Query Address
  669.74194514 Flash.exe:3080 85F8B1F8 TDI_QUERY_INFORMATION
  TCP:0.0.0.0:1126
  SUCCESS Query Address
  669.74750338 Flash.exe:3080 85FCE4A8 IRP_MJ_CREATE TCP:Connection obj
  SUCCESS Context:0x854D6E50
  669.74752489 Flash.exe:3080 85FCE4A8 TDI_ASSOCIATE_ADDRESS
  TCP:Connection
  obj  SUCCESS TCP:0.0.0.0:1126
  669.74754249 Flash.exe:3080 85FCE4A8 TDI_CONNECT TCP:0.0.0.0:1126
  127.0.0.1:8080 SUCCESS-3555
  669.74759641 tomcat5.exe:3932 854CBF90 TDI_EVENT_CONNECT
  TCP:0.0.0.0:8080
  127.0.0.1:1126 MORE_PROCESSING_REQUIRED
  669.74760815 tomcat5.exe:3932 85309578 TDI_ACCEPT TCP:0.0.0.0:8080
  127.0.0.1:1126 SUCCESS-3556
  669.74770089 tomcat5.exe:3932 861E1E98 IRP_MJ_CREATE TCP:Connection
  obj
  SUCCESS Context:0x85FB95E0
  669.74771738 tomcat5.exe:3932 861E1E98 TDI_ASSOCIATE_ADDRESS
  TCP:Connection
  obj  SUCCESS TCP:0.0.0.0:8080
  669.74784505 tomcat5.exe:3932 85309578 IRP_MJ_DEVICE_CONTROL
  TCP:0.0.0.0:8080 127.0.0.1:1126 SUCCESS IOCTL_TCP_SET_INFORMATION_EX
  669.74801350 Flash.exe:3080 85FCE4A8 IRP_MJ_DEVICE_CONTROL
  TCP:0.0.0.0:1126
  127.0.0.1:8080 SUCCESS IOCTL_TCP_SET_INFORMATION_EX
  669.74805429 Flash.exe:3080 85FCE4A8 TDI_SEND TCP:0.0.0.0:1126
  127.0.0.1:8080 SUCCESS-3563 Length:208
  669.74807580 tomcat5.exe:3932 854CBF90 TDI_EVENT_RECEIVE
  TCP:0.0.0.0:8080
  127.0.0.1:1126 SUCCESS Length:208 Flags: ENTIRE_MESSAGE LOOKAHEAD
  DISPATCH
  669.76955814 tomcat5.exe:3932 85309578 TDI_SEND TCP:0.0.0.0:8080
  127.0.0.1:1126 SUCCESS-3568 Length:3271

how to change the address of the webservices in run time?

2006-06-27 Thread Victor Sosa


The Service class will by default make a Stub which points to the
endpoint URL described in the WSDL file, but I may also specify a
different URL? and make request to the new adresss?

How to?

NOTE: I have two server, one for production and other for develop.


--
Victor Sosa
Desarrollador Java
TeKnowLogic Dominicana, C. x A.
http://www.tkl.com.do
http://vnsjava.blogspot.com/
[EMAIL PROTECTED]
Registered Linux User #369216

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re:how to change the address of the webservices in run time?

Hi.
You can set the endpoint address in this way (by acting on the xxxLocator.java 
class):

xLocator loc = new xLocator();
loc.setEndpointAddress(servicePortName,the new URL (as a String))

Hipe this can help you.
Bye,
 Angelo

-- Initial Header ---

From  : Victor Sosa [EMAIL PROTECTED]
To  : axis-user@ws.apache.org
Cc  :
Date  : Tue, 27 Jun 2006 11:04:46 -0400
Subject : how to change the address of the webservices in run time?







 The Service class will by default make a Stub which points to the
 endpoint URL described in the WSDL file, but I may also specify a
 different URL? and make request to the new adresss?

 How to?

 NOTE: I have two server, one for production and other for develop.


 --
 Victor Sosa
 Desarrollador Java
 TeKnowLogic Dominicana, C. x A.
 http://www.tkl.com.do
 http://vnsjava.blogspot.com/
 [EMAIL PROTECTED]
 Registered Linux User #369216

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: how to change the address of the webservices in run time?

2006-06-27 Thread Mark Mynsted

Create a properties file with the endpoint address.  Then put the
properties file someplace in your classpath and load the file using the
class loader.


Perhaps something like:

Properties properties = new Properties();
 java.lang.String initialEndpointAddress = null;
 try
 {

properties.load(getClass().getResourceAsStream(/endpoint.properties));
initialEndpointAddress = properties.getProperty(endpointaddress);
System.out.println(endpointaddress= + initialEndpointAddress);
 }
 catch (IOException e)
 {
System.out.println(e.getMessage());
 }
 return (initialEndpointAddress ==
null?https://myproductionendpointaddress:initialEndpointAddress);


--
MM

Victor Sosa wrote:
 The Service class will by default make a Stub which points to the
 endpoint URL described in the WSDL file, but I may also specify a
 different URL? and make request to the new adresss?
 
 How to?
 
 NOTE: I have two server, one for production and other for develop.
 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Type missing! error using Axis2 WSDL2Java w/ Amazon WS

2006-06-27 Thread Ken Yee

Anyone try the latest Axis2 1.0's WSDL2Java against
Amazon's web services?  I get a cryptic Type missing
error (it'd be nice if it printed out what type it's
looking for so we'd have a better clue about what's
going wrong ;-)

Here's the WSDL URL (I use Ant to pull the WSDL file
down locally though):
http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl

This WSDL works fine w/ Axis 1.x...

 ken

 [java] Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException:
org.apache.axis2.schema.SchemaCompilationException:
Type missing!
 [java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(C
odeGenerationEngine.java:185)
 [java] at
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
 [java] at
org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
 [java] Caused by: java.lang.RuntimeException:
org.apache.axis2.schema.Schem
aCompilationException: Type missing!
 [java] at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.eng
age(SimpleDBExtension.java:117)
 [java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(C
odeGenerationEngine.java:140)
 [java] ... 2 more
 [java] Caused by:
org.apache.axis2.schema.SchemaCompilationException:
Type
missing!
 [java] at
org.apache.axis2.schema.writer.JavaBeanWriter.addPropertyEntr
ies(JavaBeanWriter.java:464)
 [java] at
org.apache.axis2.schema.writer.JavaBeanWriter.populateInfo(Ja
vaBeanWriter.java:426)
 [java] at
org.apache.axis2.schema.writer.JavaBeanWriter.getBeanElement(
JavaBeanWriter.java:403)


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: how to change the address of the webservices in run time?

2006-06-27 Thread Victor Sosa


Pls, give me a example of servicePortName.

Thks for the answer

On 6/27/06, Angelo Immediata [EMAIL PROTECTED] wrote:

Hi.
You can set the endpoint address in this way (by acting on the xxxLocator.java 
class):

xLocator loc = new xLocator();
loc.setEndpointAddress(servicePortName,the new URL (as a String))

Hipe this can help you.
Bye,
 Angelo

-- Initial Header ---

From  : Victor Sosa [EMAIL PROTECTED]
To  : axis-user@ws.apache.org
Cc  :
Date  : Tue, 27 Jun 2006 11:04:46 -0400
Subject : how to change the address of the webservices in run time?







 The Service class will by default make a Stub which points to the
 endpoint URL described in the WSDL file, but I may also specify a
 different URL? and make request to the new adresss?

 How to?

 NOTE: I have two server, one for production and other for develop.


 --
 Victor Sosa
 Desarrollador Java
 TeKnowLogic Dominicana, C. x A.
 http://www.tkl.com.do
 http://vnsjava.blogspot.com/
 [EMAIL PROTECTED]
 Registered Linux User #369216

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Victor Sosa
Desarrollador Java
TeKnowLogic Dominicana, C. x A.
http://www.tkl.com.do
http://vnsjava.blogspot.com/
[EMAIL PROTECTED]
Registered Linux User #369216

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Axis help

2006-06-27 Thread kavithaa Rajavenkateshwaran


Hi,

I'm new to Axis.I wrote  a WS that returns array of String.But the  
result i'm getting is null and not the String array. I have few doubts


1. Does axis support Arrays by default or I need to write a custom  
serializer/ deserializer(Actually i wanted to use vectors, but I  
didn't know how to write a custom serailizer/deserializer).I'm not  
using a bean convention.


help me to resolve this.



my wsdd

deployment
xmlns=http://xml.apache.org/axis/wsdd/;
xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;

  !-- Services from fileretriveService WSDL service --

  service name=retrive provider=java:RPC style=rpc  
use=encoded

  parameter name=wsdlTargetNamespace value=urn:dbdata/
  parameter name=wsdlServiceElement value=fileretriveService/
  parameter name=schemaUnqualified value=urn:dbdata/
  parameter name=wsdlServicePort value=retrive/
  parameter name=className  
value=dbdata.ws.RetriveSoapBindingImpl/

  parameter name=wsdlPortType value=fileretrive/
  parameter name=typeMappingVersion value=1.2/
  operation name=getWave qname=operNS:getWave  
xmlns:operNS=urn:dbdata returnQName=getWaveReturn  
returnType=rtns:ArrayOf_soapenc_string xmlns:rtns=urn:dbdata  
returnItemType=tns2:string xmlns:tns2=http://schemas.xmlsoap.org/ 
soap/encoding/ soapAction= 

  /operation
  operation name=getMedia qname=operNS:getMedia  
xmlns:operNS=urn:dbdata returnQName=getMediaReturn  
returnType=rtns:ArrayOf_soapenc_string xmlns:rtns=urn:dbdata  
returnItemType=tns2:string xmlns:tns2=http://schemas.xmlsoap.org/ 
soap/encoding/ soapAction= 

  /operation
  parameter name=allowedMethods value=getMedia getWave/
  parameter name=scope value=Session/

  arrayMapping
xmlns:ns=urn:dbdata
qname=ns:ArrayOf_soapenc_string
type=java:java.lang.String[]
innerType=cmp-ns:string xmlns:cmp-ns=http:// 
schemas.xmlsoap.org/soap/encoding/

encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
  /
  /service
/deployment





here is my wsdl

?xml version=1.0 encoding=UTF-8?
wsdl:definitions targetNamespace=urn:dbdata  
xmlns:apachesoap=http://xml.apache.org/xml-soap;  
xmlns:impl=urn:dbdata xmlns:intf=urn:dbdata xmlns:soapenc=http:// 
sche
mas.xmlsoap.org/soap/encoding/ xmlns:wsdl=http:// 
schemas.xmlsoap.org/wsdl/ xmlns:wsdlsoap=http://schemas.xmlsoap.org/ 
wsdl/soap/ xmlns:xsd=http://www.w3.org/2001/XMLSchema;

!--WSDL created by Apache Axis version: 1.4
Built on Apr 22, 2006 (06:55:48 PDT)--
wsdl:types
  schema targetNamespace=urn:dbdata xmlns=http://www.w3.org/2001/ 
XMLSchema

   import namespace=http://schemas.xmlsoap.org/soap/encoding//
   complexType name=ArrayOf_soapenc_string
complexContent
 restriction base=soapenc:Array
  attribute ref=soapenc:arrayType  
wsdl:arrayType=soapenc:string[]/

 /restriction
/complexContent
   /complexType
  /schema
/wsdl:types

   wsdl:message name=getWaveResponse

  wsdl:part name=getWaveReturn  
type=impl:ArrayOf_soapenc_string/


   /wsdl:message

   wsdl:message name=getMediaRequest

   /wsdl:message

   wsdl:message name=getWaveRequest

   /wsdl:message

   wsdl:message name=getMediaResponse

  wsdl:part name=getMediaReturn  
type=impl:ArrayOf_soapenc_string/


   /wsdl:message

   wsdl:portType name=fileretrive

  wsdl:operation name=getWave

 wsdl:input message=impl:getWaveRequest  
name=getWaveRequest/


 wsdl:output message=impl:getWaveResponse  
name=getWaveResponse/


  /wsdl:operation

  wsdl:operation name=getMedia

 wsdl:input message=impl:getMediaRequest  
name=getMediaRequest/


 wsdl:output message=impl:getMediaResponse  
name=getMediaResponse/


  /wsdl:operation

   /wsdl:portType

   wsdl:binding name=retriveSoapBinding type=impl:fileretrive

  wsdlsoap:binding style=rpc transport=http:// 
schemas.xmlsoap.org/soap/http/


  wsdl:operation name=getWave

 wsdlsoap:operation soapAction=/

 wsdl:input name=getWaveRequest

wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/ 
soap/encoding/ namespace=urn:dbdata use=encoded/


 /wsdl:input

 wsdl:output name=getWaveResponse

wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/ 
soap/encoding/ namespace=urn:dbdata use=encoded/


 /wsdl:output

  /wsdl:operation

  wsdl:operation name=getMedia

 wsdlsoap:operation soapAction=/

 wsdl:input name=getMediaRequest

wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/ 
soap/encoding/ namespace=urn:dbdata use=encoded/


 /wsdl:input

 wsdl:output name=getMediaResponse

wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/ 
soap/encoding/ namespace=urn:dbdata use=encoded/


 /wsdl:output

  /wsdl:operation

   /wsdl:binding

   wsdl:service name=fileretriveService

  wsdl:port binding=impl:retriveSoapBinding name=retrive

Re: [Axis2] Handler unexpected behaviour

From my previous discussions (see the 'Stateful services question'
thread) with the Axis2 guys I though handlers were stateful:

There won't be two instance of same module , so you do not need to do
any thing . At Axis2 start up time it create Module instance and keep
that as long as server is running.

So what happen? If only an instance of the handler (should) exists, why
the instance fields are reset to their default value?

Michele

Ajith Ranabahu wrote:
 Hi
 
 from my previous posts I understood handlers are 'application scope',
 that is they maintain a state across different client invocations.
 
 Actually handlers are supposed to be stateless! They should not
 maintain anything by themselves, rather they should be using the
 appropriate context  to store anything required.
 
 I have a handler intercepting both incoming and outgoing messages and
 unfortunately I realized that instance fields are 'reset' (see logs
 below). Is there any reason for this counter intuitive behavior?

 
 So what I seem to understand is your handler implementation may not
 have been done in the recommended way.Have a look at this article [1]
 by Deepal which explains how the handlers work.
 
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Configure axis client to return logged response instead of connecting to remote service port

2006-06-27 Thread Javier Ramos


Hi everybody,

I was wondering if someone has faced the same need that I have now...

I have some code that makes use of information retrieved via a web 
service client, and then does some processing on this information.
This application logs in files every request and response that the web 
service client exchanges with the remote endpoint.
I need to debug some problems in the logic that processes the received 
information.


To do this, I need to get exactly the same response in my client that 
created the problems.
Now, it is not always possible to contact the provider of this web 
service to have them create the same conditions in their application 
that generated a given response.

Responses depend on current date and time, product inventories... etc.

What I need is to tell my web service client to generate the object 
structure that represents the response using the data in a local file ( 
one of the logged responses, which I know created the issue  ), instead 
of going to the remote endpoint to obtain it.


I am sure someone out there has faced a very similar need...
A feature like this can save a huge amount of debugging time for complex 
applications that make use of web services clients...


I am using axis 1.2.1 as the client runtime.

Does anybody have any experience / ideas about this ?

I would be very glad if you could share them...

Thanks in advance for replies,

Javier Ramos




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Handler unexpected behaviour

Ajith ,

so where do you suggest to temporarily 'store' my stuff (I need to save
some data during the incoming phase to reuse it when the response is
coming back)?, could OperationContext be fine?

p.s. I don't need to keep any data across different invocations.


Thanks,
Michele

Ajith Ranabahu wrote:
 Hi
 
 from my previous posts I understood handlers are 'application scope',
 that is they maintain a state across different client invocations.
 
 Actually handlers are supposed to be stateless! They should not
 maintain anything by themselves, rather they should be using the
 appropriate context  to store anything required.
 
 I have a handler intercepting both incoming and outgoing messages and
 unfortunately I realized that instance fields are 'reset' (see logs
 below). Is there any reason for this counter intuitive behavior?

 
 So what I seem to understand is your handler implementation may not
 have been done in the recommended way.Have a look at this article [1]
 by Deepal which explains how the handlers work.
 
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: AXIS ex: java.io.WinNTFileSystem.createFileExclusively

2006-06-27 Thread ABOU LINA

hi,i didn t resolve the problem yet. this problem occurewhen i try to send a file (size  13 ko) any idea please i tried the old version of axis 1.1 1702 April 14 2004 and the new version : 1.4
 1855 April 22 2006On 6/22/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Please make sure the TEMP / TMP environment variable is set to somedirectory that the process has write access to. See if that helps.-- dimsOn 6/21/06, ABOU LINA 
[EMAIL PROTECTED] wrote: hi, i m using axis 1.4. i can send message wiithout attach. Message with attach, i m trying to send a file (a small file 30Kb) from windows professional 2000 to another pc windows XP.
 i got this message (sorry but a part of the message is french message) : java.lang.RuntimeException: java.io.IOException: Le périphérique n'est pas prêtAxisFaultfaultCode: {
http://schemas.xmlsoap.org/soap/envelope/}Server.userExceptionfaultSubcode:faultString: java.io.IOException: Le périphérique n'est pas prêt
faultActor:faultNode:faultDetail: { http://xml.apache.org/axis/}stackTrace:java.io.IOException:
 Le périphérique n'est pas prêt at java.io.WinNTFileSystem.createFileExclusively(Native Method) at java.io.File.checkAndCreate(File.java:1314)at java.io.File.createTempFile
(File.java:1402) at org.apache.axis.attachments.ManagedMemoryDataSource.flushToDisk(ManagedMemoryDataSource.java:386) at org.apache.axis.attachments.ManagedMemoryDataSource.write
 (ManagedMemoryDataSource.java:276) at org.apache.axis.attachments.ManagedMemoryDataSource.lt;initgt;(ManagedMemoryDataSource.java:149) at org.apache.axis.attachments.MultiPartRelatedInputStream.readTillFound
 (MultiPartRelatedInputStream.java:557) at org.apache.axis.attachments.MultiPartRelatedInputStream.readAll(MultiPartRelatedInputStream.java:433) at org.apache.axis.attachments.MultiPartRelatedInputStream.getAttachments
 (MultiPartRelatedInputStream.java:439) at org.apache.axis.attachments.AttachmentsImpl.mergeinAttachments(AttachmentsImpl.java:171) at org.apache.axis.attachments.AttachmentsImpl.getAttachmentByReference
(AttachmentsImpl.java :341) at org.apache.axis.encoding.DeserializationContext.getObjectByRef(DeserializationContext.java:617) at org.apache.axis.encoding.ser.JAFDataHandlerDeserializer.populateDataHandler
(JAFDataHandlerDeserializer.java :74) at org.apache.axis.encoding.ser.JAFDataHandlerDeserializer.startElement(JAFDataHandlerDeserializer.java:59) at org.apache.axis.encoding.DeserializationContext.startElement
(DeserializationContext.java:1048) at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java
:1141) at org.apache.axis.message.RPCElement.deserialize (RPCElement.java:236) at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) at org.apache.axis.providers.java.RPCProvider.processMessage
(RPCProvider.java:81) at org.apache.axis.providers.java.JavaProvider.invoke (JavaProvider.java:323) 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:454) at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281) at org.apache.axis.transport.http.AxisServlet.doPost (AxisServlet.java:699) at
 javax.servlet.http.HttpServlet.service(HttpServlet.java:716) at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) at javax.servlet.http.HttpServlet.service
 (HttpServlet.java:809) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:200) at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java :146) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:209) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext
(StandardPipeline.java:596)at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
 at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:144) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java
:596) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java :433) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) at
 org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2358) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:133) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext
(StandardPipeline.java:596) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java :118) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext
(StandardPipeline.java:594) at

[Axis2] org.apache.axis2.AxisFault: Module not found - Problem w/ Sample

2006-06-27 Thread Eric Winter

Please help me out...I have a what must be a simple problem. I am not able to run any of the Echo*DualClient samples. For example, when I run the EchoBlockingDualClient sample, Axis2 generates an AxisFault - unable to find the addressing-1.0 module giving me the error message below.Just to be sure I downloaded a fresh copy of the addressing-1.0.mar and it is identical with what I have in  axis2\WEB-INF\modules. Tomcat is aware of it, log shows modules being loaded.What could it be?--"EchoBlockingDualClient "org.apache.axis2.AxisFault: Module not found at org.apache.axis2.description.AxisService.engageModule(AxisService.java:395) at org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:279) at
 userguide.clients.EchoBlockingDualClient.main(EchoBlockingDualClient.java:51)---Directory of C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\axi s2\WEB-INF\modules  2006-06-26 12:46 DIR . 2006-06-26 12:46 DIR .. 2006-05-25 15:23 20,503 addressing-1.0.mar 2006-06-26 12:46 2,512 logging.mar 2006-05-08 17:11 255,835 sandesha2-1.0.mar 2006-05-25 15:23 7,784 soapmonitor-1.0.mar--INFO:
 validateJarFile(C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\axis2\WEB-INF\lib\servletapi-2.3.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class- Deploying module : addressing-1.0- Deploying module : logging- Deploying module : sandesha2-1.0- Deploying module : soapmonitor-1.0Jun 27, 2006 12:13:50 PM org.apache.catal 
	
		Sneak preview the  all-new Yahoo.com. It's not radically different. Just radically better.

ava.io.IOException:The device is not ready

2006-06-27 Thread ABOU LINA

Hi , i try to send a message with attachment.(size  13 Ko) success sent.(size  13 Ko). i got the message error :--
Caused by: java.io.IOException:The device is not ready at java.io.WinNTFileSystem.createFileExclusively(Native Method) at java.io.File.checkAndCreate(File.java:1314) at java.io.File.createTempFile(File.java
:1402) at org.apache.axis.attachments.ManagedMemoryDataSource.flushToDisk(ManagedMemoryDataSource.java:386) at org.apache.axis.attachments.ManagedMemoryDataSource.write(ManagedMemoryDataSource.java:276) at 
org.apache.axis.attachments.ManagedMemoryDataSource.init(ManagedMemoryDataSource.java:149) at org.apache.axis.attachments.MultiPartRelatedInputStream.readTillFound(MultiPartRelatedInputStream.java:557) ... 52 more
 at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:260) at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:169) at org.apache.axis.encoding.DeserializationContextImpl.endElement
(DeserializationContextImpl.java:1015) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch
(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse
(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
 at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.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)--look please this part of my code :

---
DataHandler xlsDhSource = new DataHandler(new FileDataSource(xlsAbsolutePath));
   QName xlsDataHandlerAttachment = new QName(urn:Receiver,XLSDataHandler);
   call.registerTypeMapping(xlsDhSource.getClass(), xlsDataHandlerAttachment,
 JAFDataHandlerSerializerFactory.class, JAFDataHandlerDeserializerFactory.class);

   DataHandler xmlDhSource = new DataHandler(new FileDataSource(xmlAbsolutePath));
   QName xmlDataHandlerAttachment = new QName(urn:Receiver,XMLDataHandler);
   
   call.registerTypeMapping(xmlDhSource.getClass(), xmlDataHandlerAttachment,
 JAFDataHandlerSerializerFactory.class, JAFDataHandlerDeserializerFactory.class);
   call.addParameter(id, XMLType.SOAP_LONG, ParameterMode.IN);
   call.addParameter(type, XMLType.SOAP_STRING, ParameterMode.IN);
   call.addParameter(contenu, XMLType.SOAP_STRING, ParameterMode.IN);
   call.addParameter(xlsTemplateName, XMLType.SOAP_STRING, ParameterMode.IN);
   call.addParameter(xmlTemplateName, XMLType.SOAP_STRING, ParameterMode.IN);
   call.addParameter(xlsSource, xlsDataHandlerAttachment, ParameterMode.IN);
   call.addParameter(xmlSource, xmlDataHandlerAttachment, ParameterMode.IN);

   call.setReturnType(XMLType.SOAP_BOOLEAN);
   Boolean ret = (Boolean) call.invoke(new Object[]{
 message.getId(), message.getType(),
message.getContenu(), xlsTemplateName, xmlTemplateName, xlsDhSource,
xmlDhSource});
thx in adv.

Re: [Axis2] Flash Connectivity Problems

2006-06-27 Thread Luke DeWitt


Hi,

Thanks for that site, it will definately prove to be a great help to me, 
however, I cannot seem to access the webservices from Flash or from my 
analyzer. I can see the WSDL files when I log into the control panel from my 
browser, but that is it. Do you know how I could work aroudn this, or do you 
know any other sites like this?


Thanks,

--LD

- Original Message - 
From: Ajith Ranabahu [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Tuesday, June 27, 2006 12:01 PM
Subject: Re: [Axis2] Flash Connectivity Problems



Hi,
ok here is a small thing to try out.
Goto  http://tools.wso2.net/tryit/tungsten/1.0/. there are 10 tungsten
instances running (Tungsten is based on Axis2 with lot of additions
but still it is a full blown Axis2 server) each tungsten server has
the version service up and running.
point the flash code to one of the tungsten version services and try
it out. If that works we can safely assume that it is not a problem
with Axis2 in general but probably something particular to your Axis2
instance.

Ajith


On 6/27/06, Luke DeWitt [EMAIL PROTECTED] wrote:
Well I can use (pretty much) the EXACT same code to call other 
webservices

online and I get exactely what I am looking for, it's just this single
webservice that I have currently deployed in Axis2 that doesn't work. 
That's

why I was wondering if there was any sort of security setting, though it
doesn't make too much sense that the same webservice would work in my WS
Analyzer program, and not in Flash.

--LD

- Original Message -
From: Ajith Ranabahu [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, June 27, 2006 11:45 AM
Subject: Re: [Axis2] Flash Connectivity Problems


 Hmmm...
 Strange indeed. Could this be a problem with the Flash code ?(I'm zero
 about Web services in Action script)

 Ajith

 On 6/27/06, Luke DeWitt [EMAIL PROTECTED] wrote:
 Hi,

 I have tried the URL in the browser, and it does come up with the XML
 File.
 The Web Service I am currently trying to use is the default one that
 comes
 with Axis2 when I first deployed it, the 'version?WSDL'. I am just 
 trying
 this one because the webservice I will be using is not completed yet. 
 I
 really can't understand why it works for webservices which can be 
 found

 online, but not with ones I have running in Tomcat.

 Thanks,
 --LD

 - Original Message -
 From: Ajith Ranabahu [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Tuesday, June 27, 2006 11:36 AM
 Subject: Re: [Axis2] Flash Connectivity Problems


  Hi,
  From this log we do get the details of some communication between
  Flash and Axis but not what was passed in between. With TCPMon you 
  can

  actually see what's being passed (if there is any)
  But from the looks of it, I feel that the service may not be 
  properly

  deployed. Did you try the URL in the browser ? it should pop up the
  WSDL file.
 
  Ajith
 
  On 6/27/06, Luke DeWitt [EMAIL PROTECTED] wrote:
  Hello again,
 
  I'm sorry, I may have missed something when I sent my last message,
  and I
  am
  hitting an error. I am very new to Axis so I am not sure what 
  exactely

  I
  should be looking for in these logs.
 
  Here is a bit more information:
  In Flash I get the message - Error opening URL
  http://localhost:8080/axis2/services/version?wsdl;
 
  In TDIMon I get:
 
  669.74180154 Flash.exe:3080 85F8B1F8 IRP_MJ_CREATE TCP:0.0.0.0:0
  SUCCESS
  Address Open
  669.74186412 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
  TCP:0.0.0.0:1126
  SUCCESS Error Event
  669.74187753 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
  TCP:0.0.0.0:1126
  SUCCESS Disconnect Event
  669.74188926 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
  TCP:0.0.0.0:1126
  SUCCESS Receive Event
  669.74190100 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
  TCP:0.0.0.0:1126
  SUCCESS Expedited Receive Event
  669.74191189 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
  TCP:0.0.0.0:1126
  SUCCESS Chained Receive Event
  669.74192307 Flash.exe:3080 85F8B1F8 TDI_QUERY_INFORMATION
  TCP:0.0.0.0:1126
  SUCCESS Query Address
  669.74194514 Flash.exe:3080 85F8B1F8 TDI_QUERY_INFORMATION
  TCP:0.0.0.0:1126
  SUCCESS Query Address
  669.74750338 Flash.exe:3080 85FCE4A8 IRP_MJ_CREATE TCP:Connection 
  obj

  SUCCESS Context:0x854D6E50
  669.74752489 Flash.exe:3080 85FCE4A8 TDI_ASSOCIATE_ADDRESS
  TCP:Connection
  obj  SUCCESS TCP:0.0.0.0:1126
  669.74754249 Flash.exe:3080 85FCE4A8 TDI_CONNECT TCP:0.0.0.0:1126
  127.0.0.1:8080 SUCCESS-3555
  669.74759641 tomcat5.exe:3932 854CBF90 TDI_EVENT_CONNECT
  TCP:0.0.0.0:8080
  127.0.0.1:1126 MORE_PROCESSING_REQUIRED
  669.74760815 tomcat5.exe:3932 85309578 TDI_ACCEPT TCP:0.0.0.0:8080
  127.0.0.1:1126 SUCCESS-3556
  669.74770089 tomcat5.exe:3932 861E1E98 IRP_MJ_CREATE TCP:Connection
  obj
  SUCCESS Context:0x85FB95E0
  669.74771738 tomcat5.exe:3932 861E1E98 TDI_ASSOCIATE_ADDRESS
  TCP:Connection
  obj  SUCCESS TCP:0.0.0.0:8080
  669.74784505 tomcat5.exe:3932 85309578 IRP_MJ_DEVICE_CONTROL

Re: [Axis2] Handler unexpected behaviour

2006-06-27 Thread Davanum Srinivas


OperationContext?

-- dims

On 6/27/06, Michele Mazzucco [EMAIL PROTECTED] wrote:

Ajith ,

so where do you suggest to temporarily 'store' my stuff (I need to save
some data during the incoming phase to reuse it when the response is
coming back)?, could OperationContext be fine?

p.s. I don't need to keep any data across different invocations.


Thanks,
Michele

Ajith Ranabahu wrote:
 Hi

 from my previous posts I understood handlers are 'application scope',
 that is they maintain a state across different client invocations.

 Actually handlers are supposed to be stateless! They should not
 maintain anything by themselves, rather they should be using the
 appropriate context  to store anything required.

 I have a handler intercepting both incoming and outgoing messages and
 unfortunately I realized that instance fields are 'reset' (see logs
 below). Is there any reason for this counter intuitive behavior?


 So what I seem to understand is your handler implementation may not
 have been done in the recommended way.Have a look at this article [1]
 by Deepal which explains how the handlers work.




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Davanum Srinivas : http://people.apache.org/~dims/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Flash Connectivity Problems

2006-06-27 Thread Martin Gainty

Luke--

If the WSDL is provided then
java org.apache.axis.wsdl.WSDL2Java NameOfWSDL.wsdl
will generate the necessary Java Stub classes so your client can access the 
Service..
(Assuming FLASH is publishing a REAL SOAP compliant Service)

M--
*
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.



- Original Message - 
From: Luke DeWitt [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, June 27, 2006 12:46 PM
Subject: Re: [Axis2] Flash Connectivity Problems


 Hi,
 
 Thanks for that site, it will definately prove to be a great help to me, 
 however, I cannot seem to access the webservices from Flash or from my 
 analyzer. I can see the WSDL files when I log into the control panel from my 
 browser, but that is it. Do you know how I could work aroudn this, or do you 
 know any other sites like this?
 
 Thanks,
 
 --LD
 
 - Original Message - 
 From: Ajith Ranabahu [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Tuesday, June 27, 2006 12:01 PM
 Subject: Re: [Axis2] Flash Connectivity Problems
 
 
 Hi,
 ok here is a small thing to try out.
 Goto  http://tools.wso2.net/tryit/tungsten/1.0/. there are 10 tungsten
 instances running (Tungsten is based on Axis2 with lot of additions
 but still it is a full blown Axis2 server) each tungsten server has
 the version service up and running.
 point the flash code to one of the tungsten version services and try
 it out. If that works we can safely assume that it is not a problem
 with Axis2 in general but probably something particular to your Axis2
 instance.

 Ajith


 On 6/27/06, Luke DeWitt [EMAIL PROTECTED] wrote:
 Well I can use (pretty much) the EXACT same code to call other 
 webservices
 online and I get exactely what I am looking for, it's just this single
 webservice that I have currently deployed in Axis2 that doesn't work. 
 That's
 why I was wondering if there was any sort of security setting, though it
 doesn't make too much sense that the same webservice would work in my WS
 Analyzer program, and not in Flash.

 --LD

 - Original Message -
 From: Ajith Ranabahu [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Tuesday, June 27, 2006 11:45 AM
 Subject: Re: [Axis2] Flash Connectivity Problems


  Hmmm...
  Strange indeed. Could this be a problem with the Flash code ?(I'm zero
  about Web services in Action script)
 
  Ajith
 
  On 6/27/06, Luke DeWitt [EMAIL PROTECTED] wrote:
  Hi,
 
  I have tried the URL in the browser, and it does come up with the XML
  File.
  The Web Service I am currently trying to use is the default one that
  comes
  with Axis2 when I first deployed it, the 'version?WSDL'. I am just 
  trying
  this one because the webservice I will be using is not completed yet. 
  I
  really can't understand why it works for webservices which can be 
  found
  online, but not with ones I have running in Tomcat.
 
  Thanks,
  --LD
 
  - Original Message -
  From: Ajith Ranabahu [EMAIL PROTECTED]
  To: axis-user@ws.apache.org
  Sent: Tuesday, June 27, 2006 11:36 AM
  Subject: Re: [Axis2] Flash Connectivity Problems
 
 
   Hi,
   From this log we do get the details of some communication between
   Flash and Axis but not what was passed in between. With TCPMon you 
   can
   actually see what's being passed (if there is any)
   But from the looks of it, I feel that the service may not be 
   properly
   deployed. Did you try the URL in the browser ? it should pop up the
   WSDL file.
  
   Ajith
  
   On 6/27/06, Luke DeWitt [EMAIL PROTECTED] wrote:
   Hello again,
  
   I'm sorry, I may have missed something when I sent my last message,
   and I
   am
   hitting an error. I am very new to Axis so I am not sure what 
   exactely
   I
   should be looking for in these logs.
  
   Here is a bit more information:
   In Flash I get the message - Error opening URL
   http://localhost:8080/axis2/services/version?wsdl;
  
   In TDIMon I get:
  
   669.74180154 Flash.exe:3080 85F8B1F8 IRP_MJ_CREATE TCP:0.0.0.0:0
   SUCCESS
   Address Open
   669.74186412 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
   TCP:0.0.0.0:1126
   SUCCESS Error Event
   669.74187753 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
   TCP:0.0.0.0:1126
   SUCCESS Disconnect Event
   669.74188926 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
   TCP:0.0.0.0:1126
   SUCCESS Receive Event
   669.74190100 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
   TCP:0.0.0.0:1126
   SUCCESS Expedited Receive Event
   669.74191189 Flash.exe:3080 85F8B1F8 TDI_SET_EVENT_HANDLER
   TCP:0.0.0.0:1126
   SUCCESS Chained Receive Event
   669.74192307 Flash.exe:3080 85F8B1F8 TDI_QUERY_INFORMATION

Re: [Axis2] rest question

When using a RESTful service, *POST* is your method. You have only one function associated with POST to a specific URL. If you have a service that exposes methods other than GET, POST, PUT, or DELETE, then it isn't RESTful.
AnneOn 6/27/06, [EMAIL PROTECTED] 
[EMAIL PROTECTED] wrote:HiAs per the axis2 doc it seems that if I want to do a POST rest service -
the only way axis runtime would detect which method to delegate the call tois from the name of the top level element in the http message body XML -right?I have a service whose method definition is like
public OMElement dothis(OMElelemt payload)When I do the SOAP clientinvoke I send the soap action as urn:dothis andmy payload top element does not match the method name - This works finewith axis2.
But now if I have to do REST call and not have the root element as methodname - how can I acheive that using rest? [I presume soap action is notgoing to work here or is it?]thanksAnamitra
-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: No such operation

After you run java2wsdl, you then have to run wsdl2java. It should have produced an appropriate WSDD for you.The WSDL is the artifact that clients use to consume the service. It is designed to hide implementation information, therefore it isn't much use to Axis in terms of telling it how to dispatch a request. The WSDD is the artifact that contains the information that maps the abstract WSDL information to the concrete implementation. Axis uses the WSDD to dispatch requests.
SOAPAction isn't particularly useful, and it actually goes away in SOAP 1.2.AnneOn 6/27/06, Doug B
[EMAIL PROTECTED] wrote:Interesting. So does the java2wsdl -A option do anything at all? Sorry if I'm just being thick here, but something just doesn't seem right when the only artifact required for defining an interface, the WSDL, is ignored. If the interface says the operation is named Operation, why is Axis expecting it to be named Request?
Again, I'm not disputing what you're saying, I just don't understand something about why it is so. Is Axis not actually able to define the service from the WSDL but only from the Java code generated from the WSDL? Even if Axis uses only the WSDD at deployment time, why is not not reflecting what was in the WSDL? I must be missing something obvious here, so feel free to give up on me whenever you want :-)
DougOn 6/27/06, Anne Thomas Manes
[EMAIL PROTECTED] wrote:
SOAPAction is just a hint. You may notice that the WSDD doesn't reference the SOAPAction parameter. Axis uses the WSDD (not the WSDL) to figure out how to dispatch the request. If the information isn't in there, Axis can't figure it out.
AnneOn 6/26/06, Doug B

[EMAIL PROTECTED] wrote:
Hmmm... so it turns out the options he can specify in his JBoss environment correspond to those on the java2wsdl tool. -T, -A, -y, -u. To me, that should mean they're relevant only to the server side. Yet specifying SOAPAction: OPERATION (-A), doesn't seem to resolve the problem. Furthermore, such options aren't even available on wsdl2java, which is all it seems he should need to be using in this case. (That's another issue, why he can't get an actual service deployed just from wsdl2java artifacts and why he's having to go down this java2wsdl path at all (using the code originally generated from wsdl2java)).
Don't get me wrong, I believe that the wsdd option is the solution (or altering the WSDL to use the operation name as the request element name), I just want to understand why some of Axis seems to understand that the SOAPAction field might need to contain the operation name, but some of it doesn't.
Thanks again for your patient instruction.DougOn 6/26/06,
Doug B [EMAIL PROTECTED] wrote:
I'm also discovering that my Axis customer is having to do some intermediate step where he generates code from our WSDL but can't find any deployable artifacts until he takes some other steps, at which point he has to re-specify several options, including... style, encoding, SOAP Action. So far, none of those were set correctly and his ?wsdl didn't even match the contract WSDL in those crucial parameters. Will be testing soon with hopefully the correct values specified there.
(I have no details at all on my .NET customer's environment, so it's also possible he had to do some tweaking himself.)DougOn 6/26/06,

Anne Thomas Manes
[EMAIL PROTECTED] wrote:

Help -- problem marshalling back into XML using RPCMessageReceiver

2006-06-27 Thread Paul Truax









Can someone shed any light on this error that Im
getting Ive successfully traced this error back to the
formulating of the response. The request comes into, it gets properly marshaled.
My Service method gets called. The code executes properly. But as
the request is making it back out  as its getting marshaled back into
XML, I get the following error: I thought it might have to do with the
fact that a couple of my objects inherit from other objects. Would this
cause this problem? Please help if you can. Im really stuck!

Paul



- soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/

 soapenv:Header
/ 

- soapenv:Body

- soapenv:Fault

 faultcodesoapenv:Client/faultcode


 faultstringjava.lang.NullPointerException/faultstring


- detail

 Exceptionorg.apache.axis2.AxisFault:
java.lang.NullPointerException; nested exception is: org.apache.axiom.om.OMException:
java.lang.NullPointerException at
org.apache.axis2.AxisFault.makeFault(AxisFault.java:318) at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:136)
at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454) at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.choicepoint.ta.aa.servlet.DbFilter.doFilter(DbFilter.java:63) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:365)
Caused by: org.apache.axiom.om.OMException: java.lang.NullPointerException at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:206) at
org.apache.axiom.om.impl.llom.OMNodeImpl.build(OMNodeImpl.java:298) at
org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:584) at
org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:118) at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:240) at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:197) at
org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:71) at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:130)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454) at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.choicepoint.ta.aa.servlet.DbFilter.doFilter(DbFilter.java:63) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at

Re: how to change the address of the webservices in run time?

The servicePortName is the port name in your wsdl; for example in this WSDL:

?xml version=1.0 encoding=UTF-8?
definitions xmlns=http://schemas.xmlsoap.org/wsdl/; 
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tns=http://xx/; 
xmlns:xsd=http://www.w3.org/2001/XMLSchema; targetNamespace=http://x/; 
name=SiporService
  types/
  message name=SiporWs_executeResponse
part name=result type=xsd:string/
  /message
  message name=SiporWs_execute
part name=String_1 type=xsd:string/
  /message
  portType name=SiporWs
operation name=execute parameterOrder=String_1
  input message=tns:SiporWs_execute/
  output message=tns:SiporWs_executeResponse/
/operation
  /portType
  binding name=SiporWsBinding type=tns:SiporWs
soap:binding style=rpc transport=http://schemas.xmlsoap.org/soap/http/
operation name=execute
  soap:operation/
  input
soap:body use=literal namespace=http://xx//
  /input
  output
soap:body use=literal namespace=http://xxx//
  /output
/operation
  /binding
  service name=SiporService
port name=SiporWsPort binding=tns:SiporWsBinding
  soap:address location=http://xxx:/sipor/Sipor/
/port
  /service
/definitions


the portName is SiporWsPort; so you should write:
xLocator loc = new xLocator();
loc.setEndpointAddress(SiporWsPort,http://yy:yyy/sipor/Sipor;);

Hope this can help you.
Bye.
Angelo

-- Initial Header ---

From  : Victor Sosa [EMAIL PROTECTED]
To  : axis-user@ws.apache.org
Cc  :
Date  : Tue, 27 Jun 2006 11:31:08 -0400
Subject : Re: how to change the address of the webservices in run time?







 Pls, give me a example of servicePortName.

 Thks for the answer

 On 6/27/06, Angelo Immediata [EMAIL PROTECTED] wrote:
  Hi.
  You can set the endpoint address in this way (by acting on the 
  xxxLocator.java class):
 
  xLocator loc = new xLocator();
  loc.setEndpointAddress(servicePortName,the new URL (as a String))
 
  Hipe this can help you.
  Bye,
   Angelo
 
  -- Initial Header ---
 
  From  : Victor Sosa [EMAIL PROTECTED]
  To  : axis-user@ws.apache.org
  Cc  :
  Date  : Tue, 27 Jun 2006 11:04:46 -0400
  Subject : how to change the address of the webservices in run time?
 
 
 
 
 
 
 
   The Service class will by default make a Stub which points to the
   endpoint URL described in the WSDL file, but I may also specify a
   different URL? and make request to the new adresss?
  
   How to?
  
   NOTE: I have two server, one for production and other for develop.
  
  
   --
   Victor Sosa
   Desarrollador Java
   TeKnowLogic Dominicana, C. x A.
   http://www.tkl.com.do
   http://vnsjava.blogspot.com/
   [EMAIL PROTECTED]
   Registered Linux User #369216
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 Victor Sosa
 Desarrollador Java
 TeKnowLogic Dominicana, C. x A.
 http://www.tkl.com.do
 http://vnsjava.blogspot.com/
 [EMAIL PROTECTED]
 Registered Linux User #369216

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] rest question

2006-06-27 Thread Anamitra . Bhattacharyya

Hi Anne
 I am sorry - I probably didnt get the answer.
I have a service class that has 2 methods -

public OMElement dothis(OMElement om1)
public OMElement dothat(OMElement om2)

Now for this service there will be one REST endpoint address - right?
then my question is given my payload xml - how does axis decide which
method to invoke in my service?

I didnt quite get what u meant by

You have only one function associated with POST to a specific URL
Are u saying that my service can have only one method for it to be rest
enabled?
thanks
Anamitra




   
 Anne Thomas  
 Manes
 [EMAIL PROTECTED]  To 
 maxis-user@ws.apache.org 
cc 
 06/27/2006 01:17  
 PMSubject 
   Re: [Axis2] rest question   
   
 Please respond to 
 [EMAIL PROTECTED] 
  he.org   
   
   




When using a RESTful service, *POST* is your method. You have only one
function associated with POST to a specific URL. If you have a service that
exposes methods other than GET, POST, PUT, or DELETE, then it isn't
RESTful.

Anne

On 6/27/06, [EMAIL PROTECTED]  [EMAIL PROTECTED]
 wrote:

  Hi
  As per the axis2 doc it seems that if I want to do a POST rest service -
  the only way axis runtime would detect which method to delegate the call
  to
  is from the name of the top level element in the http message body XML -
  right?
  I have a service whose method definition is like

  public OMElement dothis(OMElelemt payload)

  When I do the SOAP client  invoke I send the soap action as urn:dothis
  and
  my payload top element does not match the method name - This works fine
  with axis2.

  But now if I have to do REST call and not have the root element as method
  name - how can I acheive that using rest? [I presume soap action is not
  going to work here or is it?]

  thanks
  Anamitra


  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] rest question

2006-06-27 Thread Martin Gainty

You have only one function 
public OMElement dothis(OMElement om1)
public OMElement dothat(OMElement om2)
are both considered the same signature therefore they are one function..

associated with POST 
(IN order to be RESTful you invoke using method=POST)

to a specific URL
certainly true assuming one endpoint address


The statement is correct..

Do you perhaps have more specific questions?
Martin --
*
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.



- Original Message - 
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, June 27, 2006 1:43 PM
Subject: Re: [Axis2] rest question


 Hi Anne
 I am sorry - I probably didnt get the answer.
 I have a service class that has 2 methods -
 
 public OMElement dothis(OMElement om1)
 public OMElement dothat(OMElement om2)
 
 Now for this service there will be one REST endpoint address - right?
 then my question is given my payload xml - how does axis decide which
 method to invoke in my service?
 
 I didnt quite get what u meant by
 
 You have only one function associated with POST to a specific URL
 Are u saying that my service can have only one method for it to be rest
 enabled?
 thanks
 Anamitra
 
 
 
 
   
 Anne Thomas  
 Manes
 [EMAIL PROTECTED]  To 
 maxis-user@ws.apache.org 
cc 
 06/27/2006 01:17  
 PMSubject 
   Re: [Axis2] rest question   
   
 Please respond to 
 [EMAIL PROTECTED] 
  he.org   
   
   
 
 
 
 
 When using a RESTful service, *POST* is your method. You have only one
 function associated with POST to a specific URL. If you have a service that
 exposes methods other than GET, POST, PUT, or DELETE, then it isn't
 RESTful.
 
 Anne
 
 On 6/27/06, [EMAIL PROTECTED]  [EMAIL PROTECTED]
 wrote:
 
  Hi
  As per the axis2 doc it seems that if I want to do a POST rest service -
  the only way axis runtime would detect which method to delegate the call
  to
  is from the name of the top level element in the http message body XML -
  right?
  I have a service whose method definition is like
 
  public OMElement dothis(OMElelemt payload)
 
  When I do the SOAP client  invoke I send the soap action as urn:dothis
  and
  my payload top element does not match the method name - This works fine
  with axis2.
 
  But now if I have to do REST call and not have the root element as method
  name - how can I acheive that using rest? [I presume soap action is not
  going to work here or is it?]
 
  thanks
  Anamitra
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

RE: ava.io.IOException:The device is not ready

2006-06-27 Thread Qinjian Jian









Put following in the globalConfiguration section
of your server-config.wsdd file and make sure C:\\Temp\\attachments
exist in your file system.



globalConfiguration

 parameter
name=attachments.Directory
value=C:\\Temp\\attachments/

/globalConfiguration





When having attachment, if the size of
attachment is less than 13K, axis will keep it in the memory. If it is larger
than that, it look for the attachments.Directory
as a temporary storage.



Hope this helps.



Thanks



Tim Jian

Momentum systems, Inc.











From: ABOU LINA
[mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 27, 2006 12:24
PM
To: axis-user@ws.apache.org
Subject: ava.io.IOException:The
device is not ready





Hi , 
i try to send a message with attachment.

(size  13 Ko) success sent.

(size  13 Ko). i got the message error :
-- 
Caused by: java.io.IOException:The device is not ready at
java.io.WinNTFileSystem.createFileExclusively(Native Method)
 at java.io.File.checkAndCreate(File.java:1314)
 at java.io.File.createTempFile(File.java :1402)
 at
org.apache.axis.attachments.ManagedMemoryDataSource.flushToDisk(ManagedMemoryDataSource.java:386)
 at
org.apache.axis.attachments.ManagedMemoryDataSource.write(ManagedMemoryDataSource.java:276)
 at
org.apache.axis.attachments.ManagedMemoryDataSource.init(ManagedMemoryDataSource.java:149)
 at org.apache.axis.attachments.MultiPartRelatedInputStream.readTillFound(MultiPartRelatedInputStream.java:557)
 ... 52 more 

 at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:260)
 at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:169)
 at
org.apache.axis.encoding.DeserializationContextImpl.endElement
(DeserializationContextImpl.java:1015)
 at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
 at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
 at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch
(Unknown Source)
 at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
 at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
 at org.apache.xerces.parsers.DTDConfiguration.parse (Unknown
Source)
 at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
 at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
 at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) 
 at
org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.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)
--



look please this part of my code : 
---
DataHandler xlsDhSource = new DataHandler(new FileDataSource(xlsAbsolutePath));
   QName
xlsDataHandlerAttachment = new
QName(urn:Receiver,XLSDataHandler);
  
call.registerTypeMapping(xlsDhSource.getClass(), xlsDataHandlerAttachment,
   
 JAFDataHandlerSerializerFactory.class,
JAFDataHandlerDeserializerFactory.class);

   DataHandler
xmlDhSource = new DataHandler(new FileDataSource(xmlAbsolutePath));
   QName
xmlDataHandlerAttachment = new QName(urn:Receiver,XMLDataHandler);
   
  
call.registerTypeMapping(xmlDhSource.getClass(),
xmlDataHandlerAttachment,
   
 JAFDataHandlerSerializerFactory.class,
JAFDataHandlerDeserializerFactory.class);
   call.addParameter(id,
XMLType.SOAP_LONG, ParameterMode.IN);
  
call.addParameter(type, XMLType.SOAP_STRING,
ParameterMode.IN);
  
call.addParameter(contenu, XMLType.SOAP_STRING,
ParameterMode.IN);
  
call.addParameter(xlsTemplateName, XMLType.SOAP_STRING,
ParameterMode.IN);
  
call.addParameter(xmlTemplateName, XMLType.SOAP_STRING,
ParameterMode.IN);
  
call.addParameter(xlsSource, xlsDataHandlerAttachment,
ParameterMode.IN);
  
call.addParameter(xmlSource, xmlDataHandlerAttachment,
ParameterMode.IN);

  
call.setReturnType(XMLType.SOAP_BOOLEAN);
   Boolean ret =
(Boolean) call.invoke(new Object[]{
   
 message.getId(), message.getType(),
message.getContenu(), xlsTemplateName, xmlTemplateName, xlsDhSource,
xmlDhSource});


thx in adv.





NOTICE: This message (including any attachments) from Momentum Systems, Inc. contains information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient, you are hereby notified that any dissemination of this message is strictly prohibited.  If you have received this message in error, please do not read, copy or forward this message.  Please permanently delete all copies and any

RE: The duplicate type is happening here for the WSDL file

2006-06-27 Thread Andersen_John

Hi Deepal,

I've butted my head against the same issue during the past few weeks (most
recently with the June 19 Axis2 snap) and have had to resort to fixing the
wsdl with a perl script.  Rather easy to reproduce with 2 source files:

test.MyService.java

package test;
import test.MyData;
public class MyService
{
private MyData myData = new MyData();
  
public MyData retrieveMyData()
{
return myData;
}
}

Test.MyData.java
###
package test;
public class MyData
{
private String myString = null;
public String getMyString() { return this.myString; }
public void setMyString(String arg) { this.myString = arg; }
}


I ran: 
..\bin\java2wsdl.bat -cp . -sn TEST -l
http://localhost:8080/axis2/services/Logger -st wrapped -cn test.MyService
(and I did try different styles - same result)

Which resulted in the following wsdl with the element MyData defined
twice:
###
wsdl:definitions xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:axis2=http://test;
xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:ns1=http://test/xsd;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
targetNamespace=http://test;
  wsdl:types
xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:ns=http://test/xsd; targetNamespace=http://test/xsd;
elementFormDefault=unqualified attributeFormDefault=unqualified
  xs:element type=ns:MyData name=MyData /
  xs:complexType name=MyData
xs:sequence
  xs:element type=xs:string name=myString /
/xs:sequence
  /xs:complexType
  xs:element name=retrieveMyData
xs:complexType /
  /xs:element
  xs:element name=retrieveMyDataResponse
xs:complexType
  xs:sequence
xs:element type=ns:MyData name=return /
  /xs:sequence
/xs:complexType
  /xs:element
  xs:complexType name=MyData
xs:sequence
  xs:element type=xs:string name=myString /
/xs:sequence
  /xs:complexType
/xs:schema
  /wsdl:types
  wsdl:message name=retrieveMyDataMessage
wsdl:part element=ns1:retrieveMyData name=part1 /
  /wsdl:message
  wsdl:message name=retrieveMyDataResponseMessage
wsdl:part element=ns1:retrieveMyDataResponse name=part1 /
  /wsdl:message
  wsdl:portType name=TESTPortType
wsdl:operation name=retrieveMyData
  wsdl:input message=axis2:retrieveMyDataMessage /
  wsdl:output message=axis2:retrieveMyDataResponseMessage /
/wsdl:operation
  /wsdl:portType
  wsdl:binding type=axis2:TESTPortType name=TESTSOAP11Binding
soap:binding style=wrapped
transport=http://schemas.xmlsoap.org/soap/http; /
wsdl:operation name=retrieveMyData
  soap:operation style=wrapped soapAction=urn:retrieveMyData /
  wsdl:input
soap:body namespace=http://test; use=literal /
  /wsdl:input
  wsdl:output
soap:body namespace=http://test; use=literal /
  /wsdl:output
/wsdl:operation
  /wsdl:binding
  wsdl:binding type=axis2:TESTPortType name=TESTSOAP12Binding
soap12:binding style=wrapped
transport=http://schemas.xmlsoap.org/soap/http; /
wsdl:operation name=retrieveMyData
  soap12:operation style=wrapped soapAction=urn:retrieveMyData /
  wsdl:input
soap12:body namespace=http://test; use=literal /
  /wsdl:input
  wsdl:output
soap12:body namespace=http://test; use=literal /
  /wsdl:output
/wsdl:operation
  /wsdl:binding
  wsdl:service name=TEST
wsdl:port binding=axis2:TESTSOAP11Binding name=TESTSOAP11port
  soap:address
location=http://localhost:8080/axis2/services/LoggerTEST; /
/wsdl:port
wsdl:port binding=axis2:TESTSOAP12Binding name=TESTSOAP12port
  soap12:address
location=http://localhost:8080/axis2/services/LoggerTEST; /
/wsdl:port
  /wsdl:service
/wsdl:definitions






-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 27, 2006 12:41 AM
To: axis-user@ws.apache.org
Subject: Re: The duplicate type is happening here for the WSDL file

Hi Jim;
can you please provide a way to recreate the issue , I mean any
possibility of sending java class that you use :)

Jim Bender wrote:

 I don't know the precise step, but by the time that we leave the
 generateOM() method in the Java2OMBuilder, there are two complex type
 definitions in the WSDL.

public OMElement generateOM() throws Exception {
OMFactory fac = OMAbstractFactory.getOMFactory();
wsdl = fac.createOMNamespace(WSDL_NAMESPACE,
DEFAULT_WSDL_NAMESPACE_PREFIX);
OMElement ele = fac.createOMElement(definitions, wsdl);

ele.addAttribute(targetNamespace, targetNamespace, null);

[Axis2] Determing Service Endpoint from a Module

2006-06-27 Thread Andersen_John

Hello, 
 
I need to register a suite of Axis2 web services each time they are deployed

(i.e., each time the Axis2 web app starts up) with an external registration 
service.  It appears that the Module interface engageNotify() provides the 
ability to take this action at the appropriate time, but I haven't found the

hook yet that will allow me to determine the URL of the current service at 
runtime.  I've looked a bit at the definition argument of the engageNotify()

function, but that appears to provide the stale service endpoint data from
the 
services.xml. 
 
Assistance greatly appreciated. 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: No such operation

But I'm trying to go the other direction. I don't want to have to run java2wsdl at all. I want to handwrite the WSDL and use that as the contract for both the client and the server. I want the wsdl2java --server-side to generate a deployable service which matches and honors the original WSDL, including recognizing the specified operation names.
I went ahead and generated server-side artifacts myself just to compare what I think my customer might be seeing. It seems interesting to me that, in fact, the deploy.wsdd that is generated from the --server-side option does contain the operation mappings - they're just looking for what I'd consider the wrong qname:
operation name=successfulRenewalOperation qname=SuccessfulRenewalOperation returnQName=retNS:SuccessfulRenewalResponse xmlns:retNS=
http://az.gov/doi returnType=rtns:SuccessfulRenewalResponseType xmlns:rtns=http://az.gov/doi
soapAction=http://az.gov/doi-ws/SuccessfulRenewalOperation parameter qname=pns:SuccessfulRenewalRequest
xmlns:pns=http://az.gov/doi type=tns:SuccessfulRenewalRequestType xmlns:tns=
http://az.gov/doi//operation(This is either with or without the --noWrapped option.)It gets the correct returnQName from the WSDL-defined response element, including for another operation where that response name is not at all related to the operation or request names, so why wouldn't it use the WSDL-defined request element for the qname by default?
Regarding SOAPAction, so what is supposed to be *the standard* way the service endpoint knows what operation is being requested? Is the engine supposed to have to make a best guess at mapping operation signatures based on parameters (with manual override mapping allowed)? I guess I was expecting something less ambiguous to be part of the specs or at least ws-i.
DougOn 6/27/06, Anne Thomas Manes [EMAIL PROTECTED] wrote:
After you run java2wsdl, you then have to run wsdl2java. It should have produced an appropriate WSDD for you.The WSDL is the artifact that clients use to consume the service. It is designed to hide implementation information, therefore it isn't much use to Axis in terms of telling it how to dispatch a request. The WSDD is the artifact that contains the information that maps the abstract WSDL information to the concrete implementation. Axis uses the WSDD to dispatch requests.
SOAPAction isn't particularly useful, and it actually goes away in SOAP 1.2.Anne
On 6/27/06, Doug B
[EMAIL PROTECTED] wrote:Interesting. So does the java2wsdl -A option do anything at all? Sorry if I'm just being thick here, but something just doesn't seem right when the only artifact required for defining an interface, the WSDL, is ignored. If the interface says the operation is named Operation, why is Axis expecting it to be named Request?
Again, I'm not disputing what you're saying, I just don't understand something about why it is so. Is Axis not actually able to define the service from the WSDL but only from the Java code generated from the WSDL? Even if Axis uses only the WSDD at deployment time, why is not not reflecting what was in the WSDL? I must be missing something obvious here, so feel free to give up on me whenever you want :-)
DougOn 6/27/06, Anne Thomas Manes

[EMAIL PROTECTED] wrote:
SOAPAction is just a hint. You may notice that the WSDD doesn't reference the SOAPAction parameter. Axis uses the WSDD (not the WSDL) to figure out how to dispatch the request. If the information isn't in there, Axis can't figure it out.
AnneOn 6/26/06, Doug B

Re: [Axis2] Determing Service Endpoint from a Module

2006-06-27 Thread robert lazarski


Not sure I understand the question - but if I do it's just:

invoke(MessageContext messageContext) {
 EndpointReference ref = null;

 if (messageContext.getFLOW() == MessageContext.IN_FLOW) {
   ref = messageContext.getTo();
   } else if (messageContext.getFLOW() == MessageContext.OUT_FLOW) {
   ref = messageContext.getFrom();
   }
}

HTH,
Robert
http://www.braziloutsource.com/

On 6/27/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

Hello,

I need to register a suite of Axis2 web services each time they are deployed

(i.e., each time the Axis2 web app starts up) with an external registration
service.  It appears that the Module interface engageNotify() provides the
ability to take this action at the appropriate time, but I haven't found the

hook yet that will allow me to determine the URL of the current service at
runtime.  I've looked a bit at the definition argument of the engageNotify()

function, but that appears to provide the stale service endpoint data from
the
services.xml.

Assistance greatly appreciated.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Help -- problem marshalling back into XML using RPCMessageReceiver

2006-06-27 Thread robert lazarski


I haven't used RPCMessageReceiver much, but my understanding its for
simple types like Integer and String. I'm not sure how well
inheritance is supported by RPCMessageReceiver.

I have two suggestions:

1) Upgrade to the latest nightlies - the latest source isn't matching
the stackTrace you show:

http://people.apache.org/dist/axis2/nightly/

2) Put tcpmon or the soap monitor in between your calls and post the
SOAP message you are sending. That'll help us see what you are doing.

HTH,
Robert
http://www.braziloutsource.com/

On 6/27/06, Paul Truax [EMAIL PROTECTED] wrote:





Can someone shed any light on this error that I'm getting…  I've
successfully traced this error back to the formulating of the response.  The
request comes into, it gets properly marshaled.  My Service method gets
called.  The code executes properly.  But as the request is making it back
out – as its getting marshaled back into XML, I get the following error:  I
thought it might have to do with the fact that a couple of my objects
inherit from other objects.  Would this cause this problem?  Please help if
you can.  I'm really stuck!

Paul



- soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;

  soapenv:Header /

- soapenv:Body

- soapenv:Fault

  faultcodesoapenv:Client/faultcode

  faultstringjava.lang.NullPointerException/faultstring

- detail

  Exceptionorg.apache.axis2.AxisFault: java.lang.NullPointerException;
nested exception is: org.apache.axiom.om.OMException:
java.lang.NullPointerException at
org.apache.axis2.AxisFault.makeFault(AxisFault.java:318) at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:136)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
com.choicepoint.ta.aa.servlet.DbFilter.doFilter(DbFilter.java:63)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:365)
Caused by: org.apache.axiom.om.OMException: java.lang.NullPointerException
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:206)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.build(OMNodeImpl.java:298)
at
org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:584)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:118)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:240)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:197)
at
org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:71)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:130)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at

RE: [Axis2] Determing Service Endpoint from a Module

2006-06-27 Thread Andersen_John

Thanks, Robert.

I believe you are referring below to the Handler.invoke(MessageContext)
method, which I *presumed* would only run when the service itself is
called.  If that's not true, please let me know.

If that is true, then I have a bootstrap issue because no client will be
able to find the web service until I derive the service endpoint and
register it with an external registration provider.  Which is why I am
trying to figure out how to get the URL when the
org.apache.axis2.modules.Module.engagNotify(AxisDescription) runs for
each service during Axis2 startup.

I'm probably missing something as usual ;-)


-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 27, 2006 3:32 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Determing Service Endpoint from a Module

Not sure I understand the question - but if I do it's just:

invoke(MessageContext messageContext) {
  EndpointReference ref = null;

  if (messageContext.getFLOW() == MessageContext.IN_FLOW) {
ref = messageContext.getTo();
} else if (messageContext.getFLOW() == MessageContext.OUT_FLOW) {
ref = messageContext.getFrom();
}
}

HTH,
Robert
http://www.braziloutsource.com/

On 6/27/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 Hello,

 I need to register a suite of Axis2 web services each time they are
deployed

 (i.e., each time the Axis2 web app starts up) with an external
registration
 service.  It appears that the Module interface engageNotify() provides
the
 ability to take this action at the appropriate time, but I haven't
found the

 hook yet that will allow me to determine the URL of the current
service at
 runtime.  I've looked a bit at the definition argument of the
engageNotify()

 function, but that appears to provide the stale service endpoint data
from
 the
 services.xml.

 Assistance greatly appreciated.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Axis 2 deployment as part of existing web application

2006-06-27 Thread Brian Russell









Jason,



Thanks for your solution. Sounded like
fun! I did my own form of experimentation and got it going. Basically I just
did this:



1)
copy the web.xml that was
in the book example

2)
copy the WEB-INF/conf/axis2.xml
file from the axis2.war file

3)
put my services.xml and wsdl
file in WEB-INF/services/MyService/META-INF

4)
added a WEB-INF/module
directory and added the appropriate changes to axis2.xml (I use the logging
module so I can see the Soap calls)

5)
added all of the jars
from the axis2-min-1.0-bin.zip distribution



That seemed to do it. Really I just needed
to make sure I had all the right jars. I still think theres some I can
remove. Plus I used xmlbeans to create my service using WSDL2JAVA and have even
more jars to add, which may cause me to switch that later to something less
dependent. But alls well now!



Whats documentation? ;)





Brian Russell

www.closerware.com






-Original Message-
From: Jason N
[mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 27, 2006 4:25
PM
To: axis-user@ws.apache.org
Subject: Re: Axis 2 deployment as
part of existing web application



Brian, 

I ran into the same problems as I tried to do both an embedded axis2 deploy and
get Axis2-Spring up and running. 
Undoubtedly this is the wrong way to do it, and I'm sure there's a better
way. However I couldn't find it. Chime in if you know a better way!

Here's what I did:

Starting with the axis2 war file I combined the lines from the axis2.war
web.xml file with my project's web.xml file where they were relevant.
I copied the conf directory from axis2.war over to web-inf\ of my project
copied the modules directory from axis2.war over to web-inf\ of my project
I created a services directory set up similar to the one that ws02 example
gives however I just put services.xml, and the wsdl file in
/web-inf/services/findService/META-INF
I use a limited version of Maven and I did it this way so I could have a web
service module that could be popped into the lib directory of the web app if I
ever decided to move the web service code base out of the project. So
basically all of the generated class files are in the web-inf/lib directory.
I copied most of the axis2 lib files into the web-inf/lib directory.

I can't really list them all right here, but off the top of my head: Please
keep in mind this is coming straight from my lib directory so there may be
things in here that you won't need. (xmlbeans, etc...)
Annogen, axiom all, asm, axis2-*, backport, commons-config, commonds-dbcp,
commons-digester, commons-httpclient, commons-logging, commons-pool, jaxen,
jibx, neethi, stax-api, wstx-asl, xbean, xmlschema

Anyway once all of that is in place and everything deploys ok, you should be
able to acccess the web service by ip/webservicename/services/servicename

Again this is just how I was able to get it up and running. I don't think
it's a great solution, but I had to move on to writing documentation wooho!

Good luck!

j





On 6/26/06, Brian
Russell [EMAIL PROTECTED]
wrote:

I tried using the example
referenced below [1]
(http://www.wso2.net/kb/90)but
was unable to get the mvn install to
work. I'm not familiar with maven and therefore troubleshooting will be 
pretty tough.

I followed the instructions of downloading the book.zip and then running
the mvn install war:war command, but it fails while trying to execute
the command. I'm simply trying to use it to figure out how to include 
axis2 as part of a current webapp so that I can run a web service from
it. This is much more attractive (and necessary) than to have an axis2
app running to do hot deploys, etc. Really I just want to know what jars 
I need from axis2 and how it needs to be configured. That is why I was
hoping to get this book example working.

Here is my stack trace when running $ mvn install war:war :

C:\projects\jakarta\axis\axis2-1_0\samples\bookmvn -e install war:war 
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'war'.
[INFO]
 

[INFO] Building Book Example
[INFO]task-segment: [install, war:war]
[INFO]


Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-model/2.0/maven-mod
el-2.0.pom
2K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven/2.0/maven-2.0.pom

8K downloaded
Downloading:
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.0.4/ple
xus-utils-1.0.4.pom 
6K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-project/2.0/maven-p
roject-2.0.pom
1K downloaded 
Downloading:
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-container-defau
lt/1.0-alpha-8/plexus-container-default-1.0-alpha-8.pom 

7K downloaded
Downloading:
http://repo1.maven.org/maven2/classworlds/classworlds/1.1-alpha-2/classw
orlds-1.1-alpha-2.pom 
3K

Axis fault....where to begin

2006-06-27 Thread Taylor, Clarence B

I am getting the following axis fault while attempting to deploy via the
admin client and I am not sure where to begin to figure out what is
wrong.  I am not sure how much detail would be helpful, so I'll post the
following
1. the output from the deploy (the axis fault)
2. The wsdd.deploy file
3. not sure what else?

1.) the output from the deploy

Exception: AxisFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 
 faultString: java.lang.reflect.InvocationTargetException
 faultActor: 
 faultNode: 
 faultDetail: 

2.) the wsdd.deploy file
Here is the deploy.wsdd file

!-- Use this file to deploy some handlers/chains and services  --
!-- Two ways to do this:   --
!--   java org.apache.axis.client.AdminClient deploy.wsdd  --
!--  after the axis server is running  --
!-- or --
!--   java org.apache.axis.utils.Admin client|server deploy.wsdd   --
!--  from the same directory that the Axis engine runs --

deployment
xmlns=http://xml.apache.org/axis/wsdd/;
xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;

  !-- Services from ExecutingJobsService WSDL service --

  service name=ExecutingJobs provider=java:RPC style=rpc
use=encoded
  parameter name=wsdlTargetNamespace value=urn:ExecutingJobs/
  parameter name=wsdlServiceElement
value=ExecutingJobsService/
  parameter name=schemaUnqualified value=urn:ExecutingJobs/
  parameter name=wsdlServicePort value=ExecutingJobs/
  parameter name=className
value=com.ca.zos.jobs.server.ExecutingJobsSoapBindingSkeleton/
  parameter name=wsdlPortType value=ExecutingJobs/
  parameter name=typeMappingVersion value=1.2/
  parameter name=allowedMethods value=*/
  parameter name=scope value=Session/
  typeMapping
xmlns:ns=urn:ExecutingJobs
qname=ns:JobNames
type=java:com.ca.zos.job.JobNames
serializer=org.apache.axis.encoding.ser.BeanSerializerFactory
 
deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
  /

  arrayMapping
xmlns:ns=urn:ExecutingJobs
qname=ns:ArrayOfJobNames
type=java:com.ca.zos.job.JobNames[]
innerType=cmp-ns:JobNames xmlns:cmp-ns=urn:ExecutingJobs
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
  /
  /service
/deployment 

Thank you

Brad Taylor

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] Classloader problem [does not work getResourceAsStream solution?]

2006-06-27 Thread Javier V


Hi.

I know my question has been posted several times, but the solution
does not work. I must do something wrong, sure.

I'm using JDK 1.4.2_12, Axi2 1.0 and Tomcat 4.1.31.

The aar-achive contains:

aar
|-com
   |-test
   |-myService.class
|-config
   |-special_properties.des
|-lib
  |-myPackage.jar

I want a access the resource special_properties.des (a properties
file) inside my ServiceImpl class (com.test.myService) but none of
both works:

getClass().getClassLoader().getResourceAsStream(special_properties.des);

getClass().getClassLoader().getResourceAsStream(/config/special_properties.des);

Both returns null.

What's wrong?

Regards

Janfry

_
Descubre la descarga digital con MSN Music. Más de un millón de canciones. 
http://music.msn.es/



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] Load resource not contained in .aar

2006-06-27 Thread Javier V


Hi everybody.

I want to access a resource that I don´t want to include it into the .aar 
file,

and I don´t want to hardcode the fullpath.

I want to load a properties file where I configure the information to access
the database (user,password,url-connection,...).

I'm using Axis2 1.0 and Tomcat 4.1.31.

How can I load the file without hardcoding the fullpath?
  - Relative to the installation to Axis or Tomcat?
  - Can I load the file how a resource with getResourceAsStream?

In which directory is recommended to put the properties file?

Thanks in advance,

Janfry

_
Grandes éxitos, superhéroes, imitaciones, cine y TV... 
http://es.msn.kiwee.com/ Lo mejor para tu móvil.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: No such operation

Sorry -- there's no reason to run java2wsdl, but it really helps to run wsdl2java. I'm not sure why it's producing the erroneous qname attribute in the operation element. This could be a bug in Axis 1.2 (which had pretty sketchy support for document/literal -- Axis
1.3 or 1.4 is much better). Tell your customer to make the following change to the WSDD:Change this:operation name=successfulRenewalOperation
qname=SuccessfulRenewalOperationto this:operation name=successfulRenewalOperation qname=retNS:SuccessfulRenewalRequest
In any case, to answer your questions...The hosting server determines how to dispatch a request by looking at the QName of the child element of the soap:Body. The configuration must provide the hosting service with the necessary information to map the QName to an appropriate method in the service agent.
See Section 4.7.6 in the WS-I Basic Profile:
4.7.6 Operation Signatures
Definition: operation signature

The profile defines the operation signature to be the fully qualified name of the child element of SOAP
body of the SOAP input message described by an operation in a WSDL binding.
In the case of rpc-literal binding, the operation name is used as a wrapper for the part accessors. In the
document-literal case, since a wrapper with the operation name is not present, the message signatures must be
correctly designed so that they meet this requirement.

An endpoint that supports multiple operations must unambiguously identify the operation
being invoked based on the input message that it receives. This is only possible if all the operations specified in the
wsdl:binding associated with an endpoint have a unique operation signature.

R2710

The operations in a wsdl:binding in a DESCRIPTION MUST result in operation signatures
that are different from one another.

And section 4.7.25 (second paragraph):4.7.25 Describing SOAPAction

Interoperability testing has demonstrated that requiring the SOAPAction HTTP header
field-value to be quoted increases interoperability of implementations. Even though HTTP allows for header
field-values to be unquoted, some implementations require that the value be quoted.

The SOAPAction header is purely a hint to processors. All vital information regarding the
intent of a message is carried in the envelope.

Regards,AnneOn 6/27/06, Doug B [EMAIL PROTECTED] wrote:
But I'm trying to go the other direction. I don't want to have to run java2wsdl at all. I want to handwrite the WSDL and use that as the contract for both the client and the server. I want the wsdl2java --server-side to generate a deployable service which matches and honors the original WSDL, including recognizing the specified operation names.
I went ahead and generated server-side artifacts myself just to compare what I think my customer might be seeing. It seems interesting to me that, in fact, the deploy.wsdd that is generated from the --server-side option does contain the operation mappings - they're just looking for what I'd consider the wrong qname:
operation name=successfulRenewalOperation qname=SuccessfulRenewalOperation returnQName=retNS:SuccessfulRenewalResponse xmlns:retNS=
http://az.gov/doi returnType=rtns:SuccessfulRenewalResponseType xmlns:rtns=
http://az.gov/doi
soapAction=http://az.gov/doi-ws/SuccessfulRenewalOperation
parameter qname=pns:SuccessfulRenewalRequest
xmlns:pns=http://az.gov/doi type=tns:SuccessfulRenewalRequestType
xmlns:tns=
http://az.gov/doi//operation(This is either with or without the --noWrapped option.)It gets the correct returnQName from the WSDL-defined response element, including for another operation where that response name is not at all related to the operation or request names, so why wouldn't it use the WSDL-defined request element for the qname by default?
Regarding SOAPAction, so what is supposed to be *the standard* way the service endpoint knows what operation is being requested? Is the engine supposed to have to make a best guess at mapping operation signatures based on parameters (with manual override mapping allowed)? I guess I was expecting something less ambiguous to be part of the specs or at least ws-i.
DougOn 6/27/06, Anne Thomas Manes
[EMAIL PROTECTED] wrote:
After you run java2wsdl, you then have to run wsdl2java. It should have produced an appropriate WSDD for you.The WSDL is the artifact that clients use to consume the service. It is designed to hide implementation information, therefore it isn't much use to Axis in terms of telling it how to dispatch a request. The WSDD is the artifact that contains the information that maps the abstract WSDL information to the concrete implementation. Axis uses the WSDD to dispatch requests.
SOAPAction isn't particularly useful, and it actually goes away in SOAP 1.2.Anne
On 6/27/06, Doug B
[EMAIL PROTECTED] wrote:Interesting. So does the java2wsdl

Re: [Axis2] rest question

If you have two methods, then you must have two endpoints. Otherwise, it isn't RESTful.AnneOn 6/27/06, 
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi Anne I am sorry - I probably didnt get the answer.I have a service class that has 2 methods -public OMElement dothis(OMElement om1)public OMElement dothat(OMElement om2)Now for this service there will be one REST endpoint address - right?
then my question is given my payload xml - how does axis decide whichmethod to invoke in my service?I didnt quite get what u meant byYou have only one function associated with POST to a specific URL
Are u saying that my service can have only one method for it to be restenabled?thanksAnamitra Anne Thomas Manes 
[EMAIL PROTECTED]To maxis-user@ws.apache.orgcc
 06/27/2006 01:17 PMSubject Re: [Axis2] rest question Please respond to
 [EMAIL PROTECTED]he.orgWhen using a RESTful service, *POST* is your method. You have only one
function associated with POST to a specific URL. If you have a service thatexposes methods other than GET, POST, PUT, or DELETE, then it isn'tRESTful.AnneOn 6/27/06, 
[EMAIL PROTECTED]  [EMAIL PROTECTED] wrote:HiAs per the axis2 doc it seems that if I want to do a POST rest service -
the only way axis runtime would detect which method to delegate the calltois from the name of the top level element in the http message body XML -right?I have a service whose method definition is like
public OMElement dothis(OMElelemt payload)When I do the SOAP clientinvoke I send the soap action as urn:dothisandmy payload top element does not match the method name - This works fine
with axis2.But now if I have to do REST call and not have the root element as methodname - how can I acheive that using rest? [I presume soap action is notgoing to work here or is it?]thanks
Anamitra-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]-To unsubscribe, e-mail: 
[EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

WSDL2Java and one-way binding

2006-06-27 Thread John Mani





I'm using Axis 1.4 WSDL2Java to generate skeletons for a webservice 
from a WSDL doc.

The source WSDL (generated by .NET) uses one-way binding - it just 
specifies a 
wsdl:input element, no wsdl:output element.

However, the generated skeleton code seems to be including a 
response to the request.
This is proven by checking the deployed skeleton's WSDL (deployed 
in tomcat, using
the axis war) - it contains wsdl:input and 
WSDL:output messages. Also, when
I run the .NET client against the deployed skeleton, the client 
complaints about the
unexpected entity body in the response.

Any comments/help ?

thanx
-jm

Re: No such operation

Thanks again, Anne. I had read that first BP section, but not really understanding the implications until some of this discussion. It makes more sense now. I did try with Axis 1.3, and it does the same thing, so it must be something I'm just not quite grasping. But I'm content for now that I understand what it's doing and somewhat why, so thanks for your time and effort. It's been a couple years since I spent much time in the Axis newsgroup, but I remember noting back then that your answers were thorough and knowledgable (even bought a copy of your book), so I appreciate having your input on this.
DougOn 6/27/06, Anne Thomas Manes [EMAIL PROTECTED] wrote:
Sorry -- there's no reason to run java2wsdl, but it really helps to run wsdl2java. I'm not sure why it's producing the erroneous qname attribute in the operation element. This could be a bug in Axis 1.2 (which had pretty sketchy support for document/literal -- Axis
1.3 or 1.4 is much better). Tell your customer to make the following change to the WSDD:Change this:operation name=successfulRenewalOperation

qname=SuccessfulRenewalOperationto this:operation name=successfulRenewalOperation qname=retNS:SuccessfulRenewalRequest
In any case, to answer your questions...The hosting server determines how to dispatch a request by looking at the QName of the child element of the soap:Body. The configuration must provide the hosting service with the necessary information to map the QName to an appropriate method in the service agent.
See Section 4.7.6 in the WS-I Basic Profile:
4.7.6 Operation Signatures
Definition: operation signature

R2710

The operations in a wsdl:binding in a DESCRIPTION MUST result in operation signatures
that are different from one another.

And section 4.7.25 (second paragraph):4.7.25 Describing SOAPAction

The SOAPAction header is purely a hint to processors. All vital information regarding the
intent of a message is carried in the envelope.

Regards,AnneOn 6/27/06, Doug B
[EMAIL PROTECTED] wrote:
But I'm trying to go the other direction. I don't want to have to run java2wsdl at all. I want to handwrite the WSDL and use that as the contract for both the client and the server. I want the wsdl2java --server-side to generate a deployable service which matches and honors the original WSDL, including recognizing the specified operation names.
I went ahead and generated server-side artifacts myself just to compare what I think my customer might be seeing. It seems interesting to me that, in fact, the deploy.wsdd that is generated from the --server-side option does contain the operation mappings - they're just looking for what I'd consider the wrong qname:
operation name=successfulRenewalOperation qname=SuccessfulRenewalOperation returnQName=retNS:SuccessfulRenewalResponse xmlns:retNS=
http://az.gov/doi returnType=rtns:SuccessfulRenewalResponseType xmlns:rtns=
http://az.gov/doi
soapAction=http://az.gov/doi-ws/SuccessfulRenewalOperation
parameter qname=pns:SuccessfulRenewalRequest
xmlns:pns=http://az.gov/doi type=tns:SuccessfulRenewalRequestType
xmlns:tns=
http://az.gov/doi//operation(This is either with or without the --noWrapped option.)It gets the correct returnQName from the WSDL-defined response element, including for another operation where that response name is not at all related to the operation or request names, so why wouldn't it use the WSDL-defined request element for the qname by default?
Regarding SOAPAction, so what is supposed to be *the standard* way the service endpoint knows what operation is being requested? Is the engine supposed to have to make a best guess at mapping operation signatures based on parameters (with manual override mapping allowed)? I guess I was expecting something less ambiguous to be part of the specs or at least ws-i.
DougOn 6/27/06, Anne Thomas Manes

Re: Please help with ClientSigningHandler never called

2006-06-27 Thread Mark Mynsted

Any suggestions?


Mark Mynsted wrote:
 I have created a Client Signing Handler to sign my SOAP envelopes with a
 digital signature when consuming a remote web service.
 
 Like the Axis sample I broke this into two classes:
 - ClientSigningHandler
 - SignedSOAPEnvelope
 
 I created a ClientSigningHandler.wsdd (I removed the package name prefix
 for this email following the handler type...):
 
 deployment xmlns=http://xml.apache.org/axis/wsdd/;
 xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
  globalConfiguration
   requestFlow
!-- define the client Signing handler configuration --
handler type=java:ClientSigningHandler
 parameter name=keystore value=WEB-INF/keystore.jks/
/handler
   /requestFlow
  /globalConfiguration
 /deployment
 
 I then registered my handler in the global configuration using the
 org.apache.axis.client.AdminClient tool.
 
 The problem is that the handler only seems to fire when I use the
 org.apache.axis.client.AdminClient tool to list, not when my servlet
 makes my web service call.  When I test my servlet I find that my web
 service call is made, but the ClientSigningHandler never seems to
 execute.  The result is that the SOAP packet is sent, unsigned.
 
 As I said if I execute the list command from the AdminClient, I do see
 the ClientSigningHandler executing.
 
 I searched through the mailing list archives and found where somebody
 suggested checking for two files:
 - client-config.wsdd
 - server-config.wsdd
 
 It seems that only the 'server-config.wsdd' was created.  I never
 received an error when executing the AdminClient tool, and it did appear
 to update the server-config.wsdd.
 
 Any suggestions?
 
 
 --
 MM
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
MM


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: No such operation

Doug,Can you post the portType and binding definitions for this operation? There might be something there that's not quite right.AnneOn 6/27/06,
Doug B [EMAIL PROTECTED] wrote:
Thanks again, Anne. I had read that first BP section, but not really understanding the implications until some of this discussion. It makes more sense now. I did try with Axis 1.3, and it does the same thing, so it must be something I'm just not quite grasping. But I'm content for now that I understand what it's doing and somewhat why, so thanks for your time and effort. It's been a couple years since I spent much time in the Axis newsgroup, but I remember noting back then that your answers were thorough and knowledgable (even bought a copy of your book), so I appreciate having your input on this.
DougOn 6/27/06, Anne Thomas Manes
[EMAIL PROTECTED] wrote:
Sorry -- there's no reason to run java2wsdl, but it really helps to run wsdl2java. I'm not sure why it's producing the erroneous qname attribute in the operation element. This could be a bug in Axis 1.2 (which had pretty sketchy support for document/literal -- Axis
1.3 or 1.4 is much better). Tell your customer to make the following change to the WSDD:Change this:operation name=successfulRenewalOperation

R2710

The operations in a wsdl:binding in a DESCRIPTION MUST result in operation signatures
that are different from one another.

And section 4.7.25 (second paragraph):4.7.25 Describing SOAPAction

The SOAPAction header is purely a hint to processors. All vital information regarding the
intent of a message is carried in the envelope.

Regards,AnneOn 6/27/06, Doug B

[EMAIL PROTECTED] wrote:
But I'm trying to go the other direction. I don't want to have to run java2wsdl at all. I want to handwrite the WSDL and use that as the contract for both the client and the server. I want the wsdl2java --server-side to generate a deployable service which matches and honors the original WSDL, including recognizing the specified operation names.
I went ahead and generated server-side artifacts myself just to compare what I think my customer might be seeing. It seems interesting to me that, in fact, the deploy.wsdd that is generated from the --server-side option does contain the operation mappings - they're just looking for what I'd consider the wrong qname:
operation name=successfulRenewalOperation qname=SuccessfulRenewalOperation returnQName=retNS:SuccessfulRenewalResponse xmlns:retNS=
http://az.gov/doi returnType=rtns:SuccessfulRenewalResponseType xmlns:rtns=
http://az.gov/doi
soapAction=http://az.gov/doi-ws/SuccessfulRenewalOperation
parameter qname=pns:SuccessfulRenewalRequest
xmlns:pns=http://az.gov/doi type=tns:SuccessfulRenewalRequestType
xmlns:tns=
http://az.gov/doi//operation(This is either with or without the --noWrapped option.)It gets the correct returnQName from the WSDL-defined response element, including for another operation where that response name is not at all related to the operation or request names, so why wouldn't it use the WSDL-defined request element for the qname by default?
Regarding SOAPAction, so what is supposed to be *the standard* way the service endpoint knows what operation is being requested? Is the engine supposed to have to make a best guess at mapping operation signatures based

Re: No such operation

Sure: wsdl:portType name=DOIServicesPortTypewsdl:operation name=SuccessfulRenewalOperation wsdl:input message=tns:SuccessfulRenewalRequestMessage/
wsdl:output message=tns:SuccessfulRenewalResponseMessage//wsdl:operation /wsdl:portType wsdl:binding name=DOIServicesBinding type=tns:DOIServicesPortType
soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http/wsdl:operation name=SuccessfulRenewalOperation
soap:operation soapAction=http://az.gov/doi-ws/SuccessfulRenewalOperation/ wsdl:input soap:body use=literal/
/wsdl:input wsdl:output soap:body use=literal/ /wsdl:output/wsdl:operation /wsdl:binding
On 6/27/06, Anne Thomas Manes [EMAIL PROTECTED] wrote:
Doug,Can you post the portType and binding definitions for this operation? There might be something there that's not quite right.Anne
On 6/27/06,
Doug B [EMAIL PROTECTED] wrote:

[EMAIL PROTECTED] wrote:
Sorry -- there's no reason to run java2wsdl, but it really helps to run wsdl2java. I'm not sure why it's producing the erroneous qname attribute in the operation element. This could be a bug in Axis 1.2 (which had pretty sketchy support for document/literal -- Axis
1.3 or 1.4 is much better). Tell your customer to make the following change to the WSDD:Change this:operation name=successfulRenewalOperation

R2710

The operations in a wsdl:binding in a DESCRIPTION MUST result in operation signatures
that are different from one another.

And section 4.7.25 (second paragraph):4.7.25 Describing SOAPAction

The SOAPAction header is purely a hint to processors. All vital information regarding the
intent of a message is carried in the envelope.

Regards,AnneOn 6/27/06, Doug B

Re: No such operation


Darn.  Sorry for formatting.  Let's try again:

 wsdl:portType name=DOIServicesPortType
   wsdl:operation name=SuccessfulRenewalOperation
wsdl:input message=tns:SuccessfulRenewalRequestMessage/
wsdl:output message=tns:SuccessfulRenewalResponseMessage/
   /wsdl:operation
 /wsdl:portType

 wsdl:binding name=DOIServicesBinding type=tns:DOIServicesPortType
   soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
   wsdl:operation name=SuccessfulRenewalOperation
 soap:operation
soapAction=http://az.gov/doi-ws/SuccessfulRenewalOperation/
wsdl:input
soap:body use=literal/
/wsdl:input
wsdl:output
soap:body use=literal/
/wsdl:output
   /wsdl:operation
 /wsdl:binding



Doug,

Can you post the portType and binding definitions for this operation? There 
might be something there that's not quite right.



Anne



 On 6/27/06,  Doug B [EMAIL PROTECTED] wrote:




 Thanks again, Anne.  I had read that first BP section, but not really 
understanding the implications until some of this discussion.  It makes more 
sense now.

I did try with Axis 1.3, and it does the same thing, so it must be something 
I'm just not quite grasping.  But I'm content for now that I understand what 
it's doing and somewhat why, so thanks for your time and effort.  It's been a 
couple years since I spent much time in the Axis newsgroup, but I remember 
noting back then that your answers were thorough and knowledgable (even bought 
a copy of your book), so I appreciate having your input on this.



Doug



On 6/27/06, Anne Thomas Manes   [EMAIL PROTECTED] wrote:




Sorry -- there's no reason to run java2wsdl, but it really helps to run wsdl2java. 
I'm not sure why it's producing the erroneous qname attribute in the 
operation element. This could be a bug in Axis 1.2 (which had pretty sketchy 
support for document/literal -- Axis  1.3 or 1.4 is much better).

Tell your customer to make the following change to the WSDD:

Change this:


operation name=successfulRenewalOperation

 qname=SuccessfulRenewalOperation



to this:

operation name=successfulRenewalOperation

qname=retNS:SuccessfulRenewalRequest

In any case, to answer your questions...

The hosting server determines how to dispatch a request by looking at the QName of 
the child element of the soap:Body. The configuration must provide the 
hosting service with the necessary information to map the QName to an appropriate 
method in the service agent.

See Section 4.7.6 in the WS-I Basic Profile:



4.7.6 Operation Signatures

Definition: operation signature


The profile defines the operation signature to be the fully qualified name of 
the child element of SOAP body of the 
SOAP input message described by an operation in a WSDL binding.

In the case of rpc-literal binding, the operation name is used as a wrapper for 
the part accessors. In the  
document-literal case, since a wrapper with the operation name is not present, 
the message signatures must be   correctly 
designed so that they meet this requirement.


An endpoint that supports multiple operations must unambiguously identify the 
operation being invoked based on the 
input message that it receives. This is only possible if all the operations 
specified in the wsdl:binding 
associated with an endpoint have a unique operation signature.  
   

  R2710 The operations in a 
wsdl:binding in a DESCRIPTION MUST result in operation signatures   
that are different from one another.
 And section 4.7.25 (second paragraph):


4.7.25 Describing SOAPAction


Interoperability testing has demonstrated that requiring the SOAPAction HTTP 
header field-value to be quoted 
increases interoperability of implementations. Even though HTTP allows for 
header  field-values to be 
unquoted, some implementations require that the value be quoted.
 

The SOAPAction header is purely a hint to processors. All vital information 
regarding the   intent of a message 
is carried in the envelope.  
Regards,


Anne



On 6/27/06, Doug B[EMAIL PROTECTED] wrote:




But I'm trying to go the other direction.  I don't want to have to run java2wsdl at all.  
I want to handwrite the WSDL and use that as the contract for both the client and the 
server.  I want the wsdl2java --server-side to generate a deployable service 
which matches and honors the original WSDL, including

Re: No such operation

I don't see anything wrong. Smells like a bug...On 6/27/06, Doug B [EMAIL PROTECTED] wrote:
Darn.Sorry for formatting.Let's try again:wsdl:portType name=DOIServicesPortTypewsdl:operation name=SuccessfulRenewalOperationwsdl:input message=tns:SuccessfulRenewalRequestMessage/
wsdl:output message=tns:SuccessfulRenewalResponseMessage//wsdl:operation/wsdl:portTypewsdl:binding name=DOIServicesBinding type=tns:DOIServicesPortType
soap:binding style=documenttransport=http://schemas.xmlsoap.org/soap/http/wsdl:operation name=SuccessfulRenewalOperation
soap:operationsoapAction=http://az.gov/doi-ws/SuccessfulRenewalOperation/wsdl:inputsoap:body use=literal/
/wsdl:inputwsdl:outputsoap:body use=literal//wsdl:output/wsdl:operation/wsdl:binding
 Doug, Can you post the portType and binding definitions for this operation? There might be something there that's not quite right. Anne
On 6/27/06,Doug B [EMAIL PROTECTED] wrote: Thanks again, Anne.I had read that first BP section, but not really understanding the implications until some of this discussion.It makes more sense now.
 I did try with Axis 1.3, and it does the same thing, so it must be something I'm just not quite grasping.But I'm content for now that I understand what it's doing and somewhat why, so thanks for your time and effort.It's been a couple years since I spent much time in the Axis newsgroup, but I remember noting back then that your answers were thorough and knowledgable (even bought a copy of your book), so I appreciate having your input on this.
 Doug On 6/27/06, Anne Thomas Manes [EMAIL PROTECTED] wrote:  Sorry -- there's no reason to run java2wsdl, but it really helps to run wsdl2java. I'm not sure why it's producing the erroneous qname attribute in the operation element. This could be a bug in Axis 
1.2 (which had pretty sketchy support for document/literal -- Axis1.3 or 1.4 is much better). Tell your customer to make the following change to the WSDD: Change this:
 operation name=successfulRenewalOperationqname=SuccessfulRenewalOperation to this: operation name=successfulRenewalOperation
 qname=retNS:SuccessfulRenewalRequest In any case, to answer your questions... The hosting server determines how to dispatch a request by looking at the QName of the child element of the soap:Body. The configuration must provide the hosting service with the necessary information to map the QName to an appropriate method in the service agent.
 See Section 4.7.6 in the WS-I Basic Profile: 4.7.6 Operation Signatures Definition: operation signature The profile defines the operation signature to be the fully qualified name of the child element of SOAP body of the SOAP input message described by an operation in a WSDL binding.
 In the case of rpc-literal binding, the operation name is used as a wrapper for the part accessors. In thedocument-literal case, since a wrapper with the operation name is not present, the message signatures must be correctly designed so that they meet this requirement.
 An endpoint that supports multiple operations must unambiguously identify the operation being invoked based on the input message that it receives. This is only possible if all the operations specified in the wsdl:binding associated with an endpoint have a unique operation signature.
 R2710 The operations in a wsdl:binding in a DESCRIPTION MUST result in operation signatures that are different from one another. And section 
4.7.25 (second paragraph): 4.7.25 Describing SOAPAction Interoperability testing has demonstrated that requiring the SOAPAction HTTP header field-value to be quoted increases interoperability of implementations. Even though HTTP allows for headerfield-values to be unquoted, some implementations require that the value be quoted.
 The SOAPAction header is purely a hint to processors. All vital information regarding the intent of a message is carried in the envelope.Regards,
 Anne On 6/27/06, Doug B  [EMAIL PROTECTED] wrote:  But I'm trying to go the other direction.I don't want to have to run java2wsdl at all.I want to handwrite the WSDL and use that as the contract for both the client and the server.I want the wsdl2java --server-side to generate a deployable service which matches and honors the original WSDL, including recognizing the specified operation names.
 I went ahead and generated server-side artifacts myself just to compare what I think my customer might be seeing.It seems interesting to me that, in fact, the deploy.wsdd that is generated from the --server-side option does contain the operation mappings - they're just looking for what I'd consider the wrong qname:
 operation name=successfulRenewalOperation qname=SuccessfulRenewalOperation returnQName=retNS:SuccessfulRenewalResponse
 xmlns:retNS= http://az.gov/doi returnType=rtns:SuccessfulRenewalResponseType xmlns:rtns= 
http://az.gov/doi soapAction=http://az.gov/doi-ws/SuccessfulRenewalOperation 
 parameter qname=pns:SuccessfulRenewalRequest xmlns:pns=http://az.gov/doi type=tns:SuccessfulRenewalRequestType

[1.3] Handling large values

2006-06-27 Thread Simon McMahon




Hi,

Axis throws various faults, including out-of-memory, when I pass a large 
value through a web service - e.g. a 5 Mb String.

I dont have many alternatives because the firewall only allows http. 
Otherwise I would just use FTP.

Any suggestions on how to get Axis 1.xto handle large messages? I 
dont want to try Axis 2 (again) because I already tried this some time 
agoand it required too many changes to my application.

Regards,

Simon.


Simon McMahon

Work: (07) 31311420Mobile: (043) 2294180

*
This email, including any attachments sent with it, is
confidential and for the sole use of the intended recipient(s).
This confidentiality is not waived or lost, if you receive it and
you are not the intended recipient(s), or if it is transmitted/
received in error.

Any unauthorised use, alteration, disclosure, distribution or
review of this email is strictly prohibited.  The information
contained in this email, including any attachment sent with
it, may be subject to a statutory duty of confidentiality if it
relates to health service matters.

If you are not the intended recipient(s), or if you have
received this email in error, you are asked to immediately
notify the sender by telephone collect on Australia
+61 1800 198 175 or by return email.  You should also
delete this email, and any copies, from your computer
system network and destroy any hard copies produced.

If not an intended recipient of this email, you must not copy,
distribute or take any action(s) that relies on it; any form of
disclosure, modification, distribution and/or publication of this
email is also prohibited.

Although Queensland Health takes all reasonable steps to
ensure this email does not contain malicious software,
Queensland Health does not accept responsibility for the
consequences if any person's computer inadvertently suffers
any disruption to services, loss of information, harm or is
infected with a virus, other malicious computer programme or
code that may occur as a consequence of receiving this
email.

Unless stated otherwise, this email represents only the views
of the sender and not the views of the Queensland Government.

[Axis2] uploaded .aar still using cached classes?

2006-06-27 Thread Andrew B

Hi,I have uploaded a web service (.aar) to Axis2, and it appears to keep using old versions of the service classes, even after I've made changes. Axis2 is running on JBoss 4.0.3, with JDK 1.4. I don't have the option of restarting JBoss, as it is a production environment. Anyone have any idea why this might be happening? (I've also tried deactivating and reactivating the service, and this doesn't help).Thanks,Andrew 
		Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls.  Great rates starting at 1¢/min.

Re: [Axis2] uploaded .aar still using cached classes?

2006-06-27 Thread Deepal Jayasinghe

Hi Andrew;

You need to change axis2.xml , there you have parameter called;

parameter name=hotupdate locked=falsefalse/parameter

you have to change that to
parameter name=hotupdate locked=falsetrue/parameter

Andrew B wrote:

 Hi,

 I have uploaded a web service (.aar) to Axis2, and it appears to keep
 using old versions of the service classes, even after I've made changes.

 Axis2 is running on JBoss 4.0.3, with JDK 1.4. I don't have the option
 of restarting JBoss, as it is a  production environment. Anyone have
 any idea why this might be happening? (I've also tried deactivating
 and reactivating the service, and this doesn't help).

 Thanks,

 Andrew

 
 Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great
 rates starting at 1¢/min.
 http://us.rd.yahoo.com/mail_us/taglines/postman7/*http://us.rd.yahoo.com/evt=39666/*http://messenger.yahoo.com


-- 
Thanks,
Deepal

~Future is Open~ 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Handler unexpected behaviour


yep,
OperationContext is the one for you

Ajith

On 6/27/06, Davanum Srinivas [EMAIL PROTECTED] wrote:

OperationContext?

-- dims

On 6/27/06, Michele Mazzucco [EMAIL PROTECTED] wrote:
 Ajith ,

 so where do you suggest to temporarily 'store' my stuff (I need to save
 some data during the incoming phase to reuse it when the response is
 coming back)?, could OperationContext be fine?

 p.s. I don't need to keep any data across different invocations.


 Thanks,
 Michele

 Ajith Ranabahu wrote:
  Hi
 
  from my previous posts I understood handlers are 'application scope',
  that is they maintain a state across different client invocations.
 
  Actually handlers are supposed to be stateless! They should not
  maintain anything by themselves, rather they should be using the
  appropriate context  to store anything required.
 
  I have a handler intercepting both incoming and outgoing messages and
  unfortunately I realized that instance fields are 'reset' (see logs
  below). Is there any reason for this counter intuitive behavior?
 
 
  So what I seem to understand is your handler implementation may not
  have been done in the recommended way.Have a look at this article [1]
  by Deepal which explains how the handlers work.
 
 
 

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




--
Davanum Srinivas : http://people.apache.org/~dims/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Ajith Ranabahu

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Load resource not contained in .aar

2006-06-27 Thread Deepal Jayasinghe

Well you can put your resources into WEB-INF/lib directory or to system
class path.

Javier V wrote:

 Hi everybody.

 I want to access a resource that I don´t want to include it into the
 .aar file,
 and I don´t want to hardcode the fullpath.

 I want to load a properties file where I configure the information to
 access
 the database (user,password,url-connection,...).

 I'm using Axis2 1.0 and Tomcat 4.1.31.

 How can I load the file without hardcoding the fullpath?
   - Relative to the installation to Axis or Tomcat?
   - Can I load the file how a resource with getResourceAsStream?

 In which directory is recommended to put the properties file?

 Thanks in advance,

 Janfry

 _
 Grandes éxitos, superhéroes, imitaciones, cine y TV...
 http://es.msn.kiwee.com/ Lo mejor para tu móvil.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Thanks,
Deepal

~Future is Open~ 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[1.3] Handling arrays - interop with .NET

2006-06-27 Thread Simon McMahon

 Hi,

My web service returns an array of Provider (see below).
The WSDL (see below) defines Provider with all my data elements but
adds the extra one on the end 'provider'. This appears to be a link
field, maybe to support the array of these things. This extra field
appears to mess up the consuming application (.NET).

I do the Axis side, not the .NET so I'm not sure what the .NET problem
is or how to do anything different on the Axis side. The .NET people
have asked me not to use this link field for the arrays. How can I do
that?

Any help would be appreciated.

Thanks,

Simon.

...
- wsdl:types
- schema
targetNamespace=https://dev.health.qld.gov.au/axis/services/qh-providers;
xmlns=http://www.w3.org/2001/XMLSchema;
  import namespace=http://schemas.xmlsoap.org/soap/encoding/; / 

- complexType name=Provider
- sequence
  element name=name nillable=true type=soapenc:string / 

  element name=providerId nillable=true type=soapenc:string / 

  element name=org nillable=true type=soapenc:string / 

  element name=locationId nillable=true type=soapenc:string / 

  element name=application nillable=true type=soapenc:string /


  element name=deliveryMethod nillable=true type=soapenc:string
/ 

  element name=id type=xsd:int / 

  element name=provider nillable=true type=impl:Provider / 

  /sequence


  /complexType


- complexType name=ArrayOfProvider
- complexContent
- restriction base=soapenc:Array
  attribute ref=soapenc:arrayType wsdl:arrayType=impl:Provider[]
/ 

  /restriction


  /complexContent


  /complexType








Simon McMahon

Work: (07) 31311420
Mobile: (043) 2294180



*
This email, including any attachments sent with it, is
confidential and for the sole use of the intended recipient(s).
This confidentiality is not waived or lost, if you receive it and
you are not the intended recipient(s), or if it is transmitted/
received in error.

Any unauthorised use, alteration, disclosure, distribution or
review of this email is strictly prohibited.  The information
contained in this email, including any attachment sent with
it, may be subject to a statutory duty of confidentiality if it
relates to health service matters.

If you are not the intended recipient(s), or if you have
received this email in error, you are asked to immediately
notify the sender by telephone collect on Australia
+61 1800 198 175 or by return email.  You should also
delete this email, and any copies, from your computer
system network and destroy any hard copies produced.

If not an intended recipient of this email, you must not copy,
distribute or take any action(s) that relies on it; any form of
disclosure, modification, distribution and/or publication of this
email is also prohibited.

Although Queensland Health takes all reasonable steps to
ensure this email does not contain malicious software,
Queensland Health does not accept responsibility for the
consequences if any person's computer inadvertently suffers
any disruption to services, loss of information, harm or is
infected with a virus, other malicious computer programme or
code that may occur as a consequence of receiving this
email.

Unless stated otherwise, this email represents only the views
of the sender and not the views of the Queensland Government.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Type missing! error using Axis2 WSDL2Java w/ Amazon WS


Hi,
What is the data binding you tried ? Can you try with XMLBeans (-d xmlbeans) ?

Ajith

On 6/27/06, Ken Yee [EMAIL PROTECTED] wrote:

Anyone try the latest Axis2 1.0's WSDL2Java against
Amazon's web services?  I get a cryptic Type missing
error (it'd be nice if it printed out what type it's
looking for so we'd have a better clue about what's
going wrong ;-)

Here's the WSDL URL (I use Ant to pull the WSDL file
down locally though):
http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl

This WSDL works fine w/ Axis 1.x...

 ken

 [java] Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException:
org.apache.axis2.schema.SchemaCompilationException:
Type missing!
 [java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(C
odeGenerationEngine.java:185)
 [java] at
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
 [java] at
org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
 [java] Caused by: java.lang.RuntimeException:
org.apache.axis2.schema.Schem
aCompilationException: Type missing!
 [java] at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.eng
age(SimpleDBExtension.java:117)
 [java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(C
odeGenerationEngine.java:140)
 [java] ... 2 more
 [java] Caused by:
org.apache.axis2.schema.SchemaCompilationException:
Type
missing!
 [java] at
org.apache.axis2.schema.writer.JavaBeanWriter.addPropertyEntr
ies(JavaBeanWriter.java:464)
 [java] at
org.apache.axis2.schema.writer.JavaBeanWriter.populateInfo(Ja
vaBeanWriter.java:426)
 [java] at
org.apache.axis2.schema.writer.JavaBeanWriter.getBeanElement(
JavaBeanWriter.java:403)


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Ajith Ranabahu

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: performance test

2006-06-27 Thread Warren Crossing

I'm also doing such testing, I am thinking of using the axis junit 
client modifying it somewhat and then measuring the request using jmeter.


The performance of the WS app is measured along with tomcat and axis 
because your never going to run it outside of that container. so measure 
client latencies. then you can compare with jbos and bea and oracle and 
let us know which is best =)


Don't worry about CPU and memory - just put the client on another 
machine and crank up the load until it falls over. because you will 
never have 100%CPU and Memory utilization with the app and the CPU still 
wirking.


Make sure you test with sessions and with the database and with failure 
case to get a good indication of the service latencies and throughput.


Warren.

Giovane Moura wrote:

Hello,

I'd like to evaluate the performance of my web service in face of 
differents

workloads.
I was wondering how I can do that...

As my WS runs inside Axis (that runs inside Tomcat and the last one needs
Apache httpd), it ins't that simple to get informations like:

1. How much memory required only by the WS app?
2. How much CPU time is it using?


How can I get this informations?
Is there any way to have this information(putting apart axis/tomcat/apache
consumption)?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: AXIS on a PDA

2006-06-27 Thread Warren Crossing

your using gcj gnu which uses a native xml library as opposed to sun 
java which uses ?xalan? or ?xerces?
you need to get the servlet.jar to satify runtime dependencies - as for 
the jvm you choose its entirely up to you.


check http://tuxmobil.org/pda_linux_apps_java.html for more info.

Naraghi wrote:

Martin Gainty a �crit :


Naraghi-
Quick question but I have to ask is your development environment 
conforming to requirements spec?





   Yes, in my client's librairies folder there is all  librairie :
activation.jar
   axis.jar
   commons-discovery-0.2.jar
commons-logging-1.0.4.jar
jaxrpc.jar
log4j-1.2.8.jar
log4j.properties
mail.jar
   saaj.jar
   wsdl4j-1.5.1.jar
   xercesImpl.jar

but when I execute I have that :

Jun 26, 2006 10:35:26 AM 
org.apache.axis.configuration.EngineConfigurationFactoryFinder newFactory
WARNING: Factory 
org.apache.axis.configuration.EngineConfigurationFactoryServlet Ignored: 
invoke method failed: public static EngineConfigurationFactory 
newFactory(Object).
java.lang.ClassNotFoundException: *javax/servlet/ServletConfig not found 
in java.lang.ClassLoader$1*{urls=[file:/My 
Documents/ClientSimple/amui-client-pda.jar], parent=null}

  at java.net.URLClassLoader.findClass (URLClassLoader.java:902)
  at java.lang.ClassLoader.loadClass (ClassLoader.java:342)
  at java.lang.ClassLoader$1.loadClass (ClassLoader.java:1110)

  at java.lang.ClassLoader.loadClass (ClassLoader.java:294)
  at 
org.apache.axis.configuration.EngineConfigurationFactoryServlet.newFactory 
(EngineConfigurationFactoryServlet.java:79)

  at java.lang.reflect.Method.invokeNative (Native Method)
 ...
Caused by: java.lang.ExceptionInInitializerError
  at java.lang.VMClassLoader.loadClass (Native Method)
  at java.lang.ClassLoader.loadClass (ClassLoader.java:329)
  at java.lang.ClassLoader$1.loadClass (ClassLoader.java:1110)
  at java.lang.ClassLoader.loadClass (ClassLoader.java:294)
  at org.w3c.dom.bootstrap.DOMImplementationRegistry.newInstance 
(DOMImplementationRegistry.java:140)
  at gnu.xml.dom.DomDocumentBuilderFactory.init 
(DomDocumentBuilderFactory.java:69)

  at java.lang.reflect.Constructor.constructNative (Native Method)
  at java.lang.reflect.Constructor.newInstance (Constructor.java:242)
  at java.lang.Class.newInstance (Class.java:1136)
  at javax.xml.parsers.DocumentBuilderFactory.newInstance 
(DocumentBuilderFactory.java:104)

  at org.apache.axis.utils.XMLUtils.getDOMFactory (XMLUtils.java:221)
  at org.apache.axis.utils.XMLUtils.clinit (XMLUtils.java)
  at org.apache.axis.utils.XMLUtils.clinit (XMLUtils.java)
  at org.apache.axis.configuration.FileProvider.configureEngine 
(FileProvider.java:179)

  ...15 more
*
Caused by: java.lang.UnsatisfiedLinkError: Native library `xmlj' not 
found (as file `xmlj') in gnu.classpath.boot.library.path and 
java.library.path

  at java.lang.Runtime.loadLibrary (Runtime.java:763)

And it is right that in my PDA's JVM there is no Native library `xmlj' 
or javax.servlet package**

*
  









Hi,

  I'm a student and I'm trying to use Axis on a PDA ( as a client of 
course).
But it seems that Axis doesn't have all librairies needed to work 
(example : javax.servlet package or libxmlj...).

And the problem is that my PDA's JVM doesn't have those packages.

The PDA's JVM is Mysaifu JVM ( a J2SE JVM )

My first question is why does Axis need javax.servlet package to work 
as a client ??
And my second question is : does exist a minimal version of Axis ( 
for PDA's JVM) that I can use  (for my PDA client).








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [AXIS2] Does AXIS2 support Java2WSDL?

2006-06-27 Thread Warren Crossing

find /opt/axis2/lib/ -name *.jar -print -exec jar tvf {} \; | grep 
.jar$\|WSDL


i would expect it to be in /opt/axis2/lib/axis2-tools-1.0.jar

Ajith Ranabahu wrote:

Hi,
Hmm... I'm sure the  The Java2WSDL is there in the codebase in  the
Java2WSDL (maven)module. However I'm not sure whether it is missing
from the build due to a build script problem.
Please check the build and see whether the Java2WSDL class is there
inside the build.

Ajith

On 6/26/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

As I mentioned, I used the Eclipse-Plugin. It is downloadable under 
the tools section of axis2 1.0.

Deepal advised me to us the annogen-0.1.0.jar from codehaus.
Now it works for me.

Bille

 -Urspr�ngliche Nachricht-
 Von: axis-user@ws.apache.org
 Gesendet: 26.06.06 07:22:47
 An: axis-user@ws.apache.org
 Betreff: Re: [AXIS2] Does AXIS2 support Java2WSDL?


  From a look at the codebase - no there is not this functionallity in
 axis2. I am currently using axis-1.4 for this feature.

 the invocation exception you get is because the plugin cannot find the
 java2wsdl code.

 correct me if i am wrong and i will stand corrected.

 [EMAIL PROTECTED] wrote:
  Hi Emily,
 
  yes!
  But I didn't manage to generate the WSDL-file.
  Have a look at this: 
http://marc.theaimsgroup.com/?l=axis-userm=115114727308460w=2

  to see what steps I tried.
  There's not answer to my question by now, maybe you'll get it to 
work. Let me know ;)

 
  HTH
 
  Bille
 
 
 -Ursprￜngliche Nachricht-
 Von: axis-user@ws.apache.org
 Gesendet: 25.06.06 05:43:34
 An: axis-user@ws.apache.org
 Betreff: [AXIS2] Does AXIS2 support Java2WSDL?
 
 
 
 HI,
 
 
 
 Does AXIS2 support Java2WSDL? Any pointer is very much appreciated.
 
 
 
 Thanks,
 
 Emily
 
 
 
  __
  Verschicken Sie romantische, coole und witzige Bilder per SMS!
  Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



_
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071distributionid=0071


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Flash Connectivity Problems