Well, I don't mean to toot my own horn, but I am rather impressed with my tool. It supports the following features:
* Automatically takes classes with mixed data (getters/setters) and action methods and splits them into Beans and Impl Action classes * Converts all methods to throw RemoteException * "flattens" inheritance model so that classes in the same package are inherited. All inherited methods out of package are rolled into the lowest base class that is in package. (I know, this sounds like it should not work, but it does, and if I find a case where it does not work, it can be turned off, but it works well to simplify the data beans) * Spits out either one Wsdd or one wsdd per class in package * Can convert an entire package at once * Supports outputting classes with overloaded methods or without. (adds 2,3,4 to overloaded versions) * Optionally excludes entire classes -x jim.MyClass or specific methods -x jim.MyClass.method1 or the more global *.method1 * Optionally Simplifies Vectors and Lists into array of Object. * Creates JAX-RPC interfaces for Action classes * User defined extensions for Bean, Interface, and Action classes (defaults to "","IF", and "Impl") * Automatically walks the extension tree to add beanMappings to WSDD file for all classes used in a service 1200 line program, and pretty messy (it was not designed for long term use, just to get this set of vendor classes ready for Web service consumption). But, if there is interest in a TIE (I think that is the name) gen tool that cleans up arbitrary classes for consumption, let me know. As to your suggestion below, I can if I go through the actual class code, but that is a vendor product, and I'm not sure it's going to be easy to find 9they are very heavy inheritance users) Jim Jim Brain, [EMAIL PROTECTED] "Researching tomorrow's decisions today." (319) 369-2070 (work) SYSTEMS ARCHITECT, ITS, AEGON FINANCIAL PARTNERS -----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 1:44 PM To: [EMAIL PROTECTED] Subject: Re: java.util.List and 1.1.RC2 Brain, Jim wrote: > I know, and I thought of that. > > Unfortunately, I need to expose 296 service classes, containing 5000 > references to List, and I have a program that is creating web service > wrappers for all the classes (the original classes combined data and access > logic, which had to split in half to work in the web service world. The > program I wrote can be applied to any arbitrary class, though, uses > reflection, and I am planning on cleaning it up and offering it). > Programmatically, I can't determine the data type of a List, so I have to > replace with Object[], which isn't much better (although AXIS WSDL code > seems to like that) You cant add xdoclet metadata to state the type of lists? I really miss typed datastructures, its the main bit of C++ that I still miss, even if its templating was awful compared to that of the polymorphic type inference features of Standard ML. I guess porting to the generics compiler is out too, huh :) That's OK, axis cant handle that iether. It seems to me that if Axis handles Object[] then it should be able to serialize List, at the very least by going List.toArray() & returning the object array. typing would be a nice extra, with a configurable in the WSDD declarations that stated the java class in the list. You sound like you are doing a major undertaking there. I wish you well -you could probably derive an interesting paper or two from the experience. I'll point you at my making web-services-that-work paper http://www.iseran.com/Steve/papers/wstw/ which may be of interest -steve
