Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[tigerstripe-dev] RE: Annotations - probable serious bug

Title: Re: Annotations - probable serious bug
OK - so I have figured out what my problem was. basically, there is no bug in either the basic annotations framework or I think in my TS integration code. What had happened was that my resources.xml file had a number of references to the same .annotations file which caused that to be loaded multiple (3) times which gave 3 times as many annotations as I should have had. This came about when I was working on my router and at various times I experimented with different forms of the URI for the .annotations file; all seemingly valid, and all recorded faithfully in my resources.xml file. So, all I had to do what clean up my resources.xml and all was fine.
 
Cheers,
 
JohnW


From: John Worrell (jworrell)
Sent: 02 May 2008 18:12
To: Eric Dillon (erdillon)
Cc: Steve Jerman (stjerman); Tigerstripe Developers
Subject: RE: Annotations - probable serious bug

Eh what??? Are you talking about a bug Steve has found? Or the one that I mentioned below.
 
If it is the one I was talking about below, I think I have figured out what the problem is.
 
Let's not panic!
 
Cheers,
 
JohnW


From: Eric Dillon (erdillon)
Sent: 02 May 2008 18:06
To: John Worrell (jworrell)
Cc: Steve Jerman (stjerman); Tigerstripe Developers
Subject: Re: Annotations - probable serious bug
Importance: High

Hi Steve,

First things first :-)... Annotations thru what mechanism? Do you get the same effect when you annotate a file or not? This could point towards an integration problem with the Annotation-Tigerstripe integration?

Eric


On 5/2/08 9:37 AM, "John Worrell (jworrell)" <jworrell@xxxxxxxxx> wrote:

Hi Eric,

I seem to have encountered what looks like a fairly serious bug associated with reading the annotations from the store. Basically, my annotations seem to breed... or rather each becomes instantiated multiple times. I'm trying to figure out what the problem is.

And, I think there is something a bit screwy in the storage anyway...

Cheers,

JohnW



Back to the top