EJB2.1RefactoringSupportIn5.5

As discussed in the team meeting, the EJB refactoring support hasn't been rewritten to Retouche yet and since it seems that there are no resources to do that before the feature freeze, I'm proposing that we drop it for 6.0. Note that this concerns only EJB 2.1.

In short, the refactoring support for EJB 2.1 in 5.5 checks for the references of the object being refactored in ejb-jar.xml and updates the references as needed. More specifically, it includes checks for the following elements:

  • Entity Beans:
  • rename / find usages / move / safe delete support for local interfaces, local home interfaces and for bean classes
  • rename / find usages / safe delete support for query methods
  • rename support for CMR fields
  • Session Beans:
  • rename / find usages / move / safe delete support for local interfaces, local home interfaces, remote interfaces, home interfaces and for bean classes
  • Message Driven Beans:
  • rename / find usages / move / safe delete support for bean classes
  • Other:
  • forbids renaming / deleting mandatory methods, such as ejbCreate

Due to the differences between the old and new Java infrastructure, the EJB refactoring would need to be pretty much completely rewritten. It is hard to say how much time it would take, but given that the current implementation is > 7000 lines, it would not be a matter of a day or two.

In case the support will be dropped, a warning message would still be shown to the user when performing refactoring in an EJB 2.1 project. Dropping the support has no effect on Java EE 5 / EJB 3 refactorings.

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo