Re: Services.xml
Raghavendra SM wrote: Hi Samisa, Please find the server code below, which is causing the problems as described by Manoj Rao. Please let me know if need more information than this. These are the skeleton functions of the server. I think I found the problem. In your my_svc_skeleton_ops_var variable, you have provided my_invoke as the invoke function. However, in your source, there is no such function, rather a function named acc_invoke. I think you have to rename acc_invoke to my_invoke and try. Also in the my_init function, you do not need to initialize svc_skeleton-func_array. You can safely comment whole of my_init function, leaving only the return AXIS2_SUCCESS; line in there. HTH. Thanks, Samisa... -- Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Support for PUT/DELETE in Axis2/C
Hello, I am new to Axis2/C and a basic question 1. When creating a RESTful web service using Axis2/C, can a web service be called using HTTP PUT rather than GET or POST. From whatever I have read, Axis2/C supports GET and POST but I haven't read anything about PUT or DELETE. The webservice will be written using Axis2/C but it will be called by multiple clients using Java, c#, Ruby etc Thanks in advance! Subra
Re: [Axis2/C] Attachments in Axis2/C
Hello Samisa, Thanks for the quick reply. Your answers are helping me understand whats doable and whats not. One of the requirements for the project that I am working on is that we have to let the clients make REST calls to our web service. Having said that, one more clarification. Pls tell me if this is theoretically possible to achieve in Axis2/C. And I apologize in advance if what I am saying doesn't make much sense: -- I will have a Axis2/C web service with REST enabled. -- A non Axis2/C client would make a REST (HTTP POST) call to this web service with a MIME attachment (along with some other parameters that tell the WS what to do with the attachment). -- Axis2/C framework on the server side delivers this request to the server code as a SOAP message. -- The code retrieves the attachment and the other parameters, processes the request and returns a response. Please let me know if what I said makes sense and if its doable. Thanks a lot for your help!! Subra On 7/26/07, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Subra A Narayanan wrote: Hello folks, Another newbie question: From what I understand, when a web service is called in a RESTful way, Axis2/C framework intercepts and automatically puts the parameters in a SOAP envelop before delivering it to the web service code. This means that a as far as the WS code goes, all client calls are SOAP calls. Now MTOM is specifically for SOAP. So how can a Axis2/C web service which is called my lets say a .Net client in a RESTful way, make use of MTOM since as far as the client goes, there is no SOAP involved. If the client wants to do MTOM with server, then the client got to use SOAP, because MTOM is for SOAP anyway. You cannot do MTOM with REST. How do we handle attachments in such cases on the client side and server side? Any simple server side example would be much appreciated. I am not sure how REST deals with attachments. Axis2/C currently only supports the MTOM way of attachments. Hence there is no way as of now that you can make a REST client access attachments with an Axis2/C service doing MTOM. Samisa... Subra -- Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Services.xml
Hi Samisa,
Please find the server code below, which is causing the problems as
described by Manoj Rao. Please let me know if need more information than
this.
These are the skeleton functions of the server.
--
33 int AXIS2_CALL
34 my_init(axis2_svc_skeleton_t *svc_skeleton,
35 const axutil_env_t *env)
36 {
37 SpsErrorLog(\nSPSAS: Entered my_init()\n);
38 fflush(stdout);
39 svc_skeleton-func_array = axutil_array_list_create(env, 0);
40 axutil_array_list_add(svc_skeleton-func_array, env,
(void*)create);
41 axutil_array_list_add(svc_skeleton-func_array, env,
(void*)delete);
42 axutil_array_list_add(svc_skeleton-func_array, env,
(void*)update);
43
44 /* Any initialization stuff goes here */
45 return AXIS2_SUCCESS;
46 }
48 int AXIS2_CALL
49 my_free(axis2_svc_skeleton_t *svc_skeleton,
50 const axutil_env_t *env)
51 {
52 TraceLog(\n[AG-DEBUG] entered my_free\n);
53 fflush(stdout);
54
66 if(svc_skeleton)
67 {
68 AXIS2_FREE((env)-allocator, svc_skeleton);
69 svc_skeleton = NULL;
70 }
71 return AXIS2_SUCCESS;
72 }
77 axiom_node_t* AXIS2_CALL
78 acc_invoke(axis2_svc_skeleton_t *svc_skeleton,
79 const axutil_env_t *env,
80 axiom_node_t *node,
81 axis2_msg_ctx_t *msg_ctx)
82 {
83fflush(stdout);
85 /* Depending on the function name invoke the
86 * corresponding method
87 */
88 if (node)
89 {
90 if (axiom_node_get_node_type(node, env) == AXIOM_ELEMENT)
91 {
92 axiom_element_t *element = NULL;
93 element = (axiom_element_t
*)axiom_node_get_data_element(node, env);
94 if (element)
95 {
96 axis2_char_t *op_name =
axiom_element_get_localname(element, env);
97 if (op_name)
98 {
99 if ( axutil_strcmp(op_name, create) == 0 )
100 return axis2_my_create1(env, node);
101 if ( axutil_strcmp(op_name, delete) == 0 )
102 return axis2_my_delete1(env, node);
103 if ( axutil_strcmp(op_name, modify) == 0 )
104 return axis2_my_modify1(env, node);
105 if ( axutil_strcmp(op_name, readList) == 0 )
106 return axis2_my_readList(env, node);
107 }
108 }
109 }
110 }
111 else
112 {
113 ErrorLog(ERROR: invalid OM parameters in request\n);
114 }
115
116 /** TODO: return a SOAP fault here */
117 return node;
118 }
119static const axis2_svc_skeleton_ops_t my_svc_skeleton_ops_var =
{
120 my_init,
121 my_invoke,
122 NULL,
123 my_free
124 };
125
126 axis2_svc_skeleton_t *
127 axis2_my_create(const axutil_env_t *env)
128 {
129
132 axis2_svc_skeleton_t *svc_skeleton = NULL;
133 svc_skeleton = (axis2_svc_skeleton_t*)
AXIS2_MALLOC((env)-allocator,
134 sizeof(axis2_svc_skeleton_t));
135
136
137 svc_skeleton-ops = (axis2_svc_skeleton_ops_t*)AXIS2_MALLOC(
138 (env)-allocator, sizeof(axis2_svc_skeleton_ops_t));
139
140 svc_skeleton-func_array = NULL;
141 svc_skeleton-ops = my_svc_skeleton_ops_var;
142
150 return svc_skeleton;
151 }
157 AXIS2_EXPORT int axis2_get_instance(struct axis2_svc_skeleton
**inst,
158 const axutil_env_t *env)
159 {
160 SpsTraceLog(\nCalling dlopen() inside axis2_get_instance\n);
161 ptr = dlopen(/root/lib/libMy.so,RTLD_LAZY|RTLD_GLOBAL);
162 if(NULL == ptr)
163 {
164 SpsErrorLog(\ndlopen returned NULL);
165 SpsErrorLog(\nFor dlopen()...dlerror says the
following\n%s\n,dlerror());
166 }
167 SpsTraceLog(\ndlopen returned ptr with addr %u,ptr);
168
169
170 *inst = axis2_my_create(env);
171 if(NULL == (*inst))
172 {
173 return AXIS2_FAILURE;
174 }
175
176 return AXIS2_SUCCESS;
177 }
178
179 AXIS2_EXPORT int axis2_remove_instance(axis2_svc_skeleton_t *inst,
180 const axutil_env_t *env)
181 {
182 axis2_status_t status = AXIS2_FAILURE;
183 if (inst)
184 {
185 status = AXIS2_SVC_SKELETON_FREE(inst, env);
186 }
187 return status;
188 }
Regards,
~raghav
-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 26, 2007 8:38 AM
To: Apache AXIS C User List
Subject: Re: Services.xml
Is it possible for you to send the server code?
I can try it and see what is going wrong.
Thanks,
Samisa...
Manoj Rao wrote:
Hi all,
What are the major differences in the logic of
basic http authentication
Hello, I'm trying to use basic http authentication with Axis2/c. I know when using the WSDL2Java tool with Axis1, it provides me with methods for setting the username and password. More specifically, they are setUsername and setPassword. The username token is then sent within the http header (not SOAP header). When I use the WSDL2C tool with Axis2, these methods are not generated. Is there a way to generate these methods with Axis2/C? Thanks, Mike Michael J Molé Software Engineer IBM Software Group - Rational (781)676-2710
RE: Services.xml
Oh Sorry, acc_invoke was a typo error, and it actually is my_invoke. Even then I face the same problem. Please take another look let us know if you need more information of any sort. Regards, ~raghav -Original Message- From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] Sent: Friday, July 27, 2007 6:53 AM To: Apache AXIS C User List Subject: Re: Services.xml Raghavendra SM wrote: Hi Samisa, Please find the server code below, which is causing the problems as described by Manoj Rao. Please let me know if need more information than this. These are the skeleton functions of the server. I think I found the problem. In your my_svc_skeleton_ops_var variable, you have provided my_invoke as the invoke function. However, in your source, there is no such function, rather a function named acc_invoke. I think you have to rename acc_invoke to my_invoke and try. Also in the my_init function, you do not need to initialize svc_skeleton-func_array. You can safely comment whole of my_init function, leaving only the return AXIS2_SUCCESS; line in there. HTH. Thanks, Samisa... -- Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2/C] Attachments in Axis2/C
Subra A Narayanan wrote: Hello folks, Another newbie question: From what I understand, when a web service is called in a RESTful way, Axis2/C framework intercepts and automatically puts the parameters in a SOAP envelop before delivering it to the web service code. This means that a as far as the WS code goes, all client calls are SOAP calls. Now MTOM is specifically for SOAP. So how can a Axis2/C web service which is called my lets say a .Net client in a RESTful way, make use of MTOM since as far as the client goes, there is no SOAP involved. If the client wants to do MTOM with server, then the client got to use SOAP, because MTOM is for SOAP anyway. You cannot do MTOM with REST. How do we handle attachments in such cases on the client side and server side? Any simple server side example would be much appreciated. I am not sure how REST deals with attachments. Axis2/C currently only supports the MTOM way of attachments. Hence there is no way as of now that you can make a REST client access attachments with an Axis2/C service doing MTOM. Samisa... Subra -- Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: error with configure script on solaris 9
Hi Sharada,' Do you have pkg-config installed in your system. (you can verify by executing pkg-config command). If not you can install it and then try to execute configure. If pkg-config is already in your system try setting the environment variable PKG_CONFIG to the absolute path of the pkg-config binary before executing configure. Thanks -sahan On 7/27/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, Getting the error below while running ./configure --enable-openssl=yes script on solaris9. I am trying to build the latest source from http://people.apache.org/dist/axis2/nightly/c/. What do I have to do to fix the error? checking for LIBXML2... configure: error: The pkg-config script could not be found or is too old. Make sure it is in your PATH or set the PKG_CONFIG environment variable to the full path to pkg-config. Alternatively, you may set the environment variables LIBXML2_CFLAGS and LIBXML2_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. To get pkg-config, see http://www.freedesktop.org/software/pkgconfig. See `config.log' for more details. configure: error: /bin/bash './configure' failed for axiom Thanks Sharada The contents of this email are the property of the sender. If it was not addressed to you, you have no legal right to read it. If you think you received it in error, please notify the sender. Do not forward or copy without permission of the sender. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 byte[] transfer/serialization bug ?!
Georgi
The DataHandler is a wrapper around any type of data source. Its
documented here:
http://java.sun.com/j2ee/1.4/docs/api/javax/activation/DataHandler.html
We provide (in Axiom) a DataSource that works with an existing byte[]:
So if you have byte[] bytes you can just do:
import javax.activation.DataHandler;
import org.apache.axiom.attachments.ByteArrayDataSource;
DataHandler dh = new DataHandler(new ByteArrayDataSource(bytes));
If your POJO exposes the DataHandler, instead of the bytes, it will
still map to xs:base64Binary but it can be used more efficiently.
That doesn't get you a lot because you still have the bytes in memory
- so if this is very large (many Mb or even Gb) you will run out of
heap.
However, if the data is on disk you can use:
http://java.sun.com/j2ee/1.4/docs/api/javax/activation/FileDataSource.html
And now Axis2 can directly stream the data off the disk onto the wire
- pretty cool huh?
Paul
On 7/26/07, Georgi Yonchev [EMAIL PROTECTED] wrote:
Thilina Gunarathne wrote:
Looks like a bug... Please report a JIRA...
You may also try replacing byte[] with javax.activation.DataHandler...
DataHandler is the recommended way when using large attachments...
thanks,
Thilina
On 7/24/07, Georgi Yonchev [EMAIL PROTECTED] wrote:
Thilina Gunarathne wrote:
and Deepal, yes works fine, but try it with larger byte[] size,
with larger, in the payload goes array from bytes ?!
not encoded in base64 ..
Not clear what you meant?... Do they go as native binary in the form
of an attachment or inside the soap body...
Thanks,
Thilina
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
inside in the soap body, the bytes are not encoded in base64, is
represented like integers
this is a part of the xml :
ns:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData115/ns:byteDatans:byteData105/ns:byteDatans:byteData122/ns:byteDatans:byteData101/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData49/ns:byteDatans:byteData48/ns:byteData
ns:byteData112/ns:byteDatans:byteData116/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData119/ns:byteDatans:byteData101/ns:byteDatans:byteData105/ns:byteDatans:byteData103/ns:byteDatans:byteData104/ns:byteDatans:byteData116/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData110/ns:byteDatans:byteData111/ns:byteDatans:byteData114/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData125/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData46/ns:byteDatans:byteData99/ns:byteDatans:byteData111/ns:byteDatans:byteData110/n
s:byteDatans:byteData
2000
116/ns:byteDatans:byteData101/ns:byteDatans:byteData110/ns:byteData
this happens only when i set the byte[] in Complex return object
class Result{
private byte[] bytes;
set..
get..
}
and the call likes:
public Res test(){
..set byte[] in res
return res;
}
if the call is :
public byte[] test(){
..
}
everything goes well...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Thilina,
i report it on JIRA, and is fixed on both tags/branches in the svn...
can you give some hints about this DataHandler ...
some example how to implement it,
10x a lot in advance :)
George
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
Oxygenating the Web Service Platform, www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 send xsi types
Hi all, How I can send schema xsi types from Axis2 so as to do polymorphism on the client? Thanks in advance, Jose - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Re: [Axis2] Making objects available on the response MessageContext (1.3-RC2) [SEC=UNCLASSIFIED]
No need to create a JIRA , I fixed the issues and commit to both trunk and the branch. Thanks Deepal Deepal jayasinghe wrote: Hi please create a JIRA (if possible please attach test case as well). Thanks Deepal Hello, We have just upgraded our application to the new Axis2 1.3-RC2 version to do some testing, but we're getting an exception. The exception is thrown in the application code, during a service operation call. It happens when a certain object can't be found on the message context for a SOAP response - we have created an Axis2 response handler that expects this object to be there. Currently before we calling the service operation we set this object onto the Options object that we obtain from the ServiceClient. In Axis2 1.2, this seems to make the object available on the response MessageContext for response handlers to access. However in 1.3-RC2, the object isn't available on the response MessageContext any more. I think that what we are doing (i.e. setting the object onto the Options object to make it available to response handlers) is incorrect, but it was working because of some code in Axis1.2 that has since been refactored. My question is: Is there a recommended way to make objects available on the response MessageContext? (so they can be accessed by response handlers). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 send xsi types
if you use ADB data binding at the client it should support this feature. when sending the request it sets the xsi:type correctly and parse it accordingly. Amila. On 7/26/07, Jose Luis Alba [EMAIL PROTECTED] wrote: Hi Deepal, I'm using POJO web services. All the in-out messages are managed by Axis engine, then I don't wrote the response messages. Is there any configuration parameter or I've to do something different so as to Axis sends the xsi types? Thanks Jose *Deepal Jayasinghe [EMAIL PROTECTED]* escribió: Hi Jose, You can send them as below; 10 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true / xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true / Hi all, How I can send schema xsi types from Axis2 so as to do polymorphism on the client? Thanks in advance, Jose Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . -- Thanks, Deepal The highest tower is built one brick at a time - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://us.rd.yahoo.com/mail/es/tagline/beabetter/*http://advision.webevents.yahoo.com/reto/entretenimiento.html . -- Amila Suriarachchi, WSO2 Inc.
[AXIS2] Fault Message
Hi all, i want create a MessageContext with an error. I tryed this: msgCtx.getEnvelope().getBody().addFault(new AxisFault(MyError)); But nothing happens, the body don't change. I'm trying to replicate this command org.apache.axis.Message(new AxisFault(MyError)); Where is the error? Thx - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: From Axis to Axis
Hello Demetris, Ann Manes (above-the-call-of-duty) rewrote my Axis1.4 WSDL (rpc-encoded) as so-called wrappered to assume the document-literal binding. And, Viola!, the WSDL2JAVA tool migrated the Axis1.4 code to Axis2. The only caveat is: the client has to be migrated likewise. HTH, David. Demetris G wrote .. Hi all, I asked this question once before and although a bit broad I thought I would hear something back. I am trying my luck once again - I see and hear poor souls out there struggling with real old versions of Axis and my guess is that migrating to Axis2 is a bit scary for them. Can anyone summarize what any Axis 1.X users can do to slowly make the move to Axis 2 ? Are we talking about a complete re-engineering of their designs or is there hope to migrate a bit smoother. And if this question (and I wouldn't be surprised) has been answered before then by all means, apologies, I will revert to the archives. And by the way - I wrote lots of code in Axis 1.4 and I am pretty happy with the results ... Cheers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Speak Now or Forever Hold Your Peace!
So am I correct in assuming this is branch: axis2-1.3-SNAPSHOT-war.zip axis2-1.3-SNAPSHOT-src.zip axis2-1.3-SNAPSHOT-war.zip And this is head? axis2-SNAPSHOT-bin.zip axis2-SNAPSHOT-src.zip axis2-SNAPSHOT-war.zip FYI, hope to finish testing the parts I use - spring, xmlbeans and the soapmonitor - along with some doc updates today but no later than tomorrow. Robert On 7/26/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Folks, We've cut 2 RC's for 1.3 release and nightlies are up and running for the 1.3 branch as well *PLEASE* test your scenarios with the latest RC and/or nightly and log a JIRA bug with all details needed to recreate your problem if you see something wrong. 1.3 RC2 - http://people.apache.org/~deepal/axis2/1.3-RC2/ 1.3 Branch Trunk Nightly - http://people.apache.org/dist/axis2/nightly/ JIRA - https://issues.apache.org/jira/browse/AXIS2 If 1.3 Final does not work for you when we cut it, it's your own fault :) If you have a JIRA that has not gotten the attention it deserves, please speak up and let us know. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] SOAPMonitorApplet port
Hi Robert, Only the Java executable (javaw.exe) is using the port. It does not matter what port I set in web.xml - it is always in use by the Java executable. I thought I could find an open port, but it does not seem to matter which one I use. It is *always* taken by javaw.exe. It''s almost like Axis2 is reserving the port and then trying to use it again, causing the bind error. Thanks, T robert lazarski [EMAIL PROTECTED] wrote: What is connected to 3901 ? There's 65,000 or so ports, so I'm sure you should be able to find one of them open ;-) . HTH, Robert On 7/26/07, Jack Sprat wrote: Hi Robert. I used ActivePorts for Windows, as suggested earlier. This showed the port specified in web.xml as occupied by javaw.exe. What could be the problem here? Thanks again for trying to help. T robert lazarski wrote: I'm not a windows user, but you do have the netstat command that can help you track your occupied ports. On linux it'd be 'netstat -ancp | grep 5001' . You can engage the module in either services.xml or axis2.xml - but not both. engaging in axis2.xml make the module available for all services, whereas alternatively engaging in the services,xml makes to module available to just that service. If all else fails, you could use tcpmon as an alternative. HTH, Robert On 7/25/07, Jack Sprat wrote: Hi Robert. Thanks for trying to help. This has me quite confused. The Tomcat console says that the server socket on the port specified in web.xml cannot be opened. If I set port 3901 then the console says port 3901 cannot be opened. Same for port 5001. The ports show as used by the javaw.exe process. My only other question on the SOAP monitor applet is where to set the module ref. I have this set in the services.xml file. This is the same as the logging module, with the instructions here: http://ws.apache.org/axis2/1_1/modules.html But the SOAP monitor page says to set the module reference in the axis2.xml file. Which is right? Axis2 with Tomcat 5.5 Thanks, T robert lazarski wrote: When you set the port to 3901, does it still say cannot connect to 5001? Can you try RC2? I'll try to give this scenario a spin today. HTH, Robert On 7/24/07, Jack Sprat wrote: I've tried ports 3901, 5001 and 5050. All gave the same result. robert lazarski wrote: Have you tried changing to another port in the web.xml? HTH, Robert On 7/24/07, Jack Sprat wrote: I've followed the instructions for setting up the SOAP monitor applet here: http://ws.apache.org/axis2/1_2/soapmonitor-module.html Whenever I start my server I get the following errors: 2007-07-24 18:18:20,468 ERROR SOAPMonitorService - Unable to open server socket using port: 5001 2007-07-24 18:18:20,484 ERROR SOAPMonitorService - Address already in use: JVM_Bind It does not seem to matter what port is used. What am I doing wrong? Thanks, T - Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out.
Re: [Axis2] Speak Now or Forever Hold Your Peace!
Please add a comment there asking for the priority to be set as blocker. thanks, dims On 7/26/07, Nadir Amra [EMAIL PROTECTED] wrote: dims, how about http://issues.apache.org/jira/browse/AXIS2-3017 ( I even attached a very simple example that illustrates the problem). Nadir K. Amra Davanum Srinivas [EMAIL PROTECTED] wrote on 07/26/2007 07:59:30 AM: Folks, We've cut 2 RC's for 1.3 release and nightlies are up and running for the 1.3 branch as well *PLEASE* test your scenarios with the latest RC and/or nightly and log a JIRA bug with all details needed to recreate your problem if you see something wrong. 1.3 RC2 - http://people.apache.org/~deepal/axis2/1.3-RC2/ 1.3 Branch Trunk Nightly - http://people.apache.org/dist/axis2/nightly/ JIRA - https://issues.apache.org/jira/browse/AXIS2 If 1.3 Final does not work for you when we cut it, it's your own fault :) If you have a JIRA that has not gotten the attention it deserves, please speak up and let us know. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - 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] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [1.3-RC2] Build JAX-WS server from wsdl in maven2 project
Farrukh, You can use WSDLJava.bat/sh from the command line (either nightly or 1.3 RC2) with -d jaxbri to select the JAXB RI as the data binding. -- dims On 7/26/07, Farrukh S. Najmi [EMAIL PROTECTED] wrote: Davanum Srinivas wrote: Farrukh, I just updated the ant task and maven2 mojo this morning :) docs are still in the works. will try to post something as soon as possible. Sounds good. Do you advice building against latest svn bits? Also, is it possible to use JAXB RI from Sun with Axis 2? Thanks again for your help. -- Regards, Farrukh Web: http://www.wellfleetsoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [1.3-RC2] Build JAX-WS server from wsdl in maven2 project
Davanum Srinivas wrote: Farrukh, I just updated the ant task and maven2 mojo this morning :) docs are still in the works. will try to post something as soon as possible. Sounds good. Do you advice building against latest svn bits? Also, is it possible to use JAXB RI from Sun with Axis 2? Thanks again for your help. -- Regards, Farrukh Web: http://www.wellfleetsoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[1.3-RC2] Build JAX-WS server from wsdl in maven2 project
Hello, I am a newbie to Axis2 and looking for a sample and/or bootstrap instructions on creating a service from a WSDL 2.0 source within a maven 2 project. In particular I am not finding wsdl4j:wsdl4j:pom:1.6.2 anywhere. Unfortunately I am unable to find docs, archived emails or wiki entries to help me in my quest. In fact, I am even not finding docs for Axis2 1.3-RC2 so I suspect I missing something obvious. Thanks for your help and sorry if I missed something. -- Regards, Farrukh Web: http://www.wellfleetsoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
any working example of WSE 3.0 WS-1 webservice and apache axis 2 client
I need to create a java client that will access a .net web service using WSE3.0 . The web service is secured using x509 certificates. I dont know how I can connect to it using apache axis. Does anyone has a working sample Hello Word program that shows apache axis client connecting to secured .net web services using x509 certificates. Thanks Shantanu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] accessing a policy-secured webservice using a WSDL2Java client
thank you for the reply, Amila.
The example you provided is basically what I'm using, however I'm now
getting the error Could not validate signature using any of the supported
token types
I compared the weblogic debug logs when I hit it with a clientgen client
(works) and with my Axis2 client (not working)...everything seems almost
exact. The encryption algorithms listed are exactly the same, so its not
like I'm trying to use a different signature algorithm with Axis2.
The weblogic logs show that both the clientgen client and Axis2 client send
a signed timestamp, signed body, and signed token. The weblogic log with
the clientgen client however shows that it continues on with a message about
'trying to validate identity assertion token ~ x509' and that all works and
the client is allowed to connect.
I went so far as to modify my webService to remove the Auth policy leaving
only the Sign policy. I then tried Axis2 again and got the same error about
'could not validate signature using any of the supported token types'.
I greatly appreciate your response to my earlier message and I hope you can
help me debug this problem.
Brian
On 7/26/07, Amila Suriarachchi [EMAIL PROTECTED] wrote:
this is what you can do with the Axis2 and rampart
first geneate the code using wsdl2java tool use -u and -g options as well.
then get a rampart distribution and put all requried libs to the class
path (these comes with the rampart distributtion) and put the .mar files to
the repository modules.
Install full strength security jars (with out this some security
assertions does not work)
write the client code like this
ConfigurationContext confContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(AXIS2_REPOSITORY,
AXIS2_XML);
stub = new
PingService10MutualCertificate10SignEncrypt_IPingServiceStub(confContext);
stub._getServiceClient().engageModule(rampart);
// set the rampart config properties correctly
CryptoConfig signcriptoInfo = new CryptoConfig();
signcriptoInfo.setProvider(Merlin.class.getName());
Properties properties = new Properties();
properties.setProperty(
org.apache.ws.security.crypto.merlin.keystore.type , JKS);
properties.setProperty(org.apache.ws.security.crypto.merlin.file,
security_client_wcf/conf/sec.jks);
properties.setProperty(
org.apache.ws.security.crypto.merlin.keystore.password , password);
signcriptoInfo.setProp(properties);
CryptoConfig encriptcriptoInfo = new CryptoConfig();
encriptcriptoInfo.setProp(properties);
encriptcriptoInfo.setProvider (Merlin.class.getName());
RampartConfig config = new RampartConfig();
config.setUser(alice);
config.setEncryptionUser(bob);
config.setPwCbClass( util.PasswordCallbackHandler);
config.setSigCryptoConfig(signcriptoInfo);
config.setEncrCryptoConfig(encriptcriptoInfo);
ramapConfigPolicy = new Policy();
ramapConfigPolicy.addAssertion (config);
try {
stub._getServiceClient().getAxisService().getPolicyInclude().addPolicyElement(
PolicyInclude.ANON_POLICY, ramapConfigPolicy);
String result = stub.echo (Test String);
System.out.println(Result == + result);
} catch (RemoteException e) {
e.printStackTrace();
}
here stub refers to your generated stub.
AXIS2_REPOSITORY refers to your axis2 repository. this should have the
rampart mar files.
here you have to set the key store, user names and passwords as given
above.
You may have a password callback class like this with the correct user
names and passwords.
public class PasswordCallbackHandler implements CallbackHandler {
public void handle(Callback[] callbacks) throws IOException,
UnsupportedCallbackException {
for (int i = 0; i callbacks.length; i++) {
WSPasswordCallback pwcb = (WSPasswordCallback) callbacks[i];
String id = pwcb.getIdentifer();
if (alice.equals(id)) {
pwcb.setPassword (ecila);
} else if (bob.equals(id)) {
pwcb.setPassword(bob);
}
}
}
}
thanks,
Amila.
On 7/26/07, Brian Baldwin [EMAIL PROTECTED] wrote:
I've been using Axis1.x to access my webservice using WSDL2Java
generated
stubs...works great...I use the Locator class.
I've modified my webservice to use WS-Policy directives (Sign and Auth).
The WSDL has changed as expected to include the wsp:policy elements
for
Sign and Auth.
Do I need to use Axis2/Rampart to generate the client stubs and apply
the
encryption now that my webservice is using WS-Policy directives?
Is there an example for using Axis/Axis2 to access a policy-enabled web
service?
My webservice is deployed to WLS 9.2 and I can use weblogic's
clientgen-generated stubs to encrypt
ALEServiceMessageReceiverInOut 1.3-RC2
Hi!
After wsdl2java code generation you can see:
public class ALEServiceMessageReceiverInOut extends
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver{...
where AbstractInOutSyncMessageReceiver is marked as deprecated. What is the
right approach: use AbstractInOutSyncMessageReceiver? Something else?
Thanks,
Anton
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: From Axis to Axis
And thanks much to you David as well for the information below. I was expecting that some work at least will need to be done on the client side. david wrote: Hello Demetris, Ann Manes (above-the-call-of-duty) rewrote my Axis1.4 WSDL (rpc-encoded) as so-called wrappered to assume the document-literal binding. And, Viola!, the WSDL2JAVA tool migrated the Axis1.4 code to Axis2. The only caveat is: the client has to be migrated likewise. HTH, David. Demetris G wrote .. Hi all, I asked this question once before and although a bit broad I thought I would hear something back. I am trying my luck once again - I see and hear poor souls out there struggling with real old versions of Axis and my guess is that migrating to Axis2 is a bit scary for them. Can anyone summarize what any Axis 1.X users can do to slowly make the move to Axis 2 ? Are we talking about a complete re-engineering of their designs or is there hope to migrate a bit smoother. And if this question (and I wouldn't be surprised) has been answered before then by all means, apologies, I will revert to the archives. And by the way - I wrote lots of code in Axis 1.4 and I am pretty happy with the results ... Cheers - 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: handleFault never invoked on server side
I am also having this problem. If I throw a JAXRPCException or a SOAPFaultException, a SOAP fault is not generated. Is this a bug in Axis 1.4? Anyone? mangoo4j wrote: I'm using Axis 1.4 on server side and implemented a handler extending javax.xml.rpc.handler.GenericHandler. I extended the method handleFault(MessageContext) to do some logging - but the method is never invoked. All exceptions inclusive details are returned to clients, but the method handleFault(MessageContext context) is never invoked. Any ideas why? Thanks. -- View this message in context: http://www.nabble.com/handleFault-never-invoked-on-server-side-tf3634196.html#a11815398 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] Speak Now or Forever Hold Your Peace!
Raghu, Did you try with Axis2 1.3 RC2? thanks, dims On 7/26/07, Raghu Upadhyayula [EMAIL PROTECTED] wrote: Hi Dims, I have a JIRA logged in long back Axis2-2352, the status shows as resolved, though it is not yet resolved. Thanks Raghu -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, July 26, 2007 6:00 AM To: [EMAIL PROTECTED]; axis-user@ws.apache.org Subject: [Axis2] Speak Now or Forever Hold Your Peace! Folks, We've cut 2 RC's for 1.3 release and nightlies are up and running for the 1.3 branch as well *PLEASE* test your scenarios with the latest RC and/or nightly and log a JIRA bug with all details needed to recreate your problem if you see something wrong. 1.3 RC2 - http://people.apache.org/~deepal/axis2/1.3-RC2/ 1.3 Branch Trunk Nightly - http://people.apache.org/dist/axis2/nightly/ JIRA - https://issues.apache.org/jira/browse/AXIS2 If 1.3 Final does not work for you when we cut it, it's your own fault :) If you have a JIRA that has not gotten the attention it deserves, please speak up and let us know. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ExtensionMapper
Hi, the problem is that the actual code generation blocks the use of the generated packages with common types by different web services because the generated ExtensionMappers are not identical if the web services do not share all XML/WSDL types. So it is not possible for me to write some common classes because the import of the common packages fails (except that I import all web services). Amila Suriarachchi schrieb: On 7/23/07, Michael Bell [EMAIL PROTECTED] wrote: this extension mapper is used in extensions(to support polymorphysum). if the input xml stream contains an xsi:type element then we find the corresponding class from using this. Keeping one extension mapper would make the code generation easy sine we have to find the class only in one place. other wise have to see in all the places. you can not say classes in one package has only extended from the class in the same package. I only see calls to the ExtensionMapper from classes which were generated for XML types. So it looks easy for me to modify the extension mapper in the correct way and place (this is what I do with my script). if you split the extension mapper class then you have to change the places it refer as well. some times if you only extends classes from the same package this may work. but not a genearalized approach. The ExtensionMapper is used in the generated type classes. These classes can be very easily fixed. My script looks into the classes and modify the package of the extension mapper. I don't understand which external code uses the extension mapper. Can you point me to an example please? Thanks Michael -- ___ Michael BellHumboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin ___ X.509 CA Certificates / Wurzelzertifikate http://ra.pki.hu-berlin.de smime.p7s Description: S/MIME Cryptographic Signature
Urgent Help is need, Axis1.1 -- C# (VS2005)
Hello Everybody, We have being trying to fix interoperablity issues, Axis1.1 to C#(VS2005), for last few days without much progress. I was asking some question for the same.. Any help is hightly appreciated. It's a kind of urgent. The below are the 5 services configured in WSDD file(RAD6). Only the Version service, which is very simple, is working well. But no other service is working as expected from C# client, Java client consuming the services without any issues. I have tested service1(Document/Lit) and service2(RPC/Lit), SOAP request is coming to severe and SOAP response is getting generated but client showing NULL response. In the service2(RPC/Lit) I included 'style=wrapped', but no change in the response. Here are couple of things that may be causing any issues(?) 1. wsdlTargetNamespace value is different from xmlns:ns in typeMapping element. Do I need to keep the same value for both? 2. There is complex data type like WSStrongItem[], does it make any issue? 3. In SOAP request, there is one element, name xmlns=smith/name, with xmlns is null. And in response also, xmlns is null like below. Is it okay? item xmlns= value xsi:type=ns1:DataSearchResult xmlns:ns1=http://ws.mtn.us; candidates soapenc:arrayType=ns1:DataSearchPerson[8] item birthDateEstimatedIndfalse/birthDateEstimatedInd deceasedIndfalse/deceasedInd genderCodeF/genderCode /item . . /item The Services : service name=Version provider=java:RPC parameter name=allowedMethods value=getVersion/ parameter name=className value=org.apache.axis.Version/ /service service name=service1 provider=java:RPC style=document use=literal parameter name=allowedMethods value=process/ parameter name=wsdlPortType value=WSService/ parameter name=className value=org.ws.WSService/ parameter name=wsdlServicePort value=service1port/ parameter name=wsdlTargetNamespace value=http://us.mtn/WS/services/service1/ parameter name=wsdlServiceElement value=WSService/ typeMapping deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle= qname=ns2707:WSFudge serializer=org.apache.axis.encoding.ser.BeanSerializerFactory type=java:org.ws.Fudge xmlns:ns2707=http://ws.mtn.us/ typeMapping deserializer=org.apache.axis.encoding.ser.ArrayDeserializerFactory encodingStyle= qname=ns2720:WSStrongItems serializer=org.apache.axis.encoding.ser.ArraySerializerFactory type=java:org.ws.WSStrongItem[] xmlns:ns2720=http://ws.mtn.us/ . . . /service service name=service2 provider=java:RPC use=literal parameter name=allowedMethods value=process/ parameter name=wsdlPortType value=WSService/ parameter name=className value=org.ws.WSService/ parameter name=wsdlServicePort value=service2port/ parameter name=wsdlTargetNamespace value=http://us.mtn/WS/services/service2/ parameter name=wsdlServiceElement value=WSService/ typeMapping deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle= qname=ns1723:WSFudge serializer=org.apache.axis.encoding.ser.BeanSerializerFactory type=java:org.ws.Fudge xmlns:ns1723=http://ws.mtn.us/ typeMapping deserializer=org.apache.axis.encoding.ser.ArrayDeserializerFactory encodingStyle= qname=ns1736:WSStrongItems serializer=org.apache.axis.encoding.ser.ArraySerializerFactory type=java:org.ws.WSStrongItem[] xmlns:ns1736=http://ws.mtn.us/ . . . /service service name=service3 provider=java:RPC style=document parameter name=allowedMethods value=process/ parameter name=wsdlPortType value=WSService/ parameter name=className value=org.ws.WSService/ parameter name=wsdlServicePort value=service3port/ parameter name=wsdlTargetNamespace value=http://us.mtn/WS/services/service3/ parameter name=wsdlServiceElement value=WSService/ typeMapping deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; qname=ns985:WSFudge serializer=org.apache.axis.encoding.ser.BeanSerializerFactory type=java:org.ws.Fudge xmlns:ns985=http://ws.mtn.us/ typeMapping deserializer=org.apache.axis.encoding.ser.ArrayDeserializerFactory encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; qname=ns998:WSStrongItems serializer=org.apache.axis.encoding.ser.ArraySerializerFactory type=java:org.ws.WSStrongItem[] xmlns:ns998=http://ws.mtn.us/ . . . /service service name=service4 provider=java:RPC parameter name=allowedMethods value=process/ parameter name=wsdlPortType value=WSService/ parameter name=className value=org.ws.WSService/ parameter name=wsdlServicePort value=service4port/ parameter name=wsdlTargetNamespace value=http://us.mtn/WS/services/service4/ parameter name=wsdlServiceElement value=WSService/ typeMapping deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory
Re: [Axis2] StackOverflowError after 3 hours stress campain
Fredric, What exactly does the stress tool does? call ?wsdl repeatedly? thanks, dims On 7/26/07, Frederic MOLINIERES [EMAIL PROTECTED] wrote: Hi, We use Axis2 v1.2 on tomcat 5.5.9. We use stress tools to ensure that axis works fine but 30 Vusers on 3 hours. [2007-07-25 19:02:25,536] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/axis2].[Axis Servle t].invoke :: Servlet.service() for servlet AxisServlet threw exception java.lang.StackOverflowError at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:384) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:146) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:204) at java.io.PrintWriter.write(PrintWriter.java:384) at java.io.PrintWriter.write(PrintWriter.java:384) at java.io.PrintWriter.write(PrintWriter.java:401) at java.io.PrintWriter.print(PrintWriter.java:532) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) Our axis configuration : transportReceiver name=http class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port6060/parameter !-- Here is the complete list of supported parameters (see example settings further below): port: the port to listen on (default 6060) hostname: if non-null, url prefix used in reply-to endpoint references (default null) originServer: value of http Server header in outgoing messages (default Simple-Server/1.1) requestTimeout: value in millis of time that requests can wait for data(default 2) requestTcpNoDelay: true to maximize performance and minimize latency (default true) false to minimize bandwidth consumption by combining segments requestCoreThreadPoolSize: number of threads available for request processing (unless queue fills up) (default 25) requestMaxThreadPoolSize: number of threads available for request processing if queue fills up (default 150) note that default queue never fills up: see HttpFactory threadKeepAliveTime: time to keep threads in excess of core size alive while inactive (default 180) note that no such threads can exist with default unbounded request queue threadKeepAliveTimeUnit: TimeUnit of value in threadKeepAliveTime (default SECONDS)(default SECONDS) -- !-- parameter name=hostnamehttp://www.myApp.com/ws/parameter -- !-- parameter name=originServerMy-Server/1.1/parameter -- parameter name=requestTimeout1/parameter parameter name=requestTcpNoDelaytrue/parameter !-- parameter name=requestCoreThreadPoolSize100/parameter -- !-- parameter name=RequestMaxThreadPoolSize300/parameter -- parameter name=threadKeepAliveTime3/parameter -- parameter name=threadKeepAliveTimeUnitMILLISECONDS/parameter -- /transportReceiver !--Uncomment this and configure as appropriate for JMS transport support, after setting up your JMS environment (e.g. ActiveMQ) transportReceiver name=jms class=org.apache.axis2.transport.jms.JMSListener parameter name=myTopicConnectionFactory parameter name=java.naming.factory.initialorg.apache.activemq.jndi.ActiveMQInitialC ontextFactory/parameter parameter name=java.naming.provider.urltcp://localhost:61616/parameter parameter name=transport.jms.ConnectionFactoryJNDINameTopicConnectionFactory/param eter /parameter parameter name=myQueueConnectionFactory parameter name=java.naming.factory.initialorg.apache.activemq.jndi.ActiveMQInitialC ontextFactory/parameter parameter name=java.naming.provider.urltcp://localhost:61616/parameter parameter name=transport.jms.ConnectionFactoryJNDINameQueueConnectionFactory/param eter /parameter parameter name=default parameter
[Axis2] StackOverflowError after 3 hours stress campain
Hi, We use Axis2 v1.2 on tomcat 5.5.9. We use stress tools to ensure that axis works fine but 30 Vusers on 3 hours. [2007-07-25 19:02:25,536] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/axis2].[Axis Servle t].invoke :: Servlet.service() for servlet AxisServlet threw exception java.lang.StackOverflowError at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:384) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:146) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:204) at java.io.PrintWriter.write(PrintWriter.java:384) at java.io.PrintWriter.write(PrintWriter.java:384) at java.io.PrintWriter.write(PrintWriter.java:401) at java.io.PrintWriter.print(PrintWriter.java:532) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source) Our axis configuration : transportReceiver name=http class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port6060/parameter !-- Here is the complete list of supported parameters (see example settings further below): port: the port to listen on (default 6060) hostname: if non-null, url prefix used in reply-to endpoint references (default null) originServer: value of http Server header in outgoing messages (default Simple-Server/1.1) requestTimeout: value in millis of time that requests can wait for data(default 2) requestTcpNoDelay: true to maximize performance and minimize latency (default true) false to minimize bandwidth consumption by combining segments requestCoreThreadPoolSize: number of threads available for request processing (unless queue fills up) (default 25) requestMaxThreadPoolSize: number of threads available for request processing if queue fills up (default 150) note that default queue never fills up: see HttpFactory threadKeepAliveTime: time to keep threads in excess of core size alive while inactive (default 180) note that no such threads can exist with default unbounded request queue threadKeepAliveTimeUnit: TimeUnit of value in threadKeepAliveTime (default SECONDS)(default SECONDS) -- !-- parameter name=hostnamehttp://www.myApp.com/ws/parameter -- !-- parameter name=originServerMy-Server/1.1/parameter -- parameter name=requestTimeout1/parameter parameter name=requestTcpNoDelaytrue/parameter !-- parameter name=requestCoreThreadPoolSize100/parameter -- !-- parameter name=RequestMaxThreadPoolSize300/parameter -- parameter name=threadKeepAliveTime3/parameter -- parameter name=threadKeepAliveTimeUnitMILLISECONDS/parameter -- /transportReceiver !--Uncomment this and configure as appropriate for JMS transport support, after setting up your JMS environment (e.g. ActiveMQ) transportReceiver name=jms class=org.apache.axis2.transport.jms.JMSListener parameter name=myTopicConnectionFactory parameter name=java.naming.factory.initialorg.apache.activemq.jndi.ActiveMQInitialC ontextFactory/parameter parameter name=java.naming.provider.urltcp://localhost:61616/parameter parameter name=transport.jms.ConnectionFactoryJNDINameTopicConnectionFactory/param eter /parameter parameter name=myQueueConnectionFactory parameter name=java.naming.factory.initialorg.apache.activemq.jndi.ActiveMQInitialC ontextFactory/parameter parameter name=java.naming.provider.urltcp://localhost:61616/parameter parameter name=transport.jms.ConnectionFactoryJNDINameQueueConnectionFactory/param eter /parameter parameter name=default parameter name=java.naming.factory.initialorg.apache.activemq.jndi.ActiveMQInitialC ontextFactory/parameter parameter
Re: [Axis2] Speak Now or Forever Hold Your Peace!
Stefan, Please try the same scenarios with nightly and open a JIRA bug if you would like them fixed. thanks, dims On 7/26/07, stlecho [EMAIL PROTECTED] wrote: Dims, - Is there a release of Rampart available that is compliant with this latest RC release ? - Not reported as JIRA issues, but quite annoying: http://www.nabble.com/-Axis2-1.1.1--Unable-to-generate-WSDL-for-this-service-tf3832868.html, http://www.nabble.com/-Axis2-1.1.1--Exception-generated-based-on-wsdl%3Afault-tf3876565.html#a10984514, http://www.nabble.com/-Axis2-Rampart--NullPointerException-when-calling-non-existing-Webservice-tf3926271.html#a11134524 Regards, Stefan Lecho. dims wrote: Folks, We've cut 2 RC's for 1.3 release and nightlies are up and running for the 1.3 branch as well *PLEASE* test your scenarios with the latest RC and/or nightly and log a JIRA bug with all details needed to recreate your problem if you see something wrong. 1.3 RC2 - http://people.apache.org/~deepal/axis2/1.3-RC2/ 1.3 Branch Trunk Nightly - http://people.apache.org/dist/axis2/nightly/ JIRA - https://issues.apache.org/jira/browse/AXIS2 If 1.3 Final does not work for you when we cut it, it's your own fault :) If you have a JIRA that has not gotten the attention it deserves, please speak up and let us know. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-Axis2--%22Speak-Now-or-Forever-Hold-Your-Peace%21%22-tf4151482.html#a11812287 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Speak Now or Forever Hold Your Peace!
I believe you can use Rampart nightly with Axis2 nightly http://people.apache.org/dist/rampart/nightly/ thanks dims On 7/26/07, stlecho [EMAIL PROTECTED] wrote: Dims, - Is there a release of Rampart available that is compliant with this latest RC release ? - Not reported as JIRA issues, but quite annoying: http://www.nabble.com/-Axis2-1.1.1--Unable-to-generate-WSDL-for-this-service-tf3832868.html, http://www.nabble.com/-Axis2-1.1.1--Exception-generated-based-on-wsdl%3Afault-tf3876565.html#a10984514, http://www.nabble.com/-Axis2-Rampart--NullPointerException-when-calling-non-existing-Webservice-tf3926271.html#a11134524 Regards, Stefan Lecho. dims wrote: Folks, We've cut 2 RC's for 1.3 release and nightlies are up and running for the 1.3 branch as well *PLEASE* test your scenarios with the latest RC and/or nightly and log a JIRA bug with all details needed to recreate your problem if you see something wrong. 1.3 RC2 - http://people.apache.org/~deepal/axis2/1.3-RC2/ 1.3 Branch Trunk Nightly - http://people.apache.org/dist/axis2/nightly/ JIRA - https://issues.apache.org/jira/browse/AXIS2 If 1.3 Final does not work for you when we cut it, it's your own fault :) If you have a JIRA that has not gotten the attention it deserves, please speak up and let us know. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-Axis2--%22Speak-Now-or-Forever-Hold-Your-Peace%21%22-tf4151482.html#a11812287 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
wsdl2java generates invalid xml file
Hi, I have a question about the wsdl2java plugin for eclipse. I used the wsdl2Java plugin to generate a wsdl file. I have a service class and an exceptionclass which are defined in different packages. When I generate the wsdl file, the plugin defines a second namespace in a second shema definition tag which causes the wsdl file to be invalid. If I define the exception in the same package as the service the plugin produces a correct wsdl file. Does the plugin support multiple namespaces? Thanx Babette
bean string attribute getting encoded as bytes?
Hi Am using Java Axis 1.3 and every now and then when there is a bean that has a single string attribute, the value gets encoded and sent across from the client as a base64Binary. (namespaces left out intentionally) fieldname bytesbase64encided value/bytes /fieldname instead of fieldname stringvalue /fieldname The WSDL specifically states that the field xsi:type=soapenc:string and has no information on base64/byte type in the WSDL. anyone have pointers on whats going on and how I can turn this encoding as base64 off? Sid
Re: [Axis2] Speak Now or Forever Hold Your Peace!
Dims, - Is there a release of Rampart available that is compliant with this latest RC release ? - Not reported as JIRA issues, but quite annoying: http://www.nabble.com/-Axis2-1.1.1--Unable-to-generate-WSDL-for-this-service-tf3832868.html, http://www.nabble.com/-Axis2-1.1.1--Exception-generated-based-on-wsdl%3Afault-tf3876565.html#a10984514, http://www.nabble.com/-Axis2-Rampart--NullPointerException-when-calling-non-existing-Webservice-tf3926271.html#a11134524 Regards, Stefan Lecho. dims wrote: Folks, We've cut 2 RC's for 1.3 release and nightlies are up and running for the 1.3 branch as well *PLEASE* test your scenarios with the latest RC and/or nightly and log a JIRA bug with all details needed to recreate your problem if you see something wrong. 1.3 RC2 - http://people.apache.org/~deepal/axis2/1.3-RC2/ 1.3 Branch Trunk Nightly - http://people.apache.org/dist/axis2/nightly/ JIRA - https://issues.apache.org/jira/browse/AXIS2 If 1.3 Final does not work for you when we cut it, it's your own fault :) If you have a JIRA that has not gotten the attention it deserves, please speak up and let us know. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-Axis2--%22Speak-Now-or-Forever-Hold-Your-Peace%21%22-tf4151482.html#a11812287 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] SOAPMonitorApplet port
Hi Robert. I used ActivePorts for Windows, as suggested earlier. This showed the port specified in web.xml as occupied by javaw.exe. What could be the problem here? Thanks again for trying to help. T robert lazarski [EMAIL PROTECTED] wrote: I'm not a windows user, but you do have the netstat command that can help you track your occupied ports. On linux it'd be 'netstat -ancp | grep 5001' . You can engage the module in either services.xml or axis2.xml - but not both. engaging in axis2.xml make the module available for all services, whereas alternatively engaging in the services,xml makes to module available to just that service. If all else fails, you could use tcpmon as an alternative. HTH, Robert On 7/25/07, Jack Sprat wrote: Hi Robert. Thanks for trying to help. This has me quite confused. The Tomcat console says that the server socket on the port specified in web.xml cannot be opened. If I set port 3901 then the console says port 3901 cannot be opened. Same for port 5001. The ports show as used by the javaw.exe process. My only other question on the SOAP monitor applet is where to set the module ref. I have this set in the services.xml file. This is the same as the logging module, with the instructions here: http://ws.apache.org/axis2/1_1/modules.html But the SOAP monitor page says to set the module reference in the axis2.xml file. Which is right? Axis2 with Tomcat 5.5 Thanks, T robert lazarski wrote: When you set the port to 3901, does it still say cannot connect to 5001? Can you try RC2? I'll try to give this scenario a spin today. HTH, Robert On 7/24/07, Jack Sprat wrote: I've tried ports 3901, 5001 and 5050. All gave the same result. robert lazarski wrote: Have you tried changing to another port in the web.xml? HTH, Robert On 7/24/07, Jack Sprat wrote: I've followed the instructions for setting up the SOAP monitor applet here: http://ws.apache.org/axis2/1_2/soapmonitor-module.html Whenever I start my server I get the following errors: 2007-07-24 18:18:20,468 ERROR SOAPMonitorService - Unable to open server socket using port: 5001 2007-07-24 18:18:20,484 ERROR SOAPMonitorService - Address already in use: JVM_Bind It does not seem to matter what port is used. What am I doing wrong? Thanks, T - Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out.
Re: Axis2 send xsi types
HI Amila, I'm using ADB clients and I've seen in the generated stub that he searches for the xsi schema. The problem is the response that sends the Axis server. How I do for send the xsi types? Thanks, Jose Amila Suriarachchi [EMAIL PROTECTED] escribió: if you use ADB data binding at the client it should support this feature. when sending the request it sets the xsi:type correctly and parse it accordingly. Amila. On 7/26/07, Jose Luis Alba [EMAIL PROTECTED] wrote: Hi Deepal, I'm using POJO web services. All the in-out messages are managed by Axis engine, then I don't wrote the response messages. Is there any configuration parameter or I've to do something different so as to Axis sends the xsi types? Thanks Jose Deepal Jayasinghe [EMAIL PROTECTED] escribió: Hi Jose, You can send them as below; 10 xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true / xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true / Hi all, How I can send schema xsi types from Axis2 so as to do polymorphism on the client? Thanks in advance, Jose Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . -- Thanks, Deepal The highest tower is built one brick at a time - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . -- Amila Suriarachchi, WSO2 Inc. - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Re: Axis2 send xsi types
Hi Deepal, I'm using POJO web services. All the in-out messages are managed by Axis engine, then I don't wrote the response messages. Is there any configuration parameter or I've to do something different so as to Axis sends the xsi types? Thanks Jose Deepal Jayasinghe [EMAIL PROTECTED] escribió: Hi Jose, You can send them as below; 10 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true / xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true / Hi all, How I can send schema xsi types from Axis2 so as to do polymorphism on the client? Thanks in advance, Jose Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . -- Thanks, Deepal The highest tower is built one brick at a time - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Re: Axis2 send xsi types
HI Amila, I'm using ADB clients and I've seen in the generated stub that he searches for the xsi schema. The problem is the response that sends the Axis server. How I do for send the xsi types? At the server side you can not set that , it will set that automatically. Please try with Axis2 1.3 RC2 , I think you will have what you want there. Thanks Deepal Thanks, Jose Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://us.rd.yahoo.com/mail/es/tagline/beabetter/*http://advision.webevents.yahoo.com/reto/entretenimiento.html. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] accessing a policy-secured webservice using a WSDL2Java client
this is what you can do with the Axis2 and rampart
first geneate the code using wsdl2java tool use -u and -g options as well.
then get a rampart distribution and put all requried libs to the class path
(these comes with the rampart distributtion) and put the .mar files to the
repository modules.
Install full strength security jars (with out this some security assertions
does not work)
write the client code like this
ConfigurationContext confContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(AXIS2_REPOSITORY,
AXIS2_XML);
stub = new
PingService10MutualCertificate10SignEncrypt_IPingServiceStub(confContext);
stub._getServiceClient().engageModule(rampart);
// set the rampart config properties correctly
CryptoConfig signcriptoInfo = new CryptoConfig();
signcriptoInfo.setProvider(Merlin.class.getName());
Properties properties = new Properties();
properties.setProperty(
org.apache.ws.security.crypto.merlin.keystore.type, JKS);
properties.setProperty(org.apache.ws.security.crypto.merlin.file,
security_client_wcf/conf/sec.jks);
properties.setProperty(
org.apache.ws.security.crypto.merlin.keystore.password, password);
signcriptoInfo.setProp(properties);
CryptoConfig encriptcriptoInfo = new CryptoConfig();
encriptcriptoInfo.setProp(properties);
encriptcriptoInfo.setProvider(Merlin.class.getName());
RampartConfig config = new RampartConfig();
config.setUser(alice);
config.setEncryptionUser(bob);
config.setPwCbClass(util.PasswordCallbackHandler);
config.setSigCryptoConfig(signcriptoInfo);
config.setEncrCryptoConfig(encriptcriptoInfo);
ramapConfigPolicy = new Policy();
ramapConfigPolicy.addAssertion(config);
try {
stub._getServiceClient().getAxisService().getPolicyInclude().addPolicyElement(
PolicyInclude.ANON_POLICY, ramapConfigPolicy);
String result = stub.echo(Test String);
System.out.println(Result == + result);
} catch (RemoteException e) {
e.printStackTrace();
}
here stub refers to your generated stub.
AXIS2_REPOSITORY refers to your axis2 repository. this should have the
rampart mar files.
here you have to set the key store, user names and passwords as given above.
You may have a password callback class like this with the correct user names
and passwords.
public class PasswordCallbackHandler implements CallbackHandler {
public void handle(Callback[] callbacks) throws IOException,
UnsupportedCallbackException {
for (int i = 0; i callbacks.length; i++) {
WSPasswordCallback pwcb = (WSPasswordCallback) callbacks[i];
String id = pwcb.getIdentifer();
if (alice.equals(id)) {
pwcb.setPassword(ecila);
} else if (bob.equals(id)) {
pwcb.setPassword(bob);
}
}
}
}
thanks,
Amila.
On 7/26/07, Brian Baldwin [EMAIL PROTECTED] wrote:
I've been using Axis1.x to access my webservice using WSDL2Java generated
stubs...works great...I use the Locator class.
I've modified my webservice to use WS-Policy directives (Sign and Auth).
The WSDL has changed as expected to include the wsp:policy elements for
Sign and Auth.
Do I need to use Axis2/Rampart to generate the client stubs and apply the
encryption now that my webservice is using WS-Policy directives?
Is there an example for using Axis/Axis2 to access a policy-enabled web
service?
My webservice is deployed to WLS 9.2 and I can use weblogic's
clientgen-generated stubs to encrypt and digitally-sign the
message. However, I would like my clients to be able to use Axis.
I've been trying to use Axis2/Rampart but can't get it working.
I've been getting an 'InvalidKeyException: Wrong key usage'.
Follow on question would be with WS-Policy Auth.xml does that mean I
should
use the Encrypt item in the OutflowSecurity parameter for Rampart? Does
WS-Policy Sign.xml map to the Signature item in OutflowSecurity? What
WS-Policy would cause me to need to use the Timestamp item in
OutflowSecurity?
Thank you in advance
Brian
--
Amila Suriarachchi,
WSO2 Inc.
Re: HTTP error in Axis client
Kumar, Amit {PBSG} wrote:
Hi,
I am new to Axis. I am running into an issue while invoking a webservice from
an Axis client. The webservice is deployed and running. I have verified the
endpoint URL. The webservice is not getting hit from the client. Both
webservice and the client are running on the same machine.
Below is the error message.
Thanks in advance.
best regards
amit
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (404)404
faultActor:
faultNode:
faultDetail:
{}:return code: 404
{http://xml.apache.org/axis/}HttpErrorCode:404
(404)404
at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:1910)
at webserviceCall.main(webserviceCall.java:82)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Amit,
http error code 404 means - not found
may be you missed up something in the verification of the endpoint ?! :)
George
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL message Validation with part element
When you consider the soap message it only has the detail element. ns1:faultMessage xmlns:ns1=http://ws.example.com/types; ns1:messageUserException:id is not valid/ns1:message /ns1:faultMessage So only the element (in part ) details present in the soap message. In Axis2 what we does is keep a map for fault element qname and fault message name (basically generated class) in you case client must have this map which can be populated using the wsdl. key - elementQName value -- faultMessageQname using this map client can resolve the fault message corresponding to the received element QName. Please see an Axis2 generated Stub. but this method has one problem. i.e Two fault messages can refer to the same elementQname. eg. wsdl:message name=FaultMessage1 wsdl:part name=FaultMessage element=tns:faultMessage/ /wsdl:message wsdl:message name=FaultMessage2 wsdl:part name=FaultMessage element=tns:faultMessage/ /wsdl:message for this case we can't use the above technique( Acutally Axis2 does not support this as well) for this case we have to use the fault action to map the fault to correct fault message. Amila. On 7/26/07, jaypee_p [EMAIL PROTECTED] wrote: My consumer is SAP XI client. Below is the sequence for fault message is processed in XI XI Sequence 1.First step is to identify the wsdl:Message element with the namespace http://ws.example.com/service 2.The next step is to go to the part element in http://ws.example.com/types and map the fault message. To be simple in your case http://ws.example.com/service is the namespace of Fault Message and http://ws.example.com/types is the namespace of the fault message payload (Fault XML Message). So even though the Fault XML Message has the namespace http://ws.example.com/types ,but if the fault namespace doesnot come with http://ws.example.com/service then Fault will not be triggered and processed in XI. My axis server is sending a fault response like below. soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body soapenv:Fault faultcodesoapenv:Server.generalException/faultcode faultstring/ detail ns1:faultMessage xmlns:ns1=http://ws.example.com/types; ns1:messageUserException:id is not valid/ns1:message /ns1:faultMessage ns2:exceptionName xmlns:ns2=http://xml.apache.org/axis/;com.example.ws.types.FaultMessage /ns2:exceptionName ns3:hostname xmlns:ns3=http://xml.apache.org/axis/;mymachine/ns3:hostname /detail /soapenv:Fault /soapenv:Body /soapenv:Envelope They are facing the error like Not able to match the message namespace from the fault response with the namespace http://ws.example.com/service;. How to resolve this? -- View this message in context: http://www.nabble.com/WSDL-message-Validation-with-part-element-tf4140600.html#a11804216 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: Any way to turn off the 'Unexpected subelement' message - read to understand...
Added a new option to switch off the strict validation. use -Eosv option (off strict validation) with this option on ADB treat every element has a minOccurs=0 attribute on it. i.e it accepts empty requests and on the other hand ADB user can set null to any varialble as well. (in earlier case an ADB user can set a null value to a variable only if in the schema it has declared as nillable true or minOccurs=0.) please have a look at with a nighly build. Amila. On 7/26/07, Amila Suriarachchi [EMAIL PROTECTED] wrote: this is an problem lot of people having with adb. So for Axis2 1.3 we will give an option to switch off this validation. On 7/25/07, Amila Suriarachchi [EMAIL PROTECTED] wrote: unfortunately no. please log jira as an ADB improvement. Anyway isn't possible to talk to them and ask them to put minOccurs = 0 if the send empty messages? Amila. On 7/25/07, Wayne [EMAIL PROTECTED] wrote: Hi there, I've used WSDL2Java (Axis2) to generate my code using a WSDL that is supplied by a rather large company that I have no control over. However when I use the service that they expose they don't send some elements if they are empty (in their system). However in their WSDL they don't say these elements do not have the minOccurs=0 attribute. There when I receive the response the code throws the dreaded unexpected subelement exception. So there is no way I can change the WSDL unless I do it manually - which I don't want to do every time they send a upadate. Is there any way to stop Axis from doing this? ie just ignore and carry on parsing the response? Any pointers much appecriated as I'm a newbe here. Thanks -- Amila Suriarachchi, WSO2 Inc. -- Amila Suriarachchi, WSO2 Inc. -- Amila Suriarachchi, WSO2 Inc.
Re: [1.3-RC2] Build JAX-WS server from wsdl in maven2 project
Farrukh, I just updated the ant task and maven2 mojo this morning :) docs are still in the works. will try to post something as soon as possible. thanks, dims On 7/26/07, Farrukh S. Najmi [EMAIL PROTECTED] wrote: Hello, I am a newbie to Axis2 and looking for a sample and/or bootstrap instructions on creating a service from a WSDL 2.0 source within a maven 2 project. In particular I am not finding wsdl4j:wsdl4j:pom:1.6.2 anywhere. Unfortunately I am unable to find docs, archived emails or wiki entries to help me in my quest. In fact, I am even not finding docs for Axis2 1.3-RC2 so I suspect I missing something obvious. Thanks for your help and sorry if I missed something. -- Regards, Farrukh Web: http://www.wellfleetsoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Extra characters in HTTP request
http://wso2.org/library/952 On 7/26/07, Scott Sauyet [EMAIL PROTECTED] wrote: I'm trying to use Axis2 as the client to a SOAP service supplied by an external system (RemObjects5 / Delphi). Because of certain problems, I've backed off a bit to test Axis2 itself, and I'm bothered by some extra characters that appear in the the HTTP requests and responses sent by Axis. I posted a quick session as captured by TCPMon to http://scott.sauyet.com/issues/2007-07-26a/axis2_patron_soap.txt Here is the request, with the actual SOAP elided: POST /axis2/services/PatronService?wsdl HTTP/1.1 Content-Type: text/xml; charset=UTF-8 SOAPAction: urn:getContactSummaryByEmail User-Agent: Axis2 Host: 127.0.0.1:7453 Transfer-Encoding: chunked 17a ?xml ... soap .../ 0 My problem is with the lines before and after the XML payload. One is the characters 17a; the other the character 0. This wreaks havoc with the server which doesn't know what to do with them. Can someone explain what they're doing there and how to get rigd of them? Is it even possible? Thank you very much, -- Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Extra characters in HTTP request
I'm trying to use Axis2 as the client to a SOAP service supplied by an external system (RemObjects5 / Delphi). Because of certain problems, I've backed off a bit to test Axis2 itself, and I'm bothered by some extra characters that appear in the the HTTP requests and responses sent by Axis. I posted a quick session as captured by TCPMon to http://scott.sauyet.com/issues/2007-07-26a/axis2_patron_soap.txt Here is the request, with the actual SOAP elided: POST /axis2/services/PatronService?wsdl HTTP/1.1 Content-Type: text/xml; charset=UTF-8 SOAPAction: urn:getContactSummaryByEmail User-Agent: Axis2 Host: 127.0.0.1:7453 Transfer-Encoding: chunked 17a ?xml ... soap .../ 0 My problem is with the lines before and after the XML payload. One is the characters 17a; the other the character 0. This wreaks havoc with the server which doesn't know what to do with them. Can someone explain what they're doing there and how to get rigd of them? Is it even possible? Thank you very much, -- Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] From Axis to Axis2
Thanks much Deepal - I will check out the links and see what I can use from them. Deepal Jayasinghe wrote: Hi , Well , you have bit of work to do and some of them (most commonly used ) are described in [1] . If you want to migrate to Axis2 without changing your service you could try with WSO2 WSAS [2] , since it has support to deploy Axis1 service in Axis2 without any change . [1] : http://ws.apache.org/axis2/1_2/migration.html [2] : http://wso2.com/products/wsas/ Thanks Deepal Hi all, I asked this question once before and although a bit broad I thought I would hear something back. I am trying my luck once again - I see and hear poor souls out there struggling with real old versions of Axis and my guess is that migrating to Axis2 is a bit scary for them. Can anyone summarize what any Axis 1.X users can do to slowly make the move to Axis 2 ? Are we talking about a complete re-engineering of their designs or is there hope to migrate a bit smoother. And if this question (and I wouldn't be surprised) has been answered before then by all means, apologies, I will revert to the archives. And by the way - I wrote lots of code in Axis 1.4 and I am pretty happy with the results ... Cheers - 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 Read time out with https
Hello. I am having a problem with axis2 when connecting to a https server. No matter what I do I get a Read time out error. I do not get the same problem when using axis 1.4 I can connect to the http server using HttpClient as explained at http://jakarta.apache.org/commons/httpclient/sslguide.html There is no problem with that, but when I use axis2 it just times out. I have set the time out period to 2 minutes but does not change anything. The https server have a VeriSined signed certificate, not a self signed certificate. I have put the certificate into the key store and configure the client to use the key store. System.setProperty(javax.net.ssl.trustStore, C:/dir/WebServices/dir-WS/dir-Test-WS-Client/64bcKeyStroe); System.setProperty(javax.net.ssl.trustStorePassword, pass); Does not make any difference. I get the same behaviour is I set system property javax.net.ssl.trustStore or If I don't. basically the client web service does the same thing But if I set system property javax.net.ssl.trustStore and I don't have the certificate in the keystore it complains saying it does not find it. On the internet I have found a lot of people with the same problem, but I did not find any solution. If anybody knows what to do can please post it. As well I did not find any https web service that I can use for testing rather that the one I have. Any one knows of any. Cheers Felipe This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] SOAPMonitorApplet port
I'm not a windows user, but you do have the netstat command that can help you track your occupied ports. On linux it'd be 'netstat -ancp | grep 5001' . You can engage the module in either services.xml or axis2.xml - but not both. engaging in axis2.xml make the module available for all services, whereas alternatively engaging in the services,xml makes to module available to just that service. If all else fails, you could use tcpmon as an alternative. HTH, Robert On 7/25/07, Jack Sprat [EMAIL PROTECTED] wrote: Hi Robert. Thanks for trying to help. This has me quite confused. The Tomcat console says that the server socket on the port specified in web.xml cannot be opened. If I set port 3901 then the console says port 3901 cannot be opened. Same for port 5001. The ports show as used by the javaw.exe process. My only other question on the SOAP monitor applet is where to set the module ref. I have this set in the services.xml file. This is the same as the logging module, with the instructions here: http://ws.apache.org/axis2/1_1/modules.html But the SOAP monitor page says to set the module reference in the axis2.xml file. Which is right? Axis2 with Tomcat 5.5 Thanks, T robert lazarski [EMAIL PROTECTED] wrote: When you set the port to 3901, does it still say cannot connect to 5001? Can you try RC2? I'll try to give this scenario a spin today. HTH, Robert On 7/24/07, Jack Sprat wrote: I've tried ports 3901, 5001 and 5050. All gave the same result. robert lazarski wrote: Have you tried changing to another port in the web.xml? HTH, Robert On 7/24/07, Jack Sprat wrote: I've followed the instructions for setting up the SOAP monitor applet here: http://ws.apache.org/axis2/1_2/soapmonitor-module.html Whenever I start my server I get the following errors: 2007-07-24 18:18:20,468 ERROR SOAPMonitorService - Unable to open server socket using port: 5001 2007-07-24 18:18:20,484 ERROR SOAPMonitorService - Address already in use: JVM_Bind It does not seem to matter what port is used. What am I doing wrong? Thanks, T Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Speak Now or Forever Hold Your Peace!
Folks, We've cut 2 RC's for 1.3 release and nightlies are up and running for the 1.3 branch as well *PLEASE* test your scenarios with the latest RC and/or nightly and log a JIRA bug with all details needed to recreate your problem if you see something wrong. 1.3 RC2 - http://people.apache.org/~deepal/axis2/1.3-RC2/ 1.3 Branch Trunk Nightly - http://people.apache.org/dist/axis2/nightly/ JIRA - https://issues.apache.org/jira/browse/AXIS2 If 1.3 Final does not work for you when we cut it, it's your own fault :) If you have a JIRA that has not gotten the attention it deserves, please speak up and let us know. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ExtensionMapper
On 7/23/07, Michael Bell [EMAIL PROTECTED] wrote: Hi, we create WSDL types with two different schemas - one for common types and one for special types. The idea is that we want to implement common types in a central place for all of our web services (e.g. common error handling). During the implementation we noticed that Axis2 generates some ExtensionMapper classes. The problem is that Axis2 does not generate one ExtensionMapper per package. It generates only one filled ExtensionMapper per service. So inheritance does not work because the java classes have always web service specific code inside. I noticed that the generated code can be easily splitted into different packages. Is there a special reason why there is only one ExtensionMapper? this extension mapper is used in extensions(to support polymorphysum). if the input xml stream contains an xsi:type element then we find the corresponding class from using this. Keeping one extension mapper would make the code generation easy sine we have to find the class only in one place. other wise have to see in all the places. you can not say classes in one package has only extended from the class in the same package. if you split the extension mapper class then you have to change the places it refer as well. some times if you only extends classes from the same package this may work. but not a genearalized approach. Amila. I implemented a small Perl script which loads the generated ExtensionMapper and generates mappers on a per package base. If someone is interested then I can send the script. Best regards Michael -- ___ Michael BellHumboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin ___ X.509 CA Certificates / Wurzelzertifikate http://ra.pki.hu-berlin.de -- Amila Suriarachchi, WSO2 Inc.
Re: [Axis2]. - Disable/Enable client side schema validation with axis and ADB
use -Eosv (off strict validation) option. On 7/23/07, Ravi Somepalli [EMAIL PROTECTED] wrote: My Schema contains data types for which some of the attributes are mandatory, as defined in the schema, but during testing or I just want to disable/enable schema validation. The default client from the samples does schema validation and complains about null values. xs:complexType name=Attachment xs:sequence xs:element name=dealtracid type=xs:int/ xs:element name=tviewid type=xs:int/ xs:element name=attachDesc type=xs:string/ xs:element name=docDate type=xs:date / xs:element name=file type=tns:FileAttachment / /xs:sequence /xs:complexType Please point me to the document that addresses the client setting or the build file options or a snippet of code Thanks Ravi Somepalli -- Amila Suriarachchi, WSO2 Inc.
Re: [Axis2] Making objects available on the response MessageContext (1.3-RC2) [SEC=UNCLASSIFIED]
Thank you Deepal, I have tested the fix and it seems to solve the problem we are having. Cheers, Greg Deepal Jayasinghe [EMAIL PROTECTED] 26/07/2007 06:14 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: [Axis2] Making objects available on the response MessageContext (1.3-RC2) [SEC=UNCLASSIFIED] Reference Expires No need to create a JIRA , I fixed the issues and commit to both trunk and the branch. Thanks Deepal Deepal jayasinghe wrote: Hi please create a JIRA (if possible please attach test case as well). Thanks Deepal Hello, We have just upgraded our application to the new Axis2 1.3-RC2 version to do some testing, but we're getting an exception. The exception is thrown in the application code, during a service operation call. It happens when a certain object can't be found on the message context for a SOAP response - we have created an Axis2 response handler that expects this object to be there. Currently before we calling the service operation we set this object onto the Options object that we obtain from the ServiceClient. In Axis2 1.2, this seems to make the object available on the response MessageContext for response handlers to access. However in 1.3-RC2, the object isn't available on the response MessageContext any more. I think that what we are doing (i.e. setting the object onto the Options object to make it available to response handlers) is incorrect, but it was working because of some code in Axis1.2 that has since been refactored. My question is: Is there a recommended way to make objects available on the response MessageContext? (so they can be accessed by response handlers). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ** IMPORTANT: This e-mail is intended for the use of the addressee and may contain information that is confidential, commercially valuable or subject to legal or parliamentary privilege. If you are not the intended recipient you are notified that any review, re-transmission, disclosure, use or dissemination of this communication is strictly prohibited by several Commonwealth Acts of Parliament. If you have received this communication in error please notify the sender immediately and delete all copies of this transmission together with any attachments. **
RE: [Axis2] Speak Now or Forever Hold Your Peace!
Hi Dims, I have a JIRA logged in long back Axis2-2352, the status shows as resolved, though it is not yet resolved. Thanks Raghu -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, July 26, 2007 6:00 AM To: [EMAIL PROTECTED]; axis-user@ws.apache.org Subject: [Axis2] Speak Now or Forever Hold Your Peace! Folks, We've cut 2 RC's for 1.3 release and nightlies are up and running for the 1.3 branch as well *PLEASE* test your scenarios with the latest RC and/or nightly and log a JIRA bug with all details needed to recreate your problem if you see something wrong. 1.3 RC2 - http://people.apache.org/~deepal/axis2/1.3-RC2/ 1.3 Branch Trunk Nightly - http://people.apache.org/dist/axis2/nightly/ JIRA - https://issues.apache.org/jira/browse/AXIS2 If 1.3 Final does not work for you when we cut it, it's your own fault :) If you have a JIRA that has not gotten the attention it deserves, please speak up and let us know. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] SOAPMonitorApplet port
I'm using Axis2 version 1.2. I've already got a log4j.xml config. file in place. I'll set the debugging level on oprg.apache to DEBUG and post back. Thanks again for the help. T robert lazarski [EMAIL PROTECTED] wrote: What version are you using? That's a pretty strange problem. There are people that use this tool and I've never heard of an issue like this. We're about to do a release soon - can you try these? http://people.apache.org/dist/axis2/nightly/axis2-1.3-SNAPSHOT-bin.zip http://people.apache.org/dist/axis2/nightly/axis2-1.3-SNAPSHOT-war.zip I can't think of anything off hand on windows that could track down what class loaded by java.exe is using the port. Can you put WEB-INF/classes/log4j.properties in DEBUG, along with a log4j.jar in WEB-INF/lib . That should create a bunch of axis2 content on catalina.out. If you could send that to this list, we might be able to track it down. Robert On 7/26/07, Jack Sprat wrote: Hi Robert, Only the Java executable (javaw.exe) is using the port. It does not matter what port I set in web.xml - it is always in use by the Java executable. I thought I could find an open port, but it does not seem to matter which one I use. It is *always* taken by javaw.exe. It''s almost like Axis2 is reserving the port and then trying to use it again, causing the bind error. Thanks, T robert lazarski wrote: What is connected to 3901 ? There's 65,000 or so ports, so I'm sure you should be able to find one of them open ;-) . HTH, Robert On 7/26/07, Jack Sprat wrote: Hi Robert. I used ActivePorts for Windows, as suggested earlier. This showed the port specified in web.xml as occupied by javaw.exe. What could be the problem here? Thanks again for trying to help. T robert lazarski wrote: I'm not a windows user, but you do have the netstat command that can help you track your occupied ports. On linux it'd be 'netstat -ancp | grep 5001' . You can engage the module in either services.xml or axis2.xml - but not both. engaging in axis2.xml make the module available for all services, whereas alternatively engaging in the services,xml makes to module available to just that service. If all else fails, you could use tcpmon as an alternative. HTH, Robert On 7/25/07, Jack Sprat wrote: Hi Robert. Thanks for trying to help. This has me quite confused. The Tomcat console says that the server socket on the port specified in web.xml cannot be opened. If I set port 3901 then the console says port 3901 cannot be opened. Same for port 5001. The ports show as used by the javaw.exe process. My only other question on the SOAP monitor applet is where to set the module ref. I have this set in the services.xml file. This is the same as the logging module, with the instructions here: http://ws.apache.org/axis2/1_1/modules.html But the SOAP monitor page says to set the module reference in the axis2.xml file. Which is right? Axis2 with Tomcat 5.5 Thanks, T robert lazarski wrote: When you set the port to 3901, does it still say cannot connect to 5001? Can you try RC2? I'll try to give this scenario a spin today. HTH, Robert On 7/24/07, Jack Sprat wrote: I've tried ports 3901, 5001 and 5050. All gave the same result. robert lazarski wrote: Have you tried changing to another port in the web.xml? HTH, Robert On 7/24/07, Jack Sprat wrote: I've followed the instructions for setting up the SOAP monitor applet here: http://ws.apache.org/axis2/1_2/soapmonitor-module.html Whenever I start my server I get the following errors: 2007-07-24 18:18:20,468 ERROR SOAPMonitorService - Unable to open server socket using port: 5001 2007-07-24 18:18:20,484 ERROR SOAPMonitorService - Address already in use: JVM_Bind It does not seem to matter what port is used. What am I doing wrong? Thanks, T Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Shape Yahoo! in your own image. Join our Network Research Panel today!
Re: [Axis2] SOAPMonitorApplet port
What is connected to 3901 ? There's 65,000 or so ports, so I'm sure you should be able to find one of them open ;-) . HTH, Robert On 7/26/07, Jack Sprat [EMAIL PROTECTED] wrote: Hi Robert. I used ActivePorts for Windows, as suggested earlier. This showed the port specified in web.xml as occupied by javaw.exe. What could be the problem here? Thanks again for trying to help. T robert lazarski [EMAIL PROTECTED] wrote: I'm not a windows user, but you do have the netstat command that can help you track your occupied ports. On linux it'd be 'netstat -ancp | grep 5001' . You can engage the module in either services.xml or axis2.xml - but not both. engaging in axis2.xml make the module available for all services, whereas alternatively engaging in the services,xml makes to module available to just that service. If all else fails, you could use tcpmon as an alternative. HTH, Robert On 7/25/07, Jack Sprat wrote: Hi Robert. Thanks for trying to help. This has me quite confused. The Tomcat console says that the server socket on the port specified in web.xml cannot be opened. If I set port 3901 then the console says port 3901 cannot be opened. Same for port 5001. The ports show as used by the javaw.exe process. My only other question on the SOAP monitor applet is where to set the module ref. I have this set in the services.xml file. This is the same as the logging module, with the instructions here: http://ws.apache.org/axis2/1_1/modules.html But the SOAP monitor page says to set the module reference in the axis2.xml file. Which is right? Axis2 with Tomcat 5.5 Thanks, T robert lazarski wrote: When you set the port to 3901, does it still say cannot connect to 5001? Can you try RC2? I'll try to give this scenario a spin today. HTH, Robert On 7/24/07, Jack Sprat wrote: I've tried ports 3901, 5001 and 5050. All gave the same result. robert lazarski wrote: Have you tried changing to another port in the web.xml? HTH, Robert On 7/24/07, Jack Sprat wrote: I've followed the instructions for setting up the SOAP monitor applet here: http://ws.apache.org/axis2/1_2/soapmonitor-module.html Whenever I start my server I get the following errors: 2007-07-24 18:18:20,468 ERROR SOAPMonitorService - Unable to open server socket using port: 5001 2007-07-24 18:18:20,484 ERROR SOAPMonitorService - Address already in use: JVM_Bind It does not seem to matter what port is used. What am I doing wrong? Thanks, T Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 byte[] transfer/serialization bug ?!
Thilina Gunarathne wrote:
Looks like a bug... Please report a JIRA...
You may also try replacing byte[] with javax.activation.DataHandler...
DataHandler is the recommended way when using large attachments...
thanks,
Thilina
On 7/24/07, Georgi Yonchev [EMAIL PROTECTED] wrote:
Thilina Gunarathne wrote:
and Deepal, yes works fine, but try it with larger byte[] size,
with larger, in the payload goes array from bytes ?!
not encoded in base64 ..
Not clear what you meant?... Do they go as native binary in the form
of an attachment or inside the soap body...
Thanks,
Thilina
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
inside in the soap body, the bytes are not encoded in base64, is
represented like integers
this is a part of the xml :
ns:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData115/ns:byteDatans:byteData105/ns:byteDatans:byteData122/ns:byteDatans:byteData101/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData49/ns:byteDatans:byteData48/ns:byteData
ns:byteData112/ns:byteDatans:byteData116/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData119/ns:byteDatans:byteData101/ns:byteDatans:byteData105/ns:byteDatans:byteData103/ns:byteDatans:byteData104/ns:byteDatans:byteData116/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData110/ns:byteDatans:byteData111/ns:byteDatans:byteData114/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData125/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData46/ns:byteDatans:byteData99/ns:byteDatans:byteData111/ns:byteDatans:byteData110/n
s:byteDatans:byteData
2000
116/ns:byteDatans:byteData101/ns:byteDatans:byteData110/ns:byteData
this happens only when i set the byte[] in Complex return object
class Result{
private byte[] bytes;
set..
get..
}
and the call likes:
public Res test(){
..set byte[] in res
return res;
}
if the call is :
public byte[] test(){
..
}
everything goes well...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Thilina,
i report it on JIRA, and is fixed on both tags/branches in the svn...
can you give some hints about this DataHandler ...
some example how to implement it,
10x a lot in advance :)
George
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Speak Now or Forever Hold Your Peace!
dims, how about http://issues.apache.org/jira/browse/AXIS2-3017 ( I even attached a very simple example that illustrates the problem). Nadir K. Amra Davanum Srinivas [EMAIL PROTECTED] wrote on 07/26/2007 07:59:30 AM: Folks, We've cut 2 RC's for 1.3 release and nightlies are up and running for the 1.3 branch as well *PLEASE* test your scenarios with the latest RC and/or nightly and log a JIRA bug with all details needed to recreate your problem if you see something wrong. 1.3 RC2 - http://people.apache.org/~deepal/axis2/1.3-RC2/ 1.3 Branch Trunk Nightly - http://people.apache.org/dist/axis2/nightly/ JIRA - https://issues.apache.org/jira/browse/AXIS2 If 1.3 Final does not work for you when we cut it, it's your own fault :) If you have a JIRA that has not gotten the attention it deserves, please speak up and let us know. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] SOAPMonitorApplet port
What version are you using? That's a pretty strange problem. There are people that use this tool and I've never heard of an issue like this. We're about to do a release soon - can you try these? http://people.apache.org/dist/axis2/nightly/axis2-1.3-SNAPSHOT-bin.zip http://people.apache.org/dist/axis2/nightly/axis2-1.3-SNAPSHOT-war.zip I can't think of anything off hand on windows that could track down what class loaded by java.exe is using the port. Can you put WEB-INF/classes/log4j.properties in DEBUG, along with a log4j.jar in WEB-INF/lib . That should create a bunch of axis2 content on catalina.out. If you could send that to this list, we might be able to track it down. Robert On 7/26/07, Jack Sprat [EMAIL PROTECTED] wrote: Hi Robert, Only the Java executable (javaw.exe) is using the port. It does not matter what port I set in web.xml - it is always in use by the Java executable. I thought I could find an open port, but it does not seem to matter which one I use. It is *always* taken by javaw.exe. It''s almost like Axis2 is reserving the port and then trying to use it again, causing the bind error. Thanks, T robert lazarski [EMAIL PROTECTED] wrote: What is connected to 3901 ? There's 65,000 or so ports, so I'm sure you should be able to find one of them open ;-) . HTH, Robert On 7/26/07, Jack Sprat wrote: Hi Robert. I used ActivePorts for Windows, as suggested earlier. This showed the port specified in web.xml as occupied by javaw.exe. What could be the problem here? Thanks again for trying to help. T robert lazarski wrote: I'm not a windows user, but you do have the netstat command that can help you track your occupied ports. On linux it'd be 'netstat -ancp | grep 5001' . You can engage the module in either services.xml or axis2.xml - but not both. engaging in axis2.xml make the module available for all services, whereas alternatively engaging in the services,xml makes to module available to just that service. If all else fails, you could use tcpmon as an alternative. HTH, Robert On 7/25/07, Jack Sprat wrote: Hi Robert. Thanks for trying to help. This has me quite confused. The Tomcat console says that the server socket on the port specified in web.xml cannot be opened. If I set port 3901 then the console says port 3901 cannot be opened. Same for port 5001. The ports show as used by the javaw.exe process. My only other question on the SOAP monitor applet is where to set the module ref. I have this set in the services.xml file. This is the same as the logging module, with the instructions here: http://ws.apache.org/axis2/1_1/modules.html But the SOAP monitor page says to set the module reference in the axis2.xml file. Which is right? Axis2 with Tomcat 5.5 Thanks, T robert lazarski wrote: When you set the port to 3901, does it still say cannot connect to 5001? Can you try RC2? I'll try to give this scenario a spin today. HTH, Robert On 7/24/07, Jack Sprat wrote: I've tried ports 3901, 5001 and 5050. All gave the same result. robert lazarski wrote: Have you tried changing to another port in the web.xml? HTH, Robert On 7/24/07, Jack Sprat wrote: I've followed the instructions for setting up the SOAP monitor applet here: http://ws.apache.org/axis2/1_2/soapmonitor-module.html Whenever I start my server I get the following errors: 2007-07-24 18:18:20,468 ERROR SOAPMonitorService - Unable to open server socket using port: 5001 2007-07-24 18:18:20,484 ERROR SOAPMonitorService - Address already in use: JVM_Bind It does not seem to matter what port is used. What am I doing wrong? Thanks, T Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
out of memory in Axis 1.4
Hi, I am getting the following error intermittently: - Exception: java.lang.OutOfMemoryError I am sending 1 MB payloads but I have enough memory heap size (512 MB), anybody knows what might be the issue? is there a parameter or setting I need to set or initialize? The failure seems to happen on the invoke method in the Axis servlet. Thanks, Firas
Re: Generated C-Code from WSDL2C
please raise this question at [1] Axis2 c list. [1]http://ws.apache.org/axis2/c/lists_issues.html On 7/20/07, Mustafa Cavus [EMAIL PROTECTED] wrote: Hello, I have generated C-code from a wsdl-file, but I have a lot of files and methods. I'm looking for an API or something like that, which explain the function of the methods. Can you help me? Thanks m. cavus -- Amila Suriarachchi, WSO2 Inc.
Re: axis2: Parser already accessed!
please try with ADB if it is a solution. ADB handles Mtom in an optimised way. On 7/23/07, Angus Ng [EMAIL PROTECTED] wrote: HI, We have an intermittent problem when sending a large XML message which has an encoded PDF attachment with base64. We are using a generated stub from xmlbean for sending the message. We are using Axis2 1.2 xmlbeans 2.2, Axiom 2.4, Tomat 5.5 java 5. Our assumption is that this is something to do with the cache and getting the parser but are a little confused about why this exception is being thrown. (especially only sometimes) Are there any resource that we should clean up before sending? Here is the exception trail: org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke (CommonsHTTPTransportSender.java:221) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452) at org.apache.axis2.description.OutInAxisOperationClient.send (OutInAxisOperation.java:330) at org.apache.axis2.description.OutInAxisOperationClient.execute (OutInAxisOperation.java:294) at landata.service.xmlbeans.ProvisioningServiceStub.CertificateProvision( ProvisioningServiceStub.java:152) at au.com.groupware.planningcerts.service.pipeline.ReleaseProcessor.sendV iaWebService(ReleaseProcessor.java:194) at au.com.groupware.planningcerts.service.pipeline.ReleaseProcessor.proce ss(ReleaseProcessor.java:80) at au.com.groupware.planningcerts.service.pipeline.Processor.processAppli cationsInQueue(Processor.java:201) at au.com.groupware.planningcerts.service.pipeline.Processor.run (Processor.java:172) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessag eWithCommons(CommonsHTTPTransportSender.java:314) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke (CommonsHTTPTransportSender.java:201) ... 9 more Caused by: org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.transport.http.HTTPSender.sendViaPost (HTTPSender.java:179) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java : 73) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessag eWithCommons(CommonsHTTPTransportSender.java:305) ... 10 more Caused by: org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest (AxisRequestEntity.java:98) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeReque stBody(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest (HttpMethodBase.java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute (HttpMethodBase.java:993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry (HttpMethodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod (HttpMethodDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod (HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod (HttpClient.java:346) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod (AbstractHTTPSender.java:558) at org.apache.axis2.transport.http.HTTPSender.sendViaPost (HTTPSender.java:176) ... 12 more Caused by: org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo (SOAPMessageFormatter.java:59) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest (AxisRequestEntity.java:84) ... 21 more Caused by: javax.xml.stream.XMLStreamException: problem accessing the parser. Parser already accessed! at org.apache.axiom.om.impl.llom.OMStAXWrapper.next (OMStAXWrapper.java:883) at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode (StreamingOMSerializer.java:69) at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize (StreamingOMSerializer.java:54) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream (OMSerializerUtil.java:490) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize (OMElementImpl.java:783) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsum e(OMElementImpl.java:808) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally (SOAPEnvelopeImpl.java:234) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize (SOAPEnvelopeImpl.java:222) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsum
Re: Axis2 send xsi types
Hi Jose, You can send them as below; ns:echo xmlns:ns=http://ws.apache.org/axis2; echoReq type=Man a10/a address type=Address number xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true / street xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true / /address /echoReq /ns:echo Hi all, How I can send schema xsi types from Axis2 so as to do polymorphism on the client? Thanks in advance, Jose Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://us.rd.yahoo.com/mail/es/tagline/beabetter/*http://advision.webevents.yahoo.com/reto/entretenimiento.html. -- Thanks, Deepal The highest tower is built one brick at a time - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Speak Now or Forever Hold Your Peace!
Hi, dims, How about the problem of https://issues.apache.org/jira/browse/AXIS2-2898? it seems still not resolved. Best Regards! Lizhao Chen 86-021-50800850-8395 -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, July 26, 2007 9:00 PM To: [EMAIL PROTECTED]; axis-user@ws.apache.org Subject: [Axis2] Speak Now or Forever Hold Your Peace! Folks, We've cut 2 RC's for 1.3 release and nightlies are up and running for the 1.3 branch as well *PLEASE* test your scenarios with the latest RC and/or nightly and log a JIRA bug with all details needed to recreate your problem if you see something wrong. 1.3 RC2 - http://people.apache.org/~deepal/axis2/1.3-RC2/ 1.3 Branch Trunk Nightly - http://people.apache.org/dist/axis2/nightly/ JIRA - https://issues.apache.org/jira/browse/AXIS2 If 1.3 Final does not work for you when we cut it, it's your own fault :) If you have a JIRA that has not gotten the attention it deserves, please speak up and let us know. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
