Or make a bean that can be constructed over your interface by slurping up all the properties.
> -----Original Message----- > From: Daniel Kulp [mailto:[EMAIL PROTECTED] > Sent: Friday, October 19, 2007 12:18 PM > To: [email protected] > Cc: Roberto Druetto > Subject: Re: Problem with JAXB > > > Usually, you would create a abstract superclass and return that. > > That said, there are some ways to do it. See: > https://jaxb.dev.java.net/guide/Mapping_interfaces.html > > Dan > > > On Friday 19 October 2007, Roberto Druetto wrote: > > Thanks Jim, > > do you know how can I do the same thing? My intention is to "monitor" > > some devices (some methods that I can call from a client). The devices > > are different, so I don't have only one class... > > > > 2007/10/19, Jim Ma <[EMAIL PROTECTED]>: > > > Hi , > > > > > > If the method returns an interface , jaxb can not handle it and > > > throws exception . > > > This is the reason why it can not : > > > http://weblogs.java.net/blog/kohsuke/archive/2006/06/jaxb_and_interf > > >.html, FYI. > > > > > > Cheers > > > > > > Jim > > > > -- > J. Daniel Kulp > Principal Engineer > IONA > P: 781-902-8727 C: 508-380-7194 > [EMAIL PROTECTED] > http://www.dankulp.com/blog
