should java2wsdl add wsaw:UsingAddressing element to wsdl?
Hi, I'm using axis2.14 java2wsdl batch to create a wsdl but it seem the output is missing wsaw:UsingAddressing element, does it mean it was generated wrongly? Does wsaw:UsingAddressing is mandatory element for using axis2 WS-Addressing module ? Thanks -- View this message in context: http://old.nabble.com/should-java2wsdl-add-wsaw%3AUsingAddressing-element-to-wsdl--tp27610162p27610162.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: Basic question on WSDL
this[1] may help you. please see how to specify headers. thanks, Amila. [1] http://wso2.org/library/2935 On Fri, Feb 12, 2010 at 7:48 AM, Yashwanth Rajaram -X (yrajaram - Zensar at Cisco) wrote: > Hi All: > > > > I want to expose a WebService that would take a single parameter. However I > want the caller to provide certain SOAP header parameters. Is there a way to > enforce these required header, say, by using an XSD in WSDL or anything > along those lines? > > > > thanks, > > -- > > Yashwanth > > This email does not reflect the opinion of my employer/cisco. > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Problem with service that is not found during WSDL parsing...
Hello there! I'm experiencing some problems while parsing an especific WSDL to generate "C" code for a Visual C++ application. I have already parsed another 4 WSDL regarding most of web services I need on my application, and everything works pretty fine with them. Diferently of the others, this WSDL uses WS-Eventing and is generated for use on JBossWS and count with some import files. In fact, I process the main WSDL (the one with our application namespace) that imports a separate WSDL (that points to namespace " http://schemas.xmlsoap.org/ws/2004/08/eventing";), and is on the last one that both "subscriber" and "manage" services get declared. During the parsing, if I don't point the service name (through parameter "-sn") it just inform that no service was found on WSDL. (And I just found a ticket about this condition - service not found inside import files - on a ticket of 3 years ago). But, if I use the "-sn" parameter informing the name of the service, it gives a more detailed message. Bellow is the error: Retrieving document at 'http:subscribe?wsdl&resource=ws-eventing.wsdl', relative to 'fil e:'. Retrieving schema at 'http:subscribe?wsdl&resource=ws-eventing.xsd', relative to 'file:'. Retrieving schema at 'http:subscribe?wsdl&resource=ws-addr.xsd', relative to 'http://192 .168.0.10:8080//subscribe?wsdl&resource=ws-eventing.xsd'. Retrieving schema at 'http://www.w3.org/2001/xml.xsd', relative to 'http:// //subscribe?wsdl& resource=ws-eventing.xsd'. Feb 11, 2010 12:11:42 PM org.apache.axis2.description.WSDL11ToAxisServiceBuilder populateService SEVERE: org.apache.axis2.AxisFault: Service EventSourceService was not found in the WSDL Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:112) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2C.main(WSDL2C.java:27) Caused by: org.apache.axis2.AxisFault: Service EventSourceService was not f ound in the WSDL; nested exception is: org.apache.axis2.AxisFault: Service EventSourceService was not foun d in the WSDL at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:250) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:103) ... 2 more Caused by: org.apache.axis2.AxisFault: Service EventSourceService was not f ound in the WSDL at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.findBinding(WSDL11ToAxisServiceBuilder.java:330) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:200) ... 3 more "EventSourceService" is declared on file "ws-eventing.wsdl" imported by the root WSDL file that is being processed, and "ws-eventing.wsdl" file has a different "targetNamespace" attribute than the root WSDL file. What I think is the cause of all this. I just can't find any reference of such problem on Internet besides the import issue solved at 2006. Can someone give me a hand on this? Thank's a lot and best regards, Mauro.
RE: Inaccessible WSDL files after enabling both HTTP and HTTPS in Axis2/Tomcat
Thanks for the information. I am glad to hear it is fixed in the main trunk, which I hope means it will make it into the next version of Axis2. For the time being I've implemented my own logic to create these files at deployment time by modifying the original WSDL file to contain the policy reference, the policy statements, and the modified service endpoint. They will just have to be accessible for now from the "http(s)://host:port/axis2/services/service/service.wsdl" format. -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Monday, February 08, 2010 8:44 AM To: axis-user@ws.apache.org Subject: Re: Inaccessible WSDL files after enabling both HTTP and HTTPS in Axis2/Tomcat Michael, This looks like another example of the issue described in AXIS2-4465. Not sure if it is possible to make this work properly in 1.5.1, but in the current trunk the configuration mechanism to enable HTTP and HTTPS in a servlet environment is much more transparent (and known to work properly). Andreas [1] http://people.apache.org/~veithen/axis2/1_6/servlet-transport.html On Mon, Feb 8, 2010 at 14:10, Doughty, Michael wrote: > I have a problem that I am hoping someone could shed some light on. > > > > I have enabled both HTTP and one-way HTTPS in my Tomcat 6 instance. > Likewise, I have added the correct configuration information to my axis2.xml > in the war distribution of Axis2 1.5.1. The HTTP port is 8080 and the HTTPS > port is 8443. They are running on a 1.5 JRE. > > > > Doing so seems to work ok. The Web services are all accessible at both the > HTTP and HTTPS endpoints, so there seems to be no real issue there. > However, the WSDL and XSD files are inaccessible. The same endpoints that > allow SOAP requests no longer allow any of these "GET" requests to access > WSDL and XSD files: "?wsdl", "?wsdl=somefile.wsdl", "?xsd=somefile.xsd". > In all cases, I get the message "Internal server error". This happens > whether or not I use the HTTP or HTTPS endpoints to access them. Note that > I can still access these files directly by simply adding "/somefile.wsdl" > to the end of the endpoint, but this is undesirable in the case of the main > WSDL of the service as the service endpoints are not replaced properly. > > > > Note that this happens whether or not I explicitly declare the available > transports in services.xml for the services in question. I found a FAQ > somewhere that said I needed to make sure that xalan-2.7.0.jar was copied > into the lib directory of the war distribution, but that file is already > there. > > > > Is there something else I need to do here to make this work? Or is this a > known issue that cannot be worked around at this time?
Re: Inaccessible WSDL files after enabling both HTTP and HTTPS in Axis2/Tomcat
Michael, This looks like another example of the issue described in AXIS2-4465. Not sure if it is possible to make this work properly in 1.5.1, but in the current trunk the configuration mechanism to enable HTTP and HTTPS in a servlet environment is much more transparent (and known to work properly). Andreas [1] http://people.apache.org/~veithen/axis2/1_6/servlet-transport.html On Mon, Feb 8, 2010 at 14:10, Doughty, Michael wrote: > I have a problem that I am hoping someone could shed some light on. > > > > I have enabled both HTTP and one-way HTTPS in my Tomcat 6 instance. > Likewise, I have added the correct configuration information to my axis2.xml > in the war distribution of Axis2 1.5.1. The HTTP port is 8080 and the HTTPS > port is 8443. They are running on a 1.5 JRE. > > > > Doing so seems to work ok. The Web services are all accessible at both the > HTTP and HTTPS endpoints, so there seems to be no real issue there. > However, the WSDL and XSD files are inaccessible. The same endpoints that > allow SOAP requests no longer allow any of these “GET” requests to access > WSDL and XSD files: “?wsdl”, “?wsdl=somefile.wsdl”, “?xsd=somefile.xsd”. > In all cases, I get the message “Internal server error”. This happens > whether or not I use the HTTP or HTTPS endpoints to access them. Note that > I can still access these files directly by simply adding “/somefile.wsdl” > to the end of the endpoint, but this is undesirable in the case of the main > WSDL of the service as the service endpoints are not replaced properly. > > > > Note that this happens whether or not I explicitly declare the available > transports in services.xml for the services in question. I found a FAQ > somewhere that said I needed to make sure that xalan-2.7.0.jar was copied > into the lib directory of the war distribution, but that file is already > there. > > > > Is there something else I need to do here to make this work? Or is this a > known issue that cannot be worked around at this time?
Inaccessible WSDL files after enabling both HTTP and HTTPS in Axis2/Tomcat
I have a problem that I am hoping someone could shed some light on. I have enabled both HTTP and one-way HTTPS in my Tomcat 6 instance. Likewise, I have added the correct configuration information to my axis2.xml in the war distribution of Axis2 1.5.1. The HTTP port is 8080 and the HTTPS port is 8443. They are running on a 1.5 JRE. Doing so seems to work ok. The Web services are all accessible at both the HTTP and HTTPS endpoints, so there seems to be no real issue there. However, the WSDL and XSD files are inaccessible. The same endpoints that allow SOAP requests no longer allow any of these "GET" requests to access WSDL and XSD files: "?wsdl", "?wsdl=somefile.wsdl", "?xsd=somefile.xsd". In all cases, I get the message "Internal server error". This happens whether or not I use the HTTP or HTTPS endpoints to access them. Note that I can still access these files directly by simply adding "/somefile.wsdl" to the end of the endpoint, but this is undesirable in the case of the main WSDL of the service as the service endpoints are not replaced properly. Note that this happens whether or not I explicitly declare the available transports in services.xml for the services in question. I found a FAQ somewhere that said I needed to make sure that xalan-2.7.0.jar was copied into the lib directory of the war distribution, but that file is already there. Is there something else I need to do here to make this work? Or is this a known issue that cannot be worked around at this time?
Problem in creating java source code from wsdl
Hi, I am using your axis2-1.5.1-bin project in intellij IDEA for creation of web services. I am using an axis2 plugin of intellij IDEA to generate java source code from wsdl file. Its working for most of the sample wsdl files provided by you in “samples” directory. The problem comes when I open StockQuoteService.wsdl in intellij IDEA to generate java source code. It asks to register http://w3.ibm.com/schemas/services/2002/11/15/stockquote uri. Even after registering this uri, it gives the error “Can’t resolve symbol ‘getStockQuote’” and “Can’t resolve symbol ‘getStockQuoteResponse’”. It seems there is some problem in wsdl where import is used for data types. Please suggest what is the problem The screen shot is also attached -- Thanks in advance Best Regards, *Raees Ahmad* import problem.xlsx Description: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
wsdl Service namespace
Hi, I have implemented a Service that should historicise a BPEL process. I should use this Service normally in a business process - BPEL. I implented the Service with Axis2, but there was generated a wsdl file for this Service without namespaces, that are used in this wsdl descripton. The prefixes are available through the whole document, but they are not listed in tag. After deploying this Service in Axis2 with Apache Tomcat I clicked only to the deployed Service under axis2/services and a wsdl was automatically generated, so the java2wsdl tool was used. I tried to reproduce the namespaces of the appropriate prefixes such as http://bpel.provenance"; xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:ns="http://bpel.provenance"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; > The targetNamespace was already given. But there are still two prefixes I don't know their namespaces. These are xmlns:ax210=... xmlns:urn=... Could anyone help me? Perhaps I write some code places where the prefixes are used. For example type="ax210:IOException"/> wsaw:Action="urn:initHistoryXML"/> wsaw:Action="urn:initHistoryXMLResponse"/> wsaw:Action="urn:initHistoryXMLException"/> wsaw:Action="urn:initHistoryXMLIOException"/> wsaw:Action="urn:lastUpdateHistoryXML"/> wsaw:Action="urn:lastUpdateHistoryXMLIOException"/> wsaw:Action="urn:historiciseBPELAction"/> wsaw:Action="urn:historiciseBPELActionIOException"/> regards Battal Kekec
NPE when requesting wsdl
I inherited some code from a developer that quit over a year ago. I am trying to get it up and running locally (he was doing the builds on his laptop that subsequently went with him). I am getting all the code to compile and deploy. It will pull up the listServices page too. http://localhost:8080/tink/services/listServices When I click on one of the Services displayed to get the wsdl though: http://localhost:8080/tink/services/Version?wsdl I get a Stack trace. Googling on the stack trace says to upgrade to the latest version, which I am using 1.5.1. It also says something about making sure the ServiceClass is upper case in the services.xml: http://schemas.xmlsoap.org/wsdl/ org.apache.axis2.dataretrieval.DataRetrievalException: java.lang.NullPointerException at org.apache.axis2.dataretrieval.WSDLDataLocator.outputInlineForm(WSDLDataLocator.java:135) at org.apache.axis2.dataretrieval.WSDLDataLocator.getData(WSDLDataLocator.java:73) at org.apache.axis2.dataretrieval.AxisDataLocatorImpl.getData(AxisDataLocatorImpl.java:81) at org.apache.axis2.description.AxisService.getData(AxisService.java:2808) at org.apache.axis2.description.AxisService.getWSDL(AxisService.java:1512) at org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1329) at org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:280) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:229) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) 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:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:637) Caused by: org.apache.axiom.om.OMException: java.lang.NullPointerException at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239) at org.apache.axiom.om.impl.llom.OMDocumentImpl.buildNext(OMDocumentImpl.java:167) at org.apache.axiom.om.impl.llom.OMNodeImpl.getNextOMSibling(OMNodeImpl.java:134) at org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:271) at org.apache.axiom.om.impl.llom.OMNodeImpl.detach(OMNodeImpl.java:191) at org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:585) at org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:117) at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:239) at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:195) at org.apache.axis2.description.AxisService2WSDL11.generateOM(AxisService2WSDL11.java:214) at org.apache.axis2.dataretrieval.WSDLDataLocator.outputInlineForm(WSDLDataLocator.java:131) ... 21 more Caused by: java.lang.NullPointerException at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:153) ... 31 more [INFO] getData request failed for dialect, http://schemas.xmlsoap.org/wsdl/ org.apache.axis2.dataretrieval.DataRetrievalException: java.lang.NullPointerException at org.apache.axis2.dataretrieval.WSDLDataLocator.outputInlineForm(WSDLDataLocator.java:135) at org.apache.axis2.dataretrieval.WSDLDataLocator.getData(WSDLDataLocator.java:73) at org.apache.axis2.dataretrieval.AxisDataLocatorImpl.getData(AxisDataLocatorImpl.java:81) at org.apache.axis2.description.AxisService.getData(AxisService.java:2808) at org.apache.axis2.description.AxisService.getWSDL(AxisService.java:1512) at org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1329) at org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:280) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:229) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) Thanks for any help!
Re: two similar xsd in the same wsdl databinded with xmlbean in axis2
On Thu, Jan 14, 2010 at 7:35 PM, Bartolomeo Nicolotti wrote: > Hello, > > we're using xmlbean to parse xmls as an axis2 databinding for travel > industries web services > > A web service we query has different version of the same kind of xml > > AirAvailability_8 > AirAvailability_9 > > > Is it possible to use xmlbean data binding with only one wsdl that has both > the kind of xml, i.e. something like: > > ... > > > > > > > > > > > name="LocalDateTimeCT_6_0" type="s0:LocalDateTimeCT_6_0Type"/> > name="AirAvailability_8" type="s0:AirAvailability_8Type"/> > name="AirAvailability_9" type="s0:AirAvailability_9Type"/> > > > > > > > > > My doubt is that this two kinds of xml have, oviously many similiar tags, > won't these conflict? > yes. if they have the same target namespace. thanks, Amila. > > Many many thanks > > Best regards. > > Bartolomeo Nicolotti. > > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
two similar xsd in the same wsdl databinded with xmlbean in axis2
Hello, we're using xmlbean to parse xmls as an axis2 databinding for travel industries web services A web service we query has different version of the same kind of xml AirAvailability_8 AirAvailability_9 Is it possible to use xmlbean data binding with only one wsdl that has both the kind of xml, i.e. something like: ... My doubt is that this two kinds of xml have, oviously many similiar tags, won't these conflict? Many many thanks Best regards. Bartolomeo Nicolotti.
Re: Static WSDL problems
We are using Axis2 bundled with our server, using AxisServlet. Where should this classes go? Do I still need a services.xml? Regards On Mon, Jan 11, 2010 at 12:49 PM, Yashvant chauhan wrote: > Hi Vinicius, > > As per my understanding you have to do folowing things, > 1) create a WSDL first with proper schema... > 2) generarte server side code using the Axis2 utility wsdl2Java and update > the *Impl java file your business logic > 3) create a war file with whole stuff and deploy it in a webserver > > once you completed above three steps your service should work. > > Regards, > Yashvant > > > On Mon, Jan 11, 2010 at 7:19 PM, Vinicius Carvalho > wrote: >> >> Hello there! We have an legacy WS built with Pojo based deployment >> with Axis2. I was told that in order to override a few defaults from >> axis (soap address, and some nillable properties on elements) one >> should get the generated WSDL and copy it to the same folder that the >> services.xml resides. >> >> Problem is: When we do that, Axis simply stop working. When I get the >> exact WSDL that is generated through: >> www.myserver.com/services/MyService?WSDL copy it to the folder of >> services.xml, restart tomcat. Well things get messy, and very very >> messy: One is that the marshalling stop working, parameters do not get >> converted I get lots of \n on string parameters for instance. >> >> As I said, I was told that just putting the WSDL at the services.xml >> folder should work, but it does not seems so. >> >> Any ideas please? >> >> Regards > > > > -- > > Yashvant Singh Chauhan > Mobile- 09845277271 > Bangalore > > * >
WSDL optional attributes
Hi, I have a problem with the wsdl2java code generation in axis2 for optional attributes In short, how can I make it generate Objects intead of primitives for OPTIONAL ATTRIBUTES? Axis1 would generate them as Objects, which was great since I could look for nulls as a sign that the client had not include them in the message. However, with Axis2, the class end up with primitives, instead of objects (e.g. int instead of Integer). . Take the following extract from my WSDL schema: ... ... So, how could I coerce the axis2 generator to behave like axis1 in this particular issue? Thanks in advance, --Luis R.
Re: Static WSDL problems
Hi Vinicius, As per my understanding you have to do folowing things, 1) create a WSDL first with proper schema... 2) generarte server side code using the Axis2 utility wsdl2Java and update the *Impl java file your business logic 3) create a war file with whole stuff and deploy it in a webserver once you completed above three steps your service should work. Regards, Yashvant On Mon, Jan 11, 2010 at 7:19 PM, Vinicius Carvalho wrote: > Hello there! We have an legacy WS built with Pojo based deployment > with Axis2. I was told that in order to override a few defaults from > axis (soap address, and some nillable properties on elements) one > should get the generated WSDL and copy it to the same folder that the > services.xml resides. > > Problem is: When we do that, Axis simply stop working. When I get the > exact WSDL that is generated through: > www.myserver.com/services/MyService?WSDL copy it to the folder of > services.xml, restart tomcat. Well things get messy, and very very > messy: One is that the marshalling stop working, parameters do not get > converted I get lots of \n on string parameters for instance. > > As I said, I was told that just putting the WSDL at the services.xml > folder should work, but it does not seems so. > > Any ideas please? > > Regards > -- Yashvant Singh Chauhan Mobile- 09845277271 Bangalore *
Static WSDL problems
Hello there! We have an legacy WS built with Pojo based deployment with Axis2. I was told that in order to override a few defaults from axis (soap address, and some nillable properties on elements) one should get the generated WSDL and copy it to the same folder that the services.xml resides. Problem is: When we do that, Axis simply stop working. When I get the exact WSDL that is generated through: www.myserver.com/services/MyService?WSDL copy it to the folder of services.xml, restart tomcat. Well things get messy, and very very messy: One is that the marshalling stop working, parameters do not get converted I get lots of \n on string parameters for instance. As I said, I was told that just putting the WSDL at the services.xml folder should work, but it does not seems so. Any ideas please? Regards
Axis2 supports multipart message with doc/literal wsdl style
Hi All, Does Axis2 supports multipart message with doc/literal wsdl style? Thanks, Rahul
Re: WSDL2Java: How to generating a single serivce.xml for multiple wsdl files?
Thanks for the update Amila! Amila Suriarachchi wrote: > > On Wed, Dec 30, 2009 at 11:07 AM, fazlan wrote: > >> >> Hi All, >> >> I'am trying to generate a *.aar from multiple wsdl's using the wsdl2java >> ant >> task. >> But I;am having a problem when generating services.xml files. >> >> My requirement is to generate a single services.xml for all the *.wsdl's, >> rather than services.xml files for each *.wsdl file. >> >> Is this possible? >> > no unless you merge your wsdl files into into one by creating multiple > services. > > thanks, > Amila. > >> If so, Pleases provide me with a snippet of ant script how >> to achieve this. >> >> e.g: >> I need something like the following, >> >> >> >>. . . >> >> >> . . . >> >> >> >> but, at present it generates in seperate services.xml files as, >> >> services.xml for WsdlA >> >> >>. . . >> >> >> >> services.xml for WsdlB >> >> >>. . . >> >> >> >> Thanks & Regards, >> Fazlan >> -- >> View this message in context: >> http://old.nabble.com/WSDL2Java%3A-How-to-generating-a-single-serivce.xml-for-multiple-wsdl-files--tp26964298p26964298.html >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ > > -- View this message in context: http://old.nabble.com/WSDL2Java%3A-How-to-generating-a-single-serivce.xml-for-multiple-wsdl-files--tp26964298p26984018.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: WSDL2Java: How to generating a single serivce.xml for multiple wsdl files?
On Wed, Dec 30, 2009 at 11:07 AM, fazlan wrote: > > Hi All, > > I'am trying to generate a *.aar from multiple wsdl's using the wsdl2java > ant > task. > But I;am having a problem when generating services.xml files. > > My requirement is to generate a single services.xml for all the *.wsdl's, > rather than services.xml files for each *.wsdl file. > > Is this possible? > no unless you merge your wsdl files into into one by creating multiple services. thanks, Amila. > If so, Pleases provide me with a snippet of ant script how > to achieve this. > > e.g: > I need something like the following, > > > >. . . > > > . . . > > > > but, at present it generates in seperate services.xml files as, > > services.xml for WsdlA > > >. . . > > > > services.xml for WsdlB > > >. . . > > > > Thanks & Regards, > Fazlan > -- > View this message in context: > http://old.nabble.com/WSDL2Java%3A-How-to-generating-a-single-serivce.xml-for-multiple-wsdl-files--tp26964298p26964298.html > Sent from the Axis - User mailing list archive at Nabble.com. > > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
WSDL2Java: How to generating a single serivce.xml for multiple wsdl files?
Hi All, I'am trying to generate a *.aar from multiple wsdl's using the wsdl2java ant task. But I;am having a problem when generating services.xml files. My requirement is to generate a single services.xml for all the *.wsdl's, rather than services.xml files for each *.wsdl file. Is this possible? If so, Pleases provide me with a snippet of ant script how to achieve this. e.g: I need something like the following, . . . . . . but, at present it generates in seperate services.xml files as, services.xml for WsdlA . . . services.xml for WsdlB . . . Thanks & Regards, Fazlan -- View this message in context: http://old.nabble.com/WSDL2Java%3A-How-to-generating-a-single-serivce.xml-for-multiple-wsdl-files--tp26964298p26964298.html Sent from the Axis - User mailing list archive at Nabble.com.
WSDL question
I'm having a problem with using axis on another apache project (ofbiz). I think the problem is with the way the wsdl is built. SoapUI generates a soap request as follows: http://schemas.xmlsoap.org/soap/envelope/";> http://ofbiz.apache.org/service/";> However, the above request fails unless I remove the namespace prefix from the elements below map-Map. Is there a way to change the wsdl so that the ns2 prefix is not generated by tools such as SoapUI? The wsdl is below: http://schemas.xmlsoap.org/wsdl/"; xmlns:soap=" http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:tns=" http://ofbiz.apache.org/service/"; xmlns:xsd=" http://www.w3.org/2001/XMLSchema"; targetNamespace=" http://ofbiz.apache.org/service/";> http://ofbiz.apache.org/service/";> The name of element need to be appended with name of entity such as eepk-Product for Product entity. The name of element need to be appended with name of entity such as eeval-Product for Product entity. Object content need to be in CDATA such as <cus-obj><![CDATA[--byteHex--]]></cus-obj> http://ofbiz.apache.org/service/"; optional="true" type="col-LinkedList"/> http://ofbiz.apache.org/service/"; optional="true" type="eeval-"/> http://ofbiz.apache.org/service/"; optional="false" type="std-String"/> http://ofbiz.apache.org/service/"; optional="true" type="std-String"/> http://ofbiz.apache.org/service/"; optional="true" type="std-String"/> http://ofbiz.apache.org/service/"; optional="true" type="std-String"/> http://ofbiz.apache.org/service/"; optional="false" type="std-String"/> http://ofbiz.apache.org/service/"; optional="false" type="std-String"/> http://schemas.xmlsoap.org/soap/http"/> http://localhost/webtools/control/SOAPService"; style="rpc"/> http://sc
Use autocreated WSDL as original WSDL
Hello! to use my service with the correct endpoint-address, i need to change the Endpoint-Addresses manually. Up to now I used the autocreation feature of Axis2 to generate my WSDL from AAR. As I just need to change the Endpointaddress I downloaded the auto WSDL and changed. Then I added the WSDL to my AAR, set the parameters useOriginalwsdl and modifyUserWSDLPortAddress and deployed the service again. After deployment no parameters are accepted from my freshly generated client stub. Do I have to change sth. else in the WSDL before deployment? Thanks alot and a peaceful x-mas!
Getting "org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL"
I'm trying to create the server skeleton from the available WSDL , however getting the CodeGenerationException. Attached herewith the WSDL , Schema & build file http://old.nabble.com/file/p26779983/build.xml build.xml http://old.nabble.com/file/p26779983/serviceExecute.wsdl serviceExecute.wsdl http://old.nabble.com/file/p26779983/RipandReadDetailV1.xsd RipandReadDetailV1.xsd http://old.nabble.com/file/p26779983/RipnReadOrderStatusV1Request.xsd RipnReadOrderStatusV1Request.xsd http://old.nabble.com/file/p26779983/RipnReadOrderStatusV1Response.xsd RipnReadOrderStatusV1Response.xsd -- View this message in context: http://old.nabble.com/Getting-%22org.apache.axis2.wsdl.codegen.CodeGenerationException%3A-Error-parsing-WSDL%22-tp26779983p26779983.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Creating Web Service client using HTTPS from wsdl files
I don't get it. I am the client. The server is on the other side. I can
test/connect to the server using OpenSSL which by the way takes all these
parameters (certificate, key, truststore, protocol, cipher).
Thanks
Vadim.
(310)765-3812
From: Thilina Mahesh Buddhika [mailto:thilin...@gmail.com]
Sent: Wednesday, December 09, 2009 10:28 AM
To: axis-user@ws.apache.org
Subject: Re: Creating Web Service client using HTTPS from wsdl files
AFAIK these configuration needs to be happen at the transport level and it
depends on the app server you are using for the deployment. The related
documentation of that app server will give you a thorough insight into these
configuration options.
thanks.
/thilina
Thilina Mahesh Buddhika
http://blog.thilinamb.com
On Wed, Dec 9, 2009 at 10:03 PM, Vadim Letitchevski
mailto:vletitchev...@teledyne.com>> wrote:
Thank you Thhilina.
What about the rest of it - protocol and cipher?
Thanks
Vadim.
From: Thilina Mahesh Buddhika
[mailto:thilin...@gmail.com<mailto:thilin...@gmail.com>]
Sent: Wednesday, December 09, 2009 5:13 AM
To: axis-user@ws.apache.org<mailto:axis-user@ws.apache.org>
Subject: Re: Creating Web Service client using HTTPS from wsdl files
hi,
Some of the properties you mentioned, like two-way authentication has to be
enabled in the SSL settings in the app-server where the Axis2 is deployed.
For example, in Tomcat following configuration segment available in server.xml
holds some of these parameters.
It depends on the app server you are using. Some times it is required to set
some system variables to support these parameters. For example, if you have
enabled clientAuth(two-way authentication), then you have to set
"javax.net.ssl.keyStore" and "javax.net.ssl.keyStorePassword" system properties.
thanks.
/thilina
Thilina Mahesh Buddhika
http://blog.thilinamb.com
On Wed, Dec 9, 2009 at 6:50 AM, Vadim Letitchevski
mailto:vletitchev...@teledyne.com>> wrote:
I am trying to configure my client auto-generated from WSDL to use SSL.
I have read already the recommendations to set these:
System.setProperty("javax.net.ssl.trustStore", "/path/to/.keystore");
System.setProperty("javax.net.ssl.trustStorePassword", "changeit");
Unfortunately this is not all I need to set. I care about using only TLS1, only
NULL-SHA Cipher, two way authentication and keep-alive.
The problem is, I can't find any mentioning of the property names which are
needed for me, neither a full list of supported ssl properties and their values
which can be set with System.setProperty() as well.
Thanks
Vadim.
(310)765-3812
Re: Creating Web Service client using HTTPS from wsdl files
AFAIK these configuration needs to be happen at the transport level and it
depends on the app server you are using for the deployment. The related
documentation of that app server will give you a thorough insight into these
configuration options.
thanks.
/thilina
Thilina Mahesh Buddhika
http://blog.thilinamb.com
On Wed, Dec 9, 2009 at 10:03 PM, Vadim Letitchevski <
vletitchev...@teledyne.com> wrote:
> Thank you Thhilina.
> What about the rest of it - protocol and cipher?
>
> Thanks
> Vadim.
>
>
> --
> *From:* Thilina Mahesh Buddhika [mailto:thilin...@gmail.com]
> *Sent:* Wednesday, December 09, 2009 5:13 AM
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Creating Web Service client using HTTPS from wsdl files
>
> hi,
>
> Some of the properties you mentioned, like two-way authentication has to be
> enabled in the SSL settings in the app-server where the Axis2 is deployed.
>
> For example, in Tomcat following configuration segment available in
> server.xml holds some of these parameters.
>
> maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
>enableLookups="false" disableUploadTimeout="true"
>acceptCount="100" scheme="https" secure="true"
>clientAuth="false" sslProtocol="TLS"
>keystoreFile="keystore.jks"
>keystorePass="wso2carbon" />
>
> It depends on the app server you are using. Some times it is required to
> set some system variables to support these parameters. For example, if you
> have enabled clientAuth(two-way authentication), then you have to set
> "javax.net.ssl.keyStore" and "javax.net.ssl.keyStorePassword" system
> properties.
>
> thanks.
> /thilina
>
> Thilina Mahesh Buddhika
> http://blog.thilinamb.com
>
>
> On Wed, Dec 9, 2009 at 6:50 AM, Vadim Letitchevski <
> vletitchev...@teledyne.com> wrote:
>
>> I am trying to configure my client auto-generated from WSDL to use SSL.
>> I have read already the recommendations to set these:
>> System.setProperty("javax.net.ssl.trustStore", "/path/to/.keystore");
>> System.setProperty("javax.net.ssl.trustStorePassword", "changeit");
>>
>> Unfortunately this is not all I need to set. I care about using only TLS1,
>> only NULL-SHA Cipher, two way authentication and keep-alive.
>> The problem is, I can't find any mentioning of the property names which
>> are needed for me, neither a full list of supported ssl properties and their
>> values which can be set with System.setProperty() as well.
>>
>>
>> Thanks
>> Vadim.
>> (310)765-3812
>>
>>
>>
>
RE: Creating Web Service client using HTTPS from wsdl files
Thank you Thhilina.
What about the rest of it - protocol and cipher?
Thanks
Vadim.
From: Thilina Mahesh Buddhika [mailto:thilin...@gmail.com]
Sent: Wednesday, December 09, 2009 5:13 AM
To: axis-user@ws.apache.org
Subject: Re: Creating Web Service client using HTTPS from wsdl files
hi,
Some of the properties you mentioned, like two-way authentication has to be
enabled in the SSL settings in the app-server where the Axis2 is deployed.
For example, in Tomcat following configuration segment available in server.xml
holds some of these parameters.
It depends on the app server you are using. Some times it is required to set
some system variables to support these parameters. For example, if you have
enabled clientAuth(two-way authentication), then you have to set
"javax.net.ssl.keyStore" and "javax.net.ssl.keyStorePassword" system properties.
thanks.
/thilina
Thilina Mahesh Buddhika
http://blog.thilinamb.com
On Wed, Dec 9, 2009 at 6:50 AM, Vadim Letitchevski
mailto:vletitchev...@teledyne.com>> wrote:
I am trying to configure my client auto-generated from WSDL to use SSL.
I have read already the recommendations to set these:
System.setProperty("javax.net.ssl.trustStore", "/path/to/.keystore");
System.setProperty("javax.net.ssl.trustStorePassword", "changeit");
Unfortunately this is not all I need to set. I care about using only TLS1, only
NULL-SHA Cipher, two way authentication and keep-alive.
The problem is, I can't find any mentioning of the property names which are
needed for me, neither a full list of supported ssl properties and their values
which can be set with System.setProperty() as well.
Thanks
Vadim.
(310)765-3812
Re: Creating Web Service client using HTTPS from wsdl files
hi,
Some of the properties you mentioned, like two-way authentication has to be
enabled in the SSL settings in the app-server where the Axis2 is deployed.
For example, in Tomcat following configuration segment available in
server.xml holds some of these parameters.
It depends on the app server you are using. Some times it is required to set
some system variables to support these parameters. For example, if you have
enabled clientAuth(two-way authentication), then you have to set
"javax.net.ssl.keyStore" and "javax.net.ssl.keyStorePassword" system
properties.
thanks.
/thilina
Thilina Mahesh Buddhika
http://blog.thilinamb.com
On Wed, Dec 9, 2009 at 6:50 AM, Vadim Letitchevski <
vletitchev...@teledyne.com> wrote:
> I am trying to configure my client auto-generated from WSDL to use SSL.
> I have read already the recommendations to set these:
> System.setProperty("javax.net.ssl.trustStore", "/path/to/.keystore");
> System.setProperty("javax.net.ssl.trustStorePassword", "changeit");
>
> Unfortunately this is not all I need to set. I care about using only TLS1,
> only NULL-SHA Cipher, two way authentication and keep-alive.
> The problem is, I can't find any mentioning of the property names which are
> needed for me, neither a full list of supported ssl properties and their
> values which can be set with System.setProperty() as well.
>
>
> Thanks
> Vadim.
> (310)765-3812
>
>
>
Creating Web Service client using HTTPS from wsdl files
I am trying to configure my client auto-generated from WSDL to use SSL.
I have read already the recommendations to set these:
System.setProperty("javax.net.ssl.trustStore", "/path/to/.keystore");
System.setProperty("javax.net.ssl.trustStorePassword", "changeit");
Unfortunately this is not all I need to set. I care about using only TLS1, only
NULL-SHA Cipher, two way authentication and keep-alive.
The problem is, I can't find any mentioning of the property names which are
needed for me, neither a full list of supported ssl properties and their values
which can be set with System.setProperty() as well.
Thanks
Vadim.
(310)765-3812
AXIS 2 doesn't generate WSDL without access to the Internet!
Hi all, I am working on a web service application using AXIS2 1.1.1 and Tomcat 6. It requires DNS setup and access to the Internet when the service starts to dynamical generate and validate the wsdl before making it avilable online. I'm wondering if there is a way to generate WSDL without having access to the Internet which is the case in private networks behind firewalls. If I put a static, already validated WSDL file on the web server, would it be enough for the client code generation/applications? Without DNS setup it replies the following error message when trying to access the wsdl : https://myHost/example/services/example?wsdl<https://myhost/example/services/example?wsdl> Unable to generate WSDL for this service - If you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml (/serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl: service/@name). The WSDL is in the proper place with the proper name as suggested above and AXIS2 generates the WSDL without problem if it DNS has been setup in the host with access to the Internet *when Tomcat restarts*. I'd appreciate your help, I searched online but couldn't find the answer. Thanks Joe
Re: XSLT link in WSDL removed when deployed
hi charles, I've tried that and it don't seem to have any effect. 2009/12/4 Charles Galpin > Hi Håkon > > Axis generates it's own WSDL dynamically. If you want to serve a static > copy of it you have to edit the services.xml and ser a parameter > "useOriginalwsdl" to true and possibly "modifyUserWSDLPortAddress" to > false in order to serve your original WSDL. > > hth > charles > > On Dec 3, 2009, at 3:31 AM, Håkon Sagehaug wrote: > > Hi all, > > I got a service with a WSDL that contains a link to a XSLT stylesheet, but > when i deploy my service it looks like the link is removed from the WSDL, > anyone experienced this before ? > > > > cheers, Håkon > > >
WSDL errors on AXIS/2 but works elsewhere?
Hello all, BACKGROUND: I have a WSDL file which others are successfully using. I have generated the background code and all structures from it (with a slightly older MyEclipse), and sending/receiving dummy data works for the basics. This is also my first time creating a web service from a provided WSDL. PROBLEM: Using the Eclipse SOAP Explorer I query for and get the WSDL file, but it also shows a slew of validation errors. Meanwhile the company who created the WSDL uses another SOAP client and they don't see the errors, just the partial WSDL. When I hit the same URL with a web browser it shows the XML, but it is about 1/8 of the original file size (5k instead of 42k). The most obvious problem is that every xs:complexType is missing from the returned WSDL - in fact the xsd:schema definitions are empty except for the import tags which are being reported as errors (see below). I thought the XML itself was corrupt or the namespace URLs (which I don't think are valid URLs) were the problem, but others have confirmed that they are using the same WSDL successfully even though I had problems with it in the w3 validator. I also wondered if it was because of some networking/firewall issues, but the referenced targetNamespace is pingable from the development machine and server. At this point I'm grasping at straws to identify where the problem is happening (within JAX-WS? AXIS? Apache? Tomcat?), let alone the cause of the problem and what I can do about it. Maybe I have some mis-matched JAR files - at least on the server I used findjar to solve Java problems. The problem with that theory is that MyEclipse's internal server should be JAR-consistent but has the same problems serving the WSDL. Thanks for any feedback! -Chris - part of errors reported from SOAP Explorer: IWAB0380E Errors were encountered while validating XML schemas. XSD: Type reference 'http://customerlookup.domain.webservice.midtier.websolutions.dcs/xsd#CustomerInformationInput' is unresolved XSD: Type reference 'http://customerlookup.domain.webservice.midtier.websolutions.dcs/xsd#CustomerInformationOutput' is unresolved ... XSD: The location 'http://server:8080/test/webservice?xsd=5' has not been resolved because the import is unused XSD: There is no xmlns declaration for namespace 'http://customerlookup.domain.webservice.midtier.websolutions.dcs/xsd' IWAB0381I http://server:8080/test/webservice?wsdl was successfully open
Re: XSLT link in WSDL removed when deployed
Hi Håkon Axis generates it's own WSDL dynamically. If you want to serve a static copy of it you have to edit the services.xml and ser a parameter "useOriginalwsdl" to true and possibly "modifyUserWSDLPortAddress" to false in order to serve your original WSDL. hth charles On Dec 3, 2009, at 3:31 AM, Håkon Sagehaug wrote: > Hi all, > > I got a service with a WSDL that contains a link to a XSLT stylesheet, but > when i deploy my service it looks like the link is removed from the WSDL, > anyone experienced this before ? > > > > cheers, Håkon >
AXIS2 : how to dynamically generate WSDL without access to the Internet?
Hi all, I am working on a web service application using AXIS2 1.1.1 and Tomcat 6. It requires DNS setup and access to the Internet when the service starts to dynamical generate and validate the wsdl before making it avilable online. I'm wondering if there is a way to generate WSDL without having access to the Internet which is the case in private networks behind firewalls. If I put a static, already validated WSDL file on the web server, would it be enough for the client code generation/applications? Without DNS setup it replies the following error message when trying to access the wsdl : https://myHost/example/services/example?wsdl Unable to generate WSDL for this service - If you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml (/serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl:service/@name). The WSDL is in the proper place with the proper name as suggested above and AXIS2 generates the WSDL without problem if it DNS has been setup in the host with access to the Internet *when Tomcat restarts*. I'd appreciate your help, I searched online but couldn't find the answer. Thanks Joe
XSLT link in WSDL removed when deployed
Hi all, I got a service with a WSDL that contains a link to a XSLT stylesheet, but when i deploy my service it looks like the link is removed from the WSDL, anyone experienced this before ? cheers, Håkon
Security Header in Generated POJO service WSDL
Hi all, I have problem about wsse security header in generated wsdl of POJO web service. i think wsdl generation algoritm for pojo services don't include rampart security. is there any way for manupulating of generated wsdl to include security headers? -- *Dinçer Karaduman* *Analyst Programmer * **
RE: Creating Web Service client using HTTPS from wsdl files
I think that I've see that about connection reset because of the missing
keystore javax.net.ssl.trustStore property
System.setProperty("javax.net.ssl.trustStore", "/path/to/.keystore");
System.setProperty("javax.net.ssl.trustStorePassword", "changeit");
ConfigurationContext ctx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(null);
authStub = new EmrAuthWsStub(ctx,
"https://172.17.0.24:8443/emrws"; +
"/services/emrAuthWs.emrAuthWsHttpSoap12Endpoint");
/*
//SUpport for username token (wss)
ServiceClient sc = authStub._getServiceClient();
sc.engageModule("rampart");
Options options = sc.getOptions();
options.setUserName("user");
options.setPassword("password");
*/
then you have an authStub that supports calls over https, check the port
https://172.17.0.24:8443/..., you have to copy it from your wsdl, and change
http for https and the port too.
You can generate the .keystore using, keytool.exe but I'm not pretty sure, I
just copied the one generated for the server side, but I suppose it is not the
best way.
Jaime Hablutzel | 9-8964-0369
(tildes omitidas intencionalmente)
> Date: Mon, 16 Nov 2009 16:24:45 -0500
> From: suma.subraman...@thomsonreuters.com
> Subject: RE: Creating Web Service client using HTTPS from wsdl files
> To: axis-user@ws.apache.org
>
> Hi Prabath,
>
>Sorry, I don't think I have permission to expose the client code. But
> someone who had tried a similar scenario, please help.
>
> Thanks,
> Suma
>
> -Original Message-
> From: Prabath Siriwardena [mailto:prab...@wso2.com]
> Sent: Monday, November 16, 2009 1:52 PM
> To: axis-user@ws.apache.org
> Subject: Re: Creating Web Service client using HTTPS from wsdl files
>
> Can you please attach your client code ?
>
> Thanks& regards.
> -Prabath
>
> suma.subraman...@thomsonreuters.com wrote:
> >
> > Hi
> >
> > I need to invoke a set of web services through HTTPS. The WSDL files
> > and the XSD files are provided. I was able to get the token from the
> > client with the Authentication web service. But when I invoke the
> > other web service I get a SocketException: Connection Reset. As I'm
> > new to Java and web service I'm not sure where has it gone wrong.
> >
> > If I invoke the web service without providing the token, its hitting
> > the server. But when I provide the token I get the above mentioned
> > error. Could anyone help me with the issue? Also may be if anyone has
> > a sample program for HTTPS it will be helpful. Please help
> >
> > Thanks,
> >
> > Suma
> >
> > *SUMA (Sumathi Musuwathi Subramanian)* Software Engineer
> >
> > *Thomson Reuters*
> >
> > Phone: (314)468-2565
> >
> > suma.subraman...@reuters.com
> > thomsonreuters.com
> >
> >
> >
> > This email was sent to you by Thomson Reuters, the global news and
> > information company.
> > Any views expressed in this message are those of the individual
> > sender, except where the sender specifically states them to be the
> > views of Thomson Reuters.
>
>
>
> This email was sent to you by Thomson Reuters, the global news and
> information company.
> Any views expressed in this message are those of the individual sender,
> except where the sender specifically states them to be the views of Thomson
> Reuters.
>
>
_
RE: Creating Web Service client using HTTPS from wsdl files
Hi Prabath, Sorry, I don't think I have permission to expose the client code. But someone who had tried a similar scenario, please help. Thanks, Suma -Original Message- From: Prabath Siriwardena [mailto:prab...@wso2.com] Sent: Monday, November 16, 2009 1:52 PM To: axis-user@ws.apache.org Subject: Re: Creating Web Service client using HTTPS from wsdl files Can you please attach your client code ? Thanks& regards. -Prabath suma.subraman...@thomsonreuters.com wrote: > > Hi > > I need to invoke a set of web services through HTTPS. The WSDL files > and the XSD files are provided. I was able to get the token from the > client with the Authentication web service. But when I invoke the > other web service I get a SocketException: Connection Reset. As I'm > new to Java and web service I'm not sure where has it gone wrong. > > If I invoke the web service without providing the token, its hitting > the server. But when I provide the token I get the above mentioned > error. Could anyone help me with the issue? Also may be if anyone has > a sample program for HTTPS it will be helpful. Please help > > Thanks, > > Suma > > *SUMA (Sumathi Musuwathi Subramanian)* Software Engineer > > *Thomson Reuters* > > Phone: (314)468-2565 > > suma.subraman...@reuters.com > thomsonreuters.com > > > > This email was sent to you by Thomson Reuters, the global news and > information company. > Any views expressed in this message are those of the individual > sender, except where the sender specifically states them to be the > views of Thomson Reuters. This email was sent to you by Thomson Reuters, the global news and information company. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.
Re: Creating Web Service client using HTTPS from wsdl files
Can you please attach your client code ? Thanks& regards. -Prabath suma.subraman...@thomsonreuters.com wrote: Hi I need to invoke a set of web services through HTTPS. The WSDL files and the XSD files are provided. I was able to get the token from the client with the Authentication web service. But when I invoke the other web service I get a SocketException: Connection Reset. As I'm new to Java and web service I'm not sure where has it gone wrong. If I invoke the web service without providing the token, its hitting the server. But when I provide the token I get the above mentioned error. Could anyone help me with the issue? Also may be if anyone has a sample program for HTTPS it will be helpful. Please help Thanks, Suma *SUMA (Sumathi Musuwathi Subramanian)* Software Engineer *Thomson Reuters* Phone: (314)468-2565 suma.subraman...@reuters.com thomsonreuters.com This email was sent to you by Thomson Reuters, the global news and information company. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.
Creating Web Service client using HTTPS from wsdl files
Hi I need to invoke a set of web services through HTTPS. The WSDL files and the XSD files are provided. I was able to get the token from the client with the Authentication web service. But when I invoke the other web service I get a SocketException: Connection Reset. As I'm new to Java and web service I'm not sure where has it gone wrong. If I invoke the web service without providing the token, its hitting the server. But when I provide the token I get the above mentioned error. Could anyone help me with the issue? Also may be if anyone has a sample program for HTTPS it will be helpful. Please help Thanks, Suma SUMA (Sumathi Musuwathi Subramanian) Software Engineer Thomson Reuters Phone: (314)468-2565 suma.subraman...@reuters.com thomsonreuters.com This email was sent to you by Thomson Reuters, the global news and information company. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.
Re: [Axis2] Setting nillable = false in WSDL
There are open bugs on this and related issues with the wsdl generation. Please vote for them if you care about these kinds of issues as this should help them get priority. http://issues.apache.org/jira/browse/AXIS2 thanks, charles On Nov 13, 2009, at 7:50 AM, Didav Didav wrote: Hi All, I am using Axis2 1.3 and jdk 1.5 and tomcat 6 The WSDL file generated by Axis sets the element "nillable=true", but i want to set "nillable=false"... Exemple : type="xs:boolean"/> type="xs:string"/> Is there any way I can get the 'nillable' property to true or false in a declarative fashion.. I try with the annotation @XmlElement(nillable = false, required=true) but it doesn't work :( Thanks a lot, David PC, téléphones portables, souris hi-tech. à gagner grâce à Hotmail ! C'est ici !
FW: [Axis2] Setting nillable = false in WSDL
Hi All, I am using Axis2 1.3 and jdk 1.5 and tomcat 6 The WSDL file generated by Axis sets the element "nillable=true", but i want to set "nillable=false"... Exemple : Is there any way I can get the 'nillable' property to true or false in a declarative fashion.. I try with the annotation @XmlElement(nillable = false, required=true) but it doesn't work :( Thanks a lot, David _ Nouveau ! Tout Windows Live débarque dans votre téléphone. Voir les Windows phone http://clk.atdmt.com/FRM/go/175819071/direct/01/
Re: WSDL Parser java
WSDL parsers only support for WSDL content, to read Schema you have to
use a Schema parser try for Apache XmlSchema [1].
[1] - http://ws.apache.org/commons/XmlSchema/
Thanks,
On Wed, Nov 11, 2009 at 3:27 PM, Stefano Tranquillini
wrote:
> i'm using now wsdl4j.
> also axis2 used wsdl4j, but:
> how can i read the xsd inside the wsdl?
> i'm able to read all the informations, but not the types of the
> message, i will explain better:
>
> a snippet of a wsdl:
>
>
> http://www.example.org/NewWSDLFile/";>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> i'm able to read the message :
>
> SchemaExtensibilityElement ({http://www.w3.org/2001/XMLSchema}schema):
> required=null
> element=[xsd:schema: null]
> Message: name={http://www.example.org/NewWSDLFile/}NewOperationResponse
> Part: name=parameters
> elementName={http://www.example.org/NewWSDLFile/}NewOperationResponse
> Message: name={http://www.example.org/NewWSDLFile/}NewOperationRequest
> Part: name=parameters
> elementName={http://www.example.org/NewWSDLFile/}NewOperation
> PortType: name={http://www.example.org/NewWSDLFile/}NewWSDLFile
> Operation: name=NewOperation
> style=REQUEST_RESPONSE
> Input: name=null
> Message: name={http://www.example.org/NewWSDLFile/}NewOperationRequest
> Part: name=parameters
> elementName={http://www.example.org/NewWSDLFile/}NewOperation
> Output: name=null
> Message: name={http://www.example.org/NewWSDLFile/}NewOperationResponse
> Part: name=parameters
> elementName={http://www.example.org/NewWSDLFile/}NewOperationResponse
>
>
> but i'm not able to read the definition of the content of message like
> the lines inside
>
> any hints about that?
>
> thanks all
>
> --
> Stefano
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
Re: WSDL Parser java
i'm using now wsdl4j.
also axis2 used wsdl4j, but:
how can i read the xsd inside the wsdl?
i'm able to read all the informations, but not the types of the
message, i will explain better:
a snippet of a wsdl:
http://www.example.org/NewWSDLFile/";>
i'm able to read the message :
SchemaExtensibilityElement ({http://www.w3.org/2001/XMLSchema}schema):
required=null
element=[xsd:schema: null]
Message: name={http://www.example.org/NewWSDLFile/}NewOperationResponse
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperationResponse
Message: name={http://www.example.org/NewWSDLFile/}NewOperationRequest
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperation
PortType: name={http://www.example.org/NewWSDLFile/}NewWSDLFile
Operation: name=NewOperation
style=REQUEST_RESPONSE
Input: name=null
Message: name={http://www.example.org/NewWSDLFile/}NewOperationRequest
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperation
Output: name=null
Message: name={http://www.example.org/NewWSDLFile/}NewOperationResponse
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperationResponse
but i'm not able to read the definition of the content of message like
the lines inside
any hints about that?
thanks all
--
Stefano
WSDL and XSD Design | Which design is perfect
Hi, I have a WSDL defining fault as given below 1. . 2. I got suggestion from one of the forums to change "InvalidPINInfo" as follows to minimize changes in WSDL in future if fault definition needs to changed and then define in one of the XSDs as follows(Indirect mapping), so future change only needs XSD changes Questions: 1. So always WSDL design needs to be taken care that it should not change often? 2. Even if it is XSD change it is a Service contract change.Not only WSDL. Is it right? Thanks, Appasamy
Re: Generated WSDL HTTPS Port not 8443
On Tue, Nov 10, 2009 at 18:31, v2cg4ss wrote: > > I just tried the nightly build of 10-Nov-2009 14:33 and the endpoints look > good: > > > - > location="https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.NetEffectWS_1HttpsSoap11Endpoint/"; > /> > > - > location="http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpSoap11Endpoint/"; > /> > > - > location="http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpSoap12Endpoint/"; > /> > > - > location="https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpsSoap12Endpoint/"; > /> > > - > location="https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpsEndpoint/"; > /> > > - > location="http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpEndpoint/"; > /> > > > > So this is good, I also found that axis2 1.3 works as well. The problem I > have now is a .NET client that is afraid to move forward with us using 1.5.1 > knowing that someone on their end could refresh the endpoints via Visual > Studio and blow up production. Yes, I agree that they should have test > procedures in place...But I don't understand how this worked in axis2 1.3 > and has been broken since 1.4.1, 1.5, and 1.5.1. I cannot download 1.4 to > see if it is broken in that version but this is a major miss but someone. > > So I would like to vote for this issue to be resolved quickly and a 1.5.2 > release be made. > This is very unlikely. It would mean to merge the changes from the trunk to the 1.5 branch. Technically this is not a big problem, but the code that is modified is very badly designed and there are external projects that are tightly coupled to that piece of code. I already burned my fingers with this when fixing the issue in the trunk [1] and I'm not going through this again. The fix will go into 1.6 unless somebody else volunteers to merge this into the 1.5 branch. [1] http://markmail.org/message/3gy3gnzkbh5kxt4c > > SanjayGupta wrote: >> >> Hi, >> I have the same issue and very interested in finding a solution. >> Sanjay >> >> -Original Message- >> From: v2cg4ss [mailto:ssel...@datamentors.com] >> Sent: Monday, November 09, 2009 1:40 PM >> To: axis-user@ws.apache.org >> Subject: Re: Generated WSDL HTTPS Port not 8443 >> >> >> Is this in a nightly build that I can test? Will this be axis2 1.5.2? >> >> >> Andreas Veithen-2 wrote: >>> >>> On Thu, Nov 5, 2009 at 20:49, v2cg4ss wrote: >>>> >>>> Thank you for the reply, is this being resolved soon. >>> >>> It is implemented, but the issue is not closed yet because the >>> documentation is not up to date with the changes. >>> >>>> I have a client using >>>> .NET and they are generating their client code from the WSDL. The >>>> programmer claims that they cannot change the endpoint in the .NET code >>>> like >>>> I can with java. >>>> >>>> MyWSStub stub = new MyWSStub(ctx, >>>> "https://localhost:8443/axis2/services/MyWS";); >>>> >>>> Scott >>>> >>>> >>>> Andreas Veithen-2 wrote: >>>>> >>>>> Generating the correct endpoint URIs for https is something that >>>>> doesn't work properly in the available Axis2 releases. See AXIS2-4465 >>>>> and related issues. >>>>> >>>>> Andreas >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26219924.html >>>> Sent from the Axis - User mailing list archive at Nabble.com. >>>> >>>> >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26274176.html >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> >> > > -- > View this message in context: > http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26287344.html > Sent from the Axis - User mailing list archive at Nabble.com. > >
RE: Generated WSDL HTTPS Port not 8443
I just tried the nightly build of 10-Nov-2009 14:33 and the endpoints look good: - https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.NetEffectWS_1HttpsSoap11Endpoint/"; /> - http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpSoap11Endpoint/"; /> - http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpSoap12Endpoint/"; /> - https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpsSoap12Endpoint/"; /> - https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpsEndpoint/"; /> - http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpEndpoint/"; /> So this is good, I also found that axis2 1.3 works as well. The problem I have now is a .NET client that is afraid to move forward with us using 1.5.1 knowing that someone on their end could refresh the endpoints via Visual Studio and blow up production. Yes, I agree that they should have test procedures in place...But I don't understand how this worked in axis2 1.3 and has been broken since 1.4.1, 1.5, and 1.5.1. I cannot download 1.4 to see if it is broken in that version but this is a major miss but someone. So I would like to vote for this issue to be resolved quickly and a 1.5.2 release be made. SanjayGupta wrote: > > Hi, > I have the same issue and very interested in finding a solution. > Sanjay > > -Original Message- > From: v2cg4ss [mailto:ssel...@datamentors.com] > Sent: Monday, November 09, 2009 1:40 PM > To: axis-user@ws.apache.org > Subject: Re: Generated WSDL HTTPS Port not 8443 > > > Is this in a nightly build that I can test? Will this be axis2 1.5.2? > > > Andreas Veithen-2 wrote: >> >> On Thu, Nov 5, 2009 at 20:49, v2cg4ss wrote: >>> >>> Thank you for the reply, is this being resolved soon. >> >> It is implemented, but the issue is not closed yet because the >> documentation is not up to date with the changes. >> >>> I have a client using >>> .NET and they are generating their client code from the WSDL. The >>> programmer claims that they cannot change the endpoint in the .NET code >>> like >>> I can with java. >>> >>> MyWSStub stub = new MyWSStub(ctx, >>> "https://localhost:8443/axis2/services/MyWS";); >>> >>> Scott >>> >>> >>> Andreas Veithen-2 wrote: >>>> >>>> Generating the correct endpoint URIs for https is something that >>>> doesn't work properly in the available Axis2 releases. See AXIS2-4465 >>>> and related issues. >>>> >>>> Andreas >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26219924.html >>> Sent from the Axis - User mailing list archive at Nabble.com. >>> >>> >> >> > > -- > View this message in context: > http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26274176.html > Sent from the Axis - User mailing list archive at Nabble.com. > > > -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26287344.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Generated WSDL HTTPS Port not 8443
Hi, I have the same issue and very interested in finding a solution. Sanjay -Original Message- From: v2cg4ss [mailto:ssel...@datamentors.com] Sent: Monday, November 09, 2009 1:40 PM To: axis-user@ws.apache.org Subject: Re: Generated WSDL HTTPS Port not 8443 Is this in a nightly build that I can test? Will this be axis2 1.5.2? Andreas Veithen-2 wrote: > > On Thu, Nov 5, 2009 at 20:49, v2cg4ss wrote: >> >> Thank you for the reply, is this being resolved soon. > > It is implemented, but the issue is not closed yet because the > documentation is not up to date with the changes. > >> I have a client using >> .NET and they are generating their client code from the WSDL. The >> programmer claims that they cannot change the endpoint in the .NET code >> like >> I can with java. >> >> MyWSStub stub = new MyWSStub(ctx, >> "https://localhost:8443/axis2/services/MyWS";); >> >> Scott >> >> >> Andreas Veithen-2 wrote: >>> >>> Generating the correct endpoint URIs for https is something that >>> doesn't work properly in the available Axis2 releases. See AXIS2-4465 >>> and related issues. >>> >>> Andreas >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26219924.html >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26274176.html Sent from the Axis - User mailing list archive at Nabble.com.
RuntimeException not generated correctly in the wsdl
Hi, I have my own exception SysException that externds RuntimeException However in the wsdl I don't see the RuntimeException defined well therefore when using soap ui to call myservice I get this: :0: error: src-resolve: type 'RuntimeException@ http://www.w3.org/2001/XMLSchema' not found. org.apache.xmlbeans.XmlException: .wsdl:0: error: src-resolve: type 'runtimeexcept...@http://www.w3.org/2001/XMLSchema' not found. In the generated wsdl i see: as you can see the Exception got ax22 while the RuntimeException got xs further I see this in wsdl: However there is no such definition for RuntimeException. Can anyone assist me please to understand why the RuntimeException seem not to be generated well in wsdl? Note that If I add manually to wsdl a section like the Exception with "RuntimeException" like this: and update also the RuntimeException from xs to ax22 I can call my service well with soap ui. Thanks
Re: Generated WSDL HTTPS Port not 8443
Is this in a nightly build that I can test? Will this be axis2 1.5.2? Andreas Veithen-2 wrote: > > On Thu, Nov 5, 2009 at 20:49, v2cg4ss wrote: >> >> Thank you for the reply, is this being resolved soon. > > It is implemented, but the issue is not closed yet because the > documentation is not up to date with the changes. > >> I have a client using >> .NET and they are generating their client code from the WSDL. The >> programmer claims that they cannot change the endpoint in the .NET code >> like >> I can with java. >> >> MyWSStub stub = new MyWSStub(ctx, >> "https://localhost:8443/axis2/services/MyWS";); >> >> Scott >> >> >> Andreas Veithen-2 wrote: >>> >>> Generating the correct endpoint URIs for https is something that >>> doesn't work properly in the available Axis2 releases. See AXIS2-4465 >>> and related issues. >>> >>> Andreas >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26219924.html >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26274176.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: [Axis2] Setting nillable = false in WSDL
I'm having the same problem. All the non-primitives are set to nillable=true. How do I control the "nillable" attribute when I write my java class. Didav !!! wrote: > > > Hi All, > > I am using Axis2 1.3 and jdk 1.5 > > The WSDL file generated by Axis sets all 'nillable' attribute for all > elements to true. > > Is there any way I can get the 'nillable' property to true or false in a > declarative fashion.. > > I try with the annotation @XmlElement(nillable = false required=true) but > it doesn't work :( > > Thanks, > > David > > _ > Nouveau ! Tout Windows débarque dans votre téléphone. Voir les Windows > phone > http://clk.atdmt.com/FRM/go/175819071/direct/01/ > -- View this message in context: http://old.nabble.com/-Axis2--Setting-nillable-%3D-false-in-WSDL-tp26229157p26272419.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: use supplied WSDL instead of generated WSDL: ...ADBException: Unexpected subelement
(I'm still stuck on the exception. Any ideas?)
Some additional info, since I'm really stuck on this point:
- I have 2 different classes (annotated with @Webservice) which expose a
few public methods (annotated with @Webmethod).
- I have added separate .wsdl files (same name as the @Webservice
classes) in META-INF
- The param "useOriginalwsdl" has no influence at all. If the the
.wsdl's are in META-INF, they're used. Setting to false (or removing it)
doesn't do anything.
- The WSDL's I put in META-INF are identical to what ?wsdl generates. No
modifications.
- When the .aar is deployed with the supplied WSDL's and I call the
?wsdl, the output WSDL XML is about the same as the original generated
WSDL (some order differences, nothing major it seems).
What am i doing wrong? Why am I getting the ADBException?
/Exception in thread "main" org.apache.axis2.AxisFault:
org.apache.axis2.databinding.ADBException: Unexpected subelement
debugMessage/
/at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)/
/at
nl.organization.webservices.Ws_UsersStub.fromOM(Ws_UsersStub.java:19397)/
/at
nl.organization.webservices.Ws_UsersStub.removeUser(Ws_UsersStub.java:1384)/
/at test.Client.reqRemoveUser(Client.java:65)/
/at test.Client.main(Client.java:14)/
/at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)/
/at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)/
/at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)/
/at java.lang.reflect.Method.invoke(Method.java:597)/
/at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)/
Henjo van Rees wrote:
Hi,
I've been developing an Axis based Webservice for some time now.
Right now I'm at the point where the basics function alright and that
I am starting on improving stuff like security.
One aspect of that is stop using the generated WSDL and supply my
own. Because I'm far from a WS guru, I decided to use the generated
WSDL and use that as a basis for improvement.
What I've done is the following:
- Save generated WSDL with the same name as the service name
(name.wsdl) and put that in the .aar (META-INF dir)
- Set the parameter "useOriginalwsdl" to true for that service
(services.xml)
- Keep the classes exactly the same, no other changes.
- Deploy the .aar, restart Tomcat.
- Verify webservice+operations using the listServices servlet (they
are listed exactly as they should)
So Axis2 accepts the .aar.
However, now my webservices test client does not function anymore
with this modification. This probably has to do with namespaces, but
I wonder how I should get it working.
What must I change in my services.xml to get it working with my own WSDL?
*The java classes are in the root package
/nl.organization.webservices/.*
*** services.xml snippet:*
WebServices - User Management
locked="true">nl.organization.webservices.Ws_Users
true
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
*** Generated WSDL snippet*:
http://schemas.xmlsoap.org/wsdl/";
xmlns:ns1="http://org.apache.axis2/xsd";
xmlns:ns="http://webservices.organization.nl";
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl";
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
xmlns:ax21="http://webservices.organization.nl/xsd";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
targetNamespace="http://webservices.organization.nl";>
Ws_Users
xmlns:ax22="http://webservices.organization.nl/xsd";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://webservices.organization.nl";>
namespace="http://webservices.organization.nl/xsd"/>
nillable="true" type="xs:string"/>
nillable="true" type="xs:string"/>
nillable="true" type="ax22:WsResponse"/>
elementFormDefault="qualified"
targetNamespace="http://webservices.organization.nl/xsd";>
nillable="true" type="xs:string"/>
type="xs:int
Re: Generated WSDL HTTPS Port not 8443
On Thu, Nov 5, 2009 at 20:49, v2cg4ss wrote: > > Thank you for the reply, is this being resolved soon. It is implemented, but the issue is not closed yet because the documentation is not up to date with the changes. > I have a client using > .NET and they are generating their client code from the WSDL. The > programmer claims that they cannot change the endpoint in the .NET code like > I can with java. > > MyWSStub stub = new MyWSStub(ctx, > "https://localhost:8443/axis2/services/MyWS";); > > Scott > > > Andreas Veithen-2 wrote: >> >> Generating the correct endpoint URIs for https is something that >> doesn't work properly in the available Axis2 releases. See AXIS2-4465 >> and related issues. >> >> Andreas >> >> > > -- > View this message in context: > http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26219924.html > Sent from the Axis - User mailing list archive at Nabble.com. > >
Re: WSDL Parser java
i found that there's already smt done in java library: javax.wsdl.xml.WSDLReader On Sat, Nov 7, 2009 at 16:31, Sagara Gunathunga wrote: > If you plan to write a class from the scratch to read the WSDL and get > those details you can use JWSDL API [1] with WSDL4J [2]. > > > [1] - wsdl4j.sourceforge.net/downloads/JSR110_proposed_final_draft.pdf > [2] - http://sourceforge.net/projects/wsdl4j/ > > Thanks, > > On Sat, Nov 7, 2009 at 10:10 AM, Stefano Tranquillini > wrote: > > i'm reading and trying the WSDL2AxisServiceBuilder but i'm not able to > know > > the operation name and type. > > > > there's no class that read the wsdl and has method that returns > operations > > name operations parameters and so on? > > > > thanks > > > > On Fri, Nov 6, 2009 at 18:46, Stefano Tranquillini > > wrote: > >> > >> thanks, i take a look. > >> but, i can use this class and doing what i want or the license of apache > >> blocks me for somethings i.e. use for business applications? > >> > >> On Fri, Nov 6, 2009 at 18:20, Deepal jayasinghe > wrote: > >>> > >>> Is this about Axis2 or Axis1? if it is in Axis2 look at > WSDL2AxisService > >>> Builder class. > >>> > >>> Thanks, > >>> Deepal > >>> > Hi all. > >>> > in the code of the project there's a class that parse the wsdl? which > >>> > one? > >>> > i need to know all the things inside the wsdl, in particular i'm > >>> > interested in the name of the operations and smt else. > >>> > thanks in advance. > >>> > > >>> > > >>> > -- > >>> > Stefano > >>> > >>> > >>> -- > >>> Thank you! > >>> > >>> > >>> http://blogs.deepal.org > >>> http://deepal.org > >>> > >> > >> > >> > >> -- > >> Stefano > > > > > > > > -- > > Stefano > > > > > > -- > Sagara Gunathunga > > Blog - http://ssagara.blogspot.com > Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/> > -- Stefano
Re: WSDL Parser java
If you plan to write a class from the scratch to read the WSDL and get those details you can use JWSDL API [1] with WSDL4J [2]. [1] - wsdl4j.sourceforge.net/downloads/JSR110_proposed_final_draft.pdf [2] - http://sourceforge.net/projects/wsdl4j/ Thanks, On Sat, Nov 7, 2009 at 10:10 AM, Stefano Tranquillini wrote: > i'm reading and trying the WSDL2AxisServiceBuilder but i'm not able to know > the operation name and type. > > there's no class that read the wsdl and has method that returns operations > name operations parameters and so on? > > thanks > > On Fri, Nov 6, 2009 at 18:46, Stefano Tranquillini > wrote: >> >> thanks, i take a look. >> but, i can use this class and doing what i want or the license of apache >> blocks me for somethings i.e. use for business applications? >> >> On Fri, Nov 6, 2009 at 18:20, Deepal jayasinghe wrote: >>> >>> Is this about Axis2 or Axis1? if it is in Axis2 look at WSDL2AxisService >>> Builder class. >>> >>> Thanks, >>> Deepal >>> > Hi all. >>> > in the code of the project there's a class that parse the wsdl? which >>> > one? >>> > i need to know all the things inside the wsdl, in particular i'm >>> > interested in the name of the operations and smt else. >>> > thanks in advance. >>> > >>> > >>> > -- >>> > Stefano >>> >>> >>> -- >>> Thank you! >>> >>> >>> http://blogs.deepal.org >>> http://deepal.org >>> >> >> >> >> -- >> Stefano > > > > -- > Stefano > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/
Re: WSDL Parser java
i'm reading and trying the WSDL2AxisServiceBuilder but i'm not able to know the operation name and type. there's no class that read the wsdl and has method that returns operations name operations parameters and so on? thanks On Fri, Nov 6, 2009 at 18:46, Stefano Tranquillini < stefano.tranquill...@gmail.com> wrote: > thanks, i take a look. > but, i can use this class and doing what i want or the license of apache > blocks me for somethings i.e. use for business applications? > > > On Fri, Nov 6, 2009 at 18:20, Deepal jayasinghe wrote: > >> Is this about Axis2 or Axis1? if it is in Axis2 look at WSDL2AxisService >> Builder class. >> >> Thanks, >> Deepal >> > Hi all. >> > in the code of the project there's a class that parse the wsdl? which >> one? >> > i need to know all the things inside the wsdl, in particular i'm >> > interested in the name of the operations and smt else. >> > thanks in advance. >> > >> > >> > -- >> > Stefano >> >> >> -- >> Thank you! >> >> >> http://blogs.deepal.org >> http://deepal.org >> >> > > > -- > Stefano > -- Stefano
[Axis2] Setting nillable = false in WSDL
Hi All, I am using Axis2 1.3 and jdk 1.5 The WSDL file generated by Axis sets all 'nillable' attribute for all elements to true. Is there any way I can get the 'nillable' property to true or false in a declarative fashion.. I try with the annotation @XmlElement(nillable = false required=true) but it doesn't work :( Thanks, David _ Nouveau ! Tout Windows débarque dans votre téléphone. Voir les Windows phone http://clk.atdmt.com/FRM/go/175819071/direct/01/
RE: Generated WSDL HTTPS Port not 8443
There should be a "setEndpoint" method generated in the .NET code. That will allow them to programmatically set the endpoint. -Original Message- From: v2cg4ss [mailto:ssel...@datamentors.com] Sent: Thursday, November 05, 2009 2:49 PM To: axis-user@ws.apache.org Subject: Re: Generated WSDL HTTPS Port not 8443 Thank you for the reply, is this being resolved soon. I have a client using .NET and they are generating their client code from the WSDL. The programmer claims that they cannot change the endpoint in the .NET code like I can with java. MyWSStub stub = new MyWSStub(ctx, "https://localhost:8443/axis2/services/MyWS";); Scott Andreas Veithen-2 wrote: > > Generating the correct endpoint URIs for https is something that > doesn't work properly in the available Axis2 releases. See AXIS2-4465 > and related issues. > > Andreas > > -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p2621 9924.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: Generated WSDL HTTPS Port not 8443
Thank you for the reply, is this being resolved soon. I have a client using .NET and they are generating their client code from the WSDL. The programmer claims that they cannot change the endpoint in the .NET code like I can with java. MyWSStub stub = new MyWSStub(ctx, "https://localhost:8443/axis2/services/MyWS";); Scott Andreas Veithen-2 wrote: > > Generating the correct endpoint URIs for https is something that > doesn't work properly in the available Axis2 releases. See AXIS2-4465 > and related issues. > > Andreas > > -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26219924.html Sent from the Axis - User mailing list archive at Nabble.com.
PasswordDigest not being displayed in WS-Policy in generated WSDL - bug or not bug?
Hi, I've set up a webservice with Rampart and WS-Policy to use Password Digest for authentication. However, I've noticed that when the WSDL is generated by Axis, the WS-Policy doesn't actually make any mention of this. Is this how it's supposed to work? The Ws Policy shown in the WSDL is this: http://schemas.xmlsoap.org/ws/2004/09/policy"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; wsu:Id="UsernameToken"> http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";> http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient"/> This portion that was in the services.xml seems to have been left out: Does this indicate a problem with Rampart passing on the policy information to Axis2 (or Axis2 when creating the WSDL), or is everything working as it should? Is WS-Policy in a WSDL also meant to indicate if Password Digest is used? If the idea is that WSDL represents a contract between clients and a service, then shouldn't the usage of Password digest be more explicit? thanks, Ellecer
beanMapping, typeMapping in Axis 1 (1.4) in server-config.wsdd does not generate complexType in wsdl
I am using Axis1 (1.4) to generate complex type in wsdl (e.g. my.wsdl) from
server-config.wsdd. I do not think that the complex type is not correctly
generated. This may be because my server-config.wsdd is not correct
My server-config.wsdd is:
[code]
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
http://xml.apache.org/axis/wsdd/
http://schemas.xmlsoap.org/soap/encoding/"/>
[/code]
All the methods in MySvc are exposed by web service.
MyBean is a complex bean, that is passed as argument in one of the methods
of MySvc.
MyBean.java only has two attributes and the code is:
[code]
public class MyBean{
int age;
String name;
public MyBean(){
}
public MyBean(int age, String name){
// code
}
// getter and setter for age and name
}
[/code]
MySvc.java is:
[code]
public MySvc implements IMySvc{
public MyBean getBean(){
return new MyBean(1, "a");
}
}
[/code]
The wsdl that gets generated is:
[code]
[/code]
It does not show the attributes of MyBean under sequence.
What am I missing in server-config.wsdd so that the wsdl gets generated
successfully? An attempt to generation of client from the wsdl succeds, but
the client code cannot find the correct complex type.
--
View this message in context:
http://www.nabble.com/beanMapping%2C-typeMapping-in-Axis-1-%281.4%29-in-server-config.wsdd-does-not-generate-complexType-in-wsdl-tp26121937p26121937.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: use supplied WSDL instead of generated WSDL: ...ADBException: Unexpected subelement
Amila Suriarachchi wrote:
On Thu, Oct 29, 2009 at 2:08 PM, H <mailto:he...@glasch.nl>> wrote:
Some additional info, since I'm really stuck on this point:
- I have 2 different classes (annotated with @Webservice) which
expose a few public methods (annotated with @Webmethod).
- I have added separate .wsdl files (same name as the @Webservice
classes) in META-INF
- The param "useOriginalwsdl" has no influence at all. If the the
.wsdl's are in META-INF, they're used. Setting to false (or
removing it) doesn't do anything.
- The WSDL's I put in META-INF are identical to what ?wsdl
generates. No modifications.
- When the .aar is deployed with the supplied WSDL's and I call
the ?wsdl, the output WSDL XML is about the same as the original
generated WSDL (some order differences, nothing major it seems).
What am i doing wrong? Why am I getting the ADBException?
check whether there is a difference between new and old wsdl files.
The new and old wsdl files are nearly the same. The only difference is
the order of the xml elements, which should be harmless, right?
After all, it's XML.
thanks,
Amila.
/Exception in thread "main" org.apache.axis2.AxisFault:
org.apache.axis2.databinding.ADBException: Unexpected subelement
debugMessage
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
nl.organization.webservices.Ws_UsersStub.fromOM(Ws_UsersStub.java:19397)
at
nl.organization.webservices.Ws_UsersStub.removeUser(Ws_UsersStub.java:1384)
at test.Client.reqRemoveUser(Client.java:65)
at test.Client.main(Client.java:14)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)/
Henjo van Rees wrote:
Hi,
I've been developing an Axis based Webservice for some time now.
Right now I'm at the point where the basics function alright and
that I am starting on improving stuff like security.
One aspect of that is stop using the generated WSDL and supply my
own. Because I'm far from a WS guru, I decided to use the
generated WSDL and use that as a basis for improvement.
What I've done is the following:
- Save generated WSDL with the same name as the service name
(name.wsdl) and put that in the .aar (META-INF dir)
- Set the parameter "useOriginalwsdl" to true for that service
(services.xml)
- Keep the classes exactly the same, no other changes.
- Deploy the .aar, restart Tomcat.
- Verify webservice+operations using the listServices servlet
(they are listed exactly as they should)
So Axis2 accepts the .aar.
However, now my webservices test client does not function anymore
with this modification. This probably has to do with namespaces,
but I wonder how I should get it working.
What must I change in my services.xml to get it working with my
own WSDL?
*The java classes are in the root package
/nl.organization.webservices/.*
*** services.xml snippet:*
WebServices - User Management
nl.organization.webservices.Ws_Users
true
*** Generated WSDL snippet*:
http://schemas.xmlsoap.org/wsdl/";
<http://schemas.xmlsoap.org/wsdl/>
xmlns:ns1="http://org.apache.axis2/xsd";
<http://org.apache.axis2/xsd>
xmlns:ns="http://webservices.organization.nl";
<http://webservices.organization.nl>
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl";
<http://www.w3.org/2006/05/addressing/wsdl>
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
<http://schemas.xmlsoap.org/wsdl/http/>
xmlns:ax21="http://webservices.organization.nl/xsd";
<http://webservices.organization.nl/xsd>
xmlns:xs="http://www.w3.org/2001/XMLSchema";
<http://www.w3.org/2001/XMLSchema>
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
<http://schemas.xmlsoap.org/wsdl/mime/>
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
<http://schemas.xmlsoap.org/wsdl/soap/>
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
<http://schemas.xmlsoap.org/wsdl/soap12/>
targetNamespace="http://webservices.organization.nl";
<http://webservices.organization.nl>>
Ws_Users
http://webservices.organization.nl/xsd&q
Re: use supplied WSDL instead of generated WSDL: ...ADBException: Unexpected subelement
On Thu, Oct 29, 2009 at 2:08 PM, H wrote: > Some additional info, since I'm really stuck on this point: > > - I have 2 different classes (annotated with @Webservice) which expose a > few public methods (annotated with @Webmethod). > > - I have added separate .wsdl files (same name as the @Webservice classes) > in META-INF > > - The param "useOriginalwsdl" has no influence at all. If the the .wsdl's > are in META-INF, they're used. Setting to false (or removing it) doesn't do > anything. > > - The WSDL's I put in META-INF are identical to what ?wsdl generates. No > modifications. > > - When the .aar is deployed with the supplied WSDL's and I call the ?wsdl, > the output WSDL XML is about the same as the original generated WSDL (some > order differences, nothing major it seems). > > What am i doing wrong? Why am I getting the ADBException? > check whether there is a difference between new and old wsdl files. thanks, Amila. > > > *Exception in thread "main" org.apache.axis2.AxisFault: > org.apache.axis2.databinding.ADBException: Unexpected subelement > debugMessage > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) > at > nl.organization.webservices.Ws_UsersStub.fromOM(Ws_UsersStub.java:19397) > at > nl.organization.webservices.Ws_UsersStub.removeUser(Ws_UsersStub.java:1384) > at test.Client.reqRemoveUser(Client.java:65) > at test.Client.main(Client.java:14) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) > * > > > Henjo van Rees wrote: > > Hi, > > I've been developing an Axis based Webservice for some time now. Right now > I'm at the point where the basics function alright and that I am starting on > improving stuff like security. > One aspect of that is stop using the generated WSDL and supply my own. > Because I'm far from a WS guru, I decided to use the generated WSDL and use > that as a basis for improvement. > > What I've done is the following: > - Save generated WSDL with the same name as the service name (name.wsdl) > and put that in the .aar (META-INF dir) > - Set the parameter "useOriginalwsdl" to true for that service > (services.xml) > - Keep the classes exactly the same, no other changes. > - Deploy the .aar, restart Tomcat. > - Verify webservice+operations using the listServices servlet (they are > listed exactly as they should) > > So Axis2 accepts the .aar. > > However, now my webservices test client does not function anymore with this > modification. This probably has to do with namespaces, but I wonder how I > should get it working. > What must I change in my services.xml to get it working with my own WSDL? > > *The java classes are in the root package nl.organization.webservices > .* > > *** services.xml snippet:* > > > WebServices - User Management > locked="true">nl.organization.webservices.Ws_Users > true > > class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> > > > > > *** Generated WSDL snippet*: > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";<http://schemas.xmlsoap.org/wsdl/>xmlns:ns1= > "http://org.apache.axis2/xsd"; <http://org.apache.axis2/xsd> xmlns:ns= > "http://webservices.organization.nl"; > <http://webservices.organization.nl>xmlns:wsaw= > "http://www.w3.org/2006/05/addressing/wsdl";<http://www.w3.org/2006/05/addressing/wsdl>xmlns:http= > "http://schemas.xmlsoap.org/wsdl/http/";<http://schemas.xmlsoap.org/wsdl/http/>xmlns:ax21= > "http://webservices.organization.nl/xsd";<http://webservices.organization.nl/xsd>xmlns:xs= > "http://www.w3.org/2001/XMLSchema"; > <http://www.w3.org/2001/XMLSchema>xmlns:mime= > "http://schemas.xmlsoap.org/wsdl/mime/";<http://schemas.xmlsoap.org/wsdl/mime/>xmlns:soap= > "http://schemas.xmlsoap.org/wsdl/soap/";<http://schemas.xmlsoap.org/wsdl/soap/>xmlns:soap12= > "http://schemas.xmlsoap.org/wsdl/soap12/";<http://schemas.xmlsoap.org/wsdl/soap12/>targetNamespace= > "http://webservices.organization.nl"; <http://webservices.organization.
Re: use supplied WSDL instead of generated WSDL: ...ADBException: Unexpected subelement
Some additional info, since I'm really stuck on this point:
- I have 2 different classes (annotated with @Webservice) which expose a
few public methods (annotated with @Webmethod).
- I have added separate .wsdl files (same name as the @Webservice
classes) in META-INF
- The param "useOriginalwsdl" has no influence at all. If the the
.wsdl's are in META-INF, they're used. Setting to false (or removing it)
doesn't do anything.
- The WSDL's I put in META-INF are identical to what ?wsdl generates. No
modifications.
- When the .aar is deployed with the supplied WSDL's and I call the
?wsdl, the output WSDL XML is about the same as the original generated
WSDL (some order differences, nothing major it seems).
What am i doing wrong? Why am I getting the ADBException?
/Exception in thread "main" org.apache.axis2.AxisFault:
org.apache.axis2.databinding.ADBException: Unexpected subelement
debugMessage
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
nl.organization.webservices.Ws_UsersStub.fromOM(Ws_UsersStub.java:19397)
at
nl.organization.webservices.Ws_UsersStub.removeUser(Ws_UsersStub.java:1384)
at test.Client.reqRemoveUser(Client.java:65)
at test.Client.main(Client.java:14)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)/
Henjo van Rees wrote:
Hi,
I've been developing an Axis based Webservice for some time now. Right
now I'm at the point where the basics function alright and that I am
starting on improving stuff like security.
One aspect of that is stop using the generated WSDL and supply my own.
Because I'm far from a WS guru, I decided to use the generated WSDL
and use that as a basis for improvement.
What I've done is the following:
- Save generated WSDL with the same name as the service name
(name.wsdl) and put that in the .aar (META-INF dir)
- Set the parameter "useOriginalwsdl" to true for that service
(services.xml)
- Keep the classes exactly the same, no other changes.
- Deploy the .aar, restart Tomcat.
- Verify webservice+operations using the listServices servlet (they
are listed exactly as they should)
So Axis2 accepts the .aar.
However, now my webservices test client does not function anymore with
this modification. This probably has to do with namespaces, but I
wonder how I should get it working.
What must I change in my services.xml to get it working with my own WSDL?
*The java classes are in the root package
/nl.organization.webservices/.*
*** services.xml snippet:*
WebServices - User Management
locked="true">nl.organization.webservices.Ws_Users
true
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
*** Generated WSDL snippet*:
http://schemas.xmlsoap.org/wsdl/";
xmlns:ns1="http://org.apache.axis2/xsd";
xmlns:ns="http://webservices.organization.nl";
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl";
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
xmlns:ax21="http://webservices.organization.nl/xsd";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
targetNamespace="http://webservices.organization.nl";>
Ws_Users
http://webservices.organization.nl/xsd";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://webservices.organization.nl";>
namespace="http://webservices.organization.nl/xsd"/>
nillable="true" type="xs:string"/>
nillable="true" type="xs:string"/>
nillable="true" type="ax22:WsResponse"/>
elementFormDefault="qualified"
targetNamespace="http://webservices.organization.nl/xsd";>
nillable="true" type="xs:string"/>
type="xs:int"/>
nillable="true"
use supplied WSDL instead of generated WSDL: ...ADBException: Unexpected subelement
Hi, I've been developing an Axis based Webservice for some time now. Right now I'm at the point where the basics function alright and that I am starting on improving stuff like security. One aspect of that is stop using the generated WSDL and supply my own. Because I'm far from a WS guru, I decided to use the generated WSDL and use that as a basis for improvement. What I've done is the following: - Save generated WSDL with the same name as the service name (name.wsdl) and put that in the .aar (META-INF dir) - Set the parameter "useOriginalwsdl" to true for that service (services.xml) - Keep the classes exactly the same, no other changes. - Deploy the .aar, restart Tomcat. - Verify webservice+operations using the listServices servlet (they are listed exactly as they should) So Axis2 accepts the .aar. However, now my webservices test client does not function anymore with this modification. This probably has to do with namespaces, but I wonder how I should get it working. What must I change in my services.xml to get it working with my own WSDL? *The java classes are in the root package /nl.organization.webservices/.* *** services.xml snippet:* WebServices - User Management locked="true">nl.organization.webservices.Ws_Users true class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> *** Generated WSDL snippet*: http://schemas.xmlsoap.org/wsdl/"; xmlns:ns1="http://org.apache.axis2/xsd"; xmlns:ns="http://webservices.organization.nl"; xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"; xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; xmlns:ax21="http://webservices.organization.nl/xsd"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; targetNamespace="http://webservices.organization.nl";> Ws_Users http://webservices.organization.nl/xsd"; attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://webservices.organization.nl";> http://webservices.organization.nl/xsd"/> nillable="true" type="xs:string"/> nillable="true" type="xs:string"/> nillable="true" type="ax22:WsResponse"/> elementFormDefault="qualified" targetNamespace="http://webservices.organization.nl/xsd";> nillable="true" type="xs:string"/> type="xs:int"/> nillable="true" type="xs:string"/> *** EXCEPTION WHEN RUNNING WS CLIENT:* (I've generated the stub classes with wsdl2java) Exception in thread "main" org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement debugMessage at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at nl.organization.webservices.Ws_UsersStub.fromOM(Ws_UsersStub.java:19397) at nl.organization.webservices.Ws_UsersStub.removeUser(Ws_UsersStub.java:1384) at test.Client.reqRemoveUser(Client.java:65) at test.Client.main(Client.java:14) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) Any help will be welcome! Thanks!
Re: Endpoint in wsdl using wrong ip address
On Wed, Oct 21, 2009 at 6:15 PM, Krystian Szczesny < krystian.szcze...@intecbilling.com> wrote: > Hi, > > > > I’ve changed my service.xml file to have: > > true > > true > you can keep the correct host name in wsdl file and set above parameter to false. thanks, Amila. > > > I expected to get a WSDL with the same endpoint address I can see using > List Services page. > > On the List Services page I get endpoint address with hostname but when I > load the WSDL I can see IP address. > > Unfortunately this IP address points to a network interface which is not > accessible for me as the client. > > > > Could you please help me & point me where I could find more information > about how to make it use hostname rather than IP address or how to choose > the correct network interface? > > > > My setup: > > Axis2 1.5 > > Deployed war file on Jetty 6.1.11 > > HP-UX 11 > > > > Thanks, > > Krystian > > > > > > *-- * > > *KRYSTIAN SZCZESNY* > This e-mail and any attachments are confidential and may also be legally > privileged and/or copyright material of Intec Telecom Systems PLC (or its > affiliated companies). If you are not an intended or authorised recipient > of this e-mail or have received it in error, please delete it immediately > and notify the sender by e-mail. In such a case, reading, reproducing, > printing or further dissemination of this e-mail or its contents is > strictly > prohibited and may be unlawful. > Intec Telecom Systems PLC does not represent or warrant that an attachment > hereto is free from computer viruses or other defects. The opinions > expressed in this e-mail and any attachments may be those of the author and > > are not necessarily those of Intec Telecom Systems PLC. > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Endpoint in wsdl using wrong ip address
Hi, I've changed my service.xml file to have: true true I expected to get a WSDL with the same endpoint address I can see using List Services page. On the List Services page I get endpoint address with hostname but when I load the WSDL I can see IP address. Unfortunately this IP address points to a network interface which is not accessible for me as the client. Could you please help me & point me where I could find more information about how to make it use hostname rather than IP address or how to choose the correct network interface? My setup: Axis2 1.5 Deployed war file on Jetty 6.1.11 HP-UX 11 Thanks, Krystian -- KRYSTIAN SZCZESNY This e-mail and any attachments are confidential and may also be legally privileged and/or copyright material of Intec Telecom Systems PLC (or its affiliated companies). If you are not an intended or authorised recipient of this e-mail or have received it in error, please delete it immediately and notify the sender by e-mail. In such a case, reading, reproducing, printing or further dissemination of this e-mail or its contents is strictly prohibited and may be unlawful. Intec Telecom Systems PLC does not represent or warrant that an attachment hereto is free from computer viruses or other defects. The opinions expressed in this e-mail and any attachments may be those of the author and are not necessarily those of Intec Telecom Systems PLC.
generating wsdl for complex return types
I was able to get a simple web service running w/ Axis2/C using the approach
shown here<http://wso2.org/library/3534>, which creates a WSDL file from a Java
interface using the Axis2 java2wsdl and then uses the WSDL file to create the C
skeleton and stubs using wsdl2c. So far so good. Now I'd like to create a
more sophisticated interface. For example, what if I need to return multiple
values, or a list of objects?
For example, let's say I have some data that represents a user (e.g. name,
password, id, etc.) and my service has two methods getUser and getActiveUsers.
The first would return the data for the user w/ the given id and the second
would return the data for all users that are currently logged onto the system.
I'd expect the SOAP responses to be something like the following:
fred
...
< getActiveUsersResponse>
fred
...
barney
...
How do I write the Java interface to produce such a result w/ java2wsdl? I
would have hoped something like the following would have done it, but that WSDL
generated seems like it wants to pass the object reference instead. Any help
would be greatly appreciated.
class User {
string name;
...
}
interface MyInterface {
public User getUser(int id);
public User [] getActiveUsers();
}
--
Doug Price
Research Director | Presagis
T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399
DISCLAIMER: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and/or proprietary information. Do
not read, copy, or disseminate this message unless you are the addressee. Any
unauthorized review, use, disclosure or distribution is strictly prohibited. If
you have received this message in error, please contact the sender by reply
e-mail and delete the original and any copies from your system.
--
Doug Price
Research Director | Presagis
T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399
DISCLAIMER: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and/or proprietary information. Do
not read, copy, or disseminate this message unless you are the addressee. Any
unauthorized review, use, disclosure or distribution is strictly prohibited. If
you have received this message in error, please contact the sender by reply
e-mail and delete the original and any copies from your system.
RE: wsdl2java issue when parsing wsdl that uses empty namespaces
Hi Sean, You could change PhoneType to string You lose the restriction on the possible values, but at least the SOAP agent will work. Your application that calls the Axis generated classes could handle the phone type value check. You are using the 22 April 2006 version of Axis 1.4, you could look at using a later over-night build. I have used 19 November 2006 Axis 1.4 for several years. http://people.apache.org/dist/axis/nightly/ <http://people.apache.org/dist/axis/nightly/> axis-bin-1_4.zip 19-Nov-2006 02:33 11M -Original Message- From: Sean O'Leary [mailto:razorho...@gmail.com] Sent: Friday, 16 October 2009 5:00 AM To: axis-user@ws.apache.org Subject: wsdl2java issue when parsing wsdl that uses empty namespaces Hi everyone, Using: Axis version 1.4 (4/22/2006) I'm using wsdl2java to compile a wsdl for a service that one of my customers has provided. Everything is fine except for they have one type that they have declared in a separate schema in the wsdl with no targetNamespace and then they refer to that type from another schema without putting anything in for the namespace prefix. This seems to be "valid" wsdl (using no namespace) but wsdl2java throws the following exception: java.io.IOException: Type PhoneType is referenced but not defined. at org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol Table.java:665) at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545 ) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav a:518) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav a:495) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) at java.lang.Thread.run(Unknown Source) Here's the offending WSDL snippet: http://schemas.xmlsoap.org/wsdl/soap/ <http://schemas.xmlsoap.org/wsdl/soap/> " xmlns:tm=" http://microsoft.com/wsdl/mime/textMatching/ <http://microsoft.com/wsdl/mime/textMatching/> " xmlns:soapenc=" http://schemas.xmlsoap.org/soap/encoding/ <http://schemas.xmlsoap.org/soap/encoding/> " xmlns:mime=" http://schemas.xmlsoap.org/wsdl/mime/ <http://schemas.xmlsoap.org/wsdl/mime/> " xmlns:tns=" http://services.xyzcompany.com <http://services.xyzcompany.com> " xmlns:s=" http://www.w3.org/2001/XMLSchema <http://www.w3.org/2001/XMLSchema> " xmlns:soap12=" http://schemas.xmlsoap.org/wsdl/soap12/ <http://schemas.xmlsoap.org/wsdl/soap12/> " xmlns:http=" http://schemas.xmlsoap.org/wsdl/http/ <http://schemas.xmlsoap.org/wsdl/http/> " targetNamespace=" http://services.xyzcompany.com <http://services.xyzcompany.com> " xmlns:wsdl=" http://schemas.xmlsoap.org/wsdl/ <http://schemas.xmlsoap.org/wsdl/> "> http://services.xyzcompany.com <http://services.xyzcompany.com> "> If I add targetNamespace=" http://services.xyzcompany.com <http://services.xyzcompany.com> " to the 2nd schema and then prefix the type="PhoneType" so it is type="tns:PhoneType", wsdl2java is able to compile the wsdl. Then the problem is of course as soon as I use the generated code to connect to the service it errors out as axis complains about the same issue with the service's wsdl. Any help you can provide is very much appreciated. Thanks! Sean
wsdl2java issue when parsing wsdl that uses empty namespaces
Hi everyone, Using: Axis version 1.4 (4/22/2006) I'm using wsdl2java to compile a wsdl for a service that one of my customers has provided. Everything is fine except for they have one type that they have declared in a separate schema in the wsdl with no targetNamespace and then they refer to that type from another schema without putting anything in for the namespace prefix. This seems to be "valid" wsdl (using no namespace) but wsdl2java throws the following exception: java.io.IOException: Type PhoneType is referenced but not defined. at org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol Table.java:665) at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545 ) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav a:518) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav a:495) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) at java.lang.Thread.run(Unknown Source) Here's the offending WSDL snippet: http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"; xmlns:soapenc=" http://schemas.xmlsoap.org/soap/encoding/"; xmlns:mime=" http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:tns=" http://services.xyzcompany.com"; xmlns:s="http://www.w3.org/2001/XMLSchema"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:http=" http://schemas.xmlsoap.org/wsdl/http/"; targetNamespace=" http://services.xyzcompany.com"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/ "> http://services.xyzcompany.com";> If I add targetNamespace="http://services.xyzcompany.com"; to the 2nd schema and then prefix the type="PhoneType" so it is type="tns:PhoneType", wsdl2java is able to compile the wsdl. Then the problem is of course as soon as I use the generated code to connect to the service it errors out as axis complains about the same issue with the service's wsdl. Any help you can provide is very much appreciated. Thanks! Sean
Re: processing wsdl
Hi, > The wsdl URL will be given as input from an UI, and after processing the > wsdl, the UI has to display the list of messages and fields under each > message. The fields of each message should be mapped to a position in a flat > string. > > I want to know how would i process the wsdl file in order to get the > individual messages and corresponding fields. > If it is a WSDL 1.1 document you could use WSDL4J [1] for this. Also look at JWSDL API [2] HTH. [1] - http://sourceforge.net/projects/wsdl4j/ [2] - http://wsdl4j.sourceforge.net/downloads/JSR110_proposed_final_draft.pdf Thanks, -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/
processing wsdl
Hi I am looking for implementing the following requirement using axis2. The wsdl URL will be given as input from an UI, and after processing the wsdl, the UI has to display the list of messages and fields under each message. The fields of each message should be mapped to a position in a flat string. I want to know how would i process the wsdl file in order to get the individual messages and corresponding fields. Regards, Aml
Re: Disable wsdl url
Hi, Instead of disabling wsdl it is to put an empty wsdl. In the configuration file you can mention ur empty wsdl and then this wsdl will be displayed when users try to access wsdl from URL Thanks, Suresh Metla On Oct 8, 2009, at 5:09 AM, Darshana ® wrote: Thanks amila, I'll try it and see. On Thu, Oct 8, 2009 at 11:53 AM, Amila Suriarachchi > wrote: hi, if you have deployed axis2 as a web app, try to put a servlet filter or define some url pattern in the web.xml thanks, Amila On Wed, Oct 7, 2009 at 3:50 PM, Darshana ® wr ote: Hello, I want to disable people accessing the wsdl. Currently any one can access wsdl of the my axis2 project through ":9002/web/ services/Axis2WS?wsdl". I just want to restrict people accessing the wsdl, simply I want to disable the wsdl url. But I couldnt find a way to do this, it'll be a great help if any body can give me a solution for this. Thanks -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: Disable wsdl url
Thanks amila, I'll try it and see. On Thu, Oct 8, 2009 at 11:53 AM, Amila Suriarachchi < amilasuriarach...@gmail.com> wrote: > hi, > > if you have deployed axis2 as a web app, try to put a servlet filter or > define some url pattern in the web.xml > > thanks, > Amila > > > > On Wed, Oct 7, 2009 at 3:50 PM, Darshana ® wrote: > >> Hello, >> >> I want to disable people accessing the wsdl. Currently any one can access >> wsdl of the my axis2 project through >> ":9002/web/services/Axis2WS?wsdl". >> >> I just want to restrict people accessing the wsdl, simply I want to >> disable the wsdl url. >> >> But I couldnt find a way to do this, it'll be a great help if any body can >> give me a solution for this. >> >> Thanks >> >> >> > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ >
Re: Disable wsdl url
hi, if you have deployed axis2 as a web app, try to put a servlet filter or define some url pattern in the web.xml thanks, Amila On Wed, Oct 7, 2009 at 3:50 PM, Darshana ® wrote: > Hello, > > I want to disable people accessing the wsdl. Currently any one can access > wsdl of the my axis2 project through > ":9002/web/services/Axis2WS?wsdl". > > I just want to restrict people accessing the wsdl, simply I want to disable > the wsdl url. > > But I couldnt find a way to do this, it'll be a great help if any body can > give me a solution for this. > > Thanks > > > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Disable wsdl url
Hello, I want to disable people accessing the wsdl. Currently any one can access wsdl of the my axis2 project through ":9002/web/services/Axis2WS?wsdl". I just want to restrict people accessing the wsdl, simply I want to disable the wsdl url. But I couldnt find a way to do this, it'll be a great help if any body can give me a solution for this. Thanks
RE: axis wsdl not working with axis2
Hello
can some one help about this? Could someone generate a service with axis
that takes a string and returns a structure of
Class retVal{
String cod
String err
String num
}
and try to create a client with axis2?
Many thanks
Best regards
Il giorno ven, 02/10/2009 alle 16.28 +0200, Bartolomeo Nicolotti ha
scritto:
> Hello,
>
> I don't think that it's an axis2 problem, as I've said
>
> and also with doc-literal, doc-wrapped, rpc-encoded servers. We've tried
> also with ASP.net and we got the same behaviour.
>
> so also ASP.net seems to have the same problem with this wsdl.
>
> The problem seems the wsdl generated by axis(not2)
>
> Many thanks
>
> Best Regards
>
> Il giorno ven, 02/10/2009 alle 16.05 +0200, sch...@afrigis.co.za ha
> scritto:
> > I have the exact same issue. If you search on Google, you will find
> > some bug reports related to this. Not sure whether it has been fixed
> > as I am getting it with the latest 1.5 I believe version.
> >
> >
> >
> > --
> >
> > Kind Regards
> >
> > Schalk Neethling
> >
> >
> > From: Bartolomeo Nicolotti [mailto:bnicolo...@siapcn.it]
> > Sent: 02 October 2009 03:15 PM
> > To: axis-user@ws.apache.org
> > Cc: Marco Damilano; Livio Costamagna
> > Subject: axis wsdl not working with axis2
> >
> >
> >
> >
> > Hello,
> >
> > we've generated a webservice and related attached wsdl with axis(not
> > 2) Eclipse 3.2.2 plugin.
> >
> > The web service is receiving one string and returning 3 strings, very
> > simple.
> >
> > Then we've used axis2 wsdl2java to generate the client with:
> >
> > wsdl2java.sh --noBuildXML -S ../../JavaSource -ns2p
> > http://Servizi.Pratica.APWebServices=com.siap.APPraticaXmlClient
> > -uri ./PraticaFromXml.wsdl
> >
> > The request is correctly received from the server side, the response
> > is received, as the sniffer report, by the client, but we got:
> >
> > Thu Oct 01 15:13:11 CEST
> > 2009:generaPraticaDaRes.percProvvigioneTotale20091001151201403-1
> > caught an exception: 24442574 org.a
> > pache.axis2.AxisFault
> > e.toString():org.apache.axis2.AxisFault:
> > org.apache.axis2.databinding.ADBException: Unexpected subelement
> > importaReturn,
> > e.getMessage():org.apache.axis2.databinding.ADBException: Unexpected
> > subelement importaReturn
> > org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
> > com.siap.APPraticaXmlClient.PraticaFromXmlServiceStub.fromOM(PraticaFromXmlServiceStub.java:2200)
> > com.siap.APPraticaXmlClient.PraticaFromXmlServiceStub.importa(PraticaFromXmlServiceStub.java:191)
> > com.siap.TPUtility.TPPraticaAtlanteUtil.generaPraticaDaSIAPDocumentable(TPPraticaAtlanteUtil.java:56)
> > com.siap.DPKWebServices.Util.DynPkgOTAServiceUtil.generaPraticaDaSIAPDocumentable(DynPkgOTAServiceUtil.java:1001)
> > com.siap.DPKWebServices.OTAMessages.WSMH_OTA_HotelRes_Literal.handleMessage(WSMH_OTA_HotelRes_Literal.java:166)
> > com.siap.DPKWebServices.OTAMessages.WSMD_SerialSimple.dispatchWebService_Message(WSMD_SerialSimple.java:31)
> > com.siap.DPKWebServices.Util.DynPkgOTAServiceDispacher.dispatchWebService_Message_internals(DynPkgOTAServiceDispacher.java:15
> > 3)
> > com.siap.DPKWebServices.Util.DynPkgOTAServiceDispacher.dispatchWebService_Message(DynPkgOTAServi
> >
> > Analogous messages with
> >
> > -d jaxbri
> > -d xmlbeans
> >
> > and also with doc-literal, doc-wrapped, rpc-encoded servers. We've
> > tried also with ASP.net and we got the same behaviour.
> >
> > The only client that worked was the one generated from the wsdl from
> > axis(not2) Eclipse 3.2.2 plugin.
> >
> > The problem seems that the response type
> >
> >
> >
> > is not recognized.
> >
> > Could someone have a look at the wsdl and tell us why?
> >
> >
> > Many thanks
> >
> > Best regards
> >
> >
> > --
> > Bartolomeo Nicolotti
> > SIAP s.r.l.
> > www.siapcn.it
> > v.S.Albano 13 12049
> > Trinità(CN) Italy
> > ph:+39 0172 652553
> > centralino: +39 0172 652511
> > fax: +39 0172 652519
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > AfriGIS e-mail facility may not be used for the distribution of chain
> > letters or offensive email. AfriGIS hereby distances itself from and
> > accepts no liability for the unauthorized use of its e-mail facility
> > or the sending of e-mail communication
Re: How to add explicit SOAP header in WSDL for generating SOAP message - Axis1.4
Dear All, I am facing the similar problem as posted in this post.I have done RND on google but could not find anything .Please advise. Thanks and Regards, Anita sh_santosh wrote: > > Dear All, > > I need to expose java web services. I am using Axis1.4, Java 1.5 and > Tomcat 5.0 for exposing services. > > SOAP request and SOAP response have 'authentication' tag in SOAP header. > > SOAP Request - > > > > >UserName >Password > > > >Version="1.0"> > ... > > > > -- > SOAP response - > > > > > XXUserName > XXPassword > 2007B > > > > Target="Production" > TimeStamp="2009-03-24T20:26:37.058+01:00" Version="1.006"> > > > > > > By seeing the SOAP message structure, we have decided to add SOAP header > explicitly in WSDL. > We are NOT able to differentiate between SOAP request and SOAP response > 'authentication' tag in WSDL. > > We have attempted to solve the above problem by creating 2 different type > of WSDL. > Please have look into these wsdl. > > WSDL-1 : > > http://test.com"; > xmlns:tns="http://test.com"; > xmlns="http://schemas.xmlsoap.org/wsdl/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > http://test.com";> > > > > > maxOccurs="1" name="userid" type="xsd:string"/> > maxOccurs="1" name="password" type="xsd:string"/> > > > > > > > > > maxOccurs="1" name="userid" type="xsd:string"/> > maxOccurs="1" name="password" type="xsd:string"/> > maxOccurs="1" name="payloadVersion" type="xs:string"/> > > > > > > > > > > > > > > > > > > > > > > > > transport="http://schemas.xmlsoap.org/soap/http"; /> > > > > > > > > > > > > > > > location="http://localhost:8080/hello-service/hello-service"/> > > > > > WSDL-2 : > > http://test.com"; > xmlns:tns="http://test.com"; > xmlns="http://schemas.xmlsoap.org/wsdl/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > http://test.com";> > > > > > maxOccurs="1" name="userid" type="xsd:string"/> > maxOccurs="1" name="password" type="xsd:string"/> > > > > > > > > >
Re: Does Order of attributes in SOAP message have to match WSDL .
On Mon, Oct 5, 2009 at 1:08 PM, Julianne Hansen wrote: > > > Hi All. > > > > Just after some info on whether the order of attributes in a Webservice > Request / Response has to match the order of attributes defined in the WSDL. > > > > I am using Apache Axis 2, but am currently having some issues with a > Webservice that I am connecting to. > > > > The WSDL states that the definition of an attribute is as follows: > > > > > > > *-*<http://msdwin50.dev.mincom.com:9083/eai-composite-ejb/services/WRComp/wsdl/WRComp.wsdl> > > > > > > > > > > > > > > > > > > > Yet the SOAP Response is returning the above attributes in the following > order : > > > > > CUSTOMER DOES NOT EXIST IN THIS > DISTRICT > 1896 > CustomerNo > -1 > 0 > > > > > When trying to unpack the Webservice Response, Apache Axis is throwing the > following error : > > > > > > org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: > Unexpected subelement message > > > > > > Should Apache Axis be able to handle the attributes being in a different > order, or is the webservice incorrect because its not conforming to the > WSDL. > this web service does not send the correct response. since the order has given as the sequence the attributes should follow that order. thanks, Amila. > > > If the later is true – is it stated in a wc3 spec anywhere that webservices > should return attributes in the correct order? > > > > Thanks > > Julie > > -- > This transmission is for the intended addressee only and is confidential > information. If you have received this transmission in error, please notify > the sender and delete the transmission. The contents of this e-mail are the > opinion of the writer only and are not endorsed by the Mincom Group of > companies unless expressly stated otherwise. > > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: wsdl2java and wsdl problem
Dear Anne,
I need to expose java web services. I am using Axis1.4, Java 1.5 and Tomcat
5.0 for exposing services.
SOAP request and SOAP response have 'authentication' tag in SOAP header.
SOAP Request -
UserName
Password
...
--
SOAP response -
XXUserName
XXPassword
2007B
By seeing the SOAP message structure, we have decided to add SOAP header
explicitly in WSDL.
We are NOT able to differentiate between SOAP request and SOAP response
'authentication' tag in WSDL.
We have attempted to solve the above problem by creating 2 different type of
WSDL.
Please have look into these wsdl.
WSDL-1 :
http://test.com";
xmlns:tns="http://test.com";
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
http://test.com";>
http://schemas.xmlsoap.org/soap/http"; />
http://localhost:8080/hello-service/hello-service"/>
WSDL-2 :
http://test.com";
xmlns:tns="http://test.com";
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
http://test.com";>
http://schemas.xmlsoap.org/soap/http"; />
http://localhost:8080/hello-service/hello-service"/>
Please advise.
Regards,
Santosh
Anne Thomas Manes wrote:
>
> The type declaration is valid.
>
> indicates that the element may contain one of the elements
> listed in the choice group. The minOccurs="0" attribute indicates that
> the element is optional. It is not intended to be an array; therefore,
> it would be inappropriate to say maxOccurs="unbounded".
>
> Anne
>
>
> On Fri, Sep 12, 2008 at 12:04 AM, Shehan Simen
> wrote:
>> Hi,
>>
>> I have a question about wsdl. The wsdl2java fails in following case. But
>> I
>> feel the wsdl is wrong.
>>
>> I got the following element in a complex type.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> > type="tns:IndividualName" minOccurs="0"/>
>>
>> > type="
How to add explicit SOAP header in WSDL for generating SOAP message - Axis1.4
Dear All,
I need to expose java web services. I am using Axis1.4, Java 1.5 and Tomcat
5.0 for exposing services.
SOAP request and SOAP response have 'authentication' tag in SOAP header.
SOAP Request -
UserName
Password
...
--
SOAP response -
XXUserName
XXPassword
2007B
By seeing the SOAP message structure, we have decided to add SOAP header
explicitly in WSDL.
We are NOT able to differentiate between SOAP request and SOAP response
'authentication' tag in WSDL.
We have attempted to solve the above problem by creating 2 different type of
WSDL.
Please have look into these wsdl.
WSDL-1 :
http://test.com";
xmlns:tns="http://test.com";
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
http://test.com";>
http://schemas.xmlsoap.org/soap/http"; />
http://localhost:8080/hello-service/hello-service"/>
WSDL-2 :
http://test.com";
xmlns:tns="http://test.com";
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
http://test.com";>
http://schemas.xmlsoap.org/soap/http"; />
http://localhost:8080/hello-service/hello-service"/>
Please advise.
Regards,
Santosh
--
View this message in context:
http://www.nabble.com/How-to-add-explicit-SOAP-header-in-WSDL-for-generating-SOAP-message---Axis1.4-tp25747709p25747709.html
Sent from the Axis - User mailing list archive at Nabble.com.
Does Order of attributes in SOAP message have to match WSDL .
Hi All. Just after some info on whether the order of attributes in a Webservice Request / Response has to match the order of attributes defined in the WSDL. I am using Apache Axis 2, but am currently having some issues with a Webservice that I am connecting to. The WSDL states that the definition of an attribute is as follows: -<http://msdwin50.dev.mincom.com:9083/eai-composite-ejb/services/WRComp/wsdl/WRComp.wsdl> Yet the SOAP Response is returning the above attributes in the following order : CUSTOMER DOES NOT EXIST IN THIS DISTRICT 1896 CustomerNo -1 0 When trying to unpack the Webservice Response, Apache Axis is throwing the following error : org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement message Should Apache Axis be able to handle the attributes being in a different order, or is the webservice incorrect because its not conforming to the WSDL. If the later is true - is it stated in a wc3 spec anywhere that webservices should return attributes in the correct order? Thanks Julie This transmission is for the intended addressee only and is confidential information. If you have received this transmission in error, please notify the sender and delete the transmission. The contents of this e-mail are the opinion of the writer only and are not endorsed by the Mincom Group of companies unless expressly stated otherwise.
RE: axis wsdl not working with axis2
Hello, I don't think that it's an axis2 problem, as I've said and also with doc-literal, doc-wrapped, rpc-encoded servers. We've tried also with ASP.net and we got the same behaviour. so also ASP.net seems to have the same problem with this wsdl. The problem seems the wsdl generated by axis(not2) Many thanks Best Regards Il giorno ven, 02/10/2009 alle 16.05 +0200, sch...@afrigis.co.za ha scritto: > I have the exact same issue. If you search on Google, you will find > some bug reports related to this. Not sure whether it has been fixed > as I am getting it with the latest 1.5 I believe version. > > > > -- > > Kind Regards > > Schalk Neethling > > > From: Bartolomeo Nicolotti [mailto:bnicolo...@siapcn.it] > Sent: 02 October 2009 03:15 PM > To: axis-user@ws.apache.org > Cc: Marco Damilano; Livio Costamagna > Subject: axis wsdl not working with axis2 > > > > > Hello, > > we've generated a webservice and related attached wsdl with axis(not > 2) Eclipse 3.2.2 plugin. > > The web service is receiving one string and returning 3 strings, very > simple. > > Then we've used axis2 wsdl2java to generate the client with: > > wsdl2java.sh --noBuildXML -S ../../JavaSource -ns2p > http://Servizi.Pratica.APWebServices=com.siap.APPraticaXmlClient > -uri ./PraticaFromXml.wsdl > > The request is correctly received from the server side, the response > is received, as the sniffer report, by the client, but we got: > > Thu Oct 01 15:13:11 CEST > 2009:generaPraticaDaRes.percProvvigioneTotale20091001151201403-1 > caught an exception: 24442574 org.a > pache.axis2.AxisFault > e.toString():org.apache.axis2.AxisFault: > org.apache.axis2.databinding.ADBException: Unexpected subelement > importaReturn, > e.getMessage():org.apache.axis2.databinding.ADBException: Unexpected > subelement importaReturn > org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) > com.siap.APPraticaXmlClient.PraticaFromXmlServiceStub.fromOM(PraticaFromXmlServiceStub.java:2200) > com.siap.APPraticaXmlClient.PraticaFromXmlServiceStub.importa(PraticaFromXmlServiceStub.java:191) > com.siap.TPUtility.TPPraticaAtlanteUtil.generaPraticaDaSIAPDocumentable(TPPraticaAtlanteUtil.java:56) > com.siap.DPKWebServices.Util.DynPkgOTAServiceUtil.generaPraticaDaSIAPDocumentable(DynPkgOTAServiceUtil.java:1001) > com.siap.DPKWebServices.OTAMessages.WSMH_OTA_HotelRes_Literal.handleMessage(WSMH_OTA_HotelRes_Literal.java:166) > com.siap.DPKWebServices.OTAMessages.WSMD_SerialSimple.dispatchWebService_Message(WSMD_SerialSimple.java:31) > com.siap.DPKWebServices.Util.DynPkgOTAServiceDispacher.dispatchWebService_Message_internals(DynPkgOTAServiceDispacher.java:15 > 3) > com.siap.DPKWebServices.Util.DynPkgOTAServiceDispacher.dispatchWebService_Message(DynPkgOTAServi > > Analogous messages with > > -d jaxbri > -d xmlbeans > > and also with doc-literal, doc-wrapped, rpc-encoded servers. We've > tried also with ASP.net and we got the same behaviour. > > The only client that worked was the one generated from the wsdl from > axis(not2) Eclipse 3.2.2 plugin. > > The problem seems that the response type > > > > is not recognized. > > Could someone have a look at the wsdl and tell us why? > > > Many thanks > > Best regards > > > -- > Bartolomeo Nicolotti > SIAP s.r.l. > www.siapcn.it > v.S.Albano 13 12049 > Trinità(CN) Italy > ph:+39 0172 652553 > centralino: +39 0172 652511 > fax: +39 0172 652519 > > > > > > > > > > AfriGIS e-mail facility may not be used for the distribution of chain > letters or offensive email. AfriGIS hereby distances itself from and > accepts no liability for the unauthorized use of its e-mail facility > or the sending of e-mail communications for other than strictly > business purposes. AfriGIS furthermore disclaims liability for any > unauthorized instruction for which permission was not granted. > Required as per Sec 50 Companies Act 61 of 1973 Afrigis Pty LTD Reg No > 1997/0067/1607. > > > > > > > > > > > > > > > AfriGIS e-mail facility may not be used for the distribution of chain > letters or offensive email. AfriGIS hereby distances itself from and > accepts no liability for the unauthorized use of its e-mail facility > or the sending of e-mail communications for other than strictly > business purposes. AfriGIS furthermore disclaims liability for any > unauthorized instruction for which permission was not granted. > Required as per Sec 50 Companies Act 61 of 1973 Afrigis Pty LTD Reg No > 1997/0067/1607. > > > -- Bartolomeo Nicolotti SIAP s.r.l. www.siapcn.it v.S.Albano 13 12049 Trinità(CN) Italy ph:+39 0172 652553 centralino: +39 0172 652511 fax: +39 0172 652519
RE: axis wsdl not working with axis2
I have the exact same issue. If you search on Google, you will find some bug reports related to this. Not sure whether it has been fixed as I am getting it with the latest 1.5 I believe version. -- Kind Regards Schalk Neethling From: Bartolomeo Nicolotti [mailto:bnicolo...@siapcn.it] Sent: 02 October 2009 03:15 PM To: axis-user@ws.apache.org Cc: Marco Damilano; Livio Costamagna Subject: axis wsdl not working with axis2 Hello, we've generated a webservice and related attached wsdl with axis(not 2) Eclipse 3.2.2 plugin. The web service is receiving one string and returning 3 strings, very simple. Then we've used axis2 wsdl2java to generate the client with: wsdl2java.sh --noBuildXML -S ../../JavaSource -ns2p http://Servizi.Pratica.APWebServices=com.siap.APPraticaXmlClient -uri ./PraticaFromXml.wsdl The request is correctly received from the server side, the response is received, as the sniffer report, by the client, but we got: Thu Oct 01 15:13:11 CEST 2009:generaPraticaDaRes.percProvvigioneTotale20091001151201403-1 caught an exception: 24442574 org.a pache.axis2.AxisFault e.toString():org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement importaReturn, e.getMessage():org.apache.axis2.databinding.ADBException: Unexpected subelement importaReturn org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) com.siap.APPraticaXmlClient.PraticaFromXmlServiceStub.fromOM(PraticaFromXmlServiceStub.java:2200) com.siap.APPraticaXmlClient.PraticaFromXmlServiceStub.importa(PraticaFromXmlServiceStub.java:191) com.siap.TPUtility.TPPraticaAtlanteUtil.generaPraticaDaSIAPDocumentable(TPPraticaAtlanteUtil.java:56) com.siap.DPKWebServices.Util.DynPkgOTAServiceUtil.generaPraticaDaSIAPDocumentable(DynPkgOTAServiceUtil.java:1001) com.siap.DPKWebServices.OTAMessages.WSMH_OTA_HotelRes_Literal.handleMessage(WSMH_OTA_HotelRes_Literal.java:166) com.siap.DPKWebServices.OTAMessages.WSMD_SerialSimple.dispatchWebService_Message(WSMD_SerialSimple.java:31) com.siap.DPKWebServices.Util.DynPkgOTAServiceDispacher.dispatchWebService_Message_internals(DynPkgOTAServiceDispacher.java:15 3) com.siap.DPKWebServices.Util.DynPkgOTAServiceDispacher.dispatchWebService_Message(DynPkgOTAServi Analogous messages with -d jaxbri -d xmlbeans and also with doc-literal, doc-wrapped, rpc-encoded servers. We've tried also with ASP.net and we got the same behaviour. The only client that worked was the one generated from the wsdl from axis(not2) Eclipse 3.2.2 plugin. The problem seems that the response type is not recognized. Could someone have a look at the wsdl and tell us why? Many thanks Best regards -- Bartolomeo Nicolotti SIAP s.r.l. www.siapcn.it v.S.Albano 13 12049 Trinità(CN) Italy ph:+39 0172 652553 centralino: +39 0172 652511 fax: +39 0172 652519 <http://www.marbil.co.za> AfriGIS e-mail facility may not be used for the distribution of chain letters or offensive email. AfriGIS hereby distances itself from and accepts no liability for the unauthorized use of its e-mail facility or the sending of e-mail communications for other than strictly business purposes. AfriGIS furthermore disclaims liability for any unauthorized instruction for which permission was not granted. Required as per Sec 50 Companies Act 61 of 1973 Afrigis Pty LTD Reg No 1997/0067/1607. AfriGIS e-mail facility may not be used for the distribution of chain letters or offensive email. AfriGIS hereby distances itself from and accepts no liability for the unauthorized use of its e-mail facility or the sending of e-mail communications for other than strictly business purposes. AfriGIS furthermore disclaims liability for any unauthorized instruction for which permission was not granted. Required as per Sec 50 Companies Act 61 of 1973 Afrigis Pty LTD Reg No 1997/0067/1607.
axis wsdl not working with axis2
Hello, we've generated a webservice and related attached wsdl with axis(not 2) Eclipse 3.2.2 plugin. The web service is receiving one string and returning 3 strings, very simple. Then we've used axis2 wsdl2java to generate the client with: wsdl2java.sh --noBuildXML -S ../../JavaSource -ns2p http://Servizi.Pratica.APWebServices=com.siap.APPraticaXmlClient -uri ./PraticaFromXml.wsdl The request is correctly received from the server side, the response is received, as the sniffer report, by the client, but we got: Thu Oct 01 15:13:11 CEST 2009:generaPraticaDaRes.percProvvigioneTotale20091001151201403-1 caught an exception: 24442574 org.a pache.axis2.AxisFault e.toString():org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement importaReturn, e.getMessage():org.apache.axis2.databinding.ADBException: Unexpected subelement importaReturn org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) com.siap.APPraticaXmlClient.PraticaFromXmlServiceStub.fromOM(PraticaFromXmlServiceStub.java:2200) com.siap.APPraticaXmlClient.PraticaFromXmlServiceStub.importa(PraticaFromXmlServiceStub.java:191) com.siap.TPUtility.TPPraticaAtlanteUtil.generaPraticaDaSIAPDocumentable(TPPraticaAtlanteUtil.java:56) com.siap.DPKWebServices.Util.DynPkgOTAServiceUtil.generaPraticaDaSIAPDocumentable(DynPkgOTAServiceUtil.java:1001) com.siap.DPKWebServices.OTAMessages.WSMH_OTA_HotelRes_Literal.handleMessage(WSMH_OTA_HotelRes_Literal.java:166) com.siap.DPKWebServices.OTAMessages.WSMD_SerialSimple.dispatchWebService_Message(WSMD_SerialSimple.java:31) com.siap.DPKWebServices.Util.DynPkgOTAServiceDispacher.dispatchWebService_Message_internals(DynPkgOTAServiceDispacher.java:15 3) com.siap.DPKWebServices.Util.DynPkgOTAServiceDispacher.dispatchWebService_Message(DynPkgOTAServi Analogous messages with -d jaxbri -d xmlbeans and also with doc-literal, doc-wrapped, rpc-encoded servers. We've tried also with ASP.net and we got the same behaviour. The only client that worked was the one generated from the wsdl from axis(not2) Eclipse 3.2.2 plugin. The problem seems that the response type is not recognized. Could someone have a look at the wsdl and tell us why? Many thanks Best regards -- Bartolomeo Nicolotti SIAP s.r.l. www.siapcn.it v.S.Albano 13 12049 Trinità(CN) Italy ph:+39 0172 652553 centralino: +39 0172 652511 fax: +39 0172 652519 PraticaFromXml.Struct.wsdl Description: XML document
Re: Emitter failure. There is an undefined binding (HelloBinding) in the WSDL document. Hint: make sure is fully qualified.
On Thu, Oct 1, 2009 at 12:24 AM, sh_santosh wrote: > > Dear All, > > I have a wsdl file and i am generating WSDL2Java from this wsdl file. > I am getting this IOException - > Emitter failure. There is an undefined binding (HelloBinding) in the WSDL > document. > Hint: make sure is fully qualified. > > Please advise on this. > > Please find the WSDL file - > > http://schemas.xmlsoap.org/wsdl/"; > xmlns:tns="http://test.com"; > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:xs="http://www.w3.org/2001/XMLSchema";> > try adding targetNamespace="http://test.com"; at the definitions element thanks, Amila. > > > > > > > > > > > > > > > > transport="http://schemas.xmlsoap.org/soap/http"; /> > > > > > > > > > > > > > > location="http://localhost:8080/hello-service/hello-service"/> > > > > > > Exception details - > java.io.IOException: Emitter failure. There is an undefined binding > (HelloBinding) in the WSDL document. > Hint: make sure is fully qualified. >at > > org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:570) >at > org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:715) >at > org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543) >at > org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518) >at > org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495) > at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) >at java.lang.Thread.run(Thread.java:619) > > > Regards, > Santosh > -- > View this message in context: > http://www.nabble.com/Emitter-failure.--There-is-an-undefined-binding-%28HelloBinding%29-in-the-WSDL-document.-Hint%3A-make-sure-%3Cport-binding%3D%22..%22%3E-is-fully-qualified.-tp25686826p25686826.html > Sent from the Axis - User mailing list archive at Nabble.com. > > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Emitter failure. There is an undefined binding (HelloBinding) in the WSDL document. Hint: make sure is fully qualified.
Dear All, I have a wsdl file and i am generating WSDL2Java from this wsdl file. I am getting this IOException - Emitter failure. There is an undefined binding (HelloBinding) in the WSDL document. Hint: make sure is fully qualified. Please advise on this. Please find the WSDL file - http://schemas.xmlsoap.org/wsdl/"; xmlns:tns="http://test.com"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xs="http://www.w3.org/2001/XMLSchema";> http://schemas.xmlsoap.org/soap/http"; /> http://localhost:8080/hello-service/hello-service"/> Exception details - java.io.IOException: Emitter failure. There is an undefined binding (HelloBinding) in the WSDL document. Hint: make sure is fully qualified. at org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:570) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:715) at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) at java.lang.Thread.run(Thread.java:619) Regards, Santosh -- View this message in context: http://www.nabble.com/Emitter-failure.--There-is-an-undefined-binding-%28HelloBinding%29-in-the-WSDL-document.-Hint%3A-make-sure-%3Cport-binding%3D%22..%22%3E-is-fully-qualified.-tp25686826p25686826.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: WSDL client generation. Problem with more than one part and binding style "document"
Le vendredi 25 septembre 2009 à 10:35 +0530, Amila Suriarachchi a écrit : > > How to develop the fastest way an operational client and set > the whole soap envelop > you want to send ? > > Please see here[1] > > thanks, > Amila. > > [1] > http://amilachinthaka.blogspot.com/2009/09/sending-arbitrary-soap-message-with.html Thank you very much Amila, it works perfectly !
Re: WSDL client generation. Problem with more than one part and binding style "document"
On Thu, Sep 24, 2009 at 3:58 PM, wrote: > > - "Amila Suriarachchi" a écrit : > > > [...] > > > > theName > > > > > > [...] > > > > How can I modify the WSDL to make axis2 generating a client which can > > produce the above request I want ? Is it possible ? Do I need to change > the > > style to rpc ? If it's not possible, do you know an opensource project > > which know how to deal with my wsdl ? > > > > > > I think this is not possible with Axis2 unless you write an > > operational client and set the whole soap envelop > > you want to send. > > Thanks Amila, > But why doesn't Axis2 know how to generate such a message ? > I saw nothing in w3.org/TR/wsdl saying that multi parts inside soap:body > is prohibited... I've only see this > limitation (for compatibility if I've correctly understood) on ws-i.org. > > Axis2 only how to generate WS-I ? Not wsdl in general ? > This is to solve the problem now you have faced :). If soap stacks do not follow WS-I it is very difficult to interoperate between them. > > How to develop the fastest way an operational client and set the whole soap > envelop > you want to send ? > Please see here[1] thanks, Amila. [1] http://amilachinthaka.blogspot.com/2009/09/sending-arbitrary-soap-message-with.html > > Thanx again for help and informations > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: WSDL client generation. Problem with more than one part and binding style "document"
- "Amila Suriarachchi" a écrit : > [...] > > theName > > > [...] > > How can I modify the WSDL to make axis2 generating a client which can > produce the above request I want ? Is it possible ? Do I need to change the > style to rpc ? If it's not possible, do you know an opensource project > which know how to deal with my wsdl ? > > > I think this is not possible with Axis2 unless you write an > operational client and set the whole soap envelop > you want to send. Thanks Amila, But why doesn't Axis2 know how to generate such a message ? I saw nothing in w3.org/TR/wsdl saying that multi parts inside soap:body is prohibited... I've only see this limitation (for compatibility if I've correctly understood) on ws-i.org. Axis2 only how to generate WS-I ? Not wsdl in general ? How to develop the fastest way an operational client and set the whole soap envelop you want to send ? Thanx again for help and informations
Re: WSDL client generation. Problem with more than one part and binding style "document"
On Thu, Sep 24, 2009 at 5:46 AM, error3 wrote: > Hello, > > with the attached wsdl file (it's an simplified version of mine), I'm > trying to generate WS client (in eclipse, and with Axis2). > > while trying to generate the client, I have an error saying that "more > than one part" in the message... (I do not have the message nor my > development environment at that time). > > Googlin' and found that "document" binding style shouldn't have multiple > parts message in the body. > Ok. > > So I know that, to querying the webservice (I can't modify it, it's an > application one) I must send something like : > > [...] > > theName > > > [...] > > How can I modify the WSDL to make axis2 generating a client which can > produce the request I want ? Is it possible ? Do I need to change the > style to rpc ? If it's not possible, do you know an opensource project > which know how to deal with my wsdl ? > I think this is not possible with Axis2 unless you write an operational client and set the whole soap envelop you want to send. thanks, Amila. > thank you very much for any help, > > -- > Martin > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
WSDL client generation. Problem with more than one part and binding style "document"
Hello, with the attached wsdl file (it's an simplified version of mine), I'm trying to generate WS client (in eclipse, and with Axis2). while trying to generate the client, I have an error saying that "more than one part" in the message... (I do not have the message nor my development environment at that time). Googlin' and found that "document" binding style shouldn't have multiple parts message in the body. Ok. So I know that, to querying the webservice (I can't modify it, it's an application one) I must send something like : [...] theName [...] How can I modify the WSDL to make axis2 generating a client which can produce the request I want ? Is it possible ? Do I need to change the style to rpc ? If it's not possible, do you know an opensource project which know how to deal with my wsdl ? thank you very much for any help, -- Martin TMP.WSDL Description: application/wsdl
Re: WSDL URL is Changing
On Thu, Sep 17, 2009 at 3:27 PM, E Shanaka Jayasundera wrote: > Axis 2 version is 1.4.1 > > > > What is the parameter to that we need to change? > thanks, Amila. > > > Thanks in advance. > > > > *From:* Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] > *Sent:* Thursday, September 17, 2009 11:21 AM > *To:* axis-user@ws.apache.org > *Subject:* Re: WSDL URL is Changing > > > > what is the axis2 version you use? > > there is a commented parameter in axis2.xml. try changing that. > > thanks, > Amila. > > On Wed, Sep 16, 2009 at 5:52 PM, E Shanaka Jayasundera < > shan...@aeturnum.com> wrote: > > My Application is deployed on JBOSS Application server (SSL enabled) and > WSDL access URL is https://localhost:9002/web/services/WS?wsdl > > For some reason its going to redirect to > https://localhost:9002/axis2/services/WS?wsdl<https://localhost:9002/axis2/services/PayfoneWS?wsdl> > > > > I haven’t specify /axis2/ any were and also my filter in web.xml is as > follows, > > > > > > AxisServlet > > > org.apache.axis2.transport.http.AxisServlet > > 1 > > > > > > > > AxisServlet > > /services/* > > > > > > > > Also, in the later time some home client end point change to > https://localhost:9002/web/services/PayfoneWS?wsdl and fails since this > end point is not working > > > > Thanks in advance. > > > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
RE: WSDL URL is Changing
Axis 2 version is 1.4.1 What is the parameter to that we need to change? Thanks in advance. From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] Sent: Thursday, September 17, 2009 11:21 AM To: axis-user@ws.apache.org Subject: Re: WSDL URL is Changing what is the axis2 version you use? there is a commented parameter in axis2.xml. try changing that. thanks, Amila. On Wed, Sep 16, 2009 at 5:52 PM, E Shanaka Jayasundera wrote: My Application is deployed on JBOSS Application server (SSL enabled) and WSDL access URL is https://localhost:9002/web/services/WS?wsdl For some reason its going to redirect to https://localhost:9002/axis2/services/WS?wsdl <https://localhost:9002/axis2/services/PayfoneWS?wsdl> I haven't specify /axis2/ any were and also my filter in web.xml is as follows, AxisServlet org.apache.axis2.transport.http.AxisServlet 1 AxisServlet /services/* Also, in the later time some home client end point change to https://localhost:9002/web/services/PayfoneWS?wsdl and fails since this end point is not working Thanks in advance. -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: WSDL URL is Changing
what is the axis2 version you use? there is a commented parameter in axis2.xml. try changing that. thanks, Amila. On Wed, Sep 16, 2009 at 5:52 PM, E Shanaka Jayasundera wrote: > My Application is deployed on JBOSS Application server (SSL enabled) and > WSDL access URL is https://localhost:9002/web/services/PayfoneWS?wsdl > > For some reason its going to redirect to > https://localhost:9002/axis2/services/PayfoneWS?wsdl > > > > I haven’t specify /axis2/ any were and also my filter in web.xml is as > follows, > > > > > > AxisServlet > > > org.apache.axis2.transport.http.AxisServlet > > 1 > > > > > > > > AxisServlet > > /services/* > > > > > > > > Also, in the later time some home client end point change to > https://localhost:9002/web/services/PayfoneWS?wsdl and fails since this > end point is not working > > > > Thanks in advance. > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
WSDL URL is Changing
My Application is deployed on JBOSS Application server (SSL enabled) and WSDL access URL is https://localhost:9002/web/services/PayfoneWS?wsdl For some reason its going to redirect to https://localhost:9002/axis2/services/PayfoneWS?wsdl I haven't specify /axis2/ any were and also my filter in web.xml is as follows, AxisServlet org.apache.axis2.transport.http.AxisServlet 1 AxisServlet /services/* Also, in the later time some home client end point change to https://localhost:9002/web/services/PayfoneWS?wsdl and fails since this end point is not working Thanks in advance.
Re: Generated WSDL has wrong "types"
On Fri, Sep 11, 2009 at 8:15 PM, Lorenzo Carnevale < lorenzo.carnev...@innovery.it> wrote: > Sorry, I have yet another problem. > I have to add the policy tags to the wsdl, so I use USEORIGINALWSDL to > false... the resulting WSDL copies the policy tags correctly from > SERVICES.XML, but the original 'types' of the input and output elements > disappered... > try to add the policy to relavent place in wsdl file instead of adding them to services.xml. thanks, Amila. > > Origianl WSDL : > > > > > > > > > > > > > > > > > > Generated WSDL: > > > > >nillable="true" type="xs:anyType"/> > > > > > So the usual 'wizards' that build clients from WSDLs can't really guess > what's going on. > Thanks > Lorenzo > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Generated WSDL has wrong "types"
Sorry, I have yet another problem. I have to add the policy tags to the wsdl, so I use USEORIGINALWSDL to false... the resulting WSDL copies the policy tags correctly from SERVICES.XML, but the original 'types' of the input and output elements disappered... Origianl WSDL : /> Generated WSDL: nillable="true" type="xs:anyType"/> So the usual 'wizards' that build clients from WSDLs can't really guess what's going on. Thanks Lorenzo
Re: [AXIS2] 'Unable to generate WSDL 1.1 for this service'
Thanks, it solves the problem.
- Original Message -
From: Keith Chapman
To: axis-user@ws.apache.org
Sent: Wednesday, September 09, 2009 4:17 AM
Subject: Re: [AXIS2] 'Unable to generate WSDL 1.1 for this service'
You need to have a folder call META-INF in ur aar file and place the wsdl
file in that. Also the service name in the wsdl should be the same as the
servicename you used in the services.xml.
Thanks,
Keith.
On Mon, Sep 7, 2009 at 12:13 PM, Lorenzo Carnevale
wrote:
Hello everybody.
I followed one of Sosnoski's tutorials on IBM website to create Secure w.s.
with Rampart.
In Services.xml, I have the following tag:
true
I am deploying my web service as an aar service in an axis2 standalone
server,
and I have the error "Unable to generate WSDL 1.1 for this service" when I
try to access the WS.
Please notice that:
1) I don't care if the WSDL is 1.1 or 2.0
2) I don't want to use, if possible, a 'generated' wsdl: the original wsdl
is prettier (and if I declare useOriginalwsdl = false, the generated WSDL
provides 3 end points (!) without apparent reason)
I have seen solutions suggesting to put the .wsdl file in the META-INF
folder, but working with a .aar I have no such folder.
Thanks to all
Lorenzo
--
Thanks,
Keith.
Keith Chapman
blog: http://www.keith-chapman.org
Re: [AXIS2] 'Unable to generate WSDL 1.1 for this service'
You need to have a folder call META-INF in ur aar file and place the wsdl file in that. Also the service name in the wsdl should be the same as the servicename you used in the services.xml. Thanks, Keith. On Mon, Sep 7, 2009 at 12:13 PM, Lorenzo Carnevale < lorenzo.carnev...@innovery.it> wrote: > Hello everybody. > I followed one of Sosnoski's tutorials on IBM website to create Secure w.s. > with Rampart. > > In Services.xml, I have the following tag: > > true > I am deploying my web service as an aar service in an axis2 standalone > server, > and I have the error "Unable to generate WSDL 1.1 for this service" when I > try to access the WS. > > Please notice that: > 1) I don't care if the WSDL is 1.1 or 2.0 > 2) I don't want to use, if possible, a 'generated' wsdl: the original wsdl > is prettier (and if I declare *useOriginalwsdl = false, *the generated > WSDL provides 3 end points (!) without apparent reason) > > I have seen solutions suggesting to put the .wsdl file in the META-INF > folder, but working with a .aar I have no such folder. > > Thanks to all > Lorenzo > > > > > > > > -- Thanks, Keith. Keith Chapman blog: http://www.keith-chapman.org
[AXIS2] 'Unable to generate WSDL 1.1 for this service'
Hello everybody. I followed one of Sosnoski's tutorials on IBM website to create Secure w.s. with Rampart. In Services.xml, I have the following tag: true I am deploying my web service as an aar service in an axis2 standalone server, and I have the error "Unable to generate WSDL 1.1 for this service" when I try to access the WS. Please notice that: 1) I don't care if the WSDL is 1.1 or 2.0 2) I don't want to use, if possible, a 'generated' wsdl: the original wsdl is prettier (and if I declare useOriginalwsdl = false, the generated WSDL provides 3 end points (!) without apparent reason) I have seen solutions suggesting to put the .wsdl file in the META-INF folder, but working with a .aar I have no such folder. Thanks to all Lorenzo
Re: Axis2 wsdl problem with reverse proxy
Hi the best solutions are the ones solved by oneself. :-) > I am currently trying to resolve a simple problem with the autogeneration > of the WSDL files inside of Axis2. My setup is the following: > > webserver:80/ws/ <= reverseproxy to => tomcat:8080/axis/services > > By setting the "hostname" parameter in the services.xml I can change to > hostname of delivered wsdl file from the tomcat server name to the > external webservername - however this did not work with the port. I could > not find any parameter to set the specific port. Using the "port" > parameter in services.xml did not change anything. The parameters true false together with renaming my wsdl file to the service name do exactly what I wanted. Next time I'll try to read the manual even harder :-) Regards, Alexander -- http://www.emplify.de
