[
https://issues.apache.org/jira/browse/TAP5-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thiago H. de Paula Figueiredo updated TAP5-2029:
------------------------------------------------
Component/s: (was: tapestry-jpa)
tapestry-ioc
Changing the component from tapestry-jpa to tapestry-ioc as this is actually a
shortcoming in Tapestry-IoC.
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
