Re: Segmentation fault when calling webservice
[EMAIL PROTECTED] wrote: No pb, I've already posted an issue for this (perhaps it's a mistake ?) No it is not a mistake. Raising a Jira is the preferred method. BTW, it looks like you have not included -g in your CFLAGS, please do so that the backtrace would include line numbers. Having a glance at the backtrace, it looks like there is something wrong in the service object creation. Could possibly be something wrong in the service implementation, or the configuration. Samisa... https://issues.apache.org/jira/browse/AXIS2C-612 Here's the backtrace : #0 0xb7e62b87 in axis2_msg_recv_make_new_svc_obj () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #1 0xb7e62c98 in axis2_msg_recv_get_impl_obj () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #2 0xb7e635d4 in axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #3 0xb7e63311 in axis2_msg_recv_invoke_business_logic () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #4 0xb7e63119 in axis2_msg_recv_receive_impl () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #5 0xb7e6336d in axis2_msg_recv_receive () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #6 0xb7e58092 in axis2_engine_receive () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #7 0xb7f0d5de in axis2_http_transport_utils_process_http_post_request () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_http_common.so.0 #8 0xb7f0bf20 in axis2_http_worker_process_request () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_http_common.so.0 #9 0xb7e140ca in axis2_svr_thread_worker_func () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_http_receiver.so.0 #10 0xb7ebf265 in dummy_worker () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxutil.so.0 #11 0xb7cb931b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #12 0xb7c2957e in clone () from /lib/tls/i686/cmov/libc.so.6 Thanks a lot for your help ! Jean-Louis Is it possible for you to use gdb and send the back trace at the point it segfaults please? That would help us to understand where the exact problem is. It is hard to tell the problem form the log. Thanks, Samisa... Jean-Louis LESIEUR wrote: Hello, I have a problem when I deploy a service. I've build a simple service based on the "echo" sample, except in the fact that this service call a function in other custom shared library. I'm on ubuntu linux 7.04 with axis 1.0.0. I've tried to compile my service with this command : gcc -shared -olibmajcsp.so -I$AXIS2C_HOME/include/axis2-1.0/ -L$AXIS2C_HOME/lib -laxis2 -L -l -I I have no error in compilation. So I deploy the .so of this service and try to call him with echo client sample axis_http_server crashes with a segmentation fault ... Here's the result of execution of axis_http_server : $ sudo ./axis 2_http_server -l 5 -f /dev/stderr Started Simple Axis2 HTTP Server ... [Thu Jun 7 23:19:47 2007] [info] Starting HTTP server thread [Thu Jun 7 23:19:51 2007] [debug] http_worker.c(155) Client HTTP version HTTP/1.1 [Thu Jun 7 23:19:51 2007] [debug] soap_builder.c(748) identified soap version is soap12 [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase Transport [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler request_uri_based_dispatcher within the phase Transport [Thu Jun 7 23:19:51 2007] [debug] req_uri_disp.c(103) Checking for service using target endpoint address : http://127.0.0.1:9090/axis2/services/majcsp [Thu Jun 7 23:19:51 2007] [debug] req_uri_disp.c(124) Service found using target endpoint address [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase PreDispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler AddressingInHandler within the phase PreDispatch [Thu Jun 7 23:19:51 2007] [info] Starting addressing in handler . [Thu Jun 7 23:19:51 2007] [info] addr_in_handler.c [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase Dispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Thu Jun 7 23:19:51 2007] [debug] soap_body_disp.c(217) Checking for operation using SOAP message body's first child's local name : echoString [Thu Jun 7 23:19:51 2007] [debug] soap_body_disp.c(226) Operation found using SOAP message body's first child's local name [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase PostDispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler dispat
Re: Segmentation fault when calling webservice
No pb, I've already posted an issue for this (perhaps it's a mistake ?) https://issues.apache.org/jira/browse/AXIS2C-612 Here's the backtrace : #0 0xb7e62b87 in axis2_msg_recv_make_new_svc_obj () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #1 0xb7e62c98 in axis2_msg_recv_get_impl_obj () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #2 0xb7e635d4 in axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #3 0xb7e63311 in axis2_msg_recv_invoke_business_logic () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #4 0xb7e63119 in axis2_msg_recv_receive_impl () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #5 0xb7e6336d in axis2_msg_recv_receive () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #6 0xb7e58092 in axis2_engine_receive () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0 #7 0xb7f0d5de in axis2_http_transport_utils_process_http_post_request () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_http_common.so.0 #8 0xb7f0bf20 in axis2_http_worker_process_request () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_http_common.so.0 #9 0xb7e140ca in axis2_svr_thread_worker_func () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_http_receiver.so.0 #10 0xb7ebf265 in dummy_worker () from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxutil.so.0 #11 0xb7cb931b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #12 0xb7c2957e in clone () from /lib/tls/i686/cmov/libc.so.6 Thanks a lot for your help ! Jean-Louis > Is it possible for you to use gdb and send the back trace at the point > it segfaults please? That would help us to understand where the exact > problem is. It is hard to tell the problem form the log. > > Thanks, > Samisa... > > Jean-Louis LESIEUR wrote: >> Hello, >> >> I have a problem when I deploy a service. I've build a simple service >> based on the "echo" sample, except in the fact that this service call >> a function in other custom shared library. >> >> I'm on ubuntu linux 7.04 with axis 1.0.0. >> >> I've tried to compile my service with this command : >> >> gcc -shared -olibmajcsp.so -I$AXIS2C_HOME/include/axis2-1.0/ >> -L$AXIS2C_HOME/lib -laxis2 -L -l> lib> -I >> >> I have no error in compilation. >> >> So I deploy the .so of this service and try to call him with echo >> client sample axis_http_server crashes with a segmentation fault ... >> Here's the result of execution of axis_http_server : >> >> $ sudo ./axis 2_http_server -l 5 -f /dev/stderr >> Started Simple Axis2 HTTP Server ... >> [Thu Jun 7 23:19:47 2007] [info] Starting HTTP server thread >> [Thu Jun 7 23:19:51 2007] [debug] http_worker.c(155) Client HTTP >> version HTTP/1.1 >> [Thu Jun 7 23:19:51 2007] [debug] soap_builder.c(748) identified soap >> version is soap12 >> [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase >> Transport >> [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler >> request_uri_based_dispatcher within the phase Transport >> [Thu Jun 7 23:19:51 2007] [debug] req_uri_disp.c(103) Checking for >> service using target endpoint address : >> http://127.0.0.1:9090/axis2/services/majcsp >> [Thu Jun 7 23:19:51 2007] [debug] req_uri_disp.c(124) Service found >> using target endpoint address >> [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase >> PreDispatch >> [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler >> AddressingInHandler within the phase PreDispatch >> [Thu Jun 7 23:19:51 2007] [info] Starting addressing in handler >> . >> [Thu Jun 7 23:19:51 2007] [info] addr_in_handler.c >> [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase Dispatch >> [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler >> soap_message_body_based_dispatcher within the phase Dispatch >> [Thu Jun 7 23:19:51 2007] [debug] soap_body_disp.c(217) Checking for >> operation using SOAP message body's first child's local name : >> echoString >> [Thu Jun 7 23:19:51 2007] [debug] soap_body_disp.c(226) Operation >> found using SOAP message body's first child's local name >> [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler >> addressing_based_dispatcher within the phase Dispatch >> [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler >> soap_action_based_dispatcher within the phase Dispatch >> [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase >> PostDispatch >> [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler >> dispatch_post_conditions_evaluator within the phase PostDispatch >> [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler >> context_handler within the phase PostDispatch >> Erreur de segmentation (core dumped) >> >> Does anybody have expe
Re: [AXIS2C][WSDL2C] close to despair
Hi,
Sorry about not updating the code generation samples inside
AXIS2C_HOME/samples/codegen/databinding directory. The sample
implementations in this directory are out of date because we remove macros
and do some changes to naming conventions. I will change those samples
ASAP.
If you want to try WSDL2C with data binding follow the guide lines in
README.txt inside databinding directory.
These samples only provide implementations of business logic. You have to
copy other files which are generated using WSDL2C and compile them.
I'll post a more detail guideline ASAP.
Thanks ,
Milinda
On 6/8/07, Dr. Florian Steinborn <[EMAIL PROTECTED]> wrote:
Dear group,
I am looking for one complete example of a web service for AXIS2C that was
completely created by one single WSDL file using the generator utilities
from AXIS2-Java. But I cannot find one. Can someone provide me one?
I would like to show you what I did (the webservice is just to return a
string)...
I used this interface to generate the wsdl-file I want to use...
//interface
public interface Hello {
public String sayHello();
}
I compiled it with javac.
The resulting class file should be usable to generate the wsdl.
I used this (no special parameters):
java2wsdl Hello.class
I was lucky to find a "Hello.wsdl" afterwards.
This one I ran against WSDL2C to generate the server stubs.
java -classpath ${WSCP} org.apache.axis2.wsdl.WSDL2C -uri Hello.wsdl -ss
-sd -d adb
Everythings works fine until here. I understood I have to implement the
business logic in "axis2_skel_Hello.c".
But looking at
axis2_sayHelloResponse_t* axis2_skel_Hello_sayHello (const axutil_env_t
{
/* TODO fill this with the necessary business logic */
return NULL;
}
I find it extremely difficult to compare this generated source with the
hand written sources in the samples directory. I am not sure which
functions I have to call and which not. I probably have to issue a call
for
axis2_sayHelloResponse_create()
to get the chance to send back my string, but once I did that: how do I
copy my string to the return variable? Somewhere I found the use of
AXIS2_ECHOSTRUCTRESPONSE_SET_RETURN ()
but HELL I cannot find the definition of this function (first I thought it
was a macro but I could find a macro defintion either)... Where is this
definition? How can I know that this function is useful to return a string
- how does it look like when I have to return a long?
Once I am sure the service is well defined and running I would like to
create the Java-client stubs from the same "Hello.wsdl" to connect to the
service - but this is another story...
Please don't think I am too impatient - I torture myself since monday.
Thanks a lot for your help,
Flori
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
[EMAIL PROTECTED]
WSO2, Inc: http://www.wso2.com "Oxygenating the Web Service Platform"
http://www.milindalakmal.wordpress.com
Re: Segmentation fault when calling webservice
Is it possible for you to use gdb and send the back trace at the point it segfaults please? That would help us to understand where the exact problem is. It is hard to tell the problem form the log. Thanks, Samisa... Jean-Louis LESIEUR wrote: Hello, I have a problem when I deploy a service. I've build a simple service based on the "echo" sample, except in the fact that this service call a function in other custom shared library. I'm on ubuntu linux 7.04 with axis 1.0.0. I've tried to compile my service with this command : gcc -shared -olibmajcsp.so -I$AXIS2C_HOME/include/axis2-1.0/ -L$AXIS2C_HOME/lib -laxis2 -L -llib> -I I have no error in compilation. So I deploy the .so of this service and try to call him with echo client sample axis_http_server crashes with a segmentation fault ... Here's the result of execution of axis_http_server : $ sudo ./axis 2_http_server -l 5 -f /dev/stderr Started Simple Axis2 HTTP Server ... [Thu Jun 7 23:19:47 2007] [info] Starting HTTP server thread [Thu Jun 7 23:19:51 2007] [debug] http_worker.c(155) Client HTTP version HTTP/1.1 [Thu Jun 7 23:19:51 2007] [debug] soap_builder.c(748) identified soap version is soap12 [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase Transport [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler request_uri_based_dispatcher within the phase Transport [Thu Jun 7 23:19:51 2007] [debug] req_uri_disp.c(103) Checking for service using target endpoint address : http://127.0.0.1:9090/axis2/services/majcsp [Thu Jun 7 23:19:51 2007] [debug] req_uri_disp.c(124) Service found using target endpoint address [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase PreDispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler AddressingInHandler within the phase PreDispatch [Thu Jun 7 23:19:51 2007] [info] Starting addressing in handler . [Thu Jun 7 23:19:51 2007] [info] addr_in_handler.c [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase Dispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Thu Jun 7 23:19:51 2007] [debug] soap_body_disp.c(217) Checking for operation using SOAP message body's first child's local name : echoString [Thu Jun 7 23:19:51 2007] [debug] soap_body_disp.c(226) Operation found using SOAP message body's first child's local name [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase PostDispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler context_handler within the phase PostDispatch Erreur de segmentation (core dumped) Does anybody have experienced this kind of problem ? Thanks for your help ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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]
[AXIS2C][WSDL2C] close to despair
Dear group,
I am looking for one complete example of a web service for AXIS2C that was
completely created by one single WSDL file using the generator utilities
from AXIS2-Java. But I cannot find one. Can someone provide me one?
I would like to show you what I did (the webservice is just to return a
string)...
I used this interface to generate the wsdl-file I want to use...
//interface
public interface Hello {
public String sayHello();
}
I compiled it with javac.
The resulting class file should be usable to generate the wsdl.
I used this (no special parameters):
java2wsdl Hello.class
I was lucky to find a "Hello.wsdl" afterwards.
This one I ran against WSDL2C to generate the server stubs.
java -classpath ${WSCP} org.apache.axis2.wsdl.WSDL2C -uri Hello.wsdl -ss
-sd -d adb
Everythings works fine until here. I understood I have to implement the
business logic in "axis2_skel_Hello.c".
But looking at
axis2_sayHelloResponse_t* axis2_skel_Hello_sayHello (const axutil_env_t
{
/* TODO fill this with the necessary business logic */
return NULL;
}
I find it extremely difficult to compare this generated source with the
hand written sources in the samples directory. I am not sure which
functions I have to call and which not. I probably have to issue a call for
axis2_sayHelloResponse_create()
to get the chance to send back my string, but once I did that: how do I
copy my string to the return variable? Somewhere I found the use of
AXIS2_ECHOSTRUCTRESPONSE_SET_RETURN ()
but HELL I cannot find the definition of this function (first I thought it
was a macro but I could find a macro defintion either)... Where is this
definition? How can I know that this function is useful to return a string
- how does it look like when I have to return a long?
Once I am sure the service is well defined and running I would like to
create the Java-client stubs from the same "Hello.wsdl" to connect to the
service - but this is another story...
Please don't think I am too impatient - I torture myself since monday.
Thanks a lot for your help,
Flori
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Segmentation fault when calling webservice
Hello, I have a problem when I deploy a service. I've build a simple service based on the "echo" sample, except in the fact that this service call a function in other custom shared library. I'm on ubuntu linux 7.04 with axis 1.0.0. I've tried to compile my service with this command : gcc -shared -olibmajcsp.so -I$AXIS2C_HOME/include/axis2-1.0/ -L$AXIS2C_HOME/lib -laxis2 -L -l -I I have no error in compilation. So I deploy the .so of this service and try to call him with echo client sample axis_http_server crashes with a segmentation fault ... Here's the result of execution of axis_http_server : $ sudo ./axis 2_http_server -l 5 -f /dev/stderr Started Simple Axis2 HTTP Server ... [Thu Jun 7 23:19:47 2007] [info] Starting HTTP server thread [Thu Jun 7 23:19:51 2007] [debug] http_worker.c(155) Client HTTP version HTTP/1.1 [Thu Jun 7 23:19:51 2007] [debug] soap_builder.c(748) identified soap version is soap12 [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase Transport [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler request_uri_based_dispatcher within the phase Transport [Thu Jun 7 23:19:51 2007] [debug] req_uri_disp.c(103) Checking for service using target endpoint address : http://127.0.0.1:9090/axis2/services/majcsp [Thu Jun 7 23:19:51 2007] [debug] req_uri_disp.c(124) Service found using target endpoint address [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase PreDispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler AddressingInHandler within the phase PreDispatch [Thu Jun 7 23:19:51 2007] [info] Starting addressing in handler . [Thu Jun 7 23:19:51 2007] [info] addr_in_handler.c [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase Dispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Thu Jun 7 23:19:51 2007] [debug] soap_body_disp.c(217) Checking for operation using SOAP message body's first child's local name : echoString [Thu Jun 7 23:19:51 2007] [debug] soap_body_disp.c(226) Operation found using SOAP message body's first child's local name [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Thu Jun 7 23:19:51 2007] [debug] engine.c(571) Invoking phase PostDispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Thu Jun 7 23:19:51 2007] [debug] phase.c(195) Invoke the handler context_handler within the phase PostDispatch Erreur de segmentation (core dumped) Does anybody have experienced this kind of problem ? Thanks for your help ! begin:vcard fn:Jean-Louis LESIEUR n:LESIEUR;Jean-Louis org:PROGEXIA adr:;;45 rue F. Joliot Curie;Marseille CEDEX 13;;13382;FRANCE email;internet:[EMAIL PROTECTED] tel;work:04.91.11.88.19 tel;cell:06.22.71.04.64 x-mozilla-html:TRUE version:2.1 end:vcard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Regarding running of wsdl2c tool
It seems to me that your wsdl is wrong. I cant simply open it even with a web browser. It is not formatted well. I can see that the following comment is wrong. A comment should go like Regards, Dushshantha On 6/7/07, Sushmita Sahu <[EMAIL PROTECTED]> wrote: Hi, I am a novice in web services. I am running the wsdl2c tool on a .wsdl (attached file) to get the client side stubs. I am getting the following error on running the tool on wsdl: *C:\axis2c-1\samples\client\getMachines>java -cp %AXIS2_CLASSPATH%;%AXIS2_CLASSPATH2% org.a* *pache.axis2.wsdl.WSDL2C -uri JobManagement.wsdl -d adb -u* *Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: Error pa* *rsing WSDL* *at org.apache.axis2.wsdl.codegen.CodeGenerationEngine .(CodeGenerationEngine.* *java:140)* *at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)* *at org.apache.axis2.wsdl.WSDL2C.main(WSDL2C.java:28)* *Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Parser SAX Err* *or: org.xml.sax.SAXException: Fatal Error: URI=file:///C:/axis2c-1/samples/client/getMachi* *nes/JobManagement.wsdl Line=3: The content of elements must consist of well-formed charact* *er data or markup.* *at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile (CodeGenera* *tionEngine.java:300)* *at org.apache.axis2.wsdl.codegen.CodeGenerationEngine .(CodeGenerationEngine.* *java:97)* *... 2 more* *Caused by: org.xml.sax.SAXException: Fatal Error: URI=file:///C:/axis2c-1/samples/client/g* *etMachines/JobManagement.wsdl Line=3: The content of elements must consist of well-formed* *character data or markup.* *at org.apache.axis2.util.XMLUtils$ParserErrorHandler.fatalError( XMLUtils.java:381)* * * *at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)* *at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)* *at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)* *at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)* *at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher * *.dispatch(Unknown Source)* *at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Sour* *ce)* *at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)* *at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)* *at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)* *at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)* *at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)* *at org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:196)* *at org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:241)* *at org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:224)* *at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile (CodeGenera* *tionEngine.java:294)* *... 3 more.* * * Can you tell me where exactly the problem is? Thanks and regards Sushmita CAUTION - Disclaimer * This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS End of Disclaimer INFOSYS*** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Regarding running of wsdl2c tool
Hi, I am a novice in web services. I am running the wsdl2c tool on a .wsdl (attached file) to get the client side stubs. I am getting the following error on running the tool on wsdl: C:\axis2c-1\samples\client\getMachines>java -cp %AXIS2_CLASSPATH%;%AXIS2_CLASSPATH2% org.a pache.axis2.wsdl.WSDL2C -uri JobManagement.wsdl -d adb -u Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: Error pa rsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGeneration Engine. java:140) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2C.main(WSDL2C.java:28) Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Parser SAX Err or: org.xml.sax.SAXException: Fatal Error: URI=file:///C:/axis2c-1/samples/client/getMachi nes/JobManagement.wsdl Line=3: The content of elements must consist of well-formed charact er data or markup. at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(Cod eGenera tionEngine.java:300) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGeneration Engine. java:97) ... 2 more Caused by: org.xml.sax.SAXException: Fatal Error: URI=file:///C:/axis2c-1/samples/client/g etMachines/JobManagement.wsdl Line=3: The content of elements must consist of well-formed character data or markup. at org.apache.axis2.util.XMLUtils$ParserErrorHandler.fatalError(XMLUtils.ja va:381) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDis patcher .dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno wn Sour ce) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:196) at org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:241) at org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:224) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(Cod eGenera tionEngine.java:294) ... 3 more. Can you tell me where exactly the problem is? Thanks and regards Sushmita CAUTION - Disclaimer * This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS End of Disclaimer INFOSYS*** JobManagement.wsdl Description: JobManagement.wsdl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
