I've also found that you can specify the classloader when getting a new
instance to workaround this:
JAXBContext.newInstance( "some.package",
some.package.ClassInJar.class.getClassLoader());
Cheers,
Brett
Ed Mooney wrote:
> Hi Marek,
>
> We've fixed this bug for FCS. The workaround (as you've discovered) is
> to put jaxb.properties somewhere in your classpath.
>
> Regards,
> --
> Ed Mooney |Sun Microsystems, Inc.|Time flies like
> Java Web Services |UBUR02-201 |an arrow, but
> Ed.Mooney_at_Sun.COM |1 Network Drive |fruit flies like
> 781-442-0459 |Burlington, MA 01803 |a banana. Groucho
>
> Marek Malowidzki wrote:
>
>> Hi,
>>
>> It seems that the JAXB RI cannot extract jaxb.properties files when
>> they are
>> included in jar archives. I include the jar with jaxb.properties files
>> in the
>> classpath and Java classes are found, but the property files aren't.
>> When I put
>> the files into plain (unzipped) directories, everything is ok.
>> Similarly for the
>> bgm.ser files.
>>
>> Marek