[17:09] dmlloyd: ah.  I think it's on the classpath, *but* the jaxb-api is using the wrong classloader to look it up for some reason...
[17:10] stigi:   but using the same jaxb code in a normal apps main will work
[17:10] dmlloyd: I bet if you googled for jaxb classpath problems, you'd find something
[17:10] dmlloyd: sure, because apt probably uses a different classloader structure
[17:11] stigi:   so the problem is more jaxb or more apt?
[17:12] dmlloyd: I'd say jaxb myself, just because it looks like they're using ClassLoader.loadClass() instead of Class.forName()