> Is there any plan to support abstract types for JAXB 1.0? If not, am I
> out of luck or is there any approach I can use to still use JAXB to do
> most stuff and hand code the java corresponding to abstract types?
In JAXB1.0, I think a provide is not required to support type
substitution through @xsi:type. And RI isn't going to.
An abstract complex type is a sign that @xsi:type is going to be used in
the instance document, so that's why we raise an error.
Now this doesn't mean that other providers are not going to support this
feature since they are allowed to do so by the spec. But I'm not aware
of any such implementation right now.
For RI, unfortunately there's not much workaround. If your application can
ignore the part that use the type substitution, you can cut the relevant
part from your schema.
Or if you are really desperate, I guess technically you can transform it
to another format first then unmarshal it.
Sorry.
regards,
--
Kohsuke KAWAGUCHI 408-276-7063 (x17063)
Sun Microsystems kohsuke.kawaguchi_at_sun.com