This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 178790 - Inconsistencies between EJB facade and JPA controller
Summary: Inconsistencies between EJB facade and JPA controller
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Persistence (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Sergey Petrov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-17 07:42 UTC by Petr Jiricka
Modified: 2015-09-17 13:10 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2009-12-17 07:42:44 UTC
Given existing entity classes, one can create either an EJB facade for these classes, or a JPA controller. However, the generated code is quite inconsistent between the two:

- names of the finder methods that return all entities: findCustomerEntities() (controller) vs. findAll() (facade)
- names and parameter type of the finder methods that return a single entity: findCustomer(Integer id) vs. find(Object id)
- finder parameters when finding a subset of results: (int maxresults, int firstresult) vs. (int[] range)
- there seems to be a difference in the TRANSACTIONAL vs. EXTENDED persistence context type and the closing of EntityManager (but I guess that's understandable)
Comment 1 Martin Balin 2015-09-17 13:10:31 UTC
Report from old NetBeans version. Due to code changes since it was reported likely not reproducible now. Feel free to reopen if happens in 8.0.2 or 8.1.