On Fri, 2008-01-04 at 11:52 -0500, Daniel Kulp wrote: > FYI: I deployed a 2.1 snapshot yesterday.
Silly me. Anthony, knock yourselves out :-) > > Dan > > > On Friday 04 January 2008, Benson Margulies wrote: > > Next week shouldn't be a problem. The override list has been there > > since forever. It's a lot easier to configure on the 2.1 trunk that it > > was in XFire or 2.0.3, but it's always been there as a property of the > > service -- a list of class names that get mapped and added to the > > schema. Typically, it's advertised as being needed to deal with > > inheritance and exceptions. > > > > I do strongly suggest doing an svn co of the trunk even if you don't > > compile it, as I'm not going to write enough doc to obviate the need > > to read the source code. > > > > If I can offer any help in building from svn, I'd like to, since I > > anticipate that you will hit issues, and having to make a snapshot for > > every tiny tweak is likely to be frustrating all around. I've done > > this on both Windows and Linux myself. > > > > Also, I'd like to stick with the ASF convention of keeping this > > conversation on cxf-user whenever possible so that others can benefit. > > > > On Fri, 2008-01-04 at 11:30 -0500, Vespa, Anthony J wrote: > > > Okie - rather than compile this ourselves (I've had some issues in > > > the past with it) we'll wait for the next snapshot - you think early > > > next week? > > > > > > Quick question...is the Aegis override list something new? I don't > > > think that I'm familiar with that function. In one or two of our > > > services we return a type in a response that isn't defined by > > > another function, so this would help us with a kludgey work around; > > > how does one include data types not directly called by a function? > > > > > > -----Original Message----- > > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > > Sent: Friday, January 04, 2008 11:25 AM > > > To: Vespa, Anthony J > > > Cc: Claydon, Barnaby > > > Subject: RE: anyType is not the same thing as xs:any :-) > > > > > > Anthony, > > > > > > If you grab the current trunk, I think that you might find that it > > > does what you need. > > > > > > You need to ensure that all the complex types you want to use are > > > included in the WSDL. To do that, you need to mention them in the > > > service or include them in the Aegis override list. > > > > > > If you do that, then you will get Javascript constructors for all of > > > them, and you can use the 'any holder' scheme I added to match them > > > up with the 'any' or 'anyType' slots in your service's parts. > > > > > > I'm not inclined to make a new 2.1 snapshot this week, since the > > > auto-build infrastructure for CXF is down until next week. > > > > > > --benson > > > > > > On Fri, 2008-01-04 at 10:29 -0500, Vespa, Anthony J wrote: > > > > Hi Benson, > > > > > > > > > > > > > > > > Happy New Year – hope you had a pleasant holiday. > > > > > > > > > > > > > > > > Just wanted to check in where we were with the work you were doing > > > > – I’m still sifting through my email but I can’t find where we > > > > ended up or if you were still waiting for a word from us. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > > > Tony > > >
