Dan, Would you be so kind as to explain exactly what happens as a result of that AegisServiceConfiguration? Or did you mean that we should keep it so that XFire-derived configurations that use it continue to work without having to take out reference to it?
Meanwhile, I was reading the insides of Aegis today. I note some stuff that isn't documented, I think ( uri='xxxxx' to control the soap binding?). Is the doc in svn? > -----Original Message----- > From: Dan Diephouse [mailto:[EMAIL PROTECTED] > Sent: Saturday, September 08, 2007 6:51 PM > To: [email protected] > Subject: Re: Was there a plan for more aegis? > > Benson Margulies wrote: > > I note the existence of AegisServiceFactoryBean (which implements > > nothing) > Thats cruft which I created which should be deleted. > > and AegisServiceConfiguration, which also seems to be very > > slim. > This makes provides the necessary configuration settings so that your > service works exactly as it did in XFire. So I'd like to keep this around > > Regards, > - Dan > > -- > Dan Diephouse > MuleSource > http://mulesource.com | http://netzooid.com/blog
