Re: [Tm4j-developers] TopicMapFactory refactoring

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

Oops - itchy "Send" finger.

What I meant to add was:

I'm now in the process of going through the rest of the code base and upd=
ating=20
it so as to remove any uses of the deprecated methods.=20

The createXXX() methods now throw an IntegrityViolationException if the p=
arent=20
object is not from the same topic map as the factory you are using to cre=
ate=20
the child object. I propose that a similar restriction be placed on the=20
addXXX methods such as Topic.addOccurrence() to trap such potential error=
s.

Cheers,

Kal

On Friday 13 December 2002 16:16, Kal Ahmed wrote:
> Just to let you all know, the changes have now been checked into CVS.
>
> Cheers,
>
> Kal
>
> On Thursday 12 December 2002 16:20, Kal Ahmed wrote:
> > Folks,
> >
> > Further to Ren=E9's comments, I am now considering refactoring
> > TopicMapFactory so that all createXXX() methods require the parent ob=
ject
> > of the new object to be specified. This would mean that all the old
> > createXXX() methods would be deprecated in 0.8.0 and removed in the
> > following release.
> >
> > The alternative is to hold off on this change until after 0.8.0. So t=
he
> > question is, would you prefer to get an 0.8.0 release now or get one =
with
> > these API changes made in a little while (maybe another week...might =
make
> > a nice Xmas present ;-)
> >
> > At first I was reluctant to make the change for 0.8.0, but I'm now
> > thinking that the change should be made now, so unless I hear voices
> > raised against this course of action, I will start to make those chan=
ges
> > from tomorrow.
> >
> > Cheers,
> >
> > Kal

--=20
Kal Ahmed, techquila.com
XML and Topic Map Consultancy

e: ka...@te...
p: +44 7968 529531
w: www.techquila.com