Incoming change from me that might not be likable around part configuration in the RFSB

There's an ancient festering mess in Aegis related to the documented capability to configure schema characteristics of method parameters. It's the usual three stooges: minOccurs, maxOccurs, and nillable. Aegis has a lot of confusion to go around here. In general, Aegis type objects carry these att

Re: Incoming change from me that might not be likable around part configuration in the RFSB

I now see the root of this insanity. DefaultServiceConfiguration refuses to take a minOccurs spec for a primitive type. I guess I'll be removing that clause and seeing what happens to me. On Sun, Aug 23, 2009 at 8:10 AM, Benson Margulies wrote: > There's an ancient festering mess in Aegis related

Re: Incoming change from me that might not be likable around part configuration in the RFSB

Well, something of a faux alarm. It turns out that my code works fine with no service config mods, though I'm going to go ahead and commit some neatening of DefaultServiceConfiguration. I had messed up the assert in the test case, convinced myself that the service config wasn't cooperating, and the