RE: [wtp-dev] Client Access Exception of type DANGLING_REFERENCE

[John Lanuti <jlanuti@xxxxxxxxxx>]

Hey Ted,

That is definately an option we are
still willing to explore, however at this stage of the game for 0.7, we
cannot make such a drastic change.
We can investigate this for M8 though
because 1.0 is more of the API release.

Thanks,

John Lanuti
Software Engineer, IBM Rational
jlanuti@xxxxxxxxxx
t/l 441-7861

"You see this wandering soul, he's never gonna stop, because he loves
and he feels this world can grow. 
He's not afraid of feeling, he loves what he believes, he feels, and he
grows."  - Of A Revolution

"Ted Bashor" <tbashor@xxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

06/29/2005 02:30 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	RE: [wtp-dev] Client Access Exception of type DANGLING_REFERENCE

There was a suggestion awhile
back to move to using some sort of Soft or WeakReference caching mechanism
instead of requiring this type of api.
Has anyone had a chance to investigate
the feasibility of that yet?
 
-Ted
-----Original Message-----
From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]On
Behalf Of John Lanuti
Sent: Wednesday, June 29, 2005 10:53 AM
To: General discussion of project-wide or architectural issues.
Subject: Re: [wtp-dev] Client Access Exception of type DANGLING_REFERENCE


Konstantin, 

When you access an artifact edit, you must release it.  So, anytime
you want to get an artifact edit, you want a try finally block
like the following: 

ArtifactEdit edit= null 
try  { 
edit = EARArtifactEdit.getEARArtifactEditForWrite( earhandle );
//do stuff 
} finally { 
   if (edit !=null) 
       edit.dipose() 
} 

That will prevent the client access exception. 

Hope that helps, 

John Lanuti
Software Engineer, IBM Rational
jlanuti@xxxxxxxxxx
t/l 441-7861

"You see this wandering soul, he's never gonna stop, because he loves
and he feels this world can grow. 
He's not afraid of feeling, he loves what he believes, he feels, and he
grows."  - Of A Revolution

"Konstantin Komissarchik" <kosta@xxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

06/29/2005 01:40 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	[wtp-dev] Client Access Exception of type DANGLING_REFERENCE

Hi, 
  
I keep getting this: 
  
org.eclipse.wst.common.internal.emfworkbench.edit.ClientAccessRegistryException
This exception was generated to indicate an invalid usage of reference
counts. Please examine the stack trace. 
 Client Access Exception of type DANGLING_REFERENCE
  
When I make the following call: 
  
EARArtifactEdit.getEARArtifactEditForWrite( earhandle );
  
Am I doing something wrong? I am using the 6/17 i-build. Is this something
that was fixed in a later i-build? 
  
Thanks, 
  
- Konstantin_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev