History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEADEV-21615
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Normal Normal
Assignee: Alexey Kudravtsev
Reporter: Taras Tielkes
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
IDEA: Development

spring + aop: pointcut language sometimes starts to resolve type in other open project

Created: 24 Sep 07 15:49   Updated: 06 Dec 07 18:52
Component/s: J2EE.Spring
Fix Version/s: Selena 7312, Selena 7.0.2

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Text File already-disposed.txt (19 kb)

Issue Links:
Duplicate
 
This issue is duplicated by:
IDEA-15211 spring + aop: good code red: use of b... Resolved

Build: 7,294
Fixed in build: 7,564


 Description  « Hide
I've seen this a few times with 7294.

While editing a spring xml file that contains various <aop:*> elements, the resolving of Java types in pointcut language (packages, classes) switches from resolving in current project to resolving in another project that I had open.

For example, in one case I had a project open that used spring facet, and another project open that contained a plugin module. At some point during editing, the project using spring started to resolve Java types in pointcut lanuage using the classpath of the other project: I would get package completion variants for com.intellij. etc. When closing the plugin project, the project using spring would start throwing "Already disposed" exceptions (all submitted).

Perhaps some kind of data race?



 All   Comments   Work Log   Change History      Sort Order:
Taras Tielkes - 24 Sep 07 15:51
Example of exception thrown in spring project after closing the other project.

Taras Tielkes - 24 Sep 07 16:19
I've submitted the exceptions with my JIRA login, so you may be able to find related information using that.

Taras Tielkes - 27 Sep 07 22:35
I've just experienced this again using #7312, so most likely it's not completely fixed yet.

Taras Tielkes - 19 Oct 07 14:03
I'm still occasionally seeing this in #7361.

Taras Tielkes - 07 Nov 07 00:42
This is still present in latest 7.0.2 EAP.

One detail that I noticed is that the two projects that I had open shared some package names.
To be more precise:

  • no sources or source directories were shared between the two projects
  • however, project A contains a "foo.bar.p1..." package hierachy, and project B contains a "foo.bar.p2..." package hierarchy.

I'm not sure if the problem is related to this detail, just mentioning it.

Despite many attempts, I did not succeed in coming up with a reproducible testcase. However, I can reproduce the problem with approx. 10 minutes of effort (in case it would help to run a build with some additional assertions or something...)


Irina Petrovskaya - 08 Nov 07 20:00
b 8005: the problem still exists: if i have 2 open projects, the paths in pointcut expressions in one project appear not resolved, and code completion suggests the packages from different project

Taras Tielkes - 19 Nov 07 19:54
I don't want to complain too much, but this is a real productivity killer.
It forces me to quit IDEA, restart and reopen all projects I previously has open.

Please let me know if I can in any way assist in tracking down the cause.