Definitely no need to apologize...and I agree it can have performance problems. On the interoperability I would disagree, but what fun would be software if there wasn't some of this. I wish I had more time to dig in and understand it well enough to contribute the rpc/enc mechanism.
________________________________ From: Tomek Sztelak [mailto:[EMAIL PROTECTED] Sent: Fri 11/17/2006 5:32 PM To: [email protected] Subject: Re: [xfire-user] WsGen Error On 11/17/06, Chris Thatcher <[EMAIL PROTECTED]> wrote: > I do apologize, I certainly didn't mean to imply rpc/encoded is 'bad'. No need to apologize :). Lets say RPC/encoded is "not good" ;). Lots of problems with interoperability and performance :/ > It is > rarely true that the technology world immediately adopts the latest standard > and I'm sure that if the volunteers who developed, continue developing, and > maintain Xfire had unlimited resources they would already have support for > it. It probably made more sense for them to initially support literal style > bindings since that is the current 'standard'. > > If rpc/encoded is very important to you, and you love Xfire as much as the > rest of us, you could always contribute back adding support for it. Yes, If anyone wants to contribute any code related to rpc/enc support, we will gladly add this to distribution. > Thatcher > > -----Original Message----- > From: Ron DiFrango [mailto:[EMAIL PROTECTED] > Sent: Friday, November 17, 2006 11:38 AM > To: [email protected]; [email protected] > Subject: RE: [xfire-user] WsGen Error > > > It might be, but at least in my case it is still in wide use and the standard > tools I use [TIBCO BW and Weblogic 8.1 Workshop] typically support > RPC/encoded much better than Document/literal. > > My general point is that for compatibility it should be supported because I > have seen more multiple people on this mailing list need that support. > > ________________________________ > > From: M Goodell [mailto:[EMAIL PROTECTED] > Sent: Fri 11/17/2006 10:59 AM > To: [email protected] > Subject: RE: [xfire-user] WsGen Error > > > > Isn't RPC encoding deprecated according to the WS-I Basic Profile? > > -----Original Message----- > From: Ron DiFrango [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 16, 2006 4:26 PM > To: [email protected]; [email protected] > Subject: RE: [xfire-user] WsGen Error > > > Thatcher, > > That is a good explanation, but I do have one counter point, we do know that > rpc/encoded WSDL's are out there and in production usage. Also, we know that > rpc/encoded is complete valid. Therefore, shouldn't XFire support it > especially for the client side? > > I know that rpc/encoded is a fact of life in my current situation and it will > not likely change anytime soon therefore it precludes me from using XFire. > > Ron > > ________________________________ > > From: Chris Thatcher [mailto:[EMAIL PROTECTED] > Sent: Wed 11/15/2006 6:03 PM > To: [email protected] > Subject: RE: [xfire-user] WsGen Error > > > > Apologies, I should have been more clear. You wont be able to generate an > Xfire client from the wsdl because it uses rpc/encoded style soap bindings. > ... <binding name="IACHSOAPbinding" type="tns:IACHSOAP"> > <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"; > /> > <operation name="ConnectionCheck"> > <soap:operation soapAction="urn:ACHSOAPIntf-IACHSOAP#ConnectionCheck" > style="rpc" /> > ... > > I always pause to say this, because it has somethimes been a heated debate in > years past, most of the web services community has agreed to move away from > rpc/encoded style soap bindings. Though some frameworks supports rpc, most > newer soap libraries focus on document style soap bindings, and to make > matters more confusing some older libraries may only support rpc. > > The end result of much debate was the WS-I Basic Profile (WebService > Interopability Basic Profile), a standard to help get the web service > community on the same page, which does not include support for rpc/encoded. > > The short of it is, you wont be able to generate an Xfire client because the > service and the wsdl it exposes are not WS-I Basic Profile compliant. Sorry. > > Thatcher > > -----Original Message----- > From: M Goodell [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 15, 2006 5:41 PM > To: [email protected] > Subject: RE: [xfire-user] WsGen Error > > > Thank you for the quick response! > > More specifically, what flag do I use when generating the code. > > I tried both the -binding jaxb & xmlbeans and the same exception was thrown. > > Here is a snippet from my .cmd file that generates the code: > > java -cp "%XFIRE_CLASSPATH%" org.codehaus.xfire.gen.WsGen -wsdl > http://tstsvr.achworks.com/testexec/achtstsoapbz.tss/wsdl/IACHSOAP?wsdl -o . > -overwrite true -binding xmlbeans > > Do I need to build my client differently if it uses RPC? > > Thanks, > > M Goodell > > -----Original Message----- > From: Chris Thatcher [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 15, 2006 3:30 PM > To: [email protected] > Subject: RE: [xfire-user] WsGen Error > > > Xfire does not currently support rpc style binding. Try document/literal or > document/wrapped instead. > > http://xfire.codehaus.org/Client+and+Server+Stub+Generation+from+WSDL > > Thatcher > > -----Original Message----- > From: M Goodell [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 15, 2006 5:20 PM > To: ~XFire User Mailing List > Subject: [xfire-user] WsGen Error > > > I am trying to use XFire WsGen to generate client side code from a non XFire > generated wsdl url: > > http://tstsvr.achworks.com/testexec/achtstsoapbz.tss/wsdl/IACHSOAP?wsdl > > and the following exception is thrown: > > Any ideas as to why this is? Should I be able to do this or do I need to > generate my client code differently? > > Thanks in advance! > > M Goodell > > Exception out starts here: > > Running WsGen... > wsdl : > http://tstsvr.achworks.com/testexec/achtstsoapbz.tss/wsdl/IACHSOAP?wsdl > package : null > output : . > binding : > externalBindings : > baseURI : > profile : > explictAnnotation : false > overwrite : true > Nov 15, 2006 2:19:43 PM org.codehaus.xfire.gen.Wsdl11Generator generate > INFO: Generating code for WSDL at > http://tstsvr.achworks.com/testexec/achtstsoap > bz.tss/wsdl/IACHSOAP?wsdl with a base URI of > http://tstsvr.achworks.com/testexec/achtstsoapbz.tss/wsdl/IACHSOAP?wsdl > WSDLException (at /definitions/binding/operation[1]/input): > faultCode=INVALID_WSDL: Element '{http://schemas.xmlsoap.org/wsdl/}input' > contained unexpected attributes: 'message': > at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.parseBindingInput(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.parseBindingOperation(Unknown > Source) > > at com.ibm.wsdl.xml.WSDLReaderImpl.parseBinding(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at > org.codehaus.xfire.wsdl11.parser.WSDLServiceBuilder.<init>(WSDLServiceBuilde > r.java:123) > at > org.codehaus.xfire.gen.Wsdl11Generator.generate(Wsdl11Generator.java:100) > at org.codehaus.xfire.gen.WsGen.main(WsGen.java:122) > Exception in thread "main" WSDLException (at > /definitions/binding/operation[1]/input): faultCode=INVALID_WSDL: Element > '{http://schemas.xmlsoap.org/wsdl/}input' > contained unexpected attributes: 'message': > at org.codehaus.xfire.gen.WsGen.main(WsGen.java:126) > Caused by: WSDLException (at /definitions/binding/operation[1]/input): > faultCode > =INVALID_WSDL: Element '{http://schemas.xmlsoap.org/wsdl/}input' contained > unexpected attributes: 'message': > at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.parseBindingInput(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.parseBindingOperation(Unknown > Source) > > at com.ibm.wsdl.xml.WSDLReaderImpl.parseBinding(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at > org.codehaus.xfire.wsdl11.parser.WSDLServiceBuilder.<init>(WSDLServiceBuilde > r.java:123) > at > org.codehaus.xfire.gen.Wsdl11Generator.generate(Wsdl11Generator.java:100) > at org.codehaus.xfire.gen.WsGen.main(WsGen.java:122) > --- Nested Exception --- > WSDLException (at /definitions/binding/operation[1]/input): > faultCode=INVALID_WSDL: Element '{http://schemas.xmlsoap.org/wsdl/}input' > contained unexpected attributes: 'message': > at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.parseBindingInput(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.parseBindingOperation(Unknown > Source) > > at com.ibm.wsdl.xml.WSDLReaderImpl.parseBinding(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at > org.codehaus.xfire.wsdl11.parser.WSDLServiceBuilder.<init>(WSDLServic > eBuilder.java:123) at > org.codehaus.xfire.gen.Wsdl11Generator.generate(Wsdl11Generator.java:100) > at org.codehaus.xfire.gen.WsGen.main(WsGen.java:122) > XFIRE_HOME=C:\Program Files\xfire-1.2.2 > XFIRE_LIB=C:\Program Files\xfire-1.2.2\lib XFIRE_CLASSPATH=C:\Program > Files\xfire-1.2.2\xfire-all-1.2.2.jar;C:\Program > Files\xfire-1.2.2\lib\jaxb-api-2.0.jar;C:\Program > Files\xfire-1.2.2\lib\stax-api-1.0 > .1.jar;C:\Program Files\xfire-1.2.2\lib\jdom-1.0.jar;C:\Program > Files\xfire-1.2. > 2\lib\jaxb-impl-2.0.1.jar;C:\Program > Files\xfire-1.2.2\lib\jaxb-xjc-2.0.1.jar;C: > \Program Files\xfire-1.2.2\lib\wstx-asl-2.9.3.jar;C:\Program > Files\xfire-1.2.2\l > ib\commons-logging-1.0.4.jar;C:\Program > Files\xfire-1.2.2\lib\wsdl4j-1.5.2.jar;C > :\Program Files\xfire-1.2.2\lib\XmlSchema-1.0.3.jar;C:\Program > Files\xfire-1.2.2 > \lib\xfire-jsr181-api-1.0-M1.jar;C:\Program > Files\apache-ant-1.6.5\lib\ant.jar;C > :\Program Files\Java\jaf-1.1\activation.jar > Press any key to continue . . . > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.430 / Virus Database: 268.14.6/535 - Release Date: 11/15/2006 > 3:47 PM > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.430 / Virus Database: 268.14.6/536 - Release Date: 11/16/2006 > 3:51 PM > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > -- ----- When one of our products stops working, we'll blame another vendor within 24 hours. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
