Re: useOriginalWsdl generates error when set to true.
maybe you schema definitions files not including the arr file ,when set the useOriginalwsdl=true silver17 wrote: > > Hi guys, > > I've been working on an Axis2 service and keep getting the same error. > What I WANT to do is use the original wsdl but modify the soap address and > I can't seem to do that. When I access the wsdl I would like to set the > original wsdl to true and access the service at: > http://server.com/axis2/services/service?wsdl but I get the error: > > error> > Unable to generate WSDL 1.1 for this service > > If you wish Axis2 to automatically generate the WSDL 1.1, then please +set > useOriginalwsdl as false in your services.xml > > > > As a result I am forced the use the address with a .wsdl suffix when > referencing my service via clients. It works, but since it doesn't modify > the wsdl port address I must manually modify the URL on the client side, > which is needless work. I'm currently using Axis2.1.3 on OAS. > > My service.xml > > > > > > http://www.w3.org/ns/wsdl/in-out"; > class="ca.gc.agr.services.extractaafcprofile.ExtractAAFCProfileMessageReceiverInOut"/> > > name="ServiceClass">ca.gc.agr.services.extractaafcprofile.ExtractAAFCProfileSkeleton > true > true > mep="http://www.w3.org/ns/wsdl/in-out";> > ExtractAAFCProfile > > //schemas.xmlsoap.org/wsdl/ExtractAAFCProfile_portType/ExtractAAFCProfileResponse > faultName="TranslatorFault">TranslatorException > > > > > My wsdl service name: > > > binding="nlwis:ExtractAAFCProfile_SOAP12Binding"> > > location="http://localhost:8080/axis2/services/ExtractAAFCProfile"; /> > > binding="nlwis:ExtractAAFCProfile_SOAP11Binding"> > > location="http://localhost:8080/axis2/services/ExtractAAFCProfile"; /> > > > > > -- View this message in context: http://www.nabble.com/useOriginalWsdl-generates-error-when-set-to-true.-tp16834658p25000274.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: useOriginalWsdl generates error when set to true.
Hi, Can any body help me out please... I am trying with Axis2 on Tomcat 6 (embedded as axis2.war). But while trying to deploy web services as jar using annotations (WEB-INF/servicejars/myservice.jar or WEB-INF/pojo/MyService.class) It’s generating only the wsdl2. It’s not generating the wsdl (original wsdl1 as it says…in log). Exception while trying to point to wsdl1… < Unable to generate WSDL 1.1 for this service If you wish Axis2 to automatically generate the WSDL 1.1, then please +set useOriginalwsdl as false in your services.xml javax.xml.ws.WebServiceException: Error occurred generating WSDL file for Web service implementation class {HelloPojo}: {java.lang.ClassNotFoundException: com.sun.tools.ws.spi.WSToolsObjectFactory} at org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.generateWsdl(JAXWSRIWSDLGenerator.java:187) at org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.initialize(JAXWSRIWSDLGenerator.java:371) at org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.getWSDL(JAXWSRIWSDLGenerator.java:364) at org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1322) at org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:287) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:242) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at . . …… My problem is I want to avoid the services.xml file and want to use annotations to dynamically generate the configuration files required. In that case where can I specify for the useOriginalwsdl configuration as I don’t have the services.xml file itself… This is working if I use the services.xml file and deploy it in the services/ dir as a .aar file. But my goal is to avoid the services.xml file using annotations and deploy the service as .jar without any services.xml. Your suggestion / guidance will be highly appreciated as this is critical to our portability and maintenance of our web services. With Best Regds, Upananda Singha Kodiak Networks Bangalore – 560 001 -- View this message in context: http://www.nabble.com/useOriginalWsdl-generates-error-when-set-to-true.-tp16834658p21412469.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: useOriginalWsdl generates error when set to true.
Hi, I have a similar problem, but with a slight twist. (cc'ing jibx list in case it's related.) normal wsdl2java generation produces services.xml with useOriginalwsdl=true. The service runs fine, but it produces the "Unable to generate WSDL 1.1 for this service" error when hitting the ?wsdl. If I *manually* change the useOriginalwsdl to false through the admin interface, then I get generated wsdl out. Ok, I could live with that wsdl, probably. *But*, if I set useOriginalwsdl=false in services.xml, I get a deployment error: This Web axisService has deployment faults Error: java.lang.NoClassDefFoundError: org/jibx/runtime/impl/UnmarshallingContext at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2395) at java.lang.Class.getDeclaredMethods(Class.java:1763) at org.codehaus.jam.internal.reflect.ReflectClassBuilder.populate(ReflectClassBuilder.java:105) at org.codehaus.jam.internal.elements.ClassImpl.ensureLoaded(ClassImpl.java:674) at org.codehaus.jam.internal.elements.ClassImpl.getSuperclass(ClassImpl.java:147) at org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.isDataHandler(DefaultSchemaGenerator.java:693) at org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.generateSchemaForType(DefaultSchemaGenerator.java:658) at org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.processMethods(DefaultSchemaGenerator.java:307) at org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.generateSchema(DefaultSchemaGenerator.java:181) at org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:352) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:350) at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101) at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:103) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:137) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:78) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:137) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:571) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:141) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:318) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:220) at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:312) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:64) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:71) at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:83) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) I don't think it's reasonable to have to manually change the useOriginalwsdl param by hand every time the service is reloaded. I am using axis2 1.3 with JiBX in tomcat 5.5.25. I originally thought the "cannot generate wsdl" error was due to the wsdl importing schema from relative locations, but I've removed all of that and it still fails. thanks, Linus ps, is there an option to control whether useOriginalwsdl is true or false in services.xml when generated through wsdl2java? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: useOriginalWsdl generates error when set to true.
Could you please send me the service aar file. Thank you! Deepal Hi guys, I've been working on an Axis2 service and keep getting the same error. What I WANT to do is use the original wsdl but modify the soap address and I can't seem to do that. When I access the wsdl I would like to set the original wsdl to true and access the service at: http://server.com/axis2/services/service?wsdl but I get the error: error> Unable to generate WSDL 1.1 for this service If you wish Axis2 to automatically generate the WSDL 1.1, then please +set useOriginalwsdl as false in your services.xml As a result I am forced the use the address with a .wsdl suffix when referencing my service via clients. It works, but since it doesn't modify the wsdl port address I must manually modify the URL on the client side, which is needless work. I'm currently using Axis2.1.3 on OAS. My service.xml http://www.w3.org/ns/wsdl/in-out"; class="ca.gc.agr.services.extractaafcprofile.ExtractAAFCProfileMessageReceiverInOut"/> ca.gc.agr.services.extractaafcprofile.ExtractAAFCProfileSkeleton true true http://www.w3.org/ns/wsdl/in-out";> ExtractAAFCProfile //schemas.xmlsoap.org/wsdl/ExtractAAFCProfile_portType/ExtractAAFCProfileResponse TranslatorException My wsdl service name: http://localhost:8080/axis2/services/ExtractAAFCProfile"; /> http://localhost:8080/axis2/services/ExtractAAFCProfile"; /> - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: useOriginalWsdl generates error when set to true.
I've uploaded the WSDL. On inspection of the console window for OC4J I also found this error: "Could not create URL from 'META-INF/ExtractAAFCProfile.wsdl' and 'http://www.w3.org/2005/05/xmlmime"; This seems like a major issue. silver17 wrote: > > Hi guys, > > I've been working on an Axis2 service and keep getting the same error. > What I WANT to do is use the original wsdl but modify the soap address and > I can't seem to do that. When I access the wsdl I would like to set the > original wsdl to true and access the service at: > http://server.com/axis2/services/service?wsdl but I get the error: > > error> > Unable to generate WSDL 1.1 for this service > > If you wish Axis2 to automatically generate the WSDL 1.1, then please +set > useOriginalwsdl as false in your services.xml > > > > As a result I am forced the use the address with a .wsdl suffix when > referencing my service via clients. It works, but since it doesn't modify > the wsdl port address I must manually modify the URL on the client side, > which is needless work. I'm currently using Axis2.1.3 on OAS. > > My service.xml > > > > > > http://www.w3.org/ns/wsdl/in-out"; > class="ca.gc.agr.services.extractaafcprofile.ExtractAAFCProfileMessageReceiverInOut"/> > > name="ServiceClass">ca.gc.agr.services.extractaafcprofile.ExtractAAFCProfileSkeleton > true > true > mep="http://www.w3.org/ns/wsdl/in-out";> > ExtractAAFCProfile > > //schemas.xmlsoap.org/wsdl/ExtractAAFCProfile_portType/ExtractAAFCProfileResponse > faultName="TranslatorFault">TranslatorException > > > > > My wsdl service name: > > > binding="nlwis:ExtractAAFCProfile_SOAP12Binding"> > > location="http://localhost:8080/axis2/services/ExtractAAFCProfile"; /> > > binding="nlwis:ExtractAAFCProfile_SOAP11Binding"> > > location="http://localhost:8080/axis2/services/ExtractAAFCProfile"; /> > > > > > http://www.nabble.com/file/p16834721/ExtractAAFCProfile.wsdl ExtractAAFCProfile.wsdl -- View this message in context: http://www.nabble.com/useOriginalWsdl-generates-error-when-set-to-true.-tp16834658p16834721.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
useOriginalWsdl generates error when set to true.
Hi guys, I've been working on an Axis2 service and keep getting the same error. What I WANT to do is use the original wsdl but modify the soap address and I can't seem to do that. When I access the wsdl I would like to set the original wsdl to true and access the service at: http://server.com/axis2/services/service?wsdl but I get the error: error> Unable to generate WSDL 1.1 for this service If you wish Axis2 to automatically generate the WSDL 1.1, then please +set useOriginalwsdl as false in your services.xml As a result I am forced the use the address with a .wsdl suffix when referencing my service via clients. It works, but since it doesn't modify the wsdl port address I must manually modify the URL on the client side, which is needless work. I'm currently using Axis2.1.3 on OAS. My service.xml http://www.w3.org/ns/wsdl/in-out"; class="ca.gc.agr.services.extractaafcprofile.ExtractAAFCProfileMessageReceiverInOut"/> ca.gc.agr.services.extractaafcprofile.ExtractAAFCProfileSkeleton true true http://www.w3.org/ns/wsdl/in-out";> ExtractAAFCProfile //schemas.xmlsoap.org/wsdl/ExtractAAFCProfile_portType/ExtractAAFCProfileResponse TranslatorException My wsdl service name: http://localhost:8080/axis2/services/ExtractAAFCProfile"; /> http://localhost:8080/axis2/services/ExtractAAFCProfile"; /> -- View this message in context: http://www.nabble.com/useOriginalWsdl-generates-error-when-set-to-true.-tp16834658p16834658.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]