Memory Issues in Sample Server Code
I have been stress testing axis2c for performance (using the echo sample service), to determine if this platform is a good solution for my purposes. So far I have been attempting to debug each echo.exe invocation. Each time I execute the remote client invocation, the server process increments its used memory by 4 KB. When the service thread completes this memory is not deallocated. During the debug session I notice that: echo_invoke is the only DLL function called. The other echo_skeleton.c memory management functions are not called: echo_free axis2_remove_instance Can anyone suggest how I might configure axis2c to free memory for each echo service invocation (ie. per request)?
Re: Memory Issues in Sample Server Code
There is are memory issues with simple axis server. We got to fix that. In the mean time, could you please try the same tests with httpd module? I hope that would yield better results. Samisa... David Klassen wrote: I have been stress testing axis2c for performance (using the echo sample service), to determine if this platform is a good solution for my purposes. So far I have been attempting to debug each echo.exe invocation. Each time I execute the remote client invocation, the server process increments its used memory by 4 KB. When the service thread completes this memory is not deallocated. During the debug session I notice that: echo_invoke is the only DLL function called. The other echo_skeleton.c memory management functions are not called: echo_free axis2_remove_instance Can anyone suggest how I might configure axis2c to free memory for each echo service invocation (ie. per request)? -- Samisa Abeysinghe : WSO2 WSF/PHP http://wso2.org/projects/wsf/php?WSO2nbsp;Webnbsp;Servicesnbsp;Framework%2FPHPnbsp;-nbsp;Opennbsp;sourcenbsp;PHPnbsp;extentionnbsp;fornbsp;providingnbsp;andnbsp;consumingnbsp;Webnbsp;servicesnbsp;innbsp;PHP; - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unexpected subelement return exception
Can you send your wsdl and response?
On 10/9/07, George H [EMAIL PROTECTED] wrote:
I have created a webservice and client using the Axis2 eclipse
plugin tools v1.3.0. Using Eclipse (J2EE) Version: 3.3.0 Build id:
I20070621-1340.
Axis2 v1.3
I have a webservice with many methods. Some reaturn boolean some
return an custom
class serialized as an array of bytes. They all work, except for all the
methods
that have only 1 thing in common. They both return a Vector of that
custom class.
That vector is serialized into bytes and sent back like all the others,
but it
always fails with Unexpected subelement return error.
The wsdl file is generated by the tools and so are the stub classes.
Thanks in advance to anyone who can help me figure out the problem.
The code calling the service
---
VectorCustomClass customClasses = null;
try {
byte[] barray = serializeToBytes(myMessage);
ByteArrayDataSource byteDataSource = new
ByteArrayDataSource(barray);
DataHandler dh = new DataHandler(byteDataSource);
CoreServiceStub.GetCustomClasses getCustomClassesParam = new
CoreServiceStub.GetCustomClasses();
getCustomClassesParam.setCustomClass(dh);
CoreServiceStub stub = new CoreServiceStub(TARGET_ENDPOINT);
CoreServiceStub.GetCustomClassesResponse response =
stub.getCustomClasses(getCustomClassesParam);
DataHandler dh2 = response.get_return();
Object obj = deserializeFromBytes(dh2);
if(obj instanceof Vector) {
customClasses = (VectorCustomClass)obj;
}
}
catch(Exception ex) {
ex.printStackTrace();
}
The stack trace, identical each time it is run.
---
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
Unexpected subelement return
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at serv.core.ws.CoreServiceStub.fromOM(CoreServiceStub.java:10032)
at serv.core.ws.CoreServiceStub.getCustomClasses(
CoreServiceStub.java:675)
at
serv.core.client.CoreServiceClient.getCustomClasses.CoreServiceClient.java
:403)
at serv.core.client.CoreServiceClient.main(CoreServiceClient.java
:583)
Caused by: java.lang.Exception:
org.apache.axis2.databinding.ADBException: Unexpected subelement
return
at
serv.core.ws.CoreServiceStub$GetCustomClassesResponse$Factory.parse(
CoreServiceStub.java:7156)
at serv.core.ws.CoreServiceStub.fromOM(CoreServiceStub.java:9930)
... 3 more
Caused by: org.apache.axis2.databinding.ADBException: Unexpected
subelement return
at
serv.core.ws.CoreServiceStub$GetCustomClassesResponse$Factory.parse(
CoreServiceStub.java:7152)
... 4 more
--
George H
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Amila Suriarachchi,
WSO2 Inc.
How to access incoming SOAP Message from outgoing SOAP message
Hi, I have encountered a difficult situation. I have written a simple AXIS2 service that returns an image and another AXIS2 handler to resize the outgoing image. However, when I attach the resolution of the image to incoming SOAP message, I don't know how to access it from the outgoing SOAP message (i.e. using messageContext or any other thing). I suppose the original service does not need to understand, acknowledge about the resolution. The resize is done using the handler. Is there anyway to pass the information from the Incoming Message to the Outgoing Message without invoking the Service itself? Thank you so much. Harry -- View this message in context: http://www.nabble.com/How-to-access-incoming-SOAP-Message-from-outgoing-SOAP-message-tf4598836.html#a13130152 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: faultstringThe endpoint reference (EPR) for the Operation not found is http://122.22.2.22:9090/outboundws/services/Outbound and the WSA Action = /faultstring
how did you create these two services. here since you don't have the soapaction and the don't use the addressing the only way to find the operation is to using the body based dispatching. body based dispatching works only if all your operations has unique input element qnames. i.e if there are two operations with same input element then axis2 can not find the correct operation. Can you check for this? Amila. On 10/9/07, G71 [EMAIL PROTECTED] wrote: Hi, i've this problem with axis2: i've two services in the same wsdl but the response of one of this service is faultstringThe endpoint reference (EPR) for the Operation not found is http://172.31.4.49:9090/outboundws/services/Outbound and the WSA Action = /faultstring i've read the but i didn't found the solution: http://wso2.org/library/176 Why the response of one of this is correct and the second is not correct? The soap action is null in all this message I post the example: POST /outboundws/services/Outbound HTTP/1.0 Host: 172.31.4.49:9090 Content-Type: text/xml; charset=utf-8 Content-Length: 1432 SOAPAction: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsd=http://www.w3.org/1999/XMLSchema; soapenv:Body m:outboundService dataSetVersion=1.0 xmlns:m=http://www.fasfafdw.it/outboundService/outboundService; appuntamento bla bla bla/appuntamento /m:outboundService /soapenv:Body /soapenv:Envelope In this case the response is not correct: Instead in the call of this service is correct: POST /outboundws/services/Outbound HTTP/1.0 Host: 172.31.4.49:9090 Content-Type: text/xml; charset=utf-8 Content-Length: 654 SOAPAction: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsd=http://www.w3.org/1999/XMLSchema; soapenv:Body m:SMSService dataSetVersion=1.0 xmlns:m=xmlns:m=http://www.fasfafdw.it/outboundService/SMSService; message cell=+393358478769 textMessagetestomessagio./textMessage /message /m:SMSService /soapenv:Body /soapenv:Envelope -- View this message in context: http://www.nabble.com/faultstring%3EThe-endpoint-reference-%28EPR%29-for-the-Operation-not-found-is-http%3A--122.22.2.22%3A9090-outboundws-services-Outbound-and-the-WSA-Action-%3D-%3C-faultstring%3E-tf4592781.html#a13111387 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc.
Re: first post. question on complex types
what you want to do exactly?
do you have a web service an want to invoke it using a Axis2 client?
you don't have to populate the response. Axis 2 populates it and returns the
correct
response object.
Amila.
On 10/9/07, Vaduvoiu Tiberiu [EMAIL PROTECTED] wrote:
Hi to everyone. This is my first post and I have a small question about
retrieving a complex type from a client. Read the documentation on
axis(Building stubs, skeletons, and data types from WSDL)basic examples
worked out well, I'm a little stuck on one example ...there is a web service
that returns a complex type ...the response looks like
types:UserName id=id2 xsi:type=types:UserName
Name xsi:type=xsd:stringstring/Name
Last_name xsi:type=xsd:stringstring/Last_name
...
so from what I understood I need to use wsdl2java to generate a UserName
class that implements
java.io.Serializable. Ok I done that..created that class with getters and
setters. But how do I set the variables in that class with the results from
the invoke method?
I keep getting: No deserializer defined for array type {http}UserName
it's probably easy but I'm missing something here.
some pointers would be appreciate.
Cheers
Tibi
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail,
news, photos more.
http://mobile.yahoo.com/go?refer=1GNXIC
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Amila Suriarachchi,
WSO2 Inc.
Re: first post. question on complex types
If you have a web service that returns a simple string u simply write
string result = call.invoke(Object...)
but my web service returns a complex type...and I don't know how to save that
type...because I need a deserializer and I don't know how exactly to do that. I
understood that if the complex type is called let's say User then I have to do
a User class with setters and getters but I don't know how to store the result
from the invoke method.
- Original Message
From: Amila Suriarachchi [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Wednesday, October 10, 2007 9:29:35 AM
Subject: Re: first post. question on complex types
what you want to do exactly?
do you have a web service an want to invoke it using a Axis2 client?
you don't have to populate the response. Axis 2 populates it and returns the
correct
response object.
Amila.
On 10/9/07, Vaduvoiu Tiberiu [EMAIL PROTECTED] wrote:
Hi to everyone. This is my first post and I have a small question about
retrieving a complex type from a client. Read the documentation on
axis(Building stubs, skeletons, and data types from WSDL)basic examples
worked out well, I'm a little stuck on one example ...there is a web service
that returns a complex type ...the response looks like
types:UserName id=id2 xsi:type=types:UserName
Name xsi:type=xsd:stringstring/Name
Last_name xsi:type=xsd:stringstring/Last_name
...
so from what I understood I need to use wsdl2java to generate a UserName class
that implements
java.io.Serializable. Ok I done that..created that class with getters and
setters. But how do I set the variables in that class with the results from the
invoke method?
I keep getting: No deserializer defined for array type {http}UserName
it's probably easy but I'm missing something here.
some pointers would be appreciate.
Cheers
Tibi
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news,
photos more.
http://mobile.yahoo.com/go?refer=1GNXIC
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Amila Suriarachchi,
WSO2 Inc.
Need a vacation? Get great deals
to amazing places on Yahoo! Travel.
http://travel.yahoo.com/
Re: simplest example pls help
try replacing
call.setOperationName(new QName(http://tempuri.org;;,
CelsiusToFahrenheit));
with
call.setOperationName(new QName(endpoint, CelsiusToFahrenheit));
(ie) pass the endpoint as a parameter to QName class
regards,
Vinayak
On 10/8/07, Upul Godage [EMAIL PROTECTED] wrote:
Hi,
Add this line and try.
call.setTargetEndpointAddress( new java.net.URL(endpoint) );
call.setOperationName(new QName( http://tempuri.org;;,
CelsiusToFahrenheit));
call.setSOAPActionURI(http://tempuri.org/CelsiusToFahrenheit );
Also checkout Axis2 if you are starting out.
http://ws.apache.org/axis2/
Upul
On 10/8/07, loredana loredana [EMAIL PROTECTED] wrote:
I am strugling for a couple of days now to do the most simplest web
service client using a web service on w3schools as test.
http://www.w3schools..com/webservices/tempconvert.asmx
This is the web service. has 2 possible operations with one parameter.
Can't get any simpler than this. Yet, I can't make a client for it. I
already wrote about this problems couple of days ago, but I got nowhere. so
this is what I tried:
try{
String endpoint =
http://www.w3schools.com/webservices/tempconvert.asmx;;;
Service service = new Service();
Call call= (Call) service.createCall();
call.setTargetEndpointAddress( new java.net.URL(endpoint) );
call.setOperationName(new QName(http://tempuri.org ;,
CelsiusToFahrenheit));
String ret = (String) call.invoke( new Object[] { 10 } );
System.out.println(result: + ret + ');}
catch{}
this should work but I keep getting
Server did not recognize the value of HTTP Header SOAPAction: .
can any of you give this a try?? for someone with experience in axis
this shouldn't take more than 5 min to try. I have a eclipse plugin that
generates a web service client based on the wsdl but I don't want to
cheat! I want to do it myself but i'm stuck. any help would be appreciated
it!!
Tonight's top picks. What will you watch tonight? Preview the hottest
shows on Yahoo! TV.
http://tv.yahoo.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Vinayak
http://tinyurl.com/22ph2e
Re: Axis2 v1.3 client sending unwanted soapenv:mustUnderstand=0 attribute in the SOAP Header
to which headers you get this. you can disable addressing headers mustunderstand like this clientOptions.setProperty( AddressingConstants.ADD_MUST_UNDERSTAND_TO_ADDRESSING_HEADERS, Constants.VALUE_FALSE); but default is not to send. Amila. On 10/9/07, djhess post [EMAIL PROTECTED] wrote: I am trying to use a SOAP service I don't control. The service does not like the SOAP Header attribute: soapenv:mustUnderstand=0 My client input data does not contain the mustUnderstand attribute, Axis2 is adding it! (see debug excerpt below) How can I make the unwanted mustUnderstand=0 attribute in the SOAP Header go away? I generated Axis2 client databindings using wsdl2java.sh and the -d option wsdl2java.sh -uri simple.wsdl -p ... -s -d none I wrote an Axis2 client ;-) I set options: stub._getServiceClient().getOptions().setSoapVersionURI( Constants.URI_SOAP11_ENV); stub._getServiceClient().getOptions().setProperty( HTTPConstants.CHUNKED, false); stub._getServiceClient().getOptions().setProperty( AddressingConstants.DISABLE_ADDRESSING_FOR_OUT_MESSAGES, true); The Axis2 client code generates and sends a beautiful SOAP request: [DEBUG] POST /SOAP HTTP/1.1[\r][\n] [DEBUG] Content-Type: text/xml; charset=UTF-8[\r][\n] [DEBUG] SOAPAction: Sync[\r][\n] [DEBUG] User-Agent: Axis2[\r][\n] [DEBUG] Host: somewhere.com:7443[\r][\n] [DEBUG] Content-Length: 2734[\r][\n] [DEBUG] [\r][\n] [DEBUG] ?xml version=' 1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ soapenv:Headerns:HdrElement xmlns:ns=... soapenv:mustUnderstand=0 ... The SOAP response has: [DEBUG] faultcodeSOAP-ENV:Client/faultcode [DEBUG] faultstringRequest not conforming to schema/faultstring [DEBUG] description error parsing apos;XML documentapos;:: Error at line 1: /soapenv:Envelope/soapenv:Header/ns:HdrElement: undeclared attribute: quot;mustUnderstandquot;: /soapenv:Envelope/soapenv:Header/ns:HdrElement: undeclared attribute: quot;mustUnderstandquot;#10; /description dana j hess -- Amila Suriarachchi, WSO2 Inc.
Re: No service is available at this URL--Calculator.jws
Did you reload the container, before trying to access the service??
On 10/9/07, H.Z [EMAIL PROTECTED] wrote:
I forgot the code.
The code is
public
class Calculator {
public int add(int i1, int i2) {
return i1 + i2; }
public int subtract(int i1, int i2) {
return i1 - i2; }
}
*H.Z [EMAIL PROTECTED]* wrote:
Hello,
I copy Calculator.java to my webapp directory, and rename it
Calculator.jws.
Then
http://localhost:8080/axis/Calculator.jws
I get No service is available at this URL.
However I tried another example EchoHeaders.jws that is included in the
installation package. It does work.
Why?
Thanks
--
Boardwalk for $500? In 2007? Ha!
Play Monopoly Here and
Nowhttp://us.rd.yahoo.com/evt=48223/*http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow(it's
updated for today's economy) at Yahoo! Games.
--
Catch up on fall's hot new
showshttp://us.rd.yahoo.com/tv/mail/tagline/falltv/evt=47093/*http://tv.yahoo.com/collections/3658+%0Aon
Yahoo! TV. Watch previews, get listings, and more!
--
Vinayak
http://tinyurl.com/22ph2e
Sending attachments to .NET Client
Hi all, We have a java web service which has to send an image file as attachment to a .NET compact framework client. I followed the tutorials available in the internet. All the code available in the internet returns the attachment to the client as OMElement. But since .NET compact framework does not support OMElement, we need some other way for sending the attachments. Is it possible to send the attachment as java object? If so how? Any help would be appreciated. Thanks in Advance, Raghavan.V. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Read Time out Error when calling webservice from a proxy
Hi, I am getting Read Time out Error when I try to invoke my target webservice from behind a proxy. I have configured the proxy setting in my client. The settings are as follows: EndpointReference targetEPR = new EndpointReference(http://10.236.28.196:8080/axis2/services/WeatherServi ce); /*options.setTimeOutInMilliSeconds(6); options.setTo(targetEPR);*/ /* New Bit */ Options opt = new Options(); //Options opt = serviceClient.getOptions(); ProxyProperties proxyProperties = new ProxyProperties(); proxyProperties.setProxyName(localhost); proxyProperties.setProxyPort(8090); options.setProperty(HTTPConstants.PROXY, proxyProperties); //opt.setTimeOutInMilliSeconds(12); options.setTo(targetEPR); serviceClient.getOptions().setProperty(HTTPConstants.PROXY, proxyProperties); //options.setTo(targetEPR); serviceClient.setOptions(options); But whenever I run the client, the following is the error I get [java] org.apache.axis2.AxisFault: Read timed out [java] Caused by: org.apache.axis2.AxisFault: Read timed out [java] Caused by: java.net.SocketTimeoutException: Read timed out Can somebody plz help me ?? Thanks, -Subhash- This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful.
RE: Database connection
Hi really thanx for responses. Yes it is possible for this service, that
more users can connect this service at the same time, although there should
not be so big traffic. I must think about it yet how should I implement it.
Thank s and regards Vladi
_
From: Rajith Attapattu [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 10, 2007 1:26 AM
To: axis-user@ws.apache.org
Subject: Re: Database connection
Since only one instance of the Service is used to serve all requests, your
code needs to be able to handle concurrency.
As anthony mentioned you may need to either use a connection pool or
synchronize access to the getConnection method.
Apart from the connection method, if there is any shared state that is
modified as part of a request you may need to ensure it is done a in thread
safe way.
I would say that it depends on how frequently your service is accessed.
If it's accessed once in a while then a synchronized getConnection method
might be cheaper than a thread pool.
Downfall is that concurrent requests are handled serially as they will block
on getConnection.
If it's accessed more often then offloading the burden of maintaining
connections to a connection pool might be a good idea.
Regards,
Rajith Attapattu
Red Hat.
On 10/9/07, Anthony Bull [EMAIL PROTECTED] wrote:
If this is a service that more than one user can access I'd recommend
you use commons connection pooling to handle your connections. That way
you just ask for a connection when you need one, and the commons library
handles the creation. Its not going to work very well if multiple
requests are being serviced using a single JDBC connection - and I'm not
even sure if it is threadsafe to do so.
Rajith Attapattu wrote:
If you deploy this service in Application Scope, then there will be
one and only one instance of this service throught out the life time
of the application.
This way you only create your database connection once.
Is it enough to create this service with application scope?
So the answer is yes.
Rajith Attapattu
Red Hat.
On 10/9/07, *VF* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Hi all,
I would like to ask u, how can i utilize database connection in my
web
service. I have one web service with more methods in it. Id like
to create
database connection just once and not with each call (each
operation works
with the same database connection) Is it enough to create this
service with
application scope?
It looks like this:
Available services
stkdds
Service Description : stkdds
Service Status : Active
Available Operations
* getFinishedOrderBin
* getOrderInfo
* updateOrder
* getUserInfo
* cancelOrder
* updateUser
* testOperation
* getOrdersOverview
* getAllAccountsInfo
* getFinishedOrder
* getAccountInfo
* newOrder
And my code for database connection smth like this:
public Connection setConnection() throws Exception {
if(conn != null){
return conn;
}
Class.forName (org.firebirdsql.jdbc.FBDriver);
conn = DriverManager.getConnection (p_connect_string,
sqlProps);
return conn;
Thanks Vladi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
--
Anthony
-
Anthony Bull
Senior Developer
Black Coffee Software Ltd
PO Box 10-192 The Terrace
Wellington, New Zealand
[EMAIL PROTECTED]
Ph +64 4 472 8818
Fax +64 4 472 8811
-
www.bcsoft.co.nz
---
This email may contain confidential or privileged information,
and is intended for use only by the addressee, or addressees.
If you are not the intended recipient please advise the sender
immediately and do not copy, use or disclose the contents to
any other person or organisation.
Black Coffee Software Ltd accepts no responsibility for viruses
received with this email, or to any changes made to the original
content. Any views or opinions expressed in this email may be
personal to the sender and are not necessarily those of Black
Coffee Software Ltd.
---
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Read Time out Error when calling webservice from a proxy
Hi, Have you checked whether the proxy server is running in your machine (localhost) at 8090? I think you should be able to put those values in a browser proxy settings page and access something with the browser. Upul On 10/10/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I am getting Read Time out Error when I try to invoke my target webservice from behind a proxy. I have configured the proxy setting in my client. The settings are as follows: EndpointReference targetEPR = *new* EndpointReference( http://10.236.28.196:8080/axis2/services/WeatherService;); /*options.setTimeOutInMilliSeconds(6); options.setTo(targetEPR);*/ /* New Bit */ Options opt = *new* Options(); //Options opt = serviceClient.getOptions(); ProxyProperties proxyProperties = *new* ProxyProperties(); proxyProperties.setProxyName(localhost); proxyProperties.setProxyPort(8090); options.setProperty(HTTPConstants.PROXY, proxyProperties); //opt.setTimeOutInMilliSeconds(12); options.setTo(targetEPR); serviceClient.getOptions().setProperty(HTTPConstants.PROXY, proxyProperties); //options.setTo(targetEPR); serviceClient.setOptions(options); But whenever I run the client, the following is the error I get [java] org.apache.axis2.AxisFault: Read timed out [java] Caused by: org.apache.axis2.AxisFault: Read timed out [java] Caused by: java.net.SocketTimeoutException: Read timed out Can somebody plz help me ?? Thanks, -Subhash- This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful.
AW: [Axis2] How to remove namespaces from SOAP response in Axis2
add the following entry to the services.xml: schema elementFormDefaultQualified=false/ Von: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 10. Oktober 2007 07:54 An: axis-user@ws.apache.org Betreff: RE: [Axis2] How to remove namespaces from SOAP response in Axis2 Thanks Alick. I haven't tried this option. I'll try and see. Thanks Raghu From: Alick Buckley [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 09, 2007 5:03 PM To: axis-user@ws.apache.org Subject: RE: [Axis2] How to remove namespaces from SOAP response in Axis2 Did you try the suppress-prefixes option in WSDL2Java? http://svn.apache.org/viewvc?view=revrevision=480336 http://svn.apache.org/viewvc?view=revrevision=480336 Fix for AXIS2-1784 - [ADB] Suppress prefixes in the soap request/response for performance https://issues.apache.org/jira/browse/AXIS2-1784 https://issues.apache.org/jira/browse/AXIS2-1784 added an option -sp to suppress namespace prefixes in WSDL2Java/SchemaCompiler. === -Original Message- From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Wednesday, 10 October 2007 9:54 AM To: axis-user@ws.apache.org Subject: [Axis2] How to remove namespaces from SOAP response in Axis2 Hi, Does anyone know how to remove namespaces from SOAP response in Axis2? Here is an example of what I wanted. Original SOAP Envelope soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns1:loginResponse xmlns:ns1=urn:ws.rsys.com ns1:loginReturn-31853ad2:1157fefd8cf:5b3c/ns1:loginReturn /ns1:loginResponse /soapenv:Body /soapenv:Envelope SOAP Envelope After removing namespaces soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns=urn:ws.rsys.com soapenv:Body loginResponse loginReturn-31853ad2:1157fefd8cf:5b3c/loginReturn /loginResponse /soapenv:Body /soapenv:Envelope Thanks in advance Raghu
RE: Sending attachments to .NET Client
Raghvan, To solve the problem of sending attachments between .NET and Java, you can choose MTOM attachments. In that way your server code (Java) will deal with DataHanlder object while your client code (.NET) will deal with byte array. I have done that and it's working fine. Regards, Ashish Arya, Sungard Offshore Services (India) -Original Message- From: Raghavan [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 10, 2007 12:50 PM To: axis-user@ws.apache.org Subject: Sending attachments to .NET Client Importance: High Hi all, We have a java web service which has to send an image file as attachment to a .NET compact framework client. I followed the tutorials available in the internet. All the code available in the internet returns the attachment to the client as OMElement. But since .NET compact framework does not support OMElement, we need some other way for sending the attachments. Is it possible to send the attachment as java object? If so how? Any help would be appreciated. Thanks in Advance, Raghavan.V. - 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: Unexpected subelement return exception
Thank you for your response. Below is my WSDL file (I cut out the parts not dealing with my 2 problematic methods. Below that is the SOAP response. I think that is what you wanted? I set the log4j properties to DEBUG on the client side and dumped the output. Thank you. WSDL - ?xml version=1.0 encoding=UTF-8? wsdl:definitions xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:axis2=http://ws.core.serv; xmlns:ns1=http://org.apache.axis2/xsd; xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; xmlns:ns0=http://ws.core.serv/xsd; xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; targetNamespace=http://ws.core.serv; wsdl:types xs:schema xmlns:xsd=http://ws.core.tipsws/xsd; attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://ws.core.serv/xsd; xs:element name=getCustomClasses xs:complexType xs:sequence xs:element minOccurs=0 name=GenericStructMessage nillable=true type=xs:base64Binary/ /xs:sequence /xs:complexType /xs:element xs:element name=getCustomClassesResponse xs:complexType xs:sequence xs:element minOccurs=0 name=return nillable=true type=xs:base64Binary/ /xs:sequence /xs:complexType /xs:element xs:element name=getOtherCustomClasses xs:complexType xs:sequence xs:element minOccurs=0 name=GenericStruct nillable=true type=xs:base64Binary/ /xs:sequence /xs:complexType /xs:element xs:element name=getOtherCustomClassesResponse xs:complexType xs:sequence xs:element minOccurs=0 name=return nillable=true type=xs:base64Binary/ /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types wsdl:message name=getOtherCustomClassesRequest wsdl:part name=parameters element=ns0:getOtherCustomClasses/ /wsdl:message wsdl:message name=getOtherCustomClassesResponse wsdl:part name=parameters element=ns0:getOtherCustomClassesResponse/ /wsdl:message wsdl:message name=getCustomClassesRequest wsdl:part name=parameters element=ns0:getCustomClasses/ /wsdl:message wsdl:message name=getCustomClassesResponse wsdl:part name=parameters element=ns0:getCustomClassesResponse/ /wsdl:message wsdl:portType name=CoreServicePortType wsdl:operation name=getOtherCustomClasses wsdl:input message=axis2:getOtherCustomClassesRequest wsaw:Action=urn:getOtherCustomClasses/ wsdl:output message=axis2:getOtherCustomClassesResponse wsaw:Action=urn:getOtherCustomClassesResponse/ /wsdl:operation wsdl:operation name=getCustomClasses wsdl:input message=axis2:getCustomClassesRequest wsaw:Action=urn:getCustomClasses/ wsdl:output message=axis2:getCustomClassesResponse wsaw:Action=urn:getCustomClassesResponse/ /wsdl:operation /wsdl:portType wsdl:binding name=CoreServiceSOAP11Binding type=axis2:CoreServicePortType soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=getOtherCustomClasses soap:operation soapAction=urn:getOtherCustomClasses style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation wsdl:operation name=getCustomClasses soap:operation soapAction=urn:getCustomClasses style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:binding name=CoreServiceSOAP12Binding type=axis2:CoreServicePortType soap12:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=getOtherCustomClasses soap12:operation soapAction=urn:getOtherCustomClasses style=document/ wsdl:input soap12:body use=literal/ /wsdl:input wsdl:output soap12:body use=literal/ /wsdl:output /wsdl:operation wsdl:operation name=getCustomClasses soap12:operation soapAction=urn:getCustomClasses style=document/ wsdl:input soap12:body use=literal/ /wsdl:input wsdl:output
Re: faultstringThe endpoint reference (EPR) for the Operation not found is http://122.22.2.22:9090/outboundws/services/Outbound and the WSA Action = /faultstring
Ok... Thank you... The 'core' problem is: when i set xmlns: soapenv:Body m:outboundService xmlns:m=http://www.pippo.it/blabla/; or in the other service soapenv:Body m:SMSService xmlns:m=http://www.pippo.it/blabla/; i've the same 'OK' result... Why? Why receive i a result of failure only for outbound in the case of setting in xmlns:m=http://www.paperino.it/lalala/; for the services? I tryed to modify the wsdl... but i don't receive the right response. Is wsdl check from the engine...or what??? Who check the xmlns and how is it check?... thank you... Amila Suriarachchi wrote: how did you create these two services. here since you don't have the soapaction and the don't use the addressing the only way to find the operation is to using the body based dispatching. body based dispatching works only if all your operations has unique input element qnames. i.e if there are two operations with same input element then axis2 can not find the correct operation. Can you check for this? Amila. On 10/9/07, G71 [EMAIL PROTECTED] wrote: Hi, i've this problem with axis2: i've two services in the same wsdl but the response of one of this service is faultstringThe endpoint reference (EPR) for the Operation not found is http://172.31.4.49:9090/outboundws/services/Outbound and the WSA Action = /faultstring i've read the but i didn't found the solution: http://wso2.org/library/176 Why the response of one of this is correct and the second is not correct? The soap action is null in all this message I post the example: POST /outboundws/services/Outbound HTTP/1.0 Host: 172.31.4.49:9090 Content-Type: text/xml; charset=utf-8 Content-Length: 1432 SOAPAction: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsd=http://www.w3.org/1999/XMLSchema; soapenv:Body m:outboundService dataSetVersion=1.0 xmlns:m=http://www.fasfafdw.it/outboundService/outboundService; appuntamento bla bla bla/appuntamento /m:outboundService /soapenv:Body /soapenv:Envelope In this case the response is not correct: Instead in the call of this service is correct: POST /outboundws/services/Outbound HTTP/1.0 Host: 172.31.4.49:9090 Content-Type: text/xml; charset=utf-8 Content-Length: 654 SOAPAction: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsd=http://www.w3.org/1999/XMLSchema; soapenv:Body m:SMSService dataSetVersion=1.0 xmlns:m=xmlns:m=http://www.fasfafdw.it/outboundService/SMSService; message cell=+393358478769 textMessagetestomessagio./textMessage /message /m:SMSService /soapenv:Body /soapenv:Envelope -- View this message in context: http://www.nabble.com/faultstring%3EThe-endpoint-reference-%28EPR%29-for-the-Operation-not-found-is-http%3A--122.22.2.22%3A9090-outboundws-services-Outbound-and-the-WSA-Action-%3D-%3C-faultstring%3E-tf4592781.html#a13111387 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc. -- View this message in context: http://www.nabble.com/faultstring%3EThe-endpoint-reference-%28EPR%29-for-the-Operation-not-found-is-http%3A--122.22.2.22%3A9090-outboundws-services-Outbound-and-the-WSA-Action-%3D-%3C-faultstring%3E-tf4592781.html#a13132036 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Address already in use: connect
Hi!
I have written a simple blocking client using Axis2 1.3 API's.
When I do like this:
for(int i = 0; i 100; i++) {
...
ServiceClient sender = new ServiceClient();
sender.sendReceive(payload);
...
}
there is no problem. The client runs for many hours.
When I do like this:
ServiceClient sender = new ServiceClient();
for(int i = 0; i 100; i++) {
...
sender.sendReceive(payload);
sender.cleanup();
sender.cleanupTransport();
}
I get exception AxisFault: Address already in use: connect
after a couple of thousand calls.
It seems to be something wrong in the ServiceClient class which shows up after
a while.
Any ideas?
/Pär Malmqvist
_
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+worldmkt=en-USform=QBRE
RE: Peculiar Issue while testing a service
Hi, Any ideas on this? Cheers Natraj -Original Message- From: Gudla, Natraj (GE Money, consultant) Sent: 09 October 2007 10:01 To: 'axis-user@ws.apache.org' Subject: Peculiar Issue while testing a service Hi, I am reporting a peculiar issue which i am facing since yesterday working with AXIS2 1.2. Addition of an extra simple element to an existing complex type of an xsd throws an Un Expected Element error. Following is the brief. The current set up : Working Fine. The complext type part of my xsd xsd:complexType name=GEM_Ln_LoanRequestDetails xsd:sequence xsd:element name=LoanPreference type=GEM_Ln_LoanPreference/ xsd:element name=CustomerDetails type=GEM_Ln_CustomerDetails/ xsd:element name=CustomerAddr type=GEM_Ln_CustomerAddr/ xsd:element name=EmployerDetails type=GEM_Ln_EmployerDetails/ xsd:element name=CustomerFinances type=GEM_Ln_CustomerFinances/ xsd:element name=CardDetails type=GEM_Ln_CardDetails minOccurs=0/ xsd:element name=LoanDetails type=GEM_Ln_LoanDetails minOccurs=0/ /xsd:sequence /xsd:complexType I used a wsdl, generated binding ( ADB ) classes using WSDL to Java tool on Axis2 1.2. Using the build.xml, running the jar.server task i created the services.aar and deployed on tomcat. Created a sample java class, which reads a sample loan request xml ( formed using IDE based on the xsd ) and submits a request to the service. Every thing works fine, i get the response as i coded within the skeleton method. This looks fine end to end. Change to the existing schema: : Not Working xsd:complexType name=GEM_Ln_LoanRequestDetails xsd:sequence xsd:element name=ProductId type=xsd:string/ xsd:element name=LoanPreference type=GEM_Ln_LoanPreference/ xsd:element name=CustomerDetails type=GEM_Ln_CustomerDetails/ xsd:element name=CustomerAddr type=GEM_Ln_CustomerAddr/ xsd:element name=EmployerDetails type=GEM_Ln_EmployerDetails/ xsd:element name=CustomerFinances type=GEM_Ln_CustomerFinances/ xsd:element name=CardDetails type=GEM_Ln_CardDetails minOccurs=0/ xsd:element name=LoanDetails type=GEM_Ln_LoanDetails minOccurs=0/ /xsd:sequence /xsd:complexType I have a need to add new field to hold a product id. after this, i generated the binding classes again ( to make sure, i deleted all the existing classes, and re generated every thing ). Then did the same procedure as above to generated the services.aar, then created the sample java class callling the stub. Changed the sample xml file to add a product id tag and then executed the program. This time un expectedley i get the Un expected sub element Product Id error repeatedly. Not sure what is the problem, this looks to be simple. I tried various combinations adding a test tag, then making product id a simple type etc etc. Any idea why this occurs. I made sure, i replaced the correct services.aar on the server. The new resource folder generated second time, properly refers to the product id which was included. Just as a work around, i tested with some sample test and test simple tags, observed the xml input on TCP Monitor. For your reference attached is the request and response xmls from the monitory. Observe for the test and testsimple tags. The actual loan request xml read by my program is also attached for reference. File: Response.txtFile: Request.txtFile: LnRq.xml Cheers -Natraj. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Aixs2]: generating services.xml with wsdl2java
Hi Wsdl2Java can be used to generate services.xml - but it also generates java files (skeleton code for the webservice), and the services.xml file references the generated java classes. What if I already have a complete java file (containing all the necessary code for my webservice), and I already have an associated wsdl. How do I generate the appropriate services.xml for deployment in Axis2? Is there no other way than writing services.xml by hand? Thanks, Peter
Signing a message
Greetings, We have got the wsdl file and created Stub using WSDL2Java. We need to sign the message using our certificate. I find the following code EngineConfiguration config = new FileProvider(client_deploy.wsdd); Service service = new Service(); stub.setProperty(WSHandlerConstants.ACTION, WSHandlerConstants.SIGNATURE); stub.setProperty(WSHandlerConstants.SIG_PROP_FILE, client_crypto.properties); stub.setProperty(WSHandlerConstants.USER, ceriticate alias name to be given); Please guide us how to do. TIA, -senthil
Re: Unexpected subelement return exception
I need the response soap envelop. you can use [1] to capture the request and the response. basically check whether your reponse is match to your schema. [1] http://ws.apache.org/commons/tcpmon/ Amila. On 10/10/07, George H [EMAIL PROTECTED] wrote: Thank you for your response. Below is my WSDL file (I cut out the parts not dealing with my 2 problematic methods. Below that is the SOAP response. I think that is what you wanted? I set the log4j properties to DEBUG on the client side and dumped the output. Thank you. WSDL - ?xml version=1.0 encoding=UTF-8? wsdl:definitions xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:axis2=http://ws.core.serv; xmlns:ns1=http://org.apache.axis2/xsd; xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; xmlns:ns0=http://ws.core.serv/xsd; xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; targetNamespace=http://ws.core.serv; wsdl:types xs:schema xmlns:xsd=http://ws.core.tipsws/xsd; attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://ws.core.serv/xsd; xs:element name=getCustomClasses xs:complexType xs:sequence xs:element minOccurs=0 name=GenericStructMessage nillable=true type=xs:base64Binary/ /xs:sequence /xs:complexType /xs:element xs:element name=getCustomClassesResponse xs:complexType xs:sequence xs:element minOccurs=0 name=return nillable=true type=xs:base64Binary/ /xs:sequence /xs:complexType /xs:element xs:element name=getOtherCustomClasses xs:complexType xs:sequence xs:element minOccurs=0 name=GenericStruct nillable=true type=xs:base64Binary/ /xs:sequence /xs:complexType /xs:element xs:element name=getOtherCustomClassesResponse xs:complexType xs:sequence xs:element minOccurs=0 name=return nillable=true type=xs:base64Binary/ /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types wsdl:message name=getOtherCustomClassesRequest wsdl:part name=parameters element=ns0:getOtherCustomClasses/ /wsdl:message wsdl:message name=getOtherCustomClassesResponse wsdl:part name=parameters element=ns0:getOtherCustomClassesResponse/ /wsdl:message wsdl:message name=getCustomClassesRequest wsdl:part name=parameters element=ns0:getCustomClasses/ /wsdl:message wsdl:message name=getCustomClassesResponse wsdl:part name=parameters element=ns0:getCustomClassesResponse/ /wsdl:message wsdl:portType name=CoreServicePortType wsdl:operation name=getOtherCustomClasses wsdl:input message=axis2:getOtherCustomClassesRequest wsaw:Action=urn:getOtherCustomClasses/ wsdl:output message=axis2:getOtherCustomClassesResponse wsaw:Action=urn:getOtherCustomClassesResponse/ /wsdl:operation wsdl:operation name=getCustomClasses wsdl:input message=axis2:getCustomClassesRequest wsaw:Action=urn:getCustomClasses/ wsdl:output message=axis2:getCustomClassesResponse wsaw:Action=urn:getCustomClassesResponse/ /wsdl:operation /wsdl:portType wsdl:binding name=CoreServiceSOAP11Binding type=axis2:CoreServicePortType soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=getOtherCustomClasses soap:operation soapAction=urn:getOtherCustomClasses style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation wsdl:operation name=getCustomClasses soap:operation soapAction=urn:getCustomClasses style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:binding name=CoreServiceSOAP12Binding type=axis2:CoreServicePortType soap12:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=getOtherCustomClasses soap12:operation soapAction=urn:getOtherCustomClasses style=document/ wsdl:input soap12:body use=literal/
Problem with Rampart
Hi. I try to use rampart. I folow the instructions in the doc (modify service.xml, engage module in axis2.xml and put the module file rampart-1.3in /axis2/modules directory). When I deploy the aar file axis throws the exception Error: org.apache.axis2.deployment.DeploymentException: The rampart module is not valid or has not been deployed. I must deploy the module? Docs don´t says anything.
Re: Peculiar Issue while testing a service
On 10/10/07, Gudla, Natraj (GE Money, consultant) [EMAIL PROTECTED] wrote: Hi, Any ideas on this? how do you generate this request? some problem there. Cheers Natraj -Original Message- From: Gudla, Natraj (GE Money, consultant) Sent: 09 October 2007 10:01 To: 'axis-user@ws.apache.org' Subject: Peculiar Issue while testing a service Hi, I am reporting a peculiar issue which i am facing since yesterday working with AXIS2 1.2. Addition of an extra simple element to an existing complex type of an xsd throws an Un Expected Element error. Following is the brief. The current set up : Working Fine. The complext type part of my xsd xsd:complexType name=GEM_Ln_LoanRequestDetails xsd:sequence xsd:element name=LoanPreference type=GEM_Ln_LoanPreference/ xsd:element name=CustomerDetails type=GEM_Ln_CustomerDetails/ xsd:element name=CustomerAddr type=GEM_Ln_CustomerAddr/ xsd:element name=EmployerDetails type=GEM_Ln_EmployerDetails/ xsd:element name=CustomerFinances type=GEM_Ln_CustomerFinances/ xsd:element name=CardDetails type=GEM_Ln_CardDetails minOccurs=0/ xsd:element name=LoanDetails type=GEM_Ln_LoanDetails minOccurs=0/ /xsd:sequence /xsd:complexType I used a wsdl, generated binding ( ADB ) classes using WSDL to Java tool on Axis2 1.2. Using the build.xml, running the jar.server task i created the services.aar and deployed on tomcat. Created a sample java class, which reads a sample loan request xml ( formed using IDE based on the xsd ) and submits a request to the service. Every thing works fine, i get the response as i coded within the skeleton method. This looks fine end to end. Change to the existing schema: : Not Working xsd:complexType name=GEM_Ln_LoanRequestDetails xsd:sequence xsd:element name=ProductId type=xsd:string/ xsd:element name=LoanPreference type=GEM_Ln_LoanPreference/ xsd:element name=CustomerDetails type=GEM_Ln_CustomerDetails/ xsd:element name=CustomerAddr type=GEM_Ln_CustomerAddr/ xsd:element name=EmployerDetails type=GEM_Ln_EmployerDetails/ xsd:element name=CustomerFinances type=GEM_Ln_CustomerFinances/ xsd:element name=CardDetails type=GEM_Ln_CardDetails minOccurs=0/ xsd:element name=LoanDetails type=GEM_Ln_LoanDetails minOccurs=0/ /xsd:sequence /xsd:complexType I have a need to add new field to hold a product id. after this, i generated the binding classes again ( to make sure, i deleted all the existing classes, and re generated every thing ). Then did the same procedure as above to generated the services.aar, then created the sample java class callling the stub. Changed the sample xml file to add a product id tag and then executed the program. This time un expectedley i get the Un expected sub element Product Id error repeatedly. Not sure what is the problem, this looks to be simple. I tried various combinations adding a test tag, then making product id a simple type etc etc. Any idea why this occurs. I made sure, i replaced the correct services.aar on the server. The new resource folder generated second time, properly refers to the product id which was included. Just as a work around, i tested with some sample test and test simple tags, observed the xml input on TCP Monitor. For your reference attached is the request and response xmls from the monitory. Observe for the test and testsimple tags. The actual loan request xml read by my program is also attached for reference. File: Response.txtFile: Request.txtFile: LnRq.xml Cheers -Natraj. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc.
Re: Read Time out Error when calling webservice from a proxy
web service is running on the proxy? or your SOAP petition pass through a proxy? Try to send soap message to your service from soapUI (www.soapui.org). soapui alow proxy configuration. 2007/10/10, Upul Godage [EMAIL PROTECTED]: Hi, Have you checked whether the proxy server is running in your machine (localhost) at 8090? I think you should be able to put those values in a browser proxy settings page and access something with the browser. Upul On 10/10/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I am getting Read Time out Error when I try to invoke my target webservice from behind a proxy. I have configured the proxy setting in my client. The settings are as follows: EndpointReference targetEPR = *new* EndpointReference(http://10.236.28.196:8080/axis2/services/WeatherService ); /*options.setTimeOutInMilliSeconds(6); options.setTo(targetEPR);*/ /* New Bit */ Options opt = * new* Options(); //Options opt = serviceClient.getOptions(); ProxyProperties proxyProperties = *new* ProxyProperties(); proxyProperties.setProxyName(localhost ); proxyProperties.setProxyPort(8090); options.setProperty(HTTPConstants.PROXY, proxyProperties); //opt.setTimeOutInMilliSeconds(12); options.setTo(targetEPR); serviceClient.getOptions().setProperty(HTTPConstants.PROXY, proxyProperties); //options.setTo(targetEPR); serviceClient.setOptions(options); But whenever I run the client, the following is the error I get [java] org.apache.axis2.AxisFault: Read timed out [java] Caused by: org.apache.axis2.AxisFault: Read timed out [java] Caused by: java.net.SocketTimeoutException: Read timed out Can somebody plz help me ?? Thanks, -Subhash- This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful.
RE: [Aixs2]: generating services.xml with wsdl2java
Peter, If you remove the 'serverside' and 'serverSideInterface' attribute from wsdl2Java target (in Ant), it will not generate the skeleton and interface for you. And since you don't have the complete information for generating services.xml, the same is also not generated by the tool. Thus I don't think there is any way to generate services.xml without generating server side components. If any one has any alternate approach, that would be helpful. Regards, Ashish Arya, From: Peter A. Kirk [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 10, 2007 3:02 PM To: axis-user@ws.apache.org Subject: [Aixs2]: generating services.xml with wsdl2java Hi Wsdl2Java can be used to generate services.xml - but it also generates java files (skeleton code for the webservice), and the services.xml file references the generated java classes. What if I already have a complete java file (containing all the necessary code for my webservice), and I already have an associated wsdl. How do I generate the appropriate services.xml for deployment in Axis2? Is there no other way than writing services.xml by hand? Thanks, Peter
Re: Peculiar Issue while testing a service
Do you modify the xsd in the correct place? Perhaps you are modifying the xsd and on deploy time the xsd used is other. 2007/10/10, Gudla, Natraj (GE Money, consultant) [EMAIL PROTECTED]: First i generate a sample xml file using the Eclipse IDE, using the xsd, then use the parse method of axis generated wrapper class for my request, passing it the XMLStreamReader created from the sample xml. This worked fine end to end earlier. Sample class, calling stub passing the request object, server responding properly with expected response. Only after i include a simple type element into one of the existing complex types within the xsd, it fails saying unexpected element. Just another peice of information, when i place this new simple type into its own complex type, it works fine again. Seems like only when i add it as a simple type it refuses to parse at the server side. In the intial case, i had debugged the axis client side parsing the tags, and the new simple type tag conditions pass through properly and it recognizes it. Why is it only at the server i get this error. I lieterally need some help on this. I can give the full file set if you need more information. -Original Message- *From:* Amila Suriarachchi [mailto:[EMAIL PROTECTED] *Sent:* 10 October 2007 10:39 *To:* axis-user@ws.apache.org *Subject:* Re: Peculiar Issue while testing a service On 10/10/07, Gudla, Natraj (GE Money, consultant) [EMAIL PROTECTED] wrote: Hi, Any ideas on this? how do you generate this request? some problem there. Cheers Natraj -Original Message- From: Gudla, Natraj (GE Money, consultant) Sent: 09 October 2007 10:01 To: 'axis-user@ws.apache.org ' Subject: Peculiar Issue while testing a service Hi, I am reporting a peculiar issue which i am facing since yesterday working with AXIS2 1.2. Addition of an extra simple element to an existing complex type of an xsd throws an Un Expected Element error. Following is the brief. The current set up : Working Fine. The complext type part of my xsd xsd:complexType name=GEM_Ln_LoanRequestDetails xsd:sequence xsd:element name=LoanPreference type=GEM_Ln_LoanPreference/ xsd:element name=CustomerDetails type=GEM_Ln_CustomerDetails/ xsd:element name=CustomerAddr type=GEM_Ln_CustomerAddr/ xsd:element name=EmployerDetails type=GEM_Ln_EmployerDetails/ xsd:element name=CustomerFinances type=GEM_Ln_CustomerFinances/ xsd:element name=CardDetails type=GEM_Ln_CardDetails minOccurs=0/ xsd:element name=LoanDetails type=GEM_Ln_LoanDetails minOccurs=0/ /xsd:sequence /xsd:complexType I used a wsdl, generated binding ( ADB ) classes using WSDL to Java tool on Axis2 1.2. Using the build.xml, running the jar.server task i created the services.aar and deployed on tomcat. Created a sample java class, which reads a sample loan request xml ( formed using IDE based on the xsd ) and submits a request to the service. Every thing works fine, i get the response as i coded within the skeleton method. This looks fine end to end. Change to the existing schema: : Not Working xsd:complexType name=GEM_Ln_LoanRequestDetails xsd:sequence xsd:element name=ProductId type=xsd:string/ xsd:element name=LoanPreference type=GEM_Ln_LoanPreference/ xsd:element name=CustomerDetails type=GEM_Ln_CustomerDetails/ xsd:element name=CustomerAddr type=GEM_Ln_CustomerAddr/ xsd:element name=EmployerDetails type=GEM_Ln_EmployerDetails/ xsd:element name=CustomerFinances type=GEM_Ln_CustomerFinances/ xsd:element name=CardDetails type=GEM_Ln_CardDetails minOccurs=0/ xsd:element name=LoanDetails type=GEM_Ln_LoanDetails minOccurs=0/ /xsd:sequence /xsd:complexType I have a need to add new field to hold a product id. after this, i generated the binding classes again ( to make sure, i deleted all the existing classes, and re generated every thing ). Then did the same procedure as above to generated the services.aar, then created the sample java class callling the stub. Changed the sample xml file to add a product id tag and then executed the program. This time un expectedley i get the Un expected sub element Product Id error repeatedly. Not sure what is the problem, this looks to be simple. I tried various combinations adding a test tag, then making product id a simple type etc etc. Any idea why this occurs. I made sure, i replaced the correct services.aar on the server. The new
RE: Peculiar Issue while testing a service
First i generate a sample xml file using the Eclipse IDE, using the xsd, then use the parse method of axis generated wrapper class for my request, passing it the XMLStreamReader created from the sample xml. This worked fine end to end earlier. Sample class, calling stub passing the request object, server responding properly with expected response. Only after i include a simple type element into one of the existing complex types within the xsd, it fails saying unexpected element. Just another peice of information, when i place this new simple type into its own complex type, it works fine again. Seems like only when i add it as a simple type it refuses to parse at the server side. In the intial case, i had debugged the axis client side parsing the tags, and the new simple type tag conditions pass through properly and it recognizes it. Why is it only at the server i get this error. I lieterally need some help on this. I can give the full file set if you need more information. -Original Message- From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: 10 October 2007 10:39 To: axis-user@ws.apache.org Subject: Re: Peculiar Issue while testing a service On 10/10/07, Gudla, Natraj (GE Money, consultant) [EMAIL PROTECTED] wrote: Hi, Any ideas on this? how do you generate this request? some problem there. Cheers Natraj -Original Message- From: Gudla, Natraj (GE Money, consultant) Sent: 09 October 2007 10:01 To: ' axis-user@ws.apache.org mailto:axis-user@ws.apache.org ' Subject: Peculiar Issue while testing a service Hi, I am reporting a peculiar issue which i am facing since yesterday working with AXIS2 1.2. Addition of an extra simple element to an existing complex type of an xsd throws an Un Expected Element error. Following is the brief. The current set up : Working Fine. The complext type part of my xsd xsd:complexType name=GEM_Ln_LoanRequestDetails xsd:sequence xsd:element name=LoanPreference type=GEM_Ln_LoanPreference/ xsd:element name=CustomerDetails type=GEM_Ln_CustomerDetails/ xsd:element name=CustomerAddr type=GEM_Ln_CustomerAddr/ xsd:element name=EmployerDetails type=GEM_Ln_EmployerDetails/ xsd:element name=CustomerFinances type=GEM_Ln_CustomerFinances/ xsd:element name=CardDetails type=GEM_Ln_CardDetails minOccurs=0/ xsd:element name=LoanDetails type=GEM_Ln_LoanDetails minOccurs=0/ /xsd:sequence /xsd:complexType I used a wsdl, generated binding ( ADB ) classes using WSDL to Java tool on Axis2 1.2. Using the build.xml, running the jar.server task i created the services.aar and deployed on tomcat. Created a sample java class, which reads a sample loan request xml ( formed using IDE based on the xsd ) and submits a request to the service. Every thing works fine, i get the response as i coded within the skeleton method. This looks fine end to end. Change to the existing schema: : Not Working xsd:complexType name=GEM_Ln_LoanRequestDetails xsd:sequence xsd:element name=ProductId type=xsd:string/ xsd:element name=LoanPreference type=GEM_Ln_LoanPreference/ xsd:element name=CustomerDetails type=GEM_Ln_CustomerDetails/ xsd:element name=CustomerAddr type=GEM_Ln_CustomerAddr/ xsd:element name=EmployerDetails type=GEM_Ln_EmployerDetails/ xsd:element name=CustomerFinances type=GEM_Ln_CustomerFinances/ xsd:element name=CardDetails type=GEM_Ln_CardDetails minOccurs=0/ xsd:element name=LoanDetails type=GEM_Ln_LoanDetails minOccurs=0/ /xsd:sequence /xsd:complexType I have a need to add new field to hold a product id. after this, i generated the binding classes again ( to make sure, i deleted all the existing classes, and re generated every thing ). Then did the same procedure as above to generated the services.aar, then created the sample java class callling the stub. Changed the sample xml file to add a product id tag and then executed the program. This time un expectedley i get the Un expected sub element Product Id error repeatedly. Not sure what is the problem, this looks to be simple. I tried various combinations adding a test tag, then making product id a simple type etc etc. Any idea why this occurs. I made sure, i replaced the correct services.aar on the server. The new resource folder generated second time, properly refers to the product id which was included. Just as a work around, i tested with some sample test and test simple tags, observed the xml input on TCP Monitor. For your reference attached is the
SV: [Aixs2]: generating services.xml with wsdl2java
Thanks for your reply. I do have all the info needed don't I? I have the .wsdl file, and the .java file for my web-service. All that I need is to generate the services.xml... But I guess the wsdl2java tool is written in such a way that it expects to generate services.xml from java code it also generates, not from pre-existing java code. I assume it is possible to automatically generate services.xml from pre-existing .java code... somehow. (I am only writing very simple web-services at the moment which only return ints, or strings, but later I will want to return more complex/custom types). /Peter Fra: Ashish Arya [mailto:[EMAIL PROTECTED] Sendt: 10. oktober 2007 11:48 Til: axis-user@ws.apache.org Emne: RE: [Aixs2]: generating services.xml with wsdl2java Peter, If you remove the 'serverside' and 'serverSideInterface' attribute from wsdl2Java target (in Ant), it will not generate the skeleton and interface for you. And since you don't have the complete information for generating services.xml, the same is also not generated by the tool. Thus I don't think there is any way to generate services.xml without generating server side components. If any one has any alternate approach, that would be helpful. Regards, Ashish Arya, From: Peter A. Kirk [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 10, 2007 3:02 PM To: axis-user@ws.apache.org Subject: [Aixs2]: generating services.xml with wsdl2java Hi Wsdl2Java can be used to generate services.xml - but it also generates java files (skeleton code for the webservice), and the services.xml file references the generated java classes. What if I already have a complete java file (containing all the necessary code for my webservice), and I already have an associated wsdl. How do I generate the appropriate services.xml for deployment in Axis2? Is there no other way than writing services.xml by hand? Thanks, Peter
Re: Address already in use: connect
Try to set some custom options [1], like caching/reusing the same http
client and throttling the max number of connections.
Michele
[1]
http://svn.apache.org/viewcvs.cgi//webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/async/AsyncService2Test.java
On Wed, 2007-10-10 at 11:13 +0200, Pär Malmqvist wrote:
Hi!
I have written a simple blocking client using Axis2 1.3 API's.
When I do like this:
for(int i = 0; i 100; i++) {
...
ServiceClient sender = new ServiceClient();
sender.sendReceive(payload);
...
}
there is no problem. The client runs for many hours.
When I do like this:
ServiceClient sender = new ServiceClient();
for(int i = 0; i 100; i++) {
...
sender.sendReceive(payload);
sender.cleanup();
sender.cleanupTransport();
}
I get exception AxisFault: Address already in use: connect
after a couple of thousand calls.
It seems to be something wrong in the ServiceClient class which
shows up after a while.
Any ideas?
/Pär Malmqvist
__
Explore the seven wonders of the world Learn more!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Peculiar Issue while testing a service
Yes i do. and i run the wsdl2java on the wsdl which refers to this xsd. I have
just been doing some debuggin and see how the reader.getName() differs on the
client side and the server side.
The class GEM_Ln_LoanRequestDetails which was generated by axis, returns as
test ( test is the simple element i added for testing ). The same code at
server side returns a {GEMoney:XMLI}test, GEMoney:XMLI is the name space in
which the complext type having test is defined.
Why is this difference in reading the name of the reader from the same piece of
code at client and server. Further i understand the condition below fails at
server and not in client call.
if (reader.isStartElement()
new javax.xml.namespace.QName(, test)
.equals(reader.getName())) {
The QName conditions is false at server side and hence it jumps to the
excpetion loop to create the error. Does this give some clue?
Thanks
Natraj.
[Gudta, Natraj (GE Money, consultant)] -Original Message-
From: Antonio Manuel Muñiz Martín [mailto:[EMAIL PROTECTED]
Sent: 10 October 2007 11:18
To: axis-user@ws.apache.org
Subject: Re: Peculiar Issue while testing a service
Do you modify the xsd in the correct place? Perhaps you are modifying the xsd
and on deploy time the xsd used is other.
2007/10/10, Gudla, Natraj (GE Money, consultant) mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED]:
First i generate a sample xml file using the Eclipse IDE, using the xsd, then
use the parse method of axis generated wrapper class for my request, passing it
the XMLStreamReader created from the sample xml. This worked fine end to end
earlier. Sample class, calling stub passing the request object, server
responding properly with expected response.
Only after i include a simple type element into one of the existing complex
types within the xsd, it fails saying unexpected element. Just another peice of
information, when i place this new simple type into its own complex type, it
works fine again. Seems like only when i add it as a simple type it refuses to
parse at the server side.
In the intial case, i had debugged the axis client side parsing the tags, and
the new simple type tag conditions pass through properly and it recognizes it.
Why is it only at the server i get this error.
I lieterally need some help on this. I can give the full file set if you need
more information.
-Original Message-
From: Amila Suriarachchi [mailto: [EMAIL PROTECTED]
Sent: 10 October 2007 10:39
To: axis-user@ws.apache.org
Subject: Re: Peculiar Issue while testing a service
On 10/10/07, Gudla, Natraj (GE Money, consultant) [EMAIL PROTECTED] wrote:
Hi,
Any ideas on this?
how do you generate this request? some problem there.
Cheers
Natraj
-Original Message-
From: Gudla, Natraj (GE Money, consultant)
Sent: 09 October 2007 10:01
To: ' axis-user@ws.apache.org mailto:axis-user@ws.apache.org '
Subject: Peculiar Issue while testing a service
Hi,
I am reporting a peculiar issue which i am facing since yesterday working
with AXIS2 1.2. Addition of an extra simple element to an existing complex
type of an xsd throws an Un Expected Element error. Following is the brief.
The current set up : Working Fine.
The complext type part of my xsd
xsd:complexType name=GEM_Ln_LoanRequestDetails
xsd:sequence
xsd:element name=LoanPreference
type=GEM_Ln_LoanPreference/
xsd:element name=CustomerDetails
type=GEM_Ln_CustomerDetails/
xsd:element name=CustomerAddr
type=GEM_Ln_CustomerAddr/
xsd:element name=EmployerDetails
type=GEM_Ln_EmployerDetails/
xsd:element name=CustomerFinances
type=GEM_Ln_CustomerFinances/
xsd:element name=CardDetails
type=GEM_Ln_CardDetails minOccurs=0/
xsd:element name=LoanDetails
type=GEM_Ln_LoanDetails minOccurs=0/
/xsd:sequence
/xsd:complexType
I used a wsdl, generated binding ( ADB ) classes using WSDL to Java tool on
Axis2 1.2. Using the build.xml, running the jar.server task i created the
services.aar and deployed on tomcat. Created a sample java class, which reads
a sample loan request xml ( formed using IDE based on the xsd ) and submits a
request to the service.
Every thing works fine, i get the response as i coded within the skeleton
method. This looks fine end to end.
Change to the existing schema: : Not Working
xsd:complexType name=GEM_Ln_LoanRequestDetails
xsd:sequence
xsd:element name=ProductId type=xsd:string/
xsd:element name=LoanPreference
type=GEM_Ln_LoanPreference/
xsd:element name=CustomerDetails
type=GEM_Ln_CustomerDetails/
xsd:element name=CustomerAddr
type=GEM_Ln_CustomerAddr/
xsd:element
Null Pointer when adding child to OMElement
Hi,
I am trying to add a simple child element to an OMElement I have
created, but I am getting a null pointer. I am using the same syntax I
have seen in the Axiom OM Tutorial
(http://ws.apache.org/axis2/1_0/OMTutorial.html), and am using Axis 2 1.3.
The code I try is:
public static OMElement createQuery(){
OMNamespace aon = new
OMNamespaceImpl(http://www.aoi.com/WSDA/0.1;, ao);
OMElement wsdaQueryNode = new OMElementImpl(wsdaQuery, aon, null);
wsdaQueryNode.addAttribute(name, campaign.getProductSkuId, aon);
OMElement param = new OMElementImpl(param, aon, null);
param.addAttribute(skuId, 6949, aon);
param.addChild(param);
return wsdaQueryNode;
}
The error I get is:
java.lang.NullPointerException
Error: java.lang.NullPointerException
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.init(StAXOMBuilder.java:64)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.importNode(OMNodeImpl.java:455)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:197)
at
com.aoi.ws.clients.test.WSDATestClient.createQuery(WSDATestClient.java:55)
at com.aoi.ws.clients.test.WSDATestClient.main(WSDATestClient.java:27)
Any ideas would be much appreciated.
Regards,
Chris
--
Chris Bowman
Director, Phoros Limited
mobile: +44(0)7766 881 564
email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Null Pointer when adding child to OMElement
Hi,
This will work.
public static OMElement createQuery(){
OMFactory factory = OMAbstractFactory.getOMFactory();
OMNamespace aon = factory.createOMNamespace(
http://www.aoi.com/WSDA/0.1,ao;);
OMElement wsdaQueryNode = factory.createOMElement(wsdaQuery, aon,
null);
wsdaQueryNode.addAttribute(name, campaign.getProductSkuId, aon);
OMElement param = factory.createOMElement(param, aon, null);
param.addAttribute(skuId, 6949, aon);
wsdaQueryNode.addChild(param);
return wsdaQueryNode;
}
Upul
On 10/10/07, Chris Bowman [EMAIL PROTECTED] wrote:
Hi,
I am trying to add a simple child element to an OMElement I have
created, but I am getting a null pointer. I am using the same syntax I
have seen in the Axiom OM Tutorial
(http://ws.apache.org/axis2/1_0/OMTutorial.html), and am using Axis 2 1.3.
The code I try is:
public static OMElement createQuery(){
OMNamespace aon = new
OMNamespaceImpl(http://www.aoi.com/WSDA/0.1;, ao);
OMElement wsdaQueryNode = new OMElementImpl(wsdaQuery, aon,
null);
wsdaQueryNode.addAttribute(name, campaign.getProductSkuId,
aon);
OMElement param = new OMElementImpl(param, aon, null);
param.addAttribute(skuId, 6949, aon);
param.addChild(param);
return wsdaQueryNode;
}
The error I get is:
java.lang.NullPointerException
Error: java.lang.NullPointerException
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.init(StAXOMBuilder.java
:64)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.importNode(OMNodeImpl.java:455)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java
:197)
at
com.aoi.ws.clients.test.WSDATestClient.createQuery(WSDATestClient.java:55)
at com.aoi.ws.clients.test.WSDATestClient.main(WSDATestClient.java:27)
Any ideas would be much appreciated.
Regards,
Chris
--
Chris Bowman
Director, Phoros Limited
mobile: +44(0)7766 881 564
email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Null Pointer when adding child to OMElement
Upul,
thank you very much, that has fixed it.
Much appreciated,
Chris
Upul Godage wrote:
Hi,
This will work.
public static OMElement createQuery(){
OMFactory factory = OMAbstractFactory.getOMFactory();
OMNamespace aon = factory.createOMNamespace(
http://www.aoi.com/WSDA/0.1,ao;);
OMElement wsdaQueryNode = factory.createOMElement(wsdaQuery,
aon, null);
wsdaQueryNode.addAttribute(name, campaign.getProductSkuId
, aon);
OMElement param = factory.createOMElement(param, aon, null);
param.addAttribute(skuId, 6949, aon);
wsdaQueryNode.addChild(param);
return wsdaQueryNode;
}
Upul
On 10/10/07, *Chris Bowman* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi,
I am trying to add a simple child element to an OMElement I have
created, but I am getting a null pointer. I am using the same syntax I
have seen in the Axiom OM Tutorial
( http://ws.apache.org/axis2/1_0/OMTutorial.html), and am using
Axis 2 1.3.
The code I try is:
public static OMElement createQuery(){
OMNamespace aon = new
OMNamespaceImpl( http://www.aoi.com/WSDA/0.1;, ao);
OMElement wsdaQueryNode = new OMElementImpl(wsdaQuery,
aon, null);
wsdaQueryNode.addAttribute(name,
campaign.getProductSkuId , aon);
OMElement param = new OMElementImpl(param, aon, null);
param.addAttribute(skuId, 6949, aon);
param.addChild(param);
return wsdaQueryNode;
}
The error I get is:
java.lang.NullPointerException
Error: java.lang.NullPointerException
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.init(StAXOMBuilder.java:64)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.importNode(OMNodeImpl.java:455)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:197)
at
com.aoi.ws.clients.test.WSDATestClient.createQuery
(WSDATestClient.java:55)
at
com.aoi.ws.clients.test.WSDATestClient.main(WSDATestClient.java:27)
Any ideas would be much appreciated.
Regards,
Chris
--
Chris Bowman
Director, Phoros Limited
mobile: +44(0)7766 881 564
email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
--
Chris Bowman
Director, Phoros Limited
mobile: +44(0)7766 881 564
email: [EMAIL PROTECTED]
Re: No serializer found for class in registry TypeMappingDelegate
Thanks for reply! This MyEventPub is the sample user's class fired as event on server at runtime, therefore I don't know about before. How can I marshal this with JAXB for MessageElement ? I mean this MyEventPub is well annotated class and well marshalled to StringWriter(). Where can I store it within MessageElement? Please, advise me. Alexey. On 10/5/07, Walker, Jeff [EMAIL PROTECTED] wrote: I think your missing a type mapping in the wsdd file. You need something like this inserted. (deploy.wsdd file:) ... typeMapping xmlns:ns=http://www.company.com/project; qname=ns:MyEventPub type=java:org.exoplatform.services.portletcontainer.test.portlet2.MyEve ntPub serializer=org.apache.axis.encoding.ser.BeanSerializerFactory deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle= / ... The real question is, why do you not have it? If you ran your wsdl file through the generator, the stubs and skeleton code gets created for you. This command also generates the deploy.wsdd file and should add in all of the type mappings you need for your classes. %java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy true WebServiceName.wsdl -jeff -Original Message- From: Alexey Zavizionov [mailto:[EMAIL PROTECTED] Sent: Friday, October 05, 2007 12:31 PM To: axis-user@ws.apache.org Subject: No serializer found for class in registry TypeMappingDelegate Hello list! I have an exc on server of my service: [ERROR] BeanSerializer - Exception: java.io.IOException: No serializer found for class org.exoplatform.services.portletcontainer.test.portlet2.MyEventPub in registry [EMAIL PROTECTED]java.io.IOException: No serializer found for class org.exoplatform.services.portletcontainer.test.portlet2.MyEventPub in registry [EMAIL PROTECTED] at org.apache.axis.encoding.SerializationContext.serializeActual(Serializat ionContext.java:1507) ... What could this be? PS: I use Axis1-1.4 Thanks, Alexey - 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]
[Axis2/ADB] How to check whether optional parts of a SOAP message are specified
Hi, suppose I have optional parts in an XML element used by a WSDL, e.g.: xs:complexType name=CandidateType xs:sequence ... ... xs:element name=IsHit type=xs:boolean minOccurs=0/ /xs:sequence /xs:complexType After the stub classes have been generated by wsdl2java, how can I check whether IsHit was specified based on a stub class? I know there are tracker variables in the stub class, but I cannot use these because they (1) are not accessible and they (2) are not evaluated by the retrieval methods. So for the above example, IsHit can have three states: 1) true 2) false 3) not specified Using getIsHit() on the corresponding stub I can detect 1 and 2. But how can I extract the state 3 from the stub class? Thanks for any hints, -Rainer -- __ *Dr. Rainer Menzner* Principal Engineer, RD *L-1 Identity Solutions AG* /Protecting and Securing Personal Identities and Assets/ Universitätsstr. 160 44801 Bochum, Germany Telephone: +49-234-9787-41 Facsimile: +49-234-9787-77 Mobile: 0160 / 700 99 07 email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] www.L1ID.com http://www.l1id.com/ This message is only for the use of the intended recipient and may contain information that is CONFIDENTIAL and PROPRIETARY to L-1 Identity Solutions. If you are not the intended recipient, please erase all copies of the message and its attachments and notify the sender immediately. VORSTAND / EXECUTIVE BOARD Hartmuth von Maltzahn (Vors. / Chairman), Dr. Stefan Gehlen | AUFSICHTSRAT / SUPERVISORY BOARD James H. Moar (Vors. / Chairman) | GERICHTSSTAND / REGISTER COURT Amtsgericht Bochum, HRB 69 54 | UST-ID / VAT-REG.-NO. DE 813124378 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: No serializer found for class in registry TypeMappingDelegate
Alexey, Let's step back for a minute. I'm confused as to your system setup. Let's go over the basics of Axis1-1.4 first. Assuming you started with a wsdl file first (Top-Down approach) and also assuming you are creating a Document/Literal based wsdl, you must create XML Schema for every Java class that you intend to send over the service. Therefore, the MyEventPub class (which I take it you are trying to send over the wire) must have equivalent XML Schema created for it, or at least imported from an external xsd file into your wsdl file. Therefore, to send it over the wire, you need to know the structure of this class in advance (so that you can write schema for it). The WSDL2Java generator will read the schema in the wsdl and essentially create two classes for each element/complexType it finds. One is to serialize the class (put it into xml) the other is to deserialize it (take it from xml and back into a Java object). This is a simplified view of the process, but it is essentially correct. Also generated for you, is a deploy.wsdd file. In the deploy.wsdd file, there are some namespace declarations. And then a section that describes the service, such as what methods are exposed publicly, the port name (which is the name of the web service), the name of your skeleton class (which is used by Axis to make sure the correct operation is called on your interface), and so on. Further down in deploy.wsdd there are type mappings. This is where Axis learns about the classes that can be serialized/deserialized. Each type mapping essentially holds a qualified namespace, the type of object your transferring (that is, the package and name of your class), and the names of the serializer and deserializer classes that will do the work for that type. Now, your original post hinted that a type mapping was missing from the wsdd file, for the MyEventPub class. There maybe some strange situations where a type mapping may not be created by the generator, even though the MyEventPub class has an schema equivalent in the wsdl file. But I suspected (in my first reply) that the problem was that you did not create any schema for MyEventPub in the first place and so Axis had no way of knowing how to serialize/deserialize it. Hence, the type mapping exception. Now, your following question asks where can you 'store' MyEventPub within MessageElement. The problem here, is that your hinting at trying to construct the soap parse tree yourself, and then presumably serialize that tree (with the MyEventPub fields in it somewhere). I strongly recommend that you do not approach your web service from this angle. I cannot help you further with this direction. (Perhaps you have previous experience with RPC-encoded services and serializing graphs of objects? If not, then this approach will be a difficult task indeed). I recommend you define MyEventPub in schema (in the wsdl) and let Axis do 95% of the work for you. I also recommend that you adopt the Document/Literal-Wrapped wsdl format (go here to learn about it: http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/), and abandon any attempt at an RPC service. You will get virtually no help from this mailing list if you choose to continue with an RPC-based wsdl. (That is because a wsdl based on RPC is essentially deprecated as a web service design, and nobody does web services like that anymore. Why not?Because RPC-Encoded is not WSI compliant. There is no standard way to interpret the serialize object graph across every platform that could conceivably call your service). In Document Literal-Wrapped, the methods on your interface take a single object and return a single object. Those two objects can obviously have multiple objects within them. Each object is based on schema in your wsdl. This is the approach everybody else takes with web services these days. One more thing. There are only a few of us left still using Axis1.4 on our projects. Nearly all subscribers of the Axis mailing list are using Axis2. You cannot use Axis2 to do an RPC Encoded service. Does any of this help? -jeff -Original Message- From: Alexey Zavizionov [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 10, 2007 8:28 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED]; Roman Pedchenko Subject: Re: No serializer found for class in registry TypeMappingDelegate Thanks for reply! This MyEventPub is the sample user's class fired as event on server at runtime, therefore I don't know about before. How can I marshal this with JAXB for MessageElement ? I mean this MyEventPub is well annotated class and well marshalled to StringWriter(). Where can I store it within MessageElement? Please, advise me. Alexey. On 10/5/07, Walker, Jeff [EMAIL PROTECTED] wrote: I think your missing a type mapping in the wsdd file. You need something like this inserted. (deploy.wsdd file:) ... typeMapping xmlns:ns=http://www.company.com/project; qname=ns:MyEventPub
Re: [Axis2 1.3]POJO-based RESTFul serivce
Thanks, Keith. As you can see addEntry element contains another complex type within it. Hence the parameters at the serverside cannot produce the required SOAP message that Axis2 needs. This will work perfectly with application/xml on a post though. Can you try to codegenerate a stub using the -pn AddressBookServiceSOAP11port_http option. That should work out of the box and you dont have to worry about creating the contents using OMElements. Using application/xml, the service recieved addEntry object. Thanks for your help. But, I would like to use both plain HTML and Java (include Axis2) as client. When I use the plain HTML as client, the format of POST parameters is param1=xxxparam2=xxx. Do I have to create the request by XML format ? Thanks, Takanori. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] inner class loading of a lib.jar
It seems that inner classes of a lib.jar in the service.aar cannot be loaded. I get a java.lang.ClassNotFoundException: mypackage.TestClass$InnerClass If I put the lib.jar not in the service.aar but in the axis2/WEB-INF/lib it works. Do I make a mistake or is something wrong with the axis2 class loading? Thanks. Nathan -- View this message in context: http://www.nabble.com/-Axis2--inner-class-loading-of-a-lib.jar-tf4601559.html#a13138153 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2 1.3]POJO-based RESTFul serivce
I didnt get your question clearly. If you want to send application/xml using an HTML client I think you will have to create the XML payload. Is that what you asked? Thanks, Keith. On 10/10/07, Takanori Suzuki [EMAIL PROTECTED] wrote: Thanks, Keith. As you can see addEntry element contains another complex type within it. Hence the parameters at the serverside cannot produce the required SOAP message that Axis2 needs. This will work perfectly with application/xml on a post though. Can you try to codegenerate a stub using the -pn AddressBookServiceSOAP11port_http option. That should work out of the box and you dont have to worry about creating the contents using OMElements. Using application/xml, the service recieved addEntry object. Thanks for your help. But, I would like to use both plain HTML and Java (include Axis2) as client. When I use the plain HTML as client, the format of POST parameters is param1=xxxparam2=xxx. Do I have to create the request by XML format ? Thanks, Takanori. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
WSDL2JAVA does not generate WebServiceProxy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am using WSDL2JAVA via the Eclipse plugin to generate a WS Client. Usually it generates 5 Java Classes: Foo.java FooBindingStub.java FooProxy.java FooService.java FooServiceLocator.java However my wsdl does not generate the FooProxy.java class and I can't figure what may be wrong. Any help would be appreciated. Here is the wsdl: targetNamespace=http://incm.pt/xi/PSP/Anexos; xmlns:p1=http://incm.pt/xi/PSP/Anexos; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns=http://incm.pt/xi/PSP/Anexos; xmlns:xsd=http://www.w3.org/2001/XMLSchema; source=http://sap.com/xi/TextID; 1fd5ea5057cc11dc86c1000d9d95b523 Número de Processo source=http://sap.com/xi/TextID; 1fd5ea5157cc11dcc877000d9d95b523 1: Cartão Plástico / 2: Certificados /3: Notificações / 4: Caderneta / 5:Carta PIN source=http://sap.com/xi/TextID; 1fd5ea5257cc11dc805c000d9d95b523 Identifica o layout source=http://sap.com/xi/TextID; 1fd5ea5357cc11dcb247000d9d95b523 U: Urgente / N: Normal source=http://sap.com/xi/TextID; 1fd5ea5457cc11dcb0a9000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5557cc11dcc197000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5657cc11dca185000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5757cc11dc82ed9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5857cc11dcbd35000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5957cc11dcbb05000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5a57cc11dcbf2c000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5b57cc11dcba71000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5c57cc11dcb7d5000d9d95b523 source=http://sap.com/xi/TextID; 5de9a39057cc11dc8844000d9d95b523 Número de Processo de Pedido de CC source=http://sap.com/xi/TextID; 5de9a39157cc11dc9b7d000d9d95b523 source=http://sap.com/xi/TextID; 5de9a39257cc11dc8df8000d9d95b523 source=http://sap.com/xi/TextID; 5de9a39357cc11dcbb01000d9d95b523 source=http://sap.com/xi/TextID; 5de9a39457cc11dc8de3000d9d95b523 source=http://sap.com/xi/TextID; 5de9a39557cc11dcc5f1000d9d95b523 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; / type=p1:pspAnexosCartoes_out xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; transport=http://schemas.xmlsoap.org/soap/http; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; / soapAction=http://sap.com/xi/WebService/soap1.1; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; / xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; / binding=p1:pspAnexosCartoes_outBinding xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; location= http://xidev.incm.pt:50100/XISOAPAdapter/MessageServlet?channel=:CV:SenderChannel_SOAP_AnexosCartoesamp;version=3.0amp;Sender.Service=xamp;Interface=x%5Ex xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; / - -- Dário Abdulrehman PGP Public Key: http://tinyurl.com/2pm9d7 - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: http://firegpg.tuxfamily.org iD8DBQFHDRdWHfwTJs1Ix7cRAgABAJ9VjqC/eUMXNe5egOwB2wsuP/bWTQCdH5BE eoLQb7hk5S3hQxPOGIIy3eA= =MKiU -END PGP SIGNATURE-
Error: Unexpected subelement responseCode
Hello, I am using axis2 1.3 and deploy me service on JBOSS 4.0.5. I am getting following error when I run my client: * org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement responseCode at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubStub.fromOM(StompHubStub.java:5270) at com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubStub.transmit(StompHubStub.java:180) at webservice.clients.StompHubClientUsingStubsWithWSDL.main(StompHubClientUsingStubsWithWSDL.java:35) Caused by: java.lang.Exception: org.apache.axis2.databinding.ADBException: Unexpected subelement responseCode at com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubStub$StompHubResponse$Factory.parse(StompHubStub.java:4491) at com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubStub$TransmitResponse$Factory.parse(StompHubStub.java:789) at com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubStub.fromOM(StompHubStub.java:5264) ... 2 more Caused by: org.apache.axis2.databinding.ADBException: Unexpected subelement responseCode at com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubStub$StompHubResponse$Factory.parse(StompHubStub.java:4485) ... 4 more * My WSDL looks like this: * ?xml version=1.0 encoding=UTF-8? wsdl:documentationStompHub/wsdl:documentation wsdl:types xs:complexType name=StompCredentials xs:sequence xs:element name=orgnaizationId nillable=false type=xs:string/ xs:element name=password nillable=false type=xs:string/ xs:element name=username nillable=false type=xs:string/ /xs:sequence /xs:complexType /xs:schema xs:element name=transmit xs:complexType xs:sequence xs:element name=request nillable=false type=ns2:StompHubRequest/ /xs:sequence /xs:complexType /xs:element xs:element name=transmitResponse xs:complexType xs:sequence xs:element name=return nillable=false type=ns2:StompHubResponse/ /xs:sequence /xs:complexType /xs:element /xs:schema http://inbound.adapters.transport.stomp.ens.com/xsd/ xs:complexType name=StompHubRequest xs:sequence xs:element name=credentials nillable=false type=ns0:StompCredentials/ xs:element minOccurs=0 name=payerCredentials nillable=true type=ax21:StompHubPayerCredentials/ xs:element minOccurs=0 name=payloadData nillable=true type=xs:string/ xs:element name=routing nillable=false type=ax21:StompHubRouting/ /xs:sequence /xs:complexType xs:complexType name=StompHubPayerCredentials xs:sequence xs:element minOccurs=0 name=password nillable=true type=xs:string/ xs:element minOccurs=0 name=submitterId nillable=true type=xs:string/ xs:element minOccurs=0 name=userid nillable=true type=xs:string/ /xs:sequence /xs:complexType xs:complexType name=StompHubRouting xs:sequence xs:element name=payerId nillable=false type=xs:string/ xs:element name=transactionType nillable=false type=xs:string/ /xs:sequence /xs:complexType xs:complexType name=StompHubResponse xs:sequence xs:element minOccurs=0 name=responseCode nillable=true type=xs:string/ xs:element minOccurs=0 name=responseMessage nillable=true type=xs:string/ xs:element maxOccurs=unbounded minOccurs=0 name=responsePayload nillable=true type=ax21:StompHubResponsePayload/ /xs:sequence /xs:complexType xs:complexType name=StompHubResponsePayload xs:sequence xs:element name=payloadData nillable=false type=xs:string/ xs:element name=transactionType nillable=false type=xs:string/ /xs:sequence /xs:complexType /xs:schema /wsdl:types wsdl:message name=transmitRequest wsdl:part name=parameters element=ns1:transmit/ /wsdl:message wsdl:message name=transmitResponse wsdl:part name=parameters
Axis2 memory footprint
Hi, The Axis2 Web page says that Axis2 was designed ground-up keeping low memory foot print in mind. Can anyone quantify roughly how much memory is needed for a simple Axis2 SOAP service running on top of a Tomcat server? Just the memory taken by Axis2 and Axis2 generated code. I'm just looking for a ballpark number, say, for a service with 5-10 methods plus 5-10 structures defined for arguments and results. Any help much appreciated. Thanks, Anders - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [AXIS2] Simple (?) config question
Hi Deepal, According to what you said I've changed the contextRoot servicePath in axis2.xml. I've changed it like this. parameter name=contextRoot/webservices/parameter parameter name=servicePathmyService/parameter And when I go to http://localhost/webservices/myService?wsdl I'm able to see the WSDL. But in the WSDL the end point address is shown as soap:address location=http://10.5.1.241:80/webservices/myService/myService; / Because of this when I'm trying to run the client and access my webservice, I'm getting an exception The service cannot be found for the endpoint reference (EPR) http://localhost/webservices/myService Thanks Raghu -Original Message- From: Deepal jayasinghe [mailto:[EMAIL PROTECTED] Sent: Monday, October 08, 2007 8:27 AM To: axis-user@ws.apache.org Subject: Re: [AXIS2] Simple (?) config question Lorenzo wrote: Hi all, i need to change axis2 services path from http://localhost:8080/axis2/services/myService to http://localhost:8080/axis2/myService (possibly without move .aar archives) but i didn't find where to do it.. You can do that by adding following two parameters into axis2.xml parameter name=contextRoot/axis2/parameter parameter name=servicePathmyService/parameter Thanks Deepal - 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]
[Axis2] javax.xml.ws.soap.Addressing is missing?
Hi all, from here [1, par 2.2.1] and here [2] I understand that is possible to enable the WS-Addressing on the server side via the @javax.xml.ws.soap.Addressing annotation, but I can't find it into the axis2 distribution. Is there any reason for this? Thanks, Michele [1] https://jax-ws.dev.java.net/nonav/2.1.2/docs/wsaddressing.html [2] JAX-WS spec 2.1, Maintenance Release 2, (May 7, 2007), http:// jcp.org/en/jsr/detail?id=224 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with Rampart
You also need to put all the .jar files from the lib folder of rampart into axis2/WEB-INF/lib. Antonio Manuel Muiz Martn wrote: Hi. I try to use rampart. I folow the instructions in the doc (modify service.xml, engage module in axis2.xml and put the module file rampart-1.3 in /axis2/modules directory). When I deploy the aar file axis throws the exception Error: org.apache.axis2.deployment.DeploymentException: The rampart module is not valid or has not been deployed. I must deploy the module? Docs dont says anything. -- Anthony - Anthony Bull Senior Developer Black Coffee Software Ltd PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 - www.bcsoft.co.nz --- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. Any views or opinions expressed in this email may be personal to the sender and are not necessarily those of Black Coffee Software Ltd. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[axis2] AxisFault Best Practices
I have a few questions about how to properly use the messaging of an AxisFault to clearly explain our faults. First, is the correct use of QName. I know that a QName represents a Qualified Name and has to do with namespaces, but how important is it to set the namespaceURI, localPart, and prefix? We're going to be throwing AxisFaults for data validation issues so what should our localParl look like anyways? validation_error Should we use a prefix? error:validation Also, if needed how do we determine our namespaceURI? Is it the same as our service namespace that is defined in our WSDL? Finally what should be placed in the message vs in the detail? Since we're dealing with validation should the message state that there was a validation error with all the found validation errors in the detail? Or should we place all the validation errors in the the message with the detail being blank? I'm fairly new to web services and really need any amount of friendly push in the right direction. Thank you for your time. _ Peek-a-boo FREE Tricks Treats for You! http://www.reallivemoms.com?ocid=TXT_TAGHMloc=us - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Message Receiver not found for AxisOperation
Hi,
i'm trying to access a deployed group of services,
which are shown as active, and i can see their wsld(s) (with
axis2-1.3 in three different versions: bin. war. nightly build);
however, every client i've written until now throws this kind of error (as
follows), so what am i doing wrong?
thank you.
error message:
org.apache.axis2.AxisFault: Message Receiver not found for AxisOperation:
getEtichetta
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:528)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508)
at com.clients.direct.ProtocolClient.doIt(ProtocolClient.java:31)
at
com.clients.direct.ProtocolClient.getEtichetta(ProtocolClient.java:18)
at com.clients.direct.ProtocolClient.main(ProtocolClient.java:112)
one of the implementation classes; this
one exposes only the getEtichetta method:
public final class Protocollatore implements ProtocolService {
private static Protocollo protocollo;
private static boolean set = false;
public Protocollatore() {
if(!set) {
protocollo = new Protocollo();
set = true;
}
}
protected synchronized Protocollo getProtocollo ( ) {
if(set){
protocollo.AddOne();
Protocollo p = new Protocollo(protocollo.getValue());
return p;
} else return null;
}
public synchronized OMElement getEtichetta (OMElement _null) {
OMElement method = null;
try {
OMFactory fac = OMAbstractFactory.getOMFactory();
if(set){
protocollo.AddOne();
Etichetta e = new Etichetta(protocollo.getValue());
method = e.getOMElement();
} else {
OMNamespace ens =
fac.createOMNamespace(http://soap-shop.com/error,error;);
method = fac.createOMElement(InitFault, ens);
method.addChild(fac.createOMText(method, Errore :
Protocollatore non
inizializzato));
}
} catch (XMLStreamException xse) {
System.out.println(Protocollatore.getEtichetta() :
+xse.toString());
}
return method;
}
protected synchronized Etichetta Etichetta ( ) {
if(set){
protocollo.AddOne();
Etichetta e = new Etichetta(protocollo.getValue());
return e;
} else return null;
}
}
The client class for this service:
public class ProtocolClient {
public static OMElement getEtichetta() throws AxisFault {
OMElement payload = getNewOMElement(Etichetta);
OMElement result = doIt(payload, getEtichetta);
return result;
}
private static EndpointReference targetEPR =
new EndpointReference(
http://localhost:8180/axis2/services/ProtocolService;);
public static void main(String[] args) {
try {
OMElement payload = getNewOMElement(Vuoto);
OMElement result = getEtichetta();
String response = result.getFirstElement().getText();
} catch (Exception e) {
e.printStackTrace();
}
}
private static OMElement doIt(OMElement payload, String action) throws
AxisFault {
Options options = new Options();
options.setTo(targetEPR);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setAction(urn:+action);
ServiceClient sender = new ServiceClient();
sender.setOptions(options);
OMElement result = sender.sendReceive(payload);
return result;
}
private static OMElement getNewOMElement(String tag) {
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs =
fac.createOMNamespace(http://soap-shop.com/ProtocolService;,
ProtocolServiceNS);
OMElement result = fac.createOMElement(tag,omNs);
return result;
}
}
the services.xml file:
?xml version = '1.0' encoding = 'UTF-8'?
serviceGroup
service name=AdminService scope=application
descriptionAdmin Service/description
parameter name=ServiceClass com.business_logic.Admin/parameter
operation name=evadiOrdine
Re: Message Receiver not found for AxisOperation
Hi,
I think this part,
operation name=getEtichetta
messageReceivers
messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out;
class=org.apache.axis2.receivers.RawXMLInOutMessageReceiver /
/messageReceivers
actionMappingurn:getEtichetta/actionMapping
/operation
should be like this.
operation name=getEtichetta
messageReceiver
mep=http://www.w3.org/2004/08/wsdl/in-out;
class=
org.apache.axis2.receivers.RawXMLINOutMessageReceiver /
actionMappingurn:getEtichetta/actionMapping
/operation
Upul
On 10/11/07, francesco foresti [EMAIL PROTECTED] wrote:
Hi,
i'm trying to access a deployed group of services,
which are shown as active, and i can see their wsld(s) (with
axis2-1.3 in three different versions: bin. war. nightly build);
however, every client i've written until now throws this kind of error (as
follows), so what am i doing wrong?
thank you.
error message:
org.apache.axis2.AxisFault: Message Receiver not found for AxisOperation:
getEtichetta
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java
:486)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(
OutInAxisOperation.java:343)
at
org.apache.axis2.description.OutInAxisOperationClient.send(
OutInAxisOperation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(
OutInAxisOperation.java:211)
at org.apache.axis2.client.OperationClient.execute(
OperationClient.java:163)
at org.apache.axis2.client.ServiceClient.sendReceive(
ServiceClient.java:528)
at org.apache.axis2.client.ServiceClient.sendReceive(
ServiceClient.java:508)
at com.clients.direct.ProtocolClient.doIt(ProtocolClient.java:31)
at com.clients.direct.ProtocolClient.getEtichetta(
ProtocolClient.java:18)
at com.clients.direct.ProtocolClient.main(ProtocolClient.java:112)
one of the implementation classes; this
one exposes only the getEtichetta method:
public final class Protocollatore implements ProtocolService {
private static Protocollo protocollo;
private static boolean set = false;
public Protocollatore() {
if(!set) {
protocollo = new Protocollo();
set = true;
}
}
protected synchronized Protocollo getProtocollo ( ) {
if(set){
protocollo.AddOne();
Protocollo p = new Protocollo(protocollo.getValue());
return p;
} else return null;
}
public synchronized OMElement getEtichetta (OMElement _null) {
OMElement method = null;
try {
OMFactory fac = OMAbstractFactory.getOMFactory();
if(set){
protocollo.AddOne();
Etichetta e = new Etichetta(protocollo.getValue
());
method = e.getOMElement();
} else {
OMNamespace ens =
fac.createOMNamespace(http://soap-shop.com/error,error;);
method = fac.createOMElement(InitFault, ens);
method.addChild(fac.createOMText(method, Errore
: Protocollatore non
inizializzato));
}
} catch (XMLStreamException xse) {
System.out.println(Protocollatore.getEtichetta() :
+xse.toString());
}
return method;
}
protected synchronized Etichetta Etichetta ( ) {
if(set){
protocollo.AddOne();
Etichetta e = new Etichetta(protocollo.getValue());
return e;
} else return null;
}
}
The client class for this service:
public class ProtocolClient {
public static OMElement getEtichetta() throws AxisFault {
OMElement payload = getNewOMElement(Etichetta);
OMElement result = doIt(payload, getEtichetta);
return result;
}
private static EndpointReference targetEPR =
new EndpointReference(
http://localhost:8180/axis2/services/ProtocolService;);
public static void main(String[] args) {
try {
OMElement payload = getNewOMElement(Vuoto);
OMElement result = getEtichetta();
String response = result.getFirstElement().getText();
} catch (Exception e) {
e.printStackTrace();
}
}
private static OMElement doIt(OMElement payload, String action) throws
AxisFault {
Options options = new Options();
options.setTo(targetEPR);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setAction(urn:+action);
ServiceClient sender = new ServiceClient();
sender.setOptions(options);
Re: WSDL2JAVA does not generate WebServiceProxy
Seems the WSDL we see here maybe distorted. Can you reattach it. Thanks Lahiru On 10/10/07, Dário Abdulrehman [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am using WSDL2JAVA via the Eclipse plugin to generate a WS Client. Usually it generates 5 Java Classes: Foo.java FooBindingStub.java FooProxy.java FooService.java FooServiceLocator.java However my wsdl does not generate the FooProxy.java class and I can't figure what may be wrong. Any help would be appreciated. Here is the wsdl: targetNamespace= http://incm.pt/xi/PSP/Anexos; xmlns:p1=http://incm.pt/xi/PSP/Anexos; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/ xmlns=http://incm.pt/xi/PSP/Anexos; xmlns:xsd=http://www.w3.org/2001/XMLSchema source= http://sap.com/xi/TextID; 1fd5ea5057cc11dc86c1000d9d95b523 Número de Processo source=http://sap.com/xi/TextID; 1fd5ea5157cc11dcc877000d9d95b523 1: Cartão Plástico / 2: Certificados /3: Notificações / 4: Caderneta / 5:Carta PIN source=http://sap.com/xi/TextID; 1fd5ea5257cc11dc805c000d9d95b523 Identifica o layout source= http://sap.com/xi/TextID; 1fd5ea5357cc11dcb247000d9d95b523 U: Urgente / N: Normal source=http://sap.com/xi/TextID 1fd5ea5457cc11dcb0a9000d9d95b523 source= http://sap.com/xi/TextID; 1fd5ea5557cc11dcc197000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5657cc11dca185000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5757cc11dc82ed9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5857cc11dcbd35000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5957cc11dcbb05000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5a57cc11dcbf2c000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5b57cc11dcba71000d9d95b523 source=http://sap.com/xi/TextID; 1fd5ea5c57cc11dcb7d5000d9d95b523 source= http://sap.com/xi/TextID; 5de9a39057cc11dc8844000d9d95b523 Número de Processo de Pedido de CC source=http://sap.com/xi/TextID 5de9a39157cc11dc9b7d000d9d95b523 source= http://sap.com/xi/TextID; 5de9a39257cc11dc8df8000d9d95b523 source= http://sap.com/xi/TextID; 5de9a39357cc11dcbb01000d9d95b523 source=http://sap.com/xi/TextID; 5de9a39457cc11dc8de3000d9d95b523 source=http://sap.com/xi/TextID; 5de9a39557cc11dcc5f1000d9d95b523 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; / type=p1:pspAnexosCartoes_out xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; transport= http://schemas.xmlsoap.org/soap/http; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; / soapAction=http://sap.com/xi/WebService/soap1.1; xmlns:soap= http://schemas.xmlsoap.org/wsdl/soap/; / xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; / binding=p1:pspAnexosCartoes_outBinding xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/ location=http://xidev.incm.pt:50100/XISOAPAdapter/MessageServlet?channel=:CV:SenderChannel_SOAP_AnexosCartoesamp;version=3.0amp;Sender.Service=xamp;Interface=x%5Exhttp://xidev.incm.pt:50100/XISOAPAdapter/MessageServlet?channel=:CV:SenderChannel_SOAP_AnexosCartoesversion=3.0Sender.Service=xInterface=x%5Ex xmlns:soap= http://schemas.xmlsoap.org/wsdl/soap/; / - -- Dário Abdulrehman PGP Public
RE: Sending attachments to .NET Client
Let me give you an example indicating the way I have implemented MTOM attachment transmission between .NET (client) and J2EE (Server). Assume that you want to send an image as MTOM attachment. First write an interface or Class on service side with the following method: DataHandler getImage(String name); Use Java2WSDL tool to generate WSDL and then WSDL2Java to generate skeleton. Implement the logic of converting the image bytes into Datahandler either in skeleton or in your business components. Then on client side create proxy class and call getImage() method. The return type of this method would be byte[]. Now u can use this array to retrieve the image. I hope this will help you. Regards, Ashish, -Original Message- From: Raghavan [mailto:[EMAIL PROTECTED] Sent: Thursday, October 11, 2007 9:32 AM To: axis-user@ws.apache.org Subject: RE: Sending attachments to .NET Client Importance: High Thanks Arya. Could you please guide me to some sample java code as well as .NET client code for the MTOM attachments.. Rgds, Raghavan.V. -Original Message- From: Ashish Arya [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 10, 2007 1:43 PM To: axis-user@ws.apache.org Subject: RE: Sending attachments to .NET Client Raghvan, To solve the problem of sending attachments between .NET and Java, you can choose MTOM attachments. In that way your server code (Java) will deal with DataHanlder object while your client code (.NET) will deal with byte array. I have done that and it's working fine. Regards, Ashish Arya, Sungard Offshore Services (India) -Original Message- From: Raghavan [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 10, 2007 12:50 PM To: axis-user@ws.apache.org Subject: Sending attachments to .NET Client Importance: High Hi all, We have a java web service which has to send an image file as attachment to a .NET compact framework client. I followed the tutorials available in the internet. All the code available in the internet returns the attachment to the client as OMElement. But since .NET compact framework does not support OMElement, we need some other way for sending the attachments. Is it possible to send the attachment as java object? If so how? Any help would be appreciated. Thanks in Advance, Raghavan.V. - 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]
RE: Sending attachments to .NET Client
Thanks Arya.. Will try ur steps... Rgds, Raghavan.V. -Original Message- From: Ashish Arya [mailto:[EMAIL PROTECTED] Sent: Thursday, October 11, 2007 10:22 AM To: axis-user@ws.apache.org Subject: RE: Sending attachments to .NET Client Let me give you an example indicating the way I have implemented MTOM attachment transmission between .NET (client) and J2EE (Server). Assume that you want to send an image as MTOM attachment. First write an interface or Class on service side with the following method: DataHandler getImage(String name); Use Java2WSDL tool to generate WSDL and then WSDL2Java to generate skeleton. Implement the logic of converting the image bytes into Datahandler either in skeleton or in your business components. Then on client side create proxy class and call getImage() method. The return type of this method would be byte[]. Now u can use this array to retrieve the image. I hope this will help you. Regards, Ashish, -Original Message- From: Raghavan [mailto:[EMAIL PROTECTED] Sent: Thursday, October 11, 2007 9:32 AM To: axis-user@ws.apache.org Subject: RE: Sending attachments to .NET Client Importance: High Thanks Arya. Could you please guide me to some sample java code as well as .NET client code for the MTOM attachments.. Rgds, Raghavan.V. -Original Message- From: Ashish Arya [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 10, 2007 1:43 PM To: axis-user@ws.apache.org Subject: RE: Sending attachments to .NET Client Raghvan, To solve the problem of sending attachments between .NET and Java, you can choose MTOM attachments. In that way your server code (Java) will deal with DataHanlder object while your client code (.NET) will deal with byte array. I have done that and it's working fine. Regards, Ashish Arya, Sungard Offshore Services (India) -Original Message- From: Raghavan [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 10, 2007 12:50 PM To: axis-user@ws.apache.org Subject: Sending attachments to .NET Client Importance: High Hi all, We have a java web service which has to send an image file as attachment to a .NET compact framework client. I followed the tutorials available in the internet. All the code available in the internet returns the attachment to the client as OMElement. But since .NET compact framework does not support OMElement, we need some other way for sending the attachments. Is it possible to send the attachment as java object? If so how? Any help would be appreciated. Thanks in Advance, Raghavan.V. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
