I played a bit with Office2003Betta and met the same problem as you described. I didn't have a chance to experiment with WSDD yet but what you said is a bit confusing:-) I hoped that would help.
I have no idea what Office expects to get but .net example they mention in the article works fine. But! I did another experiment. I took a WSDL that that example generates. Stored it separately as a XML file and pass to Office. It didn't work! I have no idea why. From my testing client it works w/o a problem. I'm gonna play with this on the weekend and update you in case if any news. Roman Rytov > -----Original Message----- > From: Carey Nation [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 31, 2003 06:00 AM > To: [EMAIL PROTECTED] > Subject: Office 2003 Research Pane services in Axis... > > Hi, > I'm trying to write a service in axis that can service the > new research pane in office 2003. The api for the pane is > very simple. There are two methods, Registration and Query, > both of which take a string with xml and return a string with xml. > > No matter what I try, office doesn't like what I'm sending > back. I think that my xml response is correct, so here's my question. > > In the sample .net services, they have an attribute on the > web service that looks like: > > <WebService(Namespace="urn:Microsoft.Search"> > > Now I know that this somehow associates that namespace with > the service. > I'm trying to figure out how to do this with axis. I've added: > > <namespace>urn:Microsoft.Search</namespace> > > to the services part of my wsdd file and reapplied it, but > that didn't change a thing. I know that .net in general can > talk to my service because my simple test client gets the xml > text back. > > I think it's a config thing that I've missed in axis, but I > can't find anything else beyond the namespace thing in the wsdd. > > Any ideas? > > thanks! > Carey > > > >
