version of the Uniform Electronic Transactions Act or any other statute
governing electronic transactions.
- Original Message -
From: "Huitang Li"
To: axis-user@ws.apache.org
Sent: Thursday, July 16, 2009 6:55:03 PM GMT -06:00 US/Canada Central
Subject: Re: server fault is not r
shall constitute a contract or electronic
signature under the Electronic Signatures in Global and National Commerce Act,
any version of the Uniform Electronic Transactions Act or any other statute
governing electronic transactions.
- Original Message -----
From: "Huitang Li"
To:
Hi,
I am using client-side repository with addressing module to connect to an Axis
2.1.4.1 web service(In-out pattern). The client and the web service are both
running on my local machine. One thing I notice is that when a fault is thrown
in the server, the client side got "500 Internal Server
Hi,
I chose to use asynchronous calls in Axis2 client to transmit soap
messages. The test class is generated by wsdl2java. When I tested it,
the test did not fail even if the handler is set to fail() in the
receiveErrorXXX() which in turn indeed got called.
This problem does not happen in sy
I am using axis2 1.3. I put the -Eosv there in the command line, and it
did not solve the problem. Anyway, my problem was solved by changing
wsdl. Thanks.
Amila Suriarachchi wrote:
On 10/23/07, *Huitang Li* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Excellent!
an element named fault without
minOccurs=0 or nillable=ture.
So ADB gives an exception because of this.
if you want to remove this use -Eosv when genrating the code.
Amia.
On 10/23/07, *Huitang Li* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi,
I created a web s
Hi,
I created a web service code based on a wsdl, and it is run in resin
3.1.3, and I have the soapmonitor activated. When a web service client
sent a soap message to it, it threw the following exception:
java.lang.RuntimeException: Can not serialize OM Element Envelope
at
org.apache.axi
wrote:
On 10/12/07, *Huitang Li* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
With further debugging, I found something interesting: when the
onMessage() method is done in AxisCallback, the application
proceeds on
the method "public void
It looks like I am hitting the same bug as
http://issues.apache.org/jira/browse/AXIS2-3265
Any solution?
Thanks.
Huitang Li wrote:
I mean the run() method in the private class
NonBlockingInvocationWorker in class OutInAxisOperationClient.
private class NonBlockingInvocationWorker
) { /* compiled
code */ }
public void run() { /* compiled code */ }
<= this line of code
}
Huitang Li wrote:
With further debugging, I found something interesting: when the
onMessage() method is done in AxisCallback, the application proceeds
ete = true;
}
and add a isComplete Method
boolean isComplete()
{
return _complete;
}
you can now use it like the old Callback class.
while ( !_axisCallBack.isComplete())
{
Thread.sleep(1000);
}
Hope this helps.
On 10/12/07, *Huitang Li* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>&g
Thanks, Deepal. I will be happy to create a JRIA. But can you show me a
good example using this new API in the client code? I am working on a
project, and I cannot wait for the next Axis2 release.
Thanks.
Huitang
Deepal jayasinghe wrote:
Hi Huitang ,
Definitely a bug in codegen , please cr
All these codes are auto-generated by Axis2 1.3 wsdl2java command. I do
not know whether it is an old callback or not. But it does says:
_operationClient.setCallback(new
org.apache.axis2.client.async.AxisCallback() {
// all the codes that I pasted in my previous email.
}
In the generated code
t?
Can you cut paste the code here.
Regards,
Rajith Attapattu
Red Hat.
On 10/11/07, *Huitang Li* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi,
When I use the new API AxisCallback, the application seems stuck,
and it
is taking forever to get any res
Hi,
When I use the new API AxisCallback, the application seems stuck, and it
is taking forever to get any response. However, when I switched to the
Callback class, I got the response from web service quickly.
Any idea?
Thanks.
-
.
Regards,
Rajith
On 10/8/07, *Huitang Li* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Thanks very much. I will try it. I hope axis2 developers will use the
new API in the sample codes (under userguide folder) for next axis2
release so that they can give me an id
.
(I looked at the code and I see that it is the case)
So you can be sure that the MEP is completed when the _complete
boolean is set to "true".
Regards,
Rajith Attapattu.
Red Hat Canada.
On 10/8/07, * Huitang Li* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Any thought here, please? I would love to use new API, but I do not know
how to fit it into the product.
Huitang Li wrote:
Thanks for your input. I saw the thread you mentioned before I sent
out my question to the list. However, I cannot see the solution to the
question. The main thread can
.
Huitang Li wrote:
I tested with a public accessible web service, and it has the same
result. If you want to test it out, please see the web service
http://www.tilisoft.com/ws/LocInfo/ZipCode.asmx
You can get its wsdl here:
http://www.tilisoft.com/ws/LocInfo/ZipCode.asmx?WSDL
Follow the steps
Hi,
This problem looks like resin-specific. It seems that without resin jars
loaded, the code runs ok. However, when the resin jars are loaded, the
soap message is not correctly created.
Will anyone please take a look?
Thanks.
Huitang Li wrote:
I tested with a public accessible web
message be created correctly in
resin remote-debugging mode while it is incorrectly created when resin
is not running in remote-debugging mode? It looks more like a
resin-users question. I posted this question to that user-group mailing
list as well. If you want to test it, please download
codes, it still uses the old Callback class.
I just wonder how the main thread can detect whether the spawning thread
is complete or not with the new AxisCallback API.
Any idea?
Suran Jayathilaka wrote:
Huitang Li wrote:
Hi,
I created a web service client following Async/One Channel model
(It would clear up whether it's a problem just for you and your
environment, or a wsdl-based problem).
Regards,
-jeff
-Original Message-
From: Huitang Li [mailto:[EMAIL PROTECTED]
Sent: Friday, October 05, 2007 5:32 PM
To: axis-user@ws.apache.org
Subject: Re: org.xml.sax.SAXPars
Hmm No one replies to this posting.
It seems that it is only me who does not quite like the new AxisCallback
which does not the isComplete() method. I see the beauty of it as well,
though.
Huitang Li wrote:
Hi,
I created a web service client following Async/One Channel model using
Sorry for the confusion. But all "ns2" should be "ns1".
Huitang Li wrote:
With further debugging, I notice that somehow the soap message is NOT
created correctly when the client code is running in server environment.
...
However, when it is running in debug mode or no
://test.mytest.com";>...
Again, the client code is Axis generated based on a wsdl file.
Any idea?
Thanks.
Martin Gainty wrote:
Without seeing the wsdl there is very little we can do to help you
(Nonetheless I would check Classpath delta)
M--
- Original Message -
From: &qu
Hi,
I created a web service client following Async/One Channel model using
axis2-generated stub. In the stub code, AxisCallback interface is used.
For almost all tests, no soap message response is received before the
client is finished. This is verified with the help of the excellent tool
tc
, then it might be a relatively simply
namespace fix. Let's hope so.
-jeff
-Original Message-
From: Huitang Li [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 04, 2007 2:46 PM
To: axis-user@ws.apache.org
Subject: Re: org.xml.sax.SAXParseException: The prefix "ns1" f
Hi,
I did not see any input for my question. Maybe it is a too simple and
dumb question to answer? Is it only me who gets this exception?
Experts, please help me out.
Huitang Li wrote:
Here is more information about the exception: when the code is running
in debug mode and I put a
did google search, and found quite a few postings mentioning the same
problem. However, I did not find any solution posted. If you know the
solution, please let me know.
Thanks.
Huitang Li wrote:
Hi,
I created a web service client with Axis2. When I ran it, I got the
exception. This ex
Hi,
I created a web service client with Axis2. When I ran it, I got the
exception. This exception is thrown by the axis-genenated stub code.
org.apache.axis2.AxisFault: org.xml.sax.SAXParseException: The prefix
"ns1" for element "ns1:modifyUser" is not bound.
at
org.apache.axis2.util.Util
Hi,
I am trying to create an axis2 web service client to access a
ssl-enabled web service (https://..). I got the following error. I
think that the problem is caused by the server certificate on the web
service side.
Probably if I import that server certificate and root certificate into
32 matches
Mail list logo
