Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335554 - "The resource tree is locked for modifications" when editing ejb-jar.xml
Summary: "The resource tree is locked for modifications" when editing ejb-jar.xml
Status: CLOSED INVALID
Alias: None
Product: WTP EJB Tools
Classification: WebTools
Component: jst.ejb (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: jst.ejb CLA
QA Contact: Kaloyan Raev CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-27 06:01 EST by Wolfgang Knauf CLA
Modified: 2014-02-06 14:42 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Knauf CLA 2011-01-27 06:01:47 EST 
Build Identifier: 

When editing "ejb-jar.xml" for an EJB3 project, every time I save it, I see this error message in ".log":

!ENTRY org.eclipse.core.resources 4 380 2011-01-27 11:43:42.936
!MESSAGE The resource tree is locked for modifications.


This happens with wtp-M-3.2.3-20110121005429, but I don't know whether this is a regression or I just never noticed it ;-).

My sample project can be found here: 
http://www.cs.hs-rm.de/~knauf/KomponentenArchitekturen2008/stateless/Stateless.ear
Import EAR file to a JBoss 5 server runtime.
Then select EJB project => rigt click => "Java EE tools" => "Generate Deployment descriptor" (for this you will need the new WTP version, because there was an encoding bug fixed, see #221212). 
Then change something in this file and save it. Error message is logged.

I also see this when importing an EAR file, which already contains an EJB jar.


Reproducible: Always
Comment 1 Wolfgang Knauf CLA 2011-01-27 08:49:30 EST 
Happens also in wtp-I-3.3.0-20110127064115
Comment 2 Wolfgang Knauf CLA 2014-02-06 14:42:21 EST 
I don't see this anymore with 3.5