RE: [TM4J-users] Bug in Topic Class?

[Kal A. <ka...@te...>]

Hi Norbert,

I've had a look at your code and there is nothing wrong with that - I can
also reproduce the problem, so it looks like this is a TM4J bug. I'll have a
look at this when I get a chance (prob. not until tonight) and let you know
if I find the problem. If you would like to have a look in the source code
for yourself, my guess is that the problem is probably related to
TopicImpl.removeAssociationToType() not behaving correctly.

Cheers,

Kal

> -----Original Message-----
> From: tm4...@li...
> [mailto:tm4...@li...]On Behalf Of Norbert
> Hartl
> Sent: 24 August 2001 19:47
> To: TM4J user list
> Subject: [TM4J-users] Bug in Topic Class?
>
>
> Hi,
>
> I've got a problem with the tm4j API. Maybe I misunderstood
> the purpose.
>
> Is the setTypes() method supposed to overwrite any exisiting type
> value?
>
> I have
>
> Topic A with Topics  T1 as a type of Topic A
>
> and an Topic Array B which conatains Topics T3.
>
> If I call A.setTypes(B) then I should get a Topic A
> with Topics T3 and T4 stored as types, right?
>
> But I get a Topic A with T1, T2 as Types.
>
> I append a short piece of testcode to make clear what
> I meant.
>
> I would be very glad to hear if this is a tm4j problem
> or if I misunderstood the whole thing.
>
> thanks in advance,
>
> Norbert
>