Hi Philip,
OpenJPA specific annotations do not have a counterpart in orm.xml.
The pain is obvious but that the orm.xml XSD did not allow a
<vendor-extension> clause makes it somewhat more difficult to get these
vendor-specific annotations in xml descriptors.
If a persistent entity in annotated as
@Entity
@VendorA
@VendorB
public class Schizophrenic {...}
In compile-time both @VendorA and @VendorB definition is available.
In runtime only @VendorA is available.
How does @VendorB impact the runtime? Aren't they simply ignored?
Philip Aston wrote:
>
> So far as I can tell, that useful openjpa features such as fetch groups
> and large result sets can only be configured declaratively with openjpa
> specific annotations.
>
> If true, this seems somewhat limiting:
>
> 1. It is impossible to use these features when writing provider
> neutral JPA code.
> 2. Different versions of the code are required if different settings
> are needed in different environments.
>
> Have I missed something?
>
> - Phil
>
>
>
--
View this message in context:
http://n2.nabble.com/Alternatives-to-annotations-for-metadata--tp2213505p2237202.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
