Tomas, The guy who wrote the service needs to know the best way to write/deploy the service. which is using wsdl-first. just using deploy.wsdd will cause problems.
thanks, dims On 1/6/06, Tomas Bahnik <[EMAIL PROTECTED]> wrote: > Dims, > maybe I should clarify the scenario. The wsdl was generated automaticaly by > Axis from service code (located at http://endpoint?wsdl ). Systinet client > generates interface (by wsdl2java ) from that wsdl and proxy at runtime. > Sorry, but I can't see the reasoning behind java2wsld -> adjust wsdl -> > wsdl2java in this case. > > Tomas > > ----- Original Message ----- > From: "Davanum Srinivas" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Friday, January 06, 2006 1:54 PM > Subject: Re: bad response element from service with style="document" > > > Tomas, > > We don't recommend direct deployment exactly because of problems like > you mentioned. can you please run "java2wsdl" (it has options for > wrapped etc), adjust the wsdl to your liking and then run WSDL2Java? > > thanks, > dims > > On 1/6/06, Tomas Bahnik <[EMAIL PROTECTED]> wrote: > > Hi all, > > I have encountered interop problem with Axis service using > > style="document" > > in deployment descriptor (deploy_echo.wsdd) . The response element > > string_dataReturn (echoString.txt) is not defined in > > service wsdl (ServiceDocument.wsdl). This element should > > be, according to the wsdl, impl:echoStringReturn with > > xmlns:impl="http://localhost:8080/axis/services/ServiceDocument . Is that > > known problem? Tested with Axis version: 1.3. > > > > Note that style wrapped works ok. > > > > Thanks for any hint. > > > > Tomas Bahnik > > Systinet Corp. > > > > > > > -- > Davanum Srinivas : http://wso2.com/blogs/ > > -- Davanum Srinivas : http://wso2.com/blogs/
