[Tm4j-developers] Re: TopicMapFactory refactoring

[<Ren...@da...>]

Hello,

I am that impertinent to write to the developers mailinglist, because I=
 think=20
this topic is placed best here. At first I want to epress my thanks to =
Kal=20
Ahmed for starting to fix some issues of the TopicMapFactory that fast.=
 That's=20
why I can wait a little bit with my implementations and do not have to =
refactor=20
code myself ;)

I am convinced with the new changes the whole process of creating a Top=
icMap=20
will be more consistent, comfortable and intuitive. Nevertheless I  thi=
nk that=20
this changes can not be the final solution. If I had understood Kal Ahm=
ed=20
right, he is also thinking this way. He mentioned two or three alternat=
ives he=20
is considering to be suitable. Over the weekend I also thought a little=
 bit=20
about this topic and came to a conclusion:

I think the best variant is already realized in the TM API interfaces. =
Every=20
single TopicMapObject (except from leaves) has one or more factory meth=
ods to=20
create its direct childs and/or add methods for references like the sub=
ject=20
indicator. The benefit would not only consist of an extreme increase of=
=20
usability but also of the fact that some unnecessary mistakes on part o=
f the=20
user of the TM4J API could be entirely abolished:

- Using a wrong factory when creating a TopicMapObject
- Adding a Topic that does not fit to a special TopicMap
...

Consequently the number of Exception are thrown while the creating proc=
ess of a=20
TopicMap could be reduced to a tolerable level ;).=20
But I also see that you have much more to do than refactoring your Code=
.

Greetings to all... =20


Ren=E9 Freude (Ren...@da...)=20

DaimlerChrysler AG=20
Research - Information & Communication=20
Software Technologies / Methods & Tools=20
(RIC/SM)=20

Berlin / Germany                                                   =