Bill, looks like I accidently posted a reply to a different query (that of simplifying deployment of custom serializers) in response to yours.
I was hoping to present a simple solution to custom serialization issues (that can probably be wrapped in a generic 'JavaObjectBase64Serializer'). > Umm.... I'm not sure if that would meet my needs. Maybe I'm missing a > piece of your explanation/solution (very, very possible!), but your method > seems to assume that I will be calling my own service. That will not be my > case. Our business partners will be calling the methods. I don't want to > burdon them with serialization issues. > > I'd really like to present a WSDL doc to potential clients (developers) of > my system that their systems can into use to generate java, C# or whatever > code to call my service. The WSDL aslo serves as an important communication > device in terms of explaining what data these clients can expect to provide > when using my service. > > Thanks for the response and please feel free to correct any ignorance > displayed on my part above! > > Bill Pfeiffer
