Thanks for the advice, but I need to get this done earlier, when invoking Java2WSDL. The strategy now is to use this followed by WSDL2Java to generate the deployment classes, then do one tweak to get the right service running. This is not too much for the deployment team. I don't want to have to give them a set of instructions for tweaking the .wsdl file in the middle of this if possible.
Any other thoughts anyone? Thanks! -- J On 01/07/2003 10:53:26 am Davanum Srinivas wrote: >Did you try using "--all" option in WSDL2Java? > >Thx, >dims > >--- Jeffrey J Gaynor/jqhome <[EMAIL PROTECTED]> wrote: >> Hi All, >> >> I have a project that returns an array of beans. I am using WSDL to >> generate all of the required classes. The problem is that one of the beans >> I require is not explicitly in any method as an argument or returned value, >> but may be returned in an array. Therefore, no serializer is generated. >> Before I tweak something manually, is there an easy way to get WSDL to >> generate the serializer automatically? >> >> This is important, because at some point when the project is functional, I >> will be turning it over to a deployment team which will have no knowledge >> of AXIS or WSDL. I would very much like to give them a cookbook for >> re-deploying the service and this must be as automated as possible. >> >> Thanks! >> >> -- J > > >===== >Davanum Srinivas - http://xml.apache.org/~dims/ > >__________________________________________________ >Do you Yahoo!? >Yahoo! Mail Plus - Powerful. Affordable. Sign up now. >http://mailplus.yahoo.com
