Ok, I wrote the jaxb.index file by hand and it takes care of that problem.
I'm somewhat surprised as I thought that such a file would be automatically
generated if my pojos are jaxb2 annotated. But there might be some separate
plugin or ant task for this. Does anyone know?
gnodet wrote:
>
> On 11/16/06, Anders Hammar <[EMAIL PROTECTED]> wrote:
>>
>> I believe I'm doing all this. I don't get null anymore, but what I get
>> now is
>> an XFireFault saying "Could not marshall type". This comes from a
>> JAXBException "se.a.b.c" doesnt contain ObjectFactory.class or
>> jaxb.index".
>> Any clues? I'm a little confused if a need to specify marshaller or any
>> other "helper" class, or if all this should be handled automatically as
>> long
>> as I specify annotations ("jsr181") and typeMapping ("jaxb2")?
>> In the stack trace I see AegisBindingProvider being used, which surprises
>> me
>> as I thought that was some other kind of binding than jaxb2...
>>
>
> The ObjectFactory or jaxb.index is the way for jaxb2 to discover how to
> marshal / unmarshal classes or xml. When you generate jaxb2 beans
> from an xsd, this class is automatically generated. I guess you need
> to write one by hand.
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context:
http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299s12049.html#a7396529
Sent from the ServiceMix - User mailing list archive at Nabble.com.
