The compatibility of Axis 1.4 and JAX-WS when sending attachments
Hi all, I use Axis 1.4 as the SOAP server and JAX-WS as the client, and I want to transfer attachments between them. I use WS-ISwA.xsd in WSDL http://ws-i.org/profiles/basic/1.1/xsd"; schemaLocation="WS-ISwA.xsd"/> ... But when I use WSDL2Java to generate the stub, the wsi:swaRef is mapped to org.apache.axis.types.URI and when use wsimport to generate the JAX-WS stub, the wsi:swaRef is mapped to DataHandler. So how to configure axis so it mappes wsi:swaRef to DataHandler too? Or there is another way to transfer attachements between these two libs. Thanks a lot - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Setting use of Ws-Addressing header mandatory at service
Hello David, Thanks. I looked at the link and see its the 2006 version of ws-addressing, i have to use 2005. I changed my wsdl anyway, but did not see any change in behaviour. I am using axis2 1.1.1. Should it appear after generating the code from the wsdl in the service.xml? Since i only see it mentioned in the 2006 version does this mean that axis does not support such a "feature" (i am using soap 1.1) for a ws-addressing 08-2005 version? Thanks. Kind regards, Erwin -Original Message- From: David Illsley [mailto:[EMAIL PROTECTED] Sent: Thu 5/24/2007 7:05 PM To: axis-user@ws.apache.org Cc: Subject:Re: Setting use of Ws-Addressing header mandatory at service It is possible, simply put the UsingAddressing element defined in [1] in your service WSDL with wsdl:required="true" on it. I hope that helps, David [1] http://www.w3.org/TR/2006/CR-ws-addr-wsdl-20060529/#uaee On 24/05/07, Erwin Reinhoud <[EMAIL PROTECTED]> wrote: > > > > Hello, > > I know the client can mandate the use of WS-Addressing bij use of > mustUnderstand. But i would like to impose the policy that all clients must > add a WS-addressing header on messages to a Axis2 1.1.1 service. I can not > find any information how to configure the service that it mandates this. Is > it uncommon to have such a policy? > > > Thanks. > > Kind regards, > Erwin -- David Illsley - IBM Web Services Development - 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: Help with SwA
Thanks. The following line you suggested solved my problem. outMessageContext.setProperty(Constants.Configuration.ENABLE_MTOM,Constants.VALUE_TRUE); Great... I am curious about the meanings and effects of the following two lines: outMessageContext.setDoingSwA(true); outMessageContext.setServerSide(true); These are used by our transport layers to track some properties.. Irrespective of there value, they get overridden at the transport layers.. I badly wanted to remove those things, since they mislead the users. Actually I tried to do that once and found too many implications, which made me run out of time to finish it... It would be great if you can log a JIRA about those two.. Thanks, Thilina Regards, Xinjun On 5/26/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > > I use some proprietary information. From the request url my custom message > > receiver can decide which service should be invoked. > I mean how you specify that a request message needs to be directed to > your custom message receiver. May be you are using a custom deployer > to bypass the services.xml. > > Thinking about plain Axis2, you need to have a AxisService deployed by > some name and then it needs to contain information about the message > receiver. Then when a message arrives for that particular service, > Axis2 forwards that message to your message receiver... If you have a > AxisService object like that, then you can add the following key value > pair as a parameter to that AxisService object. > Constants.Configuration.ENABLE_MTOM,Constants.VALUE_TRUE > > Thanks, > Thilina > > > > > Regards, > > Xinjun > > > > > > On 5/26/07, Thilina Gunarathne < [EMAIL PROTECTED]> wrote: > > > try this... > > > > > outMessageContext.setProperty(Constants.Configuration.ENABLE_MTOM,Constants.VALUE_TRUE); > > > > > > > I don't have service.xml. I write a custom MessageReceiver to process > > the > > > > request and response MessageContext > > > Curious to know how you are specifying your custom message receiver to > > > the services... > > > > > > Thanks, > > > Thilina > > > > how you are mentiong > > > >. In this way, is the way you suggested > > > > still workable? > > > > > > > > Regards, > > > > Xinjun > > > > > > > > > > > > On 5/25/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > > > > > > The following is the code snippet where I try to enable SwA only for > > one > > > > > > service. > > > > > > > > > > > > /** in axis2.xml, enableSwA is set to false **/ > > > > > Please add the enableSwA parameter to your services.xml to enable SwA > > > > > only for that service. Also you can add it under a respective > > > > > operation element in the services.xml to enable SwA only for that > > > > > particular operation.. > > > > > > > > > > > The out.setDoingSwA(true) seems not take effect. > > > > > Unfortunately this is not working and misleading.. This method was > > > > > used only in the transport layers. > > > > > > > > > > You may try doing the following.. > > > > > > > > > > > out.setProperty(Constants.Configuration.ENABLE_MTOM,Constants.VALUE_TRUE > > > > ); > > > > > > > > > > thanks, > > > > > Thilina > > > > > > > > > > > > > > > > > > Could you suggest how to solve the problem? I am using Axis2 1.2. > > > > > > > > > > > > > > > > > > Regards, > > > > > > Xinjun > > > > > > > > > > > > > > > > > > > > > > > > On 5/1/07, Thilina Gunarathne < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > DataHandler(byte_data,"application/octet-stream"); > > > > > > > You may use the ByteArrayDataSource for this purpose.. > > Alternatively > > > > > > > you can try using "binary" instead of the > > > > > > > "application/octet-stream"... > > > > > > > > > > > > > > HTH, > > > > > > > Thilina > > > > > > > > > BinaryData binaryData =new BinaryData(); > > > > > > > > > binaryData.setBase64Binary(dataHandler); > > > > > > > > > binaryData.setContentType(dataHandler.getContentType()); > > > > > > > > > response.setBinaryData(binaryData); > > > > > > > > > > > > > > > > > > The problem is in the method toEnvelope setting the child for > > the > > > > > > body. > > > > > > > > > > > > > > > > > > I'm getting the following exception: > > > > > > > > > > > > > > > > > > java.lang.RuntimeException: org.apache.axiom.om.OMException: > > > > > > Referenced > > > > > > > > > Attachment not found in the MIME Message. > > > > > > > > > > > > > > > > > > > > > > > ContentID: > > > > 1.urn:uuid:[EMAIL PROTECTED] > > > > > > > > > at > > > > > > > > > > > > > > > > > client.Medici_LinkSOAP12PortStub.fromOM > > > > > > (Medici_LinkSOAP12PortStub.java:5296) > > > > > > > > > at > > > > > > > > > > > > > > > > > > > > > > > > > > > > > client.Medici_LinkSOAP12PortStub.getAttachment (Medici_LinkSOAP12PortStub.java:4103) > > > > > > > > > at client.ClientUtilities.mtomTest (ClientUtilities.java :476) > > > > > > > > > at client.Client.main(Client.java:69) > > > > > > > > > Caused by: org.apache.axiom.om.OMException: Referenced > > Attachment > > > > not >
Re: Axis beginner
Hi, What is the version of Tomcat & Axis your using? Sipungora wrote: I have only newly deal with axis. And I have a problem at the installation. I have copied xercesImpl.jar and all other jar-files for XML Parser in TOMCAT\webapps\axis\WEB-INF\lib, but "happyaxis.jsp" shows me in Examining Application Server, that XML ParserLocation is unknown. Moreover I have the same Problem with JAXP. What should I do? What could I wrong make? In the axis installation instructions it is mentioned distribution directory for xml- axis(Step 7:Testing). Where is this directory located? Thank you very much beforehand. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis beginner
I have only newly deal with axis. And I have a problem at the installation. I have copied xercesImpl.jar and all other jar-files for XML Parser in TOMCAT\webapps\axis\WEB-INF\lib, but "happyaxis.jsp" shows me in Examining Application Server, that XML ParserLocation is unknown. Moreover I have the same Problem with JAXP. What should I do? What could I wrong make? In the axis installation instructions it is mentioned distribution directory for xml- axis(Step 7:Testing). Where is this directory located? Thank you very much beforehand. -- View this message in context: http://www.nabble.com/Axis-beginner-tf3825949.html#a10830979 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help with SwA
Hi Thilina, Thanks. The following line you suggested solved my problem. outMessageContext.setProperty(Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE); I am curious about the meanings and effects of the following two lines: outMessageContext.setDoingSwA(true); outMessageContext.setServerSide(true); Regards, Xinjun On 5/26/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > I use some proprietary information. From the request url my custom message > receiver can decide which service should be invoked. I mean how you specify that a request message needs to be directed to your custom message receiver. May be you are using a custom deployer to bypass the services.xml. Thinking about plain Axis2, you need to have a AxisService deployed by some name and then it needs to contain information about the message receiver. Then when a message arrives for that particular service, Axis2 forwards that message to your message receiver... If you have a AxisService object like that, then you can add the following key value pair as a parameter to that AxisService object. Constants.Configuration.ENABLE_MTOM,Constants.VALUE_TRUE Thanks, Thilina > > Regards, > Xinjun > > > On 5/26/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > > try this... > > > outMessageContext.setProperty(Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE); > > > > > I don't have service.xml. I write a custom MessageReceiver to process > the > > > request and response MessageContext > > Curious to know how you are specifying your custom message receiver to > > the services... > > > > Thanks, > > Thilina > > > how you are mentiong > > >. In this way, is the way you suggested > > > still workable? > > > > > > Regards, > > > Xinjun > > > > > > > > > On 5/25/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > > > > > The following is the code snippet where I try to enable SwA only for > one > > > > > service. > > > > > > > > > > /** in axis2.xml, enableSwA is set to false **/ > > > > Please add the enableSwA parameter to your services.xml to enable SwA > > > > only for that service. Also you can add it under a respective > > > > operation element in the services.xml to enable SwA only for that > > > > particular operation.. > > > > > > > > > The out.setDoingSwA(true) seems not take effect. > > > > Unfortunately this is not working and misleading.. This method was > > > > used only in the transport layers. > > > > > > > > You may try doing the following.. > > > > > > > > out.setProperty(Constants.Configuration.ENABLE_MTOM,Constants.VALUE_TRUE > > > ); > > > > > > > > thanks, > > > > Thilina > > > > > > > > > > > > > > > Could you suggest how to solve the problem? I am using Axis2 1.2 . > > > > > > > > > > > > > > > Regards, > > > > > Xinjun > > > > > > > > > > > > > > > > > > > > On 5/1/07, Thilina Gunarathne < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > DataHandler(byte_data,"application/octet-stream"); > > > > > > You may use the ByteArrayDataSource for this purpose.. > Alternatively > > > > > > you can try using "binary" instead of the > > > > > > "application/octet-stream"... > > > > > > > > > > > > HTH, > > > > > > Thilina > > > > > > > > BinaryData binaryData =new BinaryData(); > > > > > > > > binaryData.setBase64Binary(dataHandler); > > > > > > > > binaryData.setContentType(dataHandler.getContentType()); > > > > > > > > response.setBinaryData(binaryData); > > > > > > > > > > > > > > > > The problem is in the method toEnvelope setting the child for > the > > > > > body. > > > > > > > > > > > > > > > > I'm getting the following exception: > > > > > > > > > > > > > > > > java.lang.RuntimeException: org.apache.axiom.om.OMException: > > > > > Referenced > > > > > > > > Attachment not found in the MIME Message. > > > > > > > > > > > > > > > > > > > > ContentID: > > > 1.urn:uuid:[EMAIL PROTECTED] > > > > > > > > at > > > > > > > > > > > > > > > client.Medici_LinkSOAP12PortStub.fromOM > > > > > (Medici_LinkSOAP12PortStub.java:5296) > > > > > > > > at > > > > > > > > > > > > > > > > > > > > > > > > client.Medici_LinkSOAP12PortStub.getAttachment (Medici_LinkSOAP12PortStub.java:4103) > > > > > > > > at client.ClientUtilities.mtomTest (ClientUtilities.java:476) > > > > > > > > at client.Client.main(Client.java:69) > > > > > > > > Caused by: org.apache.axiom.om.OMException: Referenced > Attachment > > > not > > > > > > > found > > > > > > > > in the MIME Message. > > > > > > > > > > > > > > > ContentID: > > > > > > 1.urn:uuid:[EMAIL PROTECTED] > > > > > > > > at > > > > > > > > > > > > > > > > > > > > > > > > org.apache.axiom.soap.impl.builder.MTOMStAXSOAPModelBuilder.getDataHandler (MTOMStAXSOAPModelBuilder.java > :103) > > > > > > > > at > > > > > > > > > > > > > > > > > > > > medici_link.xmime.xsd.BinaryData$Factory.parse( > > > BinaryData.java:429) > > > > > > > > at > > > > > > > > > > > > > > > > > > > > > > > > medici_link.op_messages.xsd.GetAttachmentResponse$Factory.parse( GetAttachmentResponse.java:342) > > > > > > > >
Re: Help with SwA
Hi Thilina, Thanks. The following line you suggested solved my problem. outMessageContext.setProperty(Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE); I am curious about the meanings and effects of the following two lines: outMessageContext.setDoingSwA(true); outMessageContext.setServerSide(true); Regards, Xinjun On 5/26/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > I use some proprietary information. From the request url my custom message > receiver can decide which service should be invoked. I mean how you specify that a request message needs to be directed to your custom message receiver. May be you are using a custom deployer to bypass the services.xml. Thinking about plain Axis2, you need to have a AxisService deployed by some name and then it needs to contain information about the message receiver. Then when a message arrives for that particular service, Axis2 forwards that message to your message receiver... If you have a AxisService object like that, then you can add the following key value pair as a parameter to that AxisService object. Constants.Configuration.ENABLE_MTOM,Constants.VALUE_TRUE Thanks, Thilina > > Regards, > Xinjun > > > On 5/26/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > > try this... > > > outMessageContext.setProperty(Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE); > > > > > I don't have service.xml. I write a custom MessageReceiver to process > the > > > request and response MessageContext > > Curious to know how you are specifying your custom message receiver to > > the services... > > > > Thanks, > > Thilina > > > how you are mentiong > > >. In this way, is the way you suggested > > > still workable? > > > > > > Regards, > > > Xinjun > > > > > > > > > On 5/25/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > > > > > The following is the code snippet where I try to enable SwA only for > one > > > > > service. > > > > > > > > > > /** in axis2.xml, enableSwA is set to false **/ > > > > Please add the enableSwA parameter to your services.xml to enable SwA > > > > only for that service. Also you can add it under a respective > > > > operation element in the services.xml to enable SwA only for that > > > > particular operation.. > > > > > > > > > The out.setDoingSwA(true) seems not take effect. > > > > Unfortunately this is not working and misleading.. This method was > > > > used only in the transport layers. > > > > > > > > You may try doing the following.. > > > > > > > > out.setProperty(Constants.Configuration.ENABLE_MTOM,Constants.VALUE_TRUE > > > ); > > > > > > > > thanks, > > > > Thilina > > > > > > > > > > > > > > > Could you suggest how to solve the problem? I am using Axis2 1.2 . > > > > > > > > > > > > > > > Regards, > > > > > Xinjun > > > > > > > > > > > > > > > > > > > > On 5/1/07, Thilina Gunarathne < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > DataHandler(byte_data,"application/octet-stream"); > > > > > > You may use the ByteArrayDataSource for this purpose.. > Alternatively > > > > > > you can try using "binary" instead of the > > > > > > "application/octet-stream"... > > > > > > > > > > > > HTH, > > > > > > Thilina > > > > > > > > BinaryData binaryData =new BinaryData(); > > > > > > > > binaryData.setBase64Binary(dataHandler); > > > > > > > > binaryData.setContentType(dataHandler.getContentType()); > > > > > > > > response.setBinaryData(binaryData); > > > > > > > > > > > > > > > > The problem is in the method toEnvelope setting the child for > the > > > > > body. > > > > > > > > > > > > > > > > I'm getting the following exception: > > > > > > > > > > > > > > > > java.lang.RuntimeException: org.apache.axiom.om.OMException: > > > > > Referenced > > > > > > > > Attachment not found in the MIME Message. > > > > > > > > > > > > > > > > > > > > ContentID: > > > 1.urn:uuid:[EMAIL PROTECTED] > > > > > > > > at > > > > > > > > > > > > > > > client.Medici_LinkSOAP12PortStub.fromOM > > > > > (Medici_LinkSOAP12PortStub.java:5296) > > > > > > > > at > > > > > > > > > > > > > > > > > > > > > > > > client.Medici_LinkSOAP12PortStub.getAttachment (Medici_LinkSOAP12PortStub.java:4103) > > > > > > > > at client.ClientUtilities.mtomTest (ClientUtilities.java:476) > > > > > > > > at client.Client.main(Client.java:69) > > > > > > > > Caused by: org.apache.axiom.om.OMException: Referenced > Attachment > > > not > > > > > > > found > > > > > > > > in the MIME Message. > > > > > > > > > > > > > > > ContentID: > > > > > > 1.urn:uuid:[EMAIL PROTECTED] > > > > > > > > at > > > > > > > > > > > > > > > > > > > > > > > > org.apache.axiom.soap.impl.builder.MTOMStAXSOAPModelBuilder.getDataHandler (MTOMStAXSOAPModelBuilder.java > :103) > > > > > > > > at > > > > > > > > > > > > > > > > > > > > medici_link.xmime.xsd.BinaryData$Factory.parse( > > > BinaryData.java:429) > > > > > > > > at > > > > > > > > > > > > > > > > > > > > > > > > medici_link.op_messages.xsd.GetAttachmentResponse$Factory.parse( GetAttachmentResponse.java:342) > > > > > > > >
Re: Problem with wsdl2java
which shell are you using? can try please try any other alternate shell(s)? thanks, dims On 5/27/07, Genious Soul <[EMAIL PROTECTED]> wrote: - Original Message From: neiroman neiroman <[EMAIL PROTECTED]> To: axis-user@ws.apache.org Sent: Saturday, May 26, 2007 7:58:38 PM Subject: Problem with wsdl2java Hello, I use Axis2 1.2 When I try to run wsdl2java I've got the follovving error [EMAIL PROTECTED]:/usr/lib/axis2> wsdl2java.sh -uri tmp.wsdl -ss -sd Using AXIS2_HOME: /usr/lib/axis2 Using JAVA_HOME: /usr/java/jdk1.6.0 /usr/lib/axis2/bin/axis2.sh: line 38: [: !=: unary operator expected Unrecognized option: -uri Don't be flakey. Get Yahoo! Mail for Mobile and always stay connected to friends. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with JNI based web service
Hi, I just converted my JNI based program into web service. It deployed successfully but when I click to see the WSDL of the deployed service.I got the following error : 500 HTTP Internal Server Error Tomcat console is giving the following error messages: - Exception: java.lang.NoClassDefFoundError at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:219) at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:168) at java.security.AccessController.doPrivileged(Native Method) at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:160) at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:142) at org.apache.axis.utils.cache.ClassCache.lookup(ClassCache.java:85) at org.apache.axis.providers.java.JavaProvider.getServiceClass(JavaProvi der.java:428) at org.apache.axis.providers.java.JavaProvider.initServiceDesc(JavaProvi der.java:461) at org.apache.axis.handlers.soap.SOAPService.getInitializedServiceDesc(S OAPService.java:286) at org.apache.axis.handlers.JWSHandler.setupService(JWSHandler.java:273) at org.apache.axis.handlers.JWSHandler.generateWSDL(JWSHandler.java:294) at org.apache.axis.strategies.WSDLGenStrategy.visit(WSDLGenStrategy.java :33) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.generateWSDL(SimpleChain.java:104) at org.apache.axis.server.AxisServer.generateWSDL(AxisServer.java:454) at org.apache.axis.transport.http.QSWSDLHandler.invoke(QSWSDLHandler.jav a:68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.axis.transport.http.AxisServlet.processQuery(AxisServlet.j ava:1226) at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:249 ) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas e.java:327) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:199) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:145) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV alve.java:210) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex t.invokeNext(StandardPipeline.java:596) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:433) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV alve.java:139) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex t.invokeNext(StandardPipeline.java:596) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:433) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java: 2460) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j ava:133) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex t.invokeNext(StandardPipeline.java:596) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche rValve.java:119) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex t.invokeNext(StandardPipeline.java:594) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j ava:117) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex t.invokeNext(StandardPipeline.java:594) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:433) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal ve.java:127) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex t.invokeNext(StandardPipeline.java:596) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:433) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:15 7) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java :874) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p rocessConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcp
Getting an Error while deploying JNI based web service
Hi, I just converted my JNI based program into web service. It deployed successfully but when I click to see the WSDL of the deployed service.I got the following error : 500 HTTP Internal Server Error The page cannot be displayed I am getting the WSDL for other deployed services.I would appreciate if someone can tell me how to find out exactly what went wrong?Thanks for any help. Best Kashif Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html
Re: Problem with wsdl2java
- Original Message From: neiroman neiroman <[EMAIL PROTECTED]> To: axis-user@ws.apache.org Sent: Saturday, May 26, 2007 7:58:38 PM Subject: Problem with wsdl2java Hello, I use Axis2 1.2 When I try to run wsdl2java I've got the follovving error [EMAIL PROTECTED]:/usr/lib/axis2> wsdl2java.sh -uri tmp.wsdl -ss -sd Using AXIS2_HOME: /usr/lib/axis2 Using JAVA_HOME: /usr/java/jdk1.6.0 /usr/lib/axis2/bin/axis2.sh: line 38: [: !=: unary operator expected Unrecognized option: -uri Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html
Axis 1.4, ArrayMapping literal, response not as expected
Hi,
I am new to Axis 1.4. I have developed a Java Class BeanService that
has a single getCodeList method. The method returns an array of
CodeValuePair objects.
I am using Java2WSDL to generate my WSDL and have hand coded my wsdd
file. I am not getting the 'item' XML elements when the elements in
the array are serialized. I have been struggling for the past 2 days to
get the expected response. No luck so far. Could somebody point my
mistakes please?
1) Expected Response:
SGSingapore
2) Actual Response
SGSingapore
3) MultiRef disabled in server-config.wsdd
3) WSDL generated using Ant task
http://localhost:8080/axis/services/AxisService";
style="RPC"
use="literal"
deploy="true">
4) WSDD file
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
5) Service class
public BeanService {
public CodeValuePair[] getCodeList(String listName) {
/* return list of CodeValuePair */
}
}
6) Data object
public CodeValuePair {
private String code;
private String value;
/* getters and setters omitted */
}
Best Regards
Rao (Peruri Rama Mohan Rao)
T&O-ES-Imaging & Workflow
Tel: 65- 6878 2071
Mobile: 65-9389 7141
CONFIDENTIAL NOTE: The information contained in this email is intended only for
the use of the individual or entity named above and may contain information
that is privileged, confidential and exempt from disclosure under applicable
law. If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited. If you have received this message in
error, please immediately notify the sender and delete the mail.
Thank you.
Creating WSDLs that unwrap nicely
Folks, I did some research on Microsofts unwrapping/wrapping model and I've written a blog post on how to ensure that WCF 3.0 unwraps your WSDLs correctly. I think that Axis2 1.2 does this nicely now, based on some JIRAs I raised doing this, and lots of hard work by Amila to fix them! http://pzf.fremantle.org/2007/05/handlign.html -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
