Re: [Axis2/C]: SOAP request with line breaks fails
Subra A Narayanan wrote: Hey Manjula, I checked out the latest source code from svn and built it. But when I try to build the samples, I get an error. Since there is no configue.sh file in the samples directory, I had to run the build.sh script file. It dies half way through. This is the error I get ... ... checking for string.h... (cached) yes checking for an ANSI C-conforming const... yes ./configure: line 20467: syntax error near unexpected token `LIBXML2,' ./configure: line 20467: `PKG_CHECK_MODULES(LIBXML2, libxml-2.0)' make: *** No targets specified and no makefile found. Stop. make: *** No rule to make target `install'. Stop. Hi Subra, Can you please send your output to a file when you run build sh and attach it. ./build.sh out 21 Because these details are not enough to identify the problem :-( Anyway you need following packages to build axis2/c Autoconf 2.59 or higher Automake 1.9 or higher Aclocal 1.9 or higher libtool 1.9 or higher libxml2-dev zlib1g-dev pkg-config Thanks ~sanjaya I would like to mention that when I tried building axis2/c from source, it complained about pkg-config version should be atleast 0.20 and I had 0.19. So I downloaded, built and installed pkg-config 0.22 version. It was installed in the /usr/local/bin directory as compared to version 0.19 which was installed in /usr/bin directory. Thanks for the help! Subra On 8/7/07, *Manjula Peiris* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi subra, This is a bug in Axis2/C 1.0. But it has been fixed after 1.0 and in the current svn trunk it is working. -Manjula. On Mon, 2007-08-06 at 22:57 -0400, Subra A Narayanan wrote: Hey Samisa, I am using Axis2/C 1.0, source distribution on Linux. I compiled the source with the apache http module. Thanks for your follow-up abt my earlier issue. I will respond to that email separately so that someone following that thread will also benefit. Thanks again for ur quick response! Subra On 8/6/07, Samisa Abeysinghe [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: What version of Axis2/C you are using? We had a problem like this, but if I remember right we have fixed it. BTW, have you been able to solve the service compilation problem that you discussed in the other thread? Samisa... Subra A Narayanan wrote: Hello everyone, I found an interesting issue today and was wondering if someone else has seen tha same issue before. I am using Axis2/C on Linux. I have a web service running. When the client tries calling the web service using SOAP, the web service works if there are no line breaks in the SOAP request. If there are any line breaks, the server just crashes. So for eg == This works (SOAP msg with no line breaks) soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header/soapenv:Headersoapenv:BodyRemoveFileOwnerjordan/OwnerFileName sircharles.gif/FileNameFileID1234/FileID/RemoveFile/soapenv:Body/soapenv:Envelope == while this fails (formatted SOAP msg with line breaks) env:Envelope xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd= http://www.w3.org/2001/XMLSchema; env:Header/env:Header env:Body n1:RemoveFile xmlns:n1= http://www.xyz.com/2007/07/ n1:Ownerharry/n1:Owner n1:FileNamedel1.jpg /n1:FileName n1:FileIDchecksum/n1:FileID /n1:RemoveFile /env:Body /env:Envelope ==This is what I see in the axis2.log file [Mon Aug 6 13:59:22 2007] [debug] engine.c(571) Invoking phase Dispatch [Mon Aug 6 13:59:22 2007] [debug] phase.c(195) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Mon Aug 6 13:59:22 2007] [debug] soap_body_disp.c(217) Checking for operation using SOAP message body's first child's local name : RemoveFile [Mon Aug 6 13:59:22 2007] [debug] soap_body_disp.c(226) Operation found using SOAP message body's first child's local name [Mon Aug 6 13:59:22 2007]
Using AXIS2C from scripting environment
Hello, I am trying to use AXIS2C from a scripting environment. I get a access violation at axis2_engine_send::AXIS2_TRANSPORT_SENDER_INVOKE that causes my environment to crash. To detect the problem, I tried to build the axutil dll on VC++ express edition only to find that the dll I create is generating error much earlier!! Any clues? Regards, Yuva
Re: [Axis2/C]: SOAP request with line breaks fails
Hey Manjula, I got the latest source code from svn and built it. I am still getting an error when there are line breaks in the incoming SOAP request. I did an svn update and this is what it tells me: [devwsserver:~/axis2c-svn/c]$ svn update At revision 563913. Was the bug fixed in the above mentioned revision or some other revision. The server just hangs up when the request is received. Sanjaya, I installed the latest version of pkg-config and that solved my build issues. Thanks!! Subra On 8/8/07, Sanjaya Ratnaweera [EMAIL PROTECTED] wrote: Subra A Narayanan wrote: Hey Manjula, I checked out the latest source code from svn and built it. But when I try to build the samples, I get an error. Since there is no configue.sh file in the samples directory, I had to run the build.shscript file. It dies half way through. This is the error I get ... ... checking for string.h... (cached) yes checking for an ANSI C-conforming const... yes ./configure: line 20467: syntax error near unexpected token `LIBXML2,' ./configure: line 20467: `PKG_CHECK_MODULES(LIBXML2, libxml-2.0)' make: *** No targets specified and no makefile found. Stop. make: *** No rule to make target `install'. Stop. Hi Subra, Can you please send your output to a file when you run build sh and attach it. ./build.sh out 21 Because these details are not enough to identify the problem :-( Anyway you need following packages to build axis2/c Autoconf 2.59 or higher Automake 1.9 or higher Aclocal 1.9 or higher libtool 1.9 or higher libxml2-dev zlib1g-dev pkg-config Thanks ~sanjaya I would like to mention that when I tried building axis2/c from source, it complained about pkg-config version should be atleast 0.20 and I had 0.19. So I downloaded, built and installed pkg-config 0.22 version. It was installed in the /usr/local/bin directory as compared to version 0.19which was installed in /usr/bin directory. Thanks for the help! Subra On 8/7/07, Manjula Peiris [EMAIL PROTECTED] wrote: Hi subra, This is a bug in Axis2/C 1.0. But it has been fixed after 1.0 and in the current svn trunk it is working. -Manjula. On Mon, 2007-08-06 at 22:57 -0400, Subra A Narayanan wrote: Hey Samisa, I am using Axis2/C 1.0, source distribution on Linux. I compiled the source with the apache http module. Thanks for your follow-up abt my earlier issue. I will respond to that email separately so that someone following that thread will also benefit. Thanks again for ur quick response! Subra On 8/6/07, Samisa Abeysinghe [EMAIL PROTECTED] wrote: What version of Axis2/C you are using? We had a problem like this, but if I remember right we have fixed it. BTW, have you been able to solve the service compilation problem that you discussed in the other thread? Samisa... Subra A Narayanan wrote: Hello everyone, I found an interesting issue today and was wondering if someone else has seen tha same issue before. I am using Axis2/C on Linux. I have a web service running. When the client tries calling the web service using SOAP, the web service works if there are no line breaks in the SOAP request. If there are any line breaks, the server just crashes. So for eg == This works (SOAP msg with no line breaks) soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header/soapenv:Headersoapenv:BodyRemoveFileOwnerjordan/OwnerFileName sircharles.gif/FileNameFileID1234/FileID/RemoveFile/soapenv:Body/soapenv:Envelope == while this fails (formatted SOAP msg with line breaks) env:Envelope xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd= http://www.w3.org/2001/XMLSchema; env:Header/env:Header env:Body n1:RemoveFile xmlns:n1= http://www.xyz.com/2007/07/ n1:Ownerharry/n1:Owner n1:FileNamedel1.jpg /n1:FileName n1:FileIDchecksum/n1:FileID /n1:RemoveFile /env:Body /env:Envelope ==This is what I see in the axis2.log file [Mon Aug 6 13:59:22 2007] [debug] engine.c(571) Invoking phase Dispatch [Mon Aug 6 13:59:22 2007] [debug] phase.c(195) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Mon Aug 6 13:59:22 2007] [debug]
Re: Unable to run client code
Subra A Narayanan wrote: Hello folks, I am trying to write a client using Axis2/C to connect to a Axis2/C web service. These are the steps I followed 1. Created a wsdl file by hand for my web service. 2. Used the WSDL2C tool to generate the client stubs. Here is the command I used java org.apache.axis2.wsdl.WSDL2C -D org.apache.adb.properties=/org/apache/axis2/schema/c-schema-compile.properties -uri myservice.wsdl -l c -d none 3. Added code to the generated .c file 4. Compiled the client code using the following command gcc -o hello_clnt -I /usr/local/axis2c/include/axis2-1.1/ -L /usr/local/axis2c/lib/ -l axutil -l axis2_engine axis2_stub_myservice.c 5. Tried running the client and got this error ./hello_clnt: error while loading shared libraries: libaxutil.so.0: cannot open shared object file: No such file or directory You probably need to add your Axis2/C lib folder to LD_LIBRARY_PATH environment variable. e.g. If you have installed Axis2/C to /usr/local/axis2c then you will find the .so files in /usr/local/axis2c/lib, hence you can use: export LD_LIBRARY_PATH=/usr/local/axis2c/lib:$LD_LIBRARY_PATH HTH Samisa... What am I doing wrong? Am I missing any compiler options? Thank you everyone for the help! 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: [Axis2/C]: SOAP request with line breaks fails
Subra A Narayanan wrote: Hey Manjula, I got the latest source code from svn and built it. I am still getting an error when there are line breaks in the incoming SOAP request. I did an svn update and this is what it tells me: [devwsserver:~/axis2c-svn/c]$ svn update At revision 563913. This revision should be fine, the problem is solved before this revision. Just try to clean up the whole system (make distclean) and build from scratch and try. 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]
Re: [Axis2/C]: SOAP request with line breaks fails
Samisa, Where should I run the distclean from? I mean which folder? My original installation was in /usr/local/axis2c. I deleted the whole axis2c folder and built everything from scratch today. Do you think I still need to run distclean and will that solve my problem? Pls let me know. Thanks so much. On 8/8/07, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Subra A Narayanan wrote: Hey Manjula, I got the latest source code from svn and built it. I am still getting an error when there are line breaks in the incoming SOAP request. I did an svn update and this is what it tells me: [devwsserver:~/axis2c-svn/c]$ svn update At revision 563913. This revision should be fine, the problem is solved before this revision. Just try to clean up the whole system (make distclean) and build from scratch and try. 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]
Re: Using AXIS2C from scripting environment
Yuvaraj, Yuvaraj Athur Raghuvir [EMAIL PROTECTED] writes: Hello, I am trying to use AXIS2C from a scripting environment. I get a access violation at axis2_engine_send::AXIS2_TRANSPORT_SENDER_INVOKE that causes my environment to crash. What does your log file says? thanks, Dinesh -- Dinesh Premalal http://xydinesh.wordpress.com/ GPG ID : A255955C GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using AXIS2C from scripting environment
Hi Yuva, There are few posibilities that might produce this error. Try putting axiom_xml_reader_init (); function at the start of your code. This function initializes the parser for threaded environment. Thanks Nandika On 8/8/07, Yuvaraj Athur Raghuvir [EMAIL PROTECTED] wrote: Hello, I am trying to use AXIS2C from a scripting environment. I get a access violation at axis2_engine_send::AXIS2_TRANSPORT_SENDER_INVOKE that causes my environment to crash. To detect the problem, I tried to build the axutil dll on VC++ express edition only to find that the dll I create is generating error much earlier!! Any clues? Regards, Yuva -- [EMAIL PROTECTED] WSO2 Inc: http://www.wso2.com
Re: Using AXIS2C from scripting environment
Hello Dinesh, This is what the log file says: Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c- src-1.0.0\axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231) module name is:addressing [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c- src-1.0.0\axis2c-src-1.0.0\src\core\phaseresolver\phase_holder.c(129) Add handler AddressingOutHandler to phase MessageOut [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c- src-1.0.0\axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231) module name is:addressing [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c- src-1.0.0\axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231) module name is:addressing [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c- src-1.0.0\axis2c-src-1.0.0\src\core\phaseresolver\phase_holder.c(129) Add handler AddressingOutHandler to phase MessageOut [Thu Aug 09 11:27:45 2007] [debug] c:\08.utils\axis2\axis2c- src-1.0.0\axis2c-src-1.0.0\src\core\engine\engine.c(572) Invoking phase MessageOut [Thu Aug 09 11:27:45 2007] [debug] c:\08.utils\axis2\axis2c- src-1.0.0\axis2c-src-1.0.0\src\core\engine\phase.c(195) Invoke the handler AddressingOutHandler within the phase MessageOut Regards, Yuva On 8/9/07, Dinesh Premalal [EMAIL PROTECTED] wrote: Yuvaraj, Yuvaraj Athur Raghuvir [EMAIL PROTECTED] writes: Hello, I am trying to use AXIS2C from a scripting environment. I get a access violation at axis2_engine_send::AXIS2_TRANSPORT_SENDER_INVOKE that causes my environment to crash. What does your log file says? thanks, Dinesh -- Dinesh Premalal http://xydinesh.wordpress.com/ GPG ID : A255955C GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Question about Fault Structure
Hello, I have a question regarding the fault structure generated by Axis... How can we stop the generation of multiRef in the fault structure?. I have used the property: globalConfiguration ... parameter name=sendMultiRefs value=false/ ... /globalConfiguration Regretably I see still times fault structure with multiRefs. Please let me know about your ideas regarding to this problem. Thanks and Regards, Indira Hidalgo. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Setting faultactor tag in soap fault 1.1
Hello, I'm trying to generate complete SOAPFault 1.1. Using AxisFault constructor, I always get the same fault message tags: ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client.Header/faultcode faultstringHeader couldn't be validated against the xsd/faultstring detail ExceptionClientException /Exception /detail /soapenv:Fault /soapenv:Body /soapenv:Envelope The problem is that I would like to have the faultactor tag as well. Reading at the documentation, I understand that if I want faultactor tag in SOAP1.1 I have to set the faultNode. The mapping SOAP12 - SOAP11 in the javadoc seems to indicate that So when I'm building the AxisFault, I'm calling: new AxisFault(theCode, theMessage, theActor, discarded in SOAPFault 1.1, theOMElement) When I'm calling getFaultNode, the actor is correctly set. What am I missing to get the tag in the response? Thanks in advance, Pierre
Rampart SNAPSHOT problems
Hi all, Im having some problems with last rampart snapshot. First, I'm using basic configuration on client as with 1.2 and policy on server side. Rampart is engaged in both. In server is engaged in service scope and in client at global scope. I receive an exception from service that makes me thing about a problem in phases order: org.apache.axis2.AxisFault: The org.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:355) at org.apache.axis2.addressing.AddressingFaultsHelper.triggerMessageAddressingRequiredFault(AddressingFaultsHelper.java:281) at org.apache.axis2.handlers.addressing.AddressingValidationHandler.checkMessageIDHeader(AddressingValidationHandler.java:168) at org.apache.axis2.handlers.addressing.AddressingValidationHandler.invoke(AddressingValidationHandler.java:56) at org.apache.axis2.engine.Phase.invoke(Phase.java:292) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) header is required when WS-Addressing is in use but was not sent. at org.apache.axis2.handlers.addressing.AddressingInFaultHandler.invoke(AddressingInFaultHandler.java:114) at org.apache.axis2.engine.Phase.invoke(Phase.java:292) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:336) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at client.Medici_LinkStub.validate(Medici_LinkStub.java:744) at client.ClientUtilities.validateTest(ClientUtilities.java:61) at client.Client.main(Client.java:34) Second, I removed configuration from client but keeping rampart engaged and I receive this exception from the service: org.apache.axis2.AxisFault: java.lang.NullPointerException at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at client.Medici_LinkStub.validate(Medici_LinkStub.java:744) at client.ClientUtilities.validateTest(ClientUtilities.java:61) at client.Client.main(Client.java:34) Third, I remove module ref=rampart/ from services.xml and the first operation works ok but for the nexts I see an exception ocurred in the client: org.apache.axis2.AxisFault: Error in extracting message properties at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:68) at org.apache.axis2.engine.Phase.invoke(Phase.java:292) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374) at
Re: disable http chunking
Erwin, You mean the On 8/8/07, Erwin Reinhoud [EMAIL PROTECTED] wrote: Hello All, I am trying to disable serverside http chunking so i can log messages with the ws-i monitor tool. I removed the Transfer-encoding parameter from the axis2.xml but the response is still send in chunks. If i remove all content from the axis2.xml i get an eof exception, so assume it is reading the file. Now what am i overlooking here? Please comment. Thanks in advance. Kind regards, Erwin - 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: Rampart error with MustUnderstand
Hi, It looks like your client is set up to add a timestamp and signature, but the server has not been configured to expect them. I got the same error when I configured rampart on my client but not on my server. The Must Understand flag means: If the server doesn't understand this header element, then it must report an error rather than continue processing. cheers, Michael from sunny Ottawa -Original Message- From: Ford, Jennifer M. [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 07, 2007 6:17 PM To: axis-user@ws.apache.org Subject: Rampart error with MustUnderstand I have spent the last couple days trying to add Rampart to an existing web service with Policy/Sample02 as a model. I feel like I'm close, but I can't seem to get past the most recent error: 2007-08-07 16:43:12,066 DEBUG org.apache.axis2.transport.http.AxisServlet - org.apache.axis2.AxisFault: Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecu rity-secex t-1.0.xsd : Security Perhaps a stupid question, but what does the Must Understand check do exactly? And, more importantly, what might cause this problem? Thanks, Jennifer - 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: disable http chunking
Hello Dims, I disabled chuncking for the client succesfully, but for the service not so. In the service axis2.xml i removed the Transfer-encoding parameter so was hoping that both request and response would have no chunking. I left the protocol parameter to HTTP/1.1. This was all because the ws-i monitor seems to trip on the chunked request because the HTTP content-length parameter is not present. It does not seem to mind that the response is send as chunked data so i can perform the ws-i validation. However, i am still wondering why i cant get the service to send unchunked data. Thanks and kind regards, Erwin -Oorspronkelijk bericht- Van: Davanum Srinivas [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 augustus 2007 14:55 Aan: axis-user@ws.apache.org Onderwerp: Re: disable http chunking Erwin, You mean the client is using HTTP 1.0 w/o chunking and the server responds with HTTP 1.1 with chunking? -- dims On 8/8/07, Erwin Reinhoud [EMAIL PROTECTED] wrote: Hello All, I am trying to disable serverside http chunking so i can log messages with the ws-i monitor tool. I removed the Transfer-encoding parameter from the axis2.xml but the response is still send in chunks. If i remove all content from the axis2.xml i get an eof exception, so assume it is reading the file. Now what am i overlooking here? Please comment. Thanks in advance. Kind regards, Erwin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com -- 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: disable http chunking
Hello Dims, Thanks for the help. Kind regards, Erwin -Oorspronkelijk bericht- Van: Davanum Srinivas [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 augustus 2007 15:34 Aan: axis-user@ws.apache.org Onderwerp: Re: disable http chunking the chunking for the response from the server is governed by the servlet engine...not by Axis2. So if you force the client to use HTTP 1.0, the container will reply back using HTTP 1.0. See http://tomcat.apache.org/tomcat-5.5-doc/config/http.html for more info. thanks, dims On 8/8/07, Erwin Reinhoud [EMAIL PROTECTED] wrote: Hello Dims, I disabled chuncking for the client succesfully, but for the service not so. In the service axis2.xml i removed the Transfer-encoding parameter so was hoping that both request and response would have no chunking. I left the protocol parameter to HTTP/1.1. This was all because the ws-i monitor seems to trip on the chunked request because the HTTP content-length parameter is not present. It does not seem to mind that the response is send as chunked data so i can perform the ws-i validation. However, i am still wondering why i cant get the service to send unchunked data. Thanks and kind regards, Erwin -Oorspronkelijk bericht- Van: Davanum Srinivas [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 augustus 2007 14:55 Aan: axis-user@ws.apache.org Onderwerp: Re: disable http chunking Erwin, You mean the client is using HTTP 1.0 w/o chunking and the server responds with HTTP 1.1 with chunking? -- dims On 8/8/07, Erwin Reinhoud [EMAIL PROTECTED] wrote: Hello All, I am trying to disable serverside http chunking so i can log messages with the ws-i monitor tool. I removed the Transfer-encoding parameter from the axis2.xml but the response is still send in chunks. If i remove all content from the axis2.xml i get an eof exception, so assume it is reading the file. Now what am i overlooking here? Please comment. Thanks in advance. Kind regards, Erwin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com -- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: rpc-encoded vs rpc-literal vs document-literal migrate Axis1.4 wsdl (rpc-encoded) to Axis2 doc-lit
You call it an inconvenient, but it may be a blessing. I think they should be totally separate, that is, different container instances running, one for Axis2 and one for Axis1. This would allow them to run on different machines or even in different domains. It also brings up security concerns, in that the instance running Axis2 that communicates with the client may have much tighter security requirements than the web service Axis1, which is completely internal. The separation allows your production support people more flexibility. Having said that, I'm sure you probably could get both Axis1 and Axis2 running in the same Tomcat instance, or whatever container your running. But I think it would introduce problems down the road. Since all of the libraries are named differently between Axis2 and Axis1, and I believe you can use the same jdk version for both (since jdk's tend to be very good at backwards compatibility) and also considering that the Axis source code is a neatly packaged web application, in theory I think you could get them to run side by side, but again, I doubt it's good archjitectural practice to do so. Regards, -jeff -Original Message- From: Alberto Patino [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 12:26 AM To: axis-user@ws.apache.org Subject: Re: rpc-encoded vs rpc-literal vs document-literal migrate Axis1.4 wsdl (rpc-encoded) to Axis2 doc-lit OK, I got the point. Thats exactly the the way the ESB would decouple the axis2 document/literal service from the axis1 rpc/encoded. I only see an inconvenient: I'll require an axis1 engine resident in its own servlet container, could it be the same servlet container that holds the axis2 engine? Would it be a good practice? Thanks On 7/30/07, Walker, Jeff [EMAIL PROTECTED] wrote: I wouldn't try mixing Axis2 with Axis1 libraries in the same deployment. Sounds like a recipe for disaster. I'd recommend a Composite web service design. The first web service is Axis2-based and that is exposed to the Client. This uses SOAP 1.2, WSDL 2.0 and doc/lit for comms (whatever latest and greatest specs you want, really). That Axis2 service is a client of a 2nd service, which is Axis1 based (it is a totally separate deployment). This uses SOAP 1.1, WSDL 1.1 and doc/lit for comms between the two services. That Axis1 service is a client of the final RPCEncodedService, comms between these two is SOAP 1.1, WSDL 1.1 and rpc/encoded. -jeff -Original Message- From: alpatino2 [mailto:[EMAIL PROTECTED] Sent: Monday, July 30, 2007 11:17 AM To: axis-user@ws.apache.org Subject: Re: rpc-encoded vs rpc-literal vs document-literal migrate Axis1.4 wsdl (rpc-encoded) to Axis2 doc-lit Thanks for the help, I see the necessity to use axis1, now what do you think is the best way to invoke this rpc/encoded service, I want to write a higher level service in axis2 using document/literal style, and inside of this service invoke to the rpc service, but I think I need to mix axis1 and axis2 libraries, I know I could decouple service invokation using a ESB, but I cannot afford to use this. Client---Axis2 (Doc Literal)Service -- rpc/encoded __ |-- doc/literal __ |-- Thanks again Use Axis 1.4 instead. Anne On 7/30/07, Philipp Leitner [EMAIL PROTECTED] wrote: AFAIK Axis 2 does not support RPC/encoded at all since it is not WS-I compliant. /philipp alpatino2 schrieb: Hi! I have a slightly different requirement: I received wsdl's from a service provider that implements the TR-069 spec, this spec define the use of rpc/encoded style. I need to invoke this service but I am not able to generate the client, I tried to generate the client for the sample stockAvailableNotification.wsdl extracted from the Building Web Services with Java book, but I get the following error: -- View this message in context: http://www.nabble.com/rpc-encoded-vs-rpc-literal-vs-document-literal-mig rate-Axis1.4-wsdl-%28rpc-encoded%29-to-Axis2-doc-lit-tf4113634.html#a118 65674 Sent from the Axis - User mailing list archive at Nabble.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] -- Don't be evil!!! - 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][VOTE]Axis2 1.3 release artifacts (#take2)
Hi all, am I wrong or the JMS lib is missing? Michele On Wed, 2007-08-08 at 16:06 +0530, Deepal jayasinghe wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I have uploaded Axis2 1.3 into my Apache home location [1] . This release doesn't contain any SNAPSHOT dependencies and we haven't done any major changes since RC3. Please test this release as much as you can and help us to make this release stable. You can find both IntelliJ idea and Eclipse plugin artifacts in the tools folder [2] Please try to cover the following areas when testing. - - Code generation - - Sessions - - Web application - - In different application servers - - Both JDK 1.5 and JDK 1.4 - - Java2WSDL - - POJOs - - And whatever the JIRA we have marked as fixed. You can find maven2 repository under my home directory as well [3]. I will do the final release on Friday (10th Aug 2007), here is my +1 for the release date as well as for release artifacts. [1] : http://people.apache.org/~deepal/axis2/1.3-take2/ [2] : http://people.apache.org/~deepal/axis2/1.3-take2/tools/ [3] : http://people.apache.org/~deepal/axis2/1.3-take2/m2-repo/ P.S : Please note that I need to have two more PMC vote to go ahead with the release. Thanks Deepal -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGuZyhjOGcXNDx0CARAtB+AJ4zj1XbXxv24WRj+axe37reelxZywCguQby uHxCZTuam5XgtJq+uaP+CF4= =AbF+ -END PGP SIGNATURE- - 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][VOTE]Axis2 1.3 release artifacts (#take2)
Michele Mazzucco wrote: Hi all, am I wrong or the JMS lib is missing? Nope , we do not need to add JMS jars by default, since we have not unable JMS transport by default. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Does Endpoint API work in 1.3 RC2 release ?
Hi,
I tried the sample jaxws-calculator sample from axis2-1.3 RC2 dist as
AAR and it works. Then tried using Endpoint API, I am having problems.
I wrote a main class like this:
import javax.xml.ws.Endpoint;
import org.apache.axis2.jaxws.calculator.CalculatorService;
public class StandaloneServiceStartupUsingEndpointPublish
{
public static void main( String[] args )
{
System.out.println(Starting Server...);
Endpoint ep = Endpoint.create( new CalculatorService() );
ep.publish( http://localhost:9090/CalculatorService; );
}
}
Problems:
1. Even though I have specified port 9090, the transport is started on
8080.
2. Trying to get wsdl using http://localhost:9090/CalculatorService?wsdl
in browser results this error:
Exception
org.apache.axis2.AxisFault: The service cannot be found for the endpoint
reference (EPR) /services/
at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.
java:63)
at org.apache.axis2.engine.Phase.invoke(Phase.java:308)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132)
at
org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.
java:125)
at
org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil
.java:119)
at
org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:229)
at
org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHtt
pService.java:256)
at
org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(Axi
sHttpService.java:163)
at
org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServ
iceProcessor.java:85)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker
.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker
.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
/Exception
PS: This works in jaxws-ri.
Please help.
thanx
-yogen
NOTICE: If received in error, please destroy and notify sender. Sender does not
intend to waive confidentiality or privilege. Use of this email is prohibited
when received in error.
RE: [Axis2] Zero Blockers for 1.3
Hi Dims, This is regarding JIRA AXIS2-2352. Even though the NPE in AxisServlet.java is fixed in AXIS2 1.3 SNAPSHOT, I'm still getting NPE in my ResponsysWSServiceMessageReceiverInOut.java. I've updated the JIRA with the details. Thanks Raghu -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Monday, August 06, 2007 6:07 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: Re: [Axis2] Zero Blockers for 1.3 Try removing the jalopy jar. I think it is generating a huge file which jalopy has trouble reformatting. thanks, dims On 8/6/07, Jorge Fernandez [EMAIL PROTECTED] wrote: Hi Dims Axis2 3076 created. Today I tried it again and it works different. It doesn'f finish when generating the client if I do it without -u option. Yesterday it didn't work when generating both client and server at a time. I have all my schemas defined in the wsdl. I noticed one change: In version 1.2, exceptions names were built from their message name, adding Exception and now they are only formed with message name. Is this right?? Now it generates Stub only for SOAP 1.2, doesn't it? Also, it is still generating faultExceptionNameMap.put() faultExceptionClassNameMap.put() faultMessageMap.put() for each operation that throws the exception, instead of generating one for each exception, in the client populateFaults() method. There is a JIRA already opened for that:Axis2 2326. Thanks, Jorge Fernández Davanum Srinivas [EMAIL PROTECTED] escribió: oops! hit send too fast...recrusion problem with wsdl imports or schema includes. -- dims On 8/5/07, Davanum Srinivas wrote: Please log a bug in JIRA with your stripped down test. could be a recursion problem. thanks, dims On 8/5/07, Jorge Fernandez wrote: Hi Dims, I'm getting one problem with RC3. I'm trying to generate my code for doing my testing but, wsdl2java doesn't return control back and it uses a big amount of resources. It seems that is generating the code or some of them but it never finishes. Regards, Jorge Fernández Davanum Srinivas escribió: Folks, At this moment there are zero blockers in JIRA for 1.3. Please try RC3 released friday (http://people.apache.org/~deepal/axis2/1.3-RC3/) or 1.3 branch's nightly build from here - http://people.apache.org/dist/axis2/nightly/ *Please* make sure you try it out as this is the last chance before we cut 1.3 Final early next week. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - 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! . -- Davanum Srinivas :: http://davanum.wordpress.com -- Davanum Srinivas :: http://davanum.wordpress.com - 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! . -- 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]
wsdl2java.sh issue
Hello all, I'm using Axis2 1.3 RC2 and trying to generate a client stub for a web service, but I'm receiving an error. I'm generating stubs for three other web service endpoints before this one is attempted in my build script. Those are successful and work great. The last returns this error: [echo] Generating ReceiveDocumentBatch Stub... [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: Element QName is null for ReceiveDocumentBatch_faultMsg! [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate (CodeGenerationEngine.java:265) [java] at org.apache.axis2.wsdl.WSDL2Code.main (WSDL2Code.java:35) [java] at org.apache.axis2.wsdl.WSDL2Java.main (WSDL2Java.java:24) [java] Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: Element QName is null for ReceiveDocumentBatch_faultMsg! [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitt er.emitStub(AxisServiceBasedMultiLanguageEmitter.java:527) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate (CodeGenerationEngine.java:254) [java] ... 2 more [java] Caused by: java.lang.RuntimeException: Element QName is null for ReceiveDocumentBatch_faultMsg! [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitt er.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:2751) [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitt er.getFaultElement(AxisServiceBasedMultiLanguageEmitter.java:2673) [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitt er.generateMethodElement(AxisServiceBasedMultiLanguageEmitter.java:2199) [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitt er.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:2117) [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitt er.createDOMDocumentForCallbackHandler (AxisServiceBasedMultiLanguageEmitter.java:1144) [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitt er.writeCallBackHandlers(AxisServiceBasedMultiLanguageEmitter.java:1110) [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitt er.emitStub(AxisServiceBasedMultiLanguageEmitter.java:490) [java] ... 3 more Here's the WSDL: ?xml version=1.0 encoding=utf-8? wsdl:definitions xmlns:tns=http://www.regents.ohio.gov/ ReceiveDocumentBatch/ xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl=http:// schemas.xmlsoap.org/wsdl/ name=ReceiveDocumentBatch targetNamespace=http://www.regents.ohio.gov/ReceiveDocumentBatch/; wsdl:types xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema; targetNamespace=http://www.regents.ohio.gov/ReceiveDocumentBatch/; xsd:element name=ReceiveDocumentBatch xsd:complexType xsd:sequence xsd:element name=in type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element xsd:element name=ReceiveDocumentBatchResponse xsd:complexType xsd:sequence xsd:element maxOccurs=1 minOccurs=1 name=BatchID type=xsd:int/ xsd:element maxOccurs=1 minOccurs=1 name=DocumentsRemaining type=xsd:int /xsd:element xsd:element maxOccurs=1 minOccurs=1 name=DocumentCount type=xsd:int /xsd:element xsd:element maxOccurs=1 minOccurs=1 name=checkSum type=xsd:string /xsd:element xsd:element maxOccurs=1 minOccurs=1 name=Data type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element xsd:element name=ReceiveDocumentBatchList xsd:complexType xsd:sequence xsd:element name=in type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element xsd:element name=ReceiveDocumentBatchListResponse xsd:complexType xsd:sequence xsd:element maxOccurs=unbounded minOccurs=0 name=BatchID type=xsd:string/
Axis 2 https port address
Hi, I have deployed a service in weblogic which listens at both http and https addresses. My service is build using useOriginalWsdl=true option. I'm giving the wsdl and asking Axis to just change the port address. Also I haven't changed any options in axis.xml. Everything is default. Here is my problem. I'm able to get wsdl using both http and https addresses. But If I get the wsdl using https, then the port address is http. I believe it should be https. Am I missing something? Is there any configuration for this in axis.xml? Thanks, Haneef - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Does Endpoint API work in 1.3 RC2 release ?
Hello Anyone,
Has someone tried publishing the service using JAXWS Endpoint API in
Axis2 1.3 RC2 ?
I think the problem is bcoz of this code in EndpointImpl class:
public void publish(String s) {
ConfigurationContext ctx =
endpointDesc.getServiceDescription().getAxisConfigContext();
try {
// For some reason the AxisService has not been added to the
ConfigurationContext
// at this point, so we need to do it for the service to be
available.
AxisService svc = endpointDesc.getAxisService();
ctx.getAxisConfiguration().addService(svc);
} catch (AxisFault e) {
throw ExceptionFactory.makeWebServiceException(e);
}
// Remove the default axis2 context root.
ctx.setContextRoot(/);
WorkerFactory wf = new HTTPWorkerFactory();
try {
server = new SimpleHttpServer(ctx, wf, 8080); //TODO: Add a
configurable port
server.init();
server.start();
} catch (IOException e) {
throw ExceptionFactory.makeWebServiceException(e);
}
published = true;
}
-yogen
From: Yadav, Yogendra (IT)
Sent: Wednesday, August 08, 2007 12:59 PM
To: axis-user
Subject: Does Endpoint API work in 1.3 RC2 release ?
Hi,
I tried the sample jaxws-calculator sample from axis2-1.3 RC2 dist as
AAR and it works. Then tried using Endpoint API, I am having problems.
I wrote a main class like this:
import javax.xml.ws.Endpoint;
import org.apache.axis2.jaxws.calculator.CalculatorService;
public class StandaloneServiceStartupUsingEndpointPublish
{
public static void main( String[] args )
{
System.out.println(Starting Server...);
Endpoint ep = Endpoint.create( new CalculatorService() );
ep.publish( http://localhost:9090/CalculatorService; );
}
}
Problems:
1. Even though I have specified port 9090, the transport is started on
8080.
2. Trying to get wsdl using http://localhost:9090/CalculatorService?wsdl
in browser results this error:
Exception
org.apache.axis2.AxisFault: The service cannot be found for the endpoint
reference (EPR) /services/
at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.
java:63)
at org.apache.axis2.engine.Phase.invoke(Phase.java:308)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132)
at
org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.
java:125)
at
org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil
.java:119)
at
org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:229)
at
org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHtt
pService.java:256)
at
org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(Axi
sHttpService.java:163)
at
org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServ
iceProcessor.java:85)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker
.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker
.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
/Exception
PS: This works in jaxws-ri.
Please help.
thanx
-yogen
NOTICE: If received in error, please destroy and notify sender. Sender
does not intend to waive confidentiality or privilege. Use of this email
is prohibited when received in error.
NOTICE: If received in error, please destroy and notify sender. Sender does not
intend to waive confidentiality or privilege. Use of this email is prohibited
when received in error.
RE: Rampart error with MustUnderstand
Well, it has stopped giving me errors for Must Understand, but still no luck on actually authenticating. It appears to get past the Timestamp processing, and then fails. Has anyone gotten a Rampart policy with AsymmetricBinding/Signature only to work properly? I would be interested in seeing your policy file. I am seeing the following error in the logs: 2007-08-08 15:51:56,983 DEBUG org.apache.ws.security.WSSecurityEngine - Unknown Element: BinarySecurityToken http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secex t-1.0.xsd That seems like probable cause for this to fail. I looked up that error on Google, and I see a lot of references to XML Pretty Printing (which I now have disabled in my client axis2.xml, although it does not appear to have made a difference in the output) and most of those messages were using Axis 1.3, not Axis2 as I am using. The other thing I am struggling with are the X509 token types and the decryption algorithm. Is it possible to find that information on the certificate itself? I was unable to find it, but I am thinking if I were wrong that would be another reason why my signature validation would fail. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 8:07 AM To: axis-user@ws.apache.org Subject: RE: Rampart error with MustUnderstand Hi, It looks like your client is set up to add a timestamp and signature, but the server has not been configured to expect them. I got the same error when I configured rampart on my client but not on my server. The Must Understand flag means: If the server doesn't understand this header element, then it must report an error rather than continue processing. cheers, Michael from sunny Ottawa -Original Message- From: Ford, Jennifer M. [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 07, 2007 6:17 PM To: axis-user@ws.apache.org Subject: Rampart error with MustUnderstand I have spent the last couple days trying to add Rampart to an existing web service with Policy/Sample02 as a model. I feel like I'm close, but I can't seem to get past the most recent error: 2007-08-07 16:43:12,066 DEBUG org.apache.axis2.transport.http.AxisServlet - org.apache.axis2.AxisFault: Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecu rity-secex t-1.0.xsd : Security Perhaps a stupid question, but what does the Must Understand check do exactly? And, more importantly, what might cause this problem? Thanks, Jennifer - 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: unable to run EchoHeaders.jws
Kramer wrote: I'm able to bring up: http://localhost:8080/axis/ but when I try the Call link to test EchoHeaders.jws I get the following error: http://localhost:8080/axis/EchoHeaders.jws?method=list faultstring java.io.FileNotFoundException: C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\axis\WEB-INF\jwsClasses\EchoHeaders.java /faultstring I also got a FileNotFoundException. I had to create the jwsClasses dir. Probably my problem was originally caused by incorrect permissions on WEB-INF. -- View this message in context: http://www.nabble.com/unable-to-run-EchoHeaders.jws-tf2217967.html#a12064393 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Apache Axis 2 Architecture Question
Hi, I have a question regarding the architecture of my Axis 2 client applications. Application description: We are using the WS-Security username token header to authenticate and identify users making requests to a web service. There are hundreds of different users using the system, and we need to log their user details on the Axis 2 web service, hence we need each user to have different identities coming through in the SOAP requests. The client for the service is a struts webapp. The question: In order to support multiple users with different identities I need to create a stub to the service for each client (e.g. load a configuration context and then create a service stub to the service) - thus if 100 users are using the client at the same time, there will be 100 service stubs in use at that point in time - this is because the user authentication is related to the stub (via the Options object) not to the individual methods. Is this the correct way of doing things in such a situation? It seems that it was intended for a given client site to only have one service stub to serve all the users using that client site. If its wrong, how should I be doing things? Is it possible to alter the user authentication details when a request goes out in a multi-threaded situation without making the code block? cheers, Ants. -- Anthony - Anthony Bull Senior Developer Black Coffee Software Ltd PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 Mobile 021 303 692 - www.bcsoft.co.nz --- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. Any views or opinions expressed in this email may be personal to the sender and are not necessarily those of Black Coffee Software Ltd. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsdl2java.sh issue
this is a problem with the wsdl you have to add the fault message pat to the first binding operation as well. wsdl:operation name=ReceiveDocumentBatch soap:operation soapAction= http://www.regents.ohio.gov/ReceiveDocumentBatch/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output wsdl:fault name=fault soap:fault name=fault use=literal/ /wsdl:fault /wsdl:operation On 8/8/07, Keith Veleba [EMAIL PROTECTED] wrote: Hello all, I'm using Axis2 1.3 RC2 and trying to generate a client stub for a web service, but I'm receiving an error. I'm generating stubs for three other web service endpoints before this one is attempted in my build script. Those are successful and work great. The last returns this error: [echo] Generating ReceiveDocumentBatch Stub... [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: Element QName is null for ReceiveDocumentBatch_faultMsg! [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate( CodeGenerationEngine.java:265) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) [java] Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: Element QName is null for ReceiveDocumentBatch_faultMsg! [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitStub (AxisServiceBasedMultiLanguageEmitter.java:527) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate( CodeGenerationEngine.java:254) [java] ... 2 more [java] Caused by: java.lang.RuntimeException: Element QName is null for ReceiveDocumentBatch_faultMsg! [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getFaultParamElements (AxisServiceBasedMultiLanguageEmitter.java:2751) [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getFaultElement (AxisServiceBasedMultiLanguageEmitter.java:2673) [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.generateMethodElement (AxisServiceBasedMultiLanguageEmitter.java:2199) [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.loadOperations (AxisServiceBasedMultiLanguageEmitter.java:2117) [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.createDOMDocumentForCallbackHandler (AxisServiceBasedMultiLanguageEmitter.java:1144) [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeCallBackHandlers (AxisServiceBasedMultiLanguageEmitter.java:1110) [java] at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitStub (AxisServiceBasedMultiLanguageEmitter.java:490) [java] ... 3 more Here's the WSDL: ?xml version=1.0 encoding=utf-8? wsdl:definitions xmlns:tns= http://www.regents.ohio.gov/ReceiveDocumentBatch/; xmlns:xsd= http://www.w3.org/2001/XMLSchema; xmlns:soap= http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; name=ReceiveDocumentBatch targetNamespace=http://www.regents.ohio.gov/ReceiveDocumentBatch/; wsdl:types xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema; targetNamespace=http://www.regents.ohio.gov/ReceiveDocumentBatch/; xsd:element name=ReceiveDocumentBatch xsd:complexType xsd:sequence xsd:element name=in type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element xsd:element name=ReceiveDocumentBatchResponse xsd:complexType xsd:sequence xsd:element maxOccurs=1 minOccurs=1 name=BatchID type=xsd:int/ xsd:element maxOccurs=1 minOccurs=1 name=DocumentsRemaining type=xsd:int /xsd:element xsd:element maxOccurs=1 minOccurs=1 name=DocumentCount type=xsd:int /xsd:element xsd:element maxOccurs=1 minOccurs=1 name=checkSum type=xsd:string /xsd:element xsd:element maxOccurs=1 minOccurs=1 name=Data type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element xsd:element name=ReceiveDocumentBatchList xsd:complexType xsd:sequence xsd:element name=in type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element xsd:element name=ReceiveDocumentBatchListResponse xsd:complexType xsd:sequence xsd:element maxOccurs=unbounded minOccurs=0 name=BatchID type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element xsd:element name=ReceiveDocumentBatchListFault xsd:complexType xsd:sequence xsd:element maxOccurs=1 minOccurs=1 name=Reason type=xsd:string /xsd:element /xsd:sequence /xsd:complexType /xsd:element xsd:element
