[
https://issues.apache.org/jira/browse/OPENJPA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557792#action_12557792
]
Patrick Linskey commented on OPENJPA-147:
-----------------------------------------
The recent commit adds support for this feature, but currently requires that
the developer annotate interfaces with @ManagedInterface to enable the feature.
Is this appropriate? Any other ideas for configuration / interfaces?
One problem with @ManagedInterface is that it isn't intuitive for abstract
class support. Perhaps we should decide how we eventually want to support
abstract classes and see if we can make our managed interface support take that
into account.
> <T> T OpenJPAEntityManager.createInstance(Class<T> cls) fails when T is
> interface
> ---------------------------------------------------------------------------------
>
> Key: OPENJPA-147
> URL: https://issues.apache.org/jira/browse/OPENJPA-147
> Project: OpenJPA
> Issue Type: New Feature
> Components: jpa
> Reporter: Pinaki Poddar
> Fix For: 1.1.0
>
> Attachments: iface.trace.1.txt, iface.trace.2.txt, iface.trace.3.txt,
> iface.trace.4.txt, IPerson.java, TestInterface.java
>
>
> According to JavaDoc, OpenJPAEntityManager.createInstance() method
> public <T> T createInstance(Class<T> cls);
> behaves as follows:
> "Create a new instance of type <code>cls</code>. If <code>cls</code> is
> an interface or an abstract class whose abstract methods follow the
> JavaBeans convention, this method will create a concrete implementation
> according to the metadata that defines the class"
> The method fails when T is an interface. The failure may be due to incorrect
> user configuration, however, further
> information on this extension method is not available in OpenJPA
> documentation.
> Firstly, how to specify metadata for a interface that has bean-style methods?
> Possibilities are:
> a) Annotating the Java interface definition with @Entity
> b) Specifying in <class>org.acme.IPerson</class> in persistence.xml
> Either of the above fails. a) fails at parsing b) fails with "no metadata"
> There may be a correct but undocumented way of specifying a managed
> interface. If that is the case, then this JIRA report should be treated as a
> documentation bug.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
