tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiago H. de Paula Figueiredo (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (TAP5-2029) JPA annotations expose implementation details in service interfaces
Date Tue, 08 Oct 2013 00:16:42 GMT

     [ https://issues.apache.org/jira/browse/TAP5-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thiago H. de Paula Figueiredo reassigned TAP5-2029:
---------------------------------------------------

    Assignee: Thiago H. de Paula Figueiredo

> JPA annotations expose implementation details in service interfaces
> -------------------------------------------------------------------
>
>                 Key: TAP5-2029
>                 URL: https://issues.apache.org/jira/browse/TAP5-2029
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.3.6
>            Reporter: John Coleman
>            Assignee: Thiago H. de Paula Figueiredo
>            Priority: Minor
>
> The commit after and persistence context annotations are required on the service interface
definition thereby exposing internal implementation details (see below example from docs).
Details of implementation should be hidden at the interface level, both these annotations
break the rule.
> Perhaps this code could appear in the Impl classes, or be provided in configuration somehow?
> public interface UserDAO {
>    @CommitAfter
>    @PersistenceContext(unitName = "DemoUnit")
>    void add(User user);



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message