R J and All, I have started to write client methods contacting the Axis server to get the wsdd and then from there scanning it using WSDD* objects. As you mentionned in your email, the WSDD* framework does not provide a way to get the typemappings from the WSDDService.... I got stuck on that.
Here what I have done: The Call object should check for a singleton cache to check that it already contains info about typemappings. If not, the cache should get the wsdd from the server and initialize itself. I have seen in the Axis sources that you are already working on a different WSDD format, which seems more flexible (The provider becomes an element) and can be augmented depending on the platform (java, .NET, ...). What we need is a marshalling/unmarshalling framework --> WSDD 2 Java and Java 2 WSDD. I thought that the WSDD objects were providing such mechanism but they don't really map to the wsdd structure. I can see 2 solutions (to avoid unecessary coding): use JAXB to generate the framework from the DTD or using Castor from exolab to start from the XSD (I prefer the second solution). Maybe the first step could be: generate a throaway XSD schema or DTD on the present structure and generate the marshalling/unmarshalling framework from there. During my tests, and I have metionned that as well when running the WSDL2Java, there is an error for the service name: namespace vs port type. The DII takes a QName containing the targeted namespace and port type. The wsdd MUST contain the namespace as the service name !! I think that there is a confusion somewhere.... Olivier R J Scheuerle Jr wrote: >Russell and I talked about this on Friday. > >What I think should happen... > - The Call should use the type mapping registry in the service. > - The Service should use the type mapping registry set up intially by >WSDDService. > >What is happenning > - The Call is using the MessageContext type mapping registry...which >appears to > change when the MessageContext is registered as a soap service handler >(?) > - The Service object doesn't have a type mapping registry. > >So this needs to be fixed. Would like some more comments > >Rich Scheuerle >XML & Web Services Development >512-838-5115 (IBM TL 678-5115) > > > > > Doug Davis > > To: Olivier Brand ><[EMAIL PROTECTED]> > 02/11/2002 10:07 cc: Russell >Butek/Austin/IBM@IBMUS, R J Scheuerle Jr/Austin/IBM@IBMUS > AM From: Doug Davis/Raleigh/IBM@IBMUS > > Subject: Re: TypeMappingRegistry >implementation in Service ???(Document link: R J > Scheuerle Jr) > > > > > > > > > > > > > > > > > >Unfortunately I haven't had to time to work on Axis - Rich and Russell have >been working like crazy to keep us up to date with jaxrpc. >Guys - any ideas? >-Dug > >Olivier Brand <[EMAIL PROTECTED]> on 02/10/2002 08:41:21 PM > >To: Doug Davis/Raleigh/IBM@IBMUS >cc: >Subject: TypeMappingRegistry implementation in Service ??? > > > >Hi Doug, > >I have beentrying the DII features of Axis, very pleased. One thing >though: the TypeMappingRegistry. >I saw in the source code that the framework is there but the Service >class does not use it.. forcing me to use the proprietary >Call.registerTypeMapping(). >When do you think this feature will be injected in Axis to be compliant >with JAX-RPC ?? > >Thanks for the awsome work. > >Olivier > > >_________________________________________________________ >Do You Yahoo!? >Get your free @yahoo.com address at http://mail.yahoo.com > > > > > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
