[axis2] 0.95->1.1 service deployment error
hi, if have just upgraded my web services from axis 0.95 to axis 1.1. now I'm getting an exception while deploying the ws. the QueryService.wsdl which gives the error is created by axis, so I don't know what to do with this. please, can someone help me with this? thanks, andreas 12:39:31,469 ERROR [WSDL11ToAxisServiceBuilder] WSDLException: faultCode=PARSER_ERROR: Problem parsing 'META-INF/QueryService.wsdl'.: The prefix "wsaw" for attribute "wsaw:Action" associated with an element type "wsdl:output" is not bound.: org.xml.sax.SAXParseException: The prefix "wsaw" for attribute "wsaw:Action" associated with an element type "wsdl:output" is not bound. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.readInTheWSDLFile(WSDL11ToAxisServiceBuilder.java:1612) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.setup(WSDL11ToAxisServiceBuilder.java:270) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:181) at org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFile(ArchiveReader.java:215) at org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(ArchiveReader.java:306) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:513) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:196) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:227) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:174) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:88) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:252) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:373) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:317) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3915) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4176) at org.apache.geronimo.tomcat.GeronimoStandardContext.access$201(GeronimoStandardContext.java:67) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:337) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:31) at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:192) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:313) at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke() at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$533eaa5e.addContext() at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:438) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBea
Re: [Axis2]: where to put ? Can't call an ejb from inside a service!
thank you martin for your thoughts. I have to try this one. looks interresting. I would not ever hit on that! andreas Martin Gainty schrieb: > Hello Andreas- > described inside the xsd (in Axis 1.x used to be wsdl / and is now > -Axis2.xml as in this example > > targetNamespace="http://java.sun.com/xml/ns/j2ee"; > xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"; > > you can construct complexTypes based on underlying j2ee referenced objects > as in this example > > > > > > > > > > Later on we can define our own individual elements based on previously > described j2ee:descriptionType as in this example.. > > type="j2ee:descriptionType" > minOccurs="0" > maxOccurs="unbounded"/> > > Anyone else? > M- > This e-mail communication and any attachments may contain confidential and > privileged information for the use of the > designated recipients named above. If you are not the intended recipient, you > are hereby notified that you have received > this communication in error and that any review, disclosure, dissemination, > distribution or copying of it or its > contents > - Original Message - > From: "Andreas Bohnert" <[EMAIL PROTECTED]> > To: > Sent: Wednesday, November 08, 2006 10:39 AM > Subject: [Axis2]: where to put ? Can't call an ejb from inside > a service! > > >> hi, >> >> I'm using axis2 0.95 (with geronimo) and I try to call a local ejb from >> inside my service. >> >> to resolve the ejb reference I normally put a or >> to the web.xml if I call from a webapplication or to the >> ejb-jar.xml, if I call from another ejb. >> >> but now I have an aar file with no deployment descriptor! service.xml >> seems to be not the right place ... >> well, I could put it to the axis2.war, but I don't want to mess it up >> with service specific stuff. >> >> Is there a nice way todo it? >> >> thanks for your help, >> andreas >> >> >> >> - >> 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]: where to put ? Can't call an ejb from inside a service!
hi, I'm using axis2 0.95 (with geronimo) and I try to call a local ejb from inside my service. to resolve the ejb reference I normally put a or to the web.xml if I call from a webapplication or to the ejb-jar.xml, if I call from another ejb. but now I have an aar file with no deployment descriptor! service.xml seems to be not the right place ... well, I could put it to the axis2.war, but I don't want to mess it up with service specific stuff. Is there a nice way todo it? thanks for your help, andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] error parsing wsdl
Hi, I just tried to upgrade from 0.95 to 1.0, but when I used WSDL2Java I got this error: [java] Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:94) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: org.apache.axis2.AxisFault: No port found for the given name :QueryServicePort; nested exception is: [java] org.apache.axis2.AxisFault: No port found for the given name :QueryServicePort [java] at org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBuilder.java:243) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:87) [java] ... 2 more [java] Caused by: org.apache.axis2.AxisFault: No port found for the given name :QueryServicePort [java] at org.apache.axis2.description.WSDL2AxisServiceBuilder.findBinding(WSDL2AxisServiceBuilder.java:275) [java] at org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBuilder.java:225) [java] ... 3 more [java] Java Result: 1 I didn't change my wsdl since 0.95. So I don't see the reason for this. Here is the relevant part from my wsdl file: http://schemas.xmlsoap.org/soap/http"; style="document" /> http://localhost:8080/axis2/services/QueryEndpoint"; /> Any idea? Thanks for any help!! andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] read documentation but still lost
@Ajith Ranabahu it's just the wsdl from the Code Generator Wizard - Command Line Tool tutorial, however I have attached it. @Chinthaka - axis2 snaphot compile failed I have started a new thread 'junit tests on today svn build failed' thanks for your help! andreas > Hi, > Can you attach the WSDL ? > > Ajith > > On 2/22/06, Andreas Bohnert <[EMAIL PROTECTED]> wrote: >>> You could try >>> minOccurs = 0 on any new fields, and my guess is that since the service >>> doesn't require them to be part of then envelope, they won't be missed if >>> they are not there. IOW, they can't be mandatory fields. >> I tried it with XMLBean databinding and it even works if I do not set >> them to minOccurs=0. >> thats perfect for me! >> >> I would like to check out if adb works as well, but since wsdl2java does >> not support adb right now (gives me a nullpointer exception), I have to >> wait for the next release. >> tried to compile current axis2 snapshot, but it failed :( >> >> >> thanks very much for your help, robert! >> andreas >> >> > > > -- > Ajith Ranabahu > http://login"; xmlns:tns="http://login"; xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:ns2="http://login/types";> http://login/types"; xmlns:tns="http://login/types"; xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns="http://www.w3.org/2001/XMLSchema";> http://schemas.xmlsoap.org/soap/encoding/"/> http://schemas.xmlsoap.org/soap/http"; style="document"/> http://localhost:8080/axis2/services/LoginEndpoint"/>
Re: [Axis2] read documentation but still lost
> You could try > minOccurs = 0 on any new fields, and my guess is that since the service > doesn't require them to be part of then envelope, they won't be missed if > they are not there. IOW, they can't be mandatory fields. I tried it with XMLBean databinding and it even works if I do not set them to minOccurs=0. thats perfect for me! I would like to check out if adb works as well, but since wsdl2java does not support adb right now (gives me a nullpointer exception), I have to wait for the next release. tried to compile current axis2 snapshot, but it failed :( thanks very much for your help, robert! andreas
junit tests on today svn build failed
some junit test on the today svn sources failed: test:test: [junit] Running samples.wsdl.perf.PerfPortTypeTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 13,588 sec [junit] Running org.apache.axis2.integration.EchoTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,486 sec [junit] Running org.apache.axis2.rpc.RPCCallTest [junit] Tests run: 16, Failures: 0, Errors: 0, Time elapsed: 45,255 sec [junit] Running org.apache.axis2.rpc.MultirefTest [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 26,033 sec [junit] Running org.apache.axis2.engine.ThreadingTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5,512 sec [junit] Running org.apache.axis2.engine.EchoRawXMLOnTwoChannelsSyncTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4,01 sec [junit] Running org.apache.axis2.engine.EchoRawXMLTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 11,606 sec [junit] Running org.apache.axis2.engine.CharactersetEncodingTest [junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 31,739 sec [junit] Running org.apache.axis2.engine.ServiceGroupContextTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4,158 sec [junit] Running org.apache.axis2.engine.ServiceCreateTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4,636 sec [junit] Running org.apache.axis2.engine.EchoRawXMLMultipleTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 12,948 sec [junit] Running org.apache.axis2.engine.MessageContextInjectionTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1,449 sec [junit] Running org.apache.axis2.engine.OneWayRawXMLTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4,077 sec [junit] Running org.apache.axis2.engine.CommonsHTTPEchoRawXMLTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6,335 sec [junit] Running org.apache.axis2.engine.MessageWithServerTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 64,298 sec [junit] Running org.apache.axis2.engine.WSDLClientTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4,664 sec [junit] Running org.apache.axis2.engine.SOAPversionTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 8,193 sec [junit] Running org.apache.axis2.engine.EchoRawXMLLoadTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3,934 sec [junit] Running org.apache.axis2.engine.EchoRawXMLChunkedTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4,041 sec [junit] Running org.apache.axis2.engine.EchoRawXMLOnTwoChannelsTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3,683 sec [junit] Running org.apache.axis2.engine.CallUnregisteredServiceTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3,712 sec [junit] Running org.apache.axis2.engine.ServiceDispatchingTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3,978 sec [junit] Running org.apache.axis2.engine.FaultHandlingTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6,031 sec [junit] Running org.apache.axis2.engine.HandlerFailureTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3,663 sec [junit] Running org.apache.axis2.engine.AxisServiceBuilderTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,772 sec [junit] Running org.apache.axis2.engine.EchoRawRuntimeProxyTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3,829 sec [junit] Running org.apache.axis2.groovy.GroovyServiceTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 13,046 sec [junit] Running org.apache.axis2.tcp.TCPEchoRawXMLTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 11,065 sec [junit] Running org.apache.axis2.tcp.TCPTwoChannelEchoRawXMLTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3,32 sec [junit] Running org.apache.axis2.security.Scenario1Test [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8,629 sec [junit] Running org.apache.axis2.security.Scenario2Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 13,439 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario2Test FAILED [junit] Running org.apache.axis2.security.Scenario2aTest [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 14,039 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario2aTest FAILED [junit] Running org.apache.axis2.security.Scenario3Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 13,102 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario3Test FAILED [junit] Running org.apache.axis2.security.Scenario4Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 13,097 sec [junit] [ERROR] TEST org.apac
Re: [Axis2] read documentation but still lost
thanks a lot for your answer, robert! > Do search for Axis2SampleDocLit.wsdl and you'll find that it is indeed rpc / > lit. You can find a simple doc / lit example in the code generation guide - > showing how to use ant with wsdl2java. ah, great, I missed that because I was working with the eclipse plugin instead. isn't it strange, that axis2 goes for document literal and provides a rpc literal example? > > This question comes up a lot recently. First, AFAIK you won't see the axis > 1.x > deserialization errors in axis2. As far as not syncing changes, I myself > haven't found a compelling reason to not sync changes and so I haven't tried > it. However, what you could do is trying to define your new elements as: > > element minOccurs="0" maxOccurs="1" I'm not sure what you mean with 'sync changes'.Is there a technique to automatically sync wsdl changes to the webservice client? Am I'm doing something wrong? my situation is this: the webservice client asks for data and the service is returning an array of complex data objects. the client displays the data or whatever. I give the client to different customers. some of them will use the client, some of them will build their own solution based on my example client. now, if I have to change my webservice ( add fields to my complex data object) our customers will be notified. some of them will update their client, but some of them wont. And I want to satisfy both with one webservice. when I use wsdl2java generator to build up the client, a java bean is generated for each complex type, so this beans (the old and the one after the update) do not match after a change and that's why I was asking for deserialization errors. > You can implement handlers to access the bodies and access all the elements, > but I don't see how it solves your problem. If you have fewer fields arriving > from the client because it hasn't been synced, how does modifying the body > help you? Maybe I misunderstand the question. I don't want to modify the body. I just want to read the content on the client side. If I write the client in such a way, that it parse the returned soap body (the returned array of data objects), in this case, I don't depend on a static bean. this will still work after an update (adding fields) to the service. please correct me, if I have someting wrong on my mind. thanks again, andreas
[Axis2] read documentation but still lost
hello, I have downloaded 0.94, have had a look at the documentation and the samples, but I have still a couple of questions and I hope the axis community can help me out: 1.) Axis2SampleDocLit seems to be an example for document literal, so why are the operations (echoString, echoStringArray..) inside the wsdl are type rpc? 2.) My webservice client has to be independant from further changes to the wsdl. That means: if I do enhance my webservice and change the wsdl (e.g.: add fields to a complex type structure) my client should still run without modifications ( get the content minus the new fields) Is that possible or do I get deserialization errors then (because the complex type has changend)? 3.) the best thing for me would be, if I'm able to deal with the soap body entries directly. it seems to be easy to iterate through the entries and get what I want. so I would not run into the problems I descriped in 2.) a.) is there a technique for doing so? b.) how can I do this with axis or shouldn't I use axis in this case? I'm really thankfull for any advices!! andreas
Re: AXIS-2033 (Re: Blockers for Axis 1.2.1 Release(?))
dims,
I have tested a bit and I believe, the patch you have submitted works
well, but I'm just not able to set chunked property :(
this seems not the way to do it :
org.apache.axis.client.Call _call = createCall();
MessageContext msgContext = _call.getMessageContext();
Hashtable userHeaderTable = new Hashtable();
userHeaderTable.put(HTTPConstants.HEADER_TRANSFER_ENCODING_CHUNKED,
"false");
msgContext.setProperty(HTTPConstants.REQUEST_HEADERS,
userHeaderTable );
.
_resp = _call.invoke(new java.lang.Object[] {in0});
thanks,
andreas
Davanum Srinivas wrote:
Andreas,
if you can help with reviewing the code in CommonsHTTPSender and
coming up with a patch that will be the quickest way to deal with
this. you see I don't have a way to test this. Please open a new bug
or add comments for me to reopen this one once u have a patch.
thanks,
dims
On 6/13/05, Andreas Bohnert <[EMAIL PROTECTED]> wrote:
hi,
for me http://issues.apache.org/jira/browse/AXIS-2033 is still a
blocker. http 1.1 connections are not working with older apache proxies
(<=1.3.33)
the issue is already marked as fixed, but unfortunately the patch
doesn't work for me. I still stuck with axis 1.2RC3
I have added a comment to this issue together with a snippet of my
client code.
regards,
andreas
Re: AXIS-2033 (Re: Blockers for Axis 1.2.1 Release(?))
thanks! Davanum Srinivas wrote: The jdk15 comes with dom3 which is a not compatible with SAAJ 1.2 spec. can you please drop the xercesImpl.jar and xmlParserAPIs.jar in java/lib directory. if that does not work, please drop them into JDK15\jre\lib\endorsed directory (as per http://java.sun.com/j2se/1.4.2/docs/guide/standards/). thanks, dims On 6/13/05, Andreas Bohnert <[EMAIL PROTECTED]> wrote: hi dims, I would like to help, but I am not able to compile the sources. the problem is related to org.w3c.dom.* which comes with the the jdk 1.5 (rt.jar). I get this: [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/NodeImpl.java:45: org.apache.axis.message.NodeImpl is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class NodeImpl implements org.w3c.dom.Node, javax.xml.soap.Node, [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/MessageElement.java:73: org.apache.axis.message.MessageElement is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class MessageElement extends NodeImpl implements SOAPElement, [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPHeaderElement.java:40: org.apache.axis.message.SOAPHeaderElement is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class SOAPHeaderElement extends MessageElement [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/SOAPPart.java:90: org.apache.axis.SOAPPart is not abstract and does not override abstract method renameNode(org.w3c.dom.Node,java.lang.String,java.lang.String) in org.w3c.dom.Document [javac] public class SOAPPart extends javax.xml.soap.SOAPPart implements Part [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPEnvelope.java:50: org.apache.axis.message.SOAPEnvelope is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class SOAPEnvelope extends MessageElement [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPHeader.java:50: org.apache.axis.message.SOAPHeader is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class SOAPHeader extends MessageElement [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPBody.java:46: org.apache.axis.message.SOAPBody is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class SOAPBody extends MessageElement [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPBodyElement.java:37: org.apache.axis.message.SOAPBodyElement is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class SOAPBodyElement extends MessageElement regards, andreas Davanum Srinivas wrote: Andreas, if you can help with reviewing the code in CommonsHTTPSender and coming up with a patch that will be the quickest way to deal with this. you see I don't have a way to test this. Please open a new bug or add comments for me to reopen this one once u have a patch. thanks, dims On 6/13/05, Andreas Bohnert <[EMAIL PROTECTED]> wrote: hi, for me http://issues.apache.org/jira/browse/AXIS-2033 is still a blocker. http 1.1 connections are not working with older apache proxies (<=1.3.33) the issue is already marked as fixed, but unfortunately the patch doesn't work for me. I still stuck with axis 1.2RC3 I have added a comment to this issue together with a snippet of my client code. regards, andreas
Re: AXIS-2033 (Re: Blockers for Axis 1.2.1 Release(?))
hi dims, I would like to help, but I am not able to compile the sources. the problem is related to org.w3c.dom.* which comes with the the jdk 1.5 (rt.jar). I get this: [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/NodeImpl.java:45: org.apache.axis.message.NodeImpl is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class NodeImpl implements org.w3c.dom.Node, javax.xml.soap.Node, [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/MessageElement.java:73: org.apache.axis.message.MessageElement is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class MessageElement extends NodeImpl implements SOAPElement, [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPHeaderElement.java:40: org.apache.axis.message.SOAPHeaderElement is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class SOAPHeaderElement extends MessageElement [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/SOAPPart.java:90: org.apache.axis.SOAPPart is not abstract and does not override abstract method renameNode(org.w3c.dom.Node,java.lang.String,java.lang.String) in org.w3c.dom.Document [javac] public class SOAPPart extends javax.xml.soap.SOAPPart implements Part [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPEnvelope.java:50: org.apache.axis.message.SOAPEnvelope is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class SOAPEnvelope extends MessageElement [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPHeader.java:50: org.apache.axis.message.SOAPHeader is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class SOAPHeader extends MessageElement [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPBody.java:46: org.apache.axis.message.SOAPBody is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class SOAPBody extends MessageElement [javac] ^ [javac] /home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPBodyElement.java:37: org.apache.axis.message.SOAPBodyElement is not abstract and does not override abstract method getUserData(java.lang.String) in org.w3c.dom.Node [javac] public class SOAPBodyElement extends MessageElement regards, andreas Davanum Srinivas wrote: Andreas, if you can help with reviewing the code in CommonsHTTPSender and coming up with a patch that will be the quickest way to deal with this. you see I don't have a way to test this. Please open a new bug or add comments for me to reopen this one once u have a patch. thanks, dims On 6/13/05, Andreas Bohnert <[EMAIL PROTECTED]> wrote: hi, for me http://issues.apache.org/jira/browse/AXIS-2033 is still a blocker. http 1.1 connections are not working with older apache proxies (<=1.3.33) the issue is already marked as fixed, but unfortunately the patch doesn't work for me. I still stuck with axis 1.2RC3 I have added a comment to this issue together with a snippet of my client code. regards, andreas
Re: Blockers for Axis 1.2.1 Release(?)
hi, for me http://issues.apache.org/jira/browse/AXIS-2033 is still a blocker. http 1.1 connections are not working with older apache proxies (<=1.3.33) the issue is already marked as fixed, but unfortunately the patch doesn't work for me. I still stuck with axis 1.2RC3 I have added a comment to this issue together with a snippet of my client code. regards, andreas
Re: Bug 1.2RC3->1.2: Using CommonsHttpClient fails
unfortunately the patch it's not working for me.
what am I'm doing wrong?
I added this to my stub code:
protected void setUserHeader( MessageContext msgContext ) {
Hashtable userHeaderTable = new Hashtable();
userHeaderTable.put(HTTPConstants.HEADER_TRANSFER_ENCODING_CHUNKED,
"false");
msgContext.setProperty(HTTPConstants.REQUEST_HEADERS,
userHeaderTable );
}
org.apache.axis.client.Call _call = createCall();
_call.setOperation(_operations[0]);
_call.setUseSOAPAction(true);
_call.setSOAPActionURI("");
_call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS);
_call.setOperationName(new
javax.xml.namespace.QName("urn:Eusoda", "lastChange"));
setUserHeader( _call.getMessageContext() );
I'm still getting the old error message. I didn't update the code on the
server side, but I think this is not necessary, right?
I have used this nightly build:
axis-bin-1_2_1.zip 09-Jun-2005 21:07 11M
regards,
andreas
Getting Errors during compilation of current CVS
hi,
I just get the current cvs and I'm not able to compile it.
What I'm doing wrong?
regards,
andreas
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/NodeImpl.java:45:
org.apache.axis.message.NodeImpl is not abstract and does not override
abstract method getUserData(java.lang.String) in org.w3c.dom.Node
[javac] public class NodeImpl implements org.w3c.dom.Node,
javax.xml.soap.Node,
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/MessageElement.java:73:
org.apache.axis.message.MessageElement is not abstract and does not
override abstract method getUserData(java.lang.String) in org.w3c.dom.Node
[javac] public class MessageElement extends NodeImpl implements
SOAPElement,
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPHeaderElement.java:40:
org.apache.axis.message.SOAPHeaderElement is not abstract and does not
override abstract method getUserData(java.lang.String) in org.w3c.dom.Node
[javac] public class SOAPHeaderElement extends MessageElement
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/SOAPPart.java:89:
org.apache.axis.SOAPPart is not abstract and does not override abstract
method renameNode(org.w3c.dom.Node,java.lang.String,java.lang.String) in
org.w3c.dom.Document
[javac] public class SOAPPart extends javax.xml.soap.SOAPPart
implements Part
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPEnvelope.java:50:
org.apache.axis.message.SOAPEnvelope is not abstract and does not
override abstract method getUserData(java.lang.String) in org.w3c.dom.Node
[javac] public class SOAPEnvelope extends MessageElement
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPHeader.java:50:
org.apache.axis.message.SOAPHeader is not abstract and does not override
abstract method getUserData(java.lang.String) in org.w3c.dom.Node
[javac] public class SOAPHeader extends MessageElement
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPBody.java:46:
org.apache.axis.message.SOAPBody is not abstract and does not override
abstract method getUserData(java.lang.String) in org.w3c.dom.Node
[javac] public class SOAPBody extends MessageElement
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPBodyElement.java:37:
org.apache.axis.message.SOAPBodyElement is not abstract and does not
override abstract method getUserData(java.lang.String) in org.w3c.dom.Node
[javac] public class SOAPBodyElement extends MessageElement
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:82:
warning: [deprecation] com.sun.net.ssl.SSLContext in com.sun.net.ssl has
been deprecated
[javac] SSLContext context = getContext();
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:101:
warning: [deprecation] com.sun.net.ssl.SSLContext in com.sun.net.ssl has
been deprecated
[javac] SSLContext context =
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:102:
warning: [deprecation] com.sun.net.ssl.SSLContext in com.sun.net.ssl has
been deprecated
[javac] com.sun.net.ssl.SSLContext.getInstance("SSL");// SSL
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:150:
warning: [deprecation] com.sun.net.ssl.KeyManagerFactory in
com.sun.net.ssl has been deprecated
[javac] com.sun.net.ssl.KeyManagerFactory kmf =
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:151:
warning: [deprecation] com.sun.net.ssl.KeyManagerFactory in
com.sun.net.ssl has been deprecated
[javac] com.sun.net.ssl.KeyManagerFactory.getInstance(algorithm);
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:156:
warning: [deprecation] com.sun.net.ssl.TrustManager in com.sun.net.ssl
has been deprecated
[javac] com.sun.net.ssl.TrustManager[] tm = null;
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:159:
warning: [deprecation] com.sun.net.ssl.TrustManagerFactory in
com.sun.net.ssl has been deprecated
[javac] com.sun.net.ssl.TrustManagerFactory tmf =
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:160:
warning: [deprecation] com.sun.net.ssl.TrustManagerFactory in
com.sun.net.ssl has been deprecated
[javac] com.sun.net.ssl.TrustManagerFactory.getInstance("SunX509");
[javac] ^
[javac]
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:168:
Re: Bug 1.2RC3->1.2: Using CommonsHttpClient fails
Hey Mike, could you have a look at http://issues.apache.org/jira/browse/AXIS-2033. Maybe you know how to do it? regards, andreas Mike Moran wrote: Andreas Bohnert wrote: Yepp, I just did it. But maybe it would be helpful to post your fix to the database as well?! what do you think? I've updated http://issues.apache.org/jira/browse/AXIS-2033 with the code which worked for me (just in case you missed a notification)
Re: Bug 1.2RC3->1.2: Using CommonsHttpClient fails
I have seen it. great! so, let's hope for new release :) Mike Moran wrote: Andreas Bohnert wrote: Yepp, I just did it. But maybe it would be helpful to post your fix to the database as well?! what do you think? I've updated http://issues.apache.org/jira/browse/AXIS-2033 with the code which worked for me (just in case you missed a notification)
Re: Bug 1.2RC3->1.2: Using CommonsHttpClient fails
Yepp, I just did it. But maybe it would be helpful to post your fix to the database as well?! what do you think? regards, andreas Mike Moran wrote: On 2 Jun 2005, at 12:27, Andreas Bohnert wrote: hi list, I found a bug if the common http client is used. this bug can be reproduced with 1.2 final and 1.2.1 nightly build. with 1.2RC3 it works fine! with new releases I can't call my webservice from my client anymore. I get this: [ ... content length related trace ... ] This sounds like what I found: "The problem is that, because CommonsHTTPSender.MessageRequestEntity#getContentLength() is defined to only return a content-length when the HTTP version is 1.0 *and* no exception is thrown from message.getContentLength(), then it will not even try if the HTTP version is 1.1. The upshot of this is that a Transfer-Encoding: chunked header is set on the request." (see http://marc.theaimsgroup.com/?l=axis-dev&m=111523156110949&w=2) should I but this in the bug database? I think you should. I didn't put it in because it only affected me and I patched the src to work round it. It's also technically ok, I think, but from what you've found it seems like it might not or it might make sense to always default to sending content-length; I can't see any reason why Transfer-Encoding: chunked is the default.
Bug 1.2RC3->1.2: Using CommonsHttpClient fails
hi list,
I found a bug if the common http client is used. this bug can be
reproduced with 1.2 final and 1.2.1 nightly build.
with 1.2RC3 it works fine!
with new releases I can't call my webservice from my client anymore. I
get this:
2005-06-02 11:45:24,291 WARN [main] httpclient.HttpMethodBase - Going
to buf
fer response body of large or unknown size. Using getResponseAsStream
instead
is recommended.
2005-06-02 11:45:24,298 ERROR [main] exchange.ExchangeServiceClient -
(411)Le
ngth Required
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (411)Length Required
faultActor:
faultNode:
faultDetail:
{}:return code: 411
411 Length Required
Length Required
A request of the requested method POST requires a valid
Content-length.
Apache/1.3.33 Server at www.myserver.net Port 80
{http://xml.apache.org/axis/}HttpErrorCode:411
(411)Length Required
at
org.apache.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTT
PSender.java:208)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStra
tegy.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:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
at
at.weberhofer.eusoda.client.services.exchange.ExchangeSoapBindingS
tub.lastChange(ExchangeSoapBindingStub.java:466)
at
at.weberhofer.eusoda.client.services.exchange.ExchangeServiceClien
t.clientPollsTransaction(ExchangeServiceClient.java:90)
at
at.weberhofer.eusoda.client.services.exchange.ExchangeServiceClien
t.replicate(ExchangeServiceClient.java:354)
at
at.weberhofer.eusoda.client.services.exchange.ExchangeServiceClien
t.replicate(ExchangeServiceClient.java:233)
at
at.weberhofer.eusoda.client.services.exchange.ExchangeServiceMain.
main(ExchangeServiceMain.java:38)
should I but this in the bug database?
regards, andreas
