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 34644 - ProjectMember operations have to operate over DataSystem
Summary: ProjectMember operations have to operate over DataSystem
Status: CLOSED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 3.x
Hardware: All All
: P1 blocker (vote)
Assignee: Vitezslav Stejskal
URL:
Keywords:
Depends on:
Blocks: 30962
  Show dependency tree
 
Reported: 2003-06-26 20:17 UTC by Jan Pokorsky
Modified: 2004-04-19 16:20 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
patch using the DataSystem API (3.42 KB, patch)
2003-06-26 20:18 UTC, Jan Pokorsky 		Details | Diff
xtests output + thread dump (13.10 KB, patch)
2003-06-26 20:19 UTC, Jan Pokorsky 		Details | Diff
xtests results (4.65 KB, text/html)
2003-06-26 20:52 UTC, Jan Pokorsky 		Details
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 Jan Pokorsky 2003-06-26 20:17:13 UTC 
At least before there will be introduced the File
Manipulation API or something like that which
would replace the DataSystem API.

I have prepared a patch for this but there might
be some problems with timing (you know, datasystem
;-) I have been running projects/core xtests
several times and it freezes always during
ProjectMemberTest. The attached thread dump did
not help much. OperationsTest was passed
successfully. Maybe you will be luckier.

FYI: jdk1.4.1_02-b06 + ant1.5.3-1/ant1.4.1
Comment 1 Jan Pokorsky 2003-06-26 20:18:42 UTC 
Created attachment 10818 [details]
patch using the DataSystem API
Comment 2 Jan Pokorsky 2003-06-26 20:19:43 UTC 
Created attachment 10819 [details]
xtests output + thread dump
Comment 3 Jan Pokorsky 2003-06-26 20:49:27 UTC 
Progress: I left tests to run by mistake after taking the thread dump
and almost all xtests pass through. It took an age (~10-20 min) to
continue running. The xtest suite (ProjectMemberTest) ended up with
result unknown for ProjectMemberTest.testPersistance. Some idea what
is wrong?
Comment 4 Jan Pokorsky 2003-06-26 20:52:34 UTC 
Created attachment 10820 [details]
xtests results
Comment 5 Vitezslav Stejskal 2003-06-27 09:33:43 UTC 
Thanks for the patch. I have no idea why it hung, the thread dump is
useless because it doesn't contain threads from inside the IDE (not
sure why, but I never saw this working in tests).

BTW, the patch isn't correct, it doesn't honor target names passed to
operations. I think, we will have to simulate this by calling two DO
operations in row like e.g. copy and rename. This doesn't look well
and we should probably use it only as a fallback when there is no
projectized operation handler registered in the system.
Comment 6 Pavel Buzek 2003-06-27 13:04:43 UTC 
ad Thread dump: I think that it's because you are doing a thread dump
on a different JVM then the one in which nb is running ;-) (the one
used by Ant). The same problem happens when you use "ant tryme".
Comment 7 Dusan Balek 2003-07-22 16:57:04 UTC 
Fixed by modifying the proposed patch to consider target names and
applying it.
Running projects/core xtests several times,
I have encountered only one deadlock related to ContainersList.Updater
Comment 8 Jan Becicka 2003-11-25 14:02:44 UTC 
As described in
http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the
current work on projects prototype has been stopped.

Marking issue as VERIFIED --->
Comment 9 Jan Becicka 2003-11-25 14:11:43 UTC 
---> CLOSED