b job);
>>
>> where there exists the following classes:
>>
>> public class BigJob extends Job { ... }
>> public class SmallJob extends Job {...}
>>
>> In this case, Job will be bound to XML elements, but BigJob and
> SmallJob
>> will not. XFire does support this, documented at
>> http://xfire.codehaus.org/Aegis+Inheritance. Howe
uot;/>
http://localhost:8080/services/GetDummy"/>
InJeNiErO.
>I pessimistically think that you've found a bug. Could you please drop
>this into JIRA?
> -----Original Message-----
> From:
I pessimistically think that you've found a bug. Could you please drop
this into JIRA?
> -Original Message-
> From: Segal, Jeffrey [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 01, 2007 4:31 PM
> To: cxf-user@incubator.apache.org
> Subject: Migrating XFire/Aegi
I'd like to bump the question posed a few weeks ago by Nalyd (see
http://www.nabble.com/Aegis-inheritance-tf4668138.html#a13335122).
I am attempting to ensure that some additional classes which are not
present in my service interfaces get bound along with the others, a
common problem given a serv
