[amattas]

When renaming a package under an EJB3.0 bean, the bean breaks. Part of this is caused due to the fact that persistance.xml doesn’t refactor. Also anything with an interface seams to break as well, havn’t figured out why.

Heirchy for my project is

AcountEJB
—-com.mycompany.mybean
——–AccountMgrLocal
——–AccountMgr
——–EntityManagerHelper
——–Groups
——–GroupsFacade
——–GroupsFacadeLocal
——–Users
——–UsersFacade
——–UsersFacadeLocal

Eclipse Installation Detail is

*** Date:
Thursday, June 21, 2007 1:29:45 PM EDT

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.6.0_01

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 5.5.1 GA
Build id: 20070521-5.5.1-GA

*** Eclipse details:
Eclipse SDK

Version: 3.2.2
Build id: M20070212-1330

Eclipse Project SDK

Version: 3.2.2.r322_v20070104-dCGKm0Ln38lm-8s
Build id: M20070212-1330

Eclipse Platform

Version: 3.2.2.r322_v20070119-RQghndJN8IM0MsK
Build id: M20070212-1330

Eclipse RCP

Version: 3.2.2.r322_v20070104-8pcviKVqd8J7C1U
Build id: M20070212-1330

Eclipse Plug-in Development Environment

Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
Build id: M20070212-1330

Eclipse Java Development Tools

Version: 3.2.2.r322_v20070104-R4CR0Znkvtfjv9-
Build id: M20070212-1330

Eclipse Graphical Editing Framework

Version: 3.2.2.v20070208
Build id: 20070208-1315

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\java\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
e18_7c
-vm
C:\WINDOWS\system32\javaw.exe

[Riyad Kalla]

amattas,
You mentioned this in another thread, I’ve filed it as a bug for the dev team to look into, thanks for the heads up.

[amattas]

This one is slightly different than the prior bug I mentioned, the first one had to do with the add remove module command. This one occurs when refactor->renaming. 🙂 Thanks for the support

[Riyad Kalla]

amattas,
I want to clarify this bug, please point out where I’m right/wrong:

1) When you refactor and change the name of a package a bean lives in, the bean can no longer be deployed?

2) Even if you manually fix the persistence.xml file, it still doesn’t deploy correctly?

3) In relation to #1, what happens when you refactor the *name* of the bean itself… same story?

[amattas]

If you refactor the name of the Bean itself it will not deploy properly in the EAR package. (application.xml file, previous bug I mentioned)

If you refactor a package within the bean, it doesn’t work properly, even after editing the persistance.xml file I still have to re-reverseengineer the database for EJB3, it seems to affect classes that have an interface.

[Author]

Posts