tm4j-users — Forum for users of the TM4J API or apps developed by this project.

[TM4J-users] FW: Madhuri garigipati

[Madhuri g. <mad...@ya...>]

wer    
http://anarchy.gr/ixalsib/mvpaelwhzei/bjh/ppipliwijh.php    Madhuri garigipati

[TM4J-users] Ο Γι ργος σου έχει στείλει ένα μήνυμα ...

[Badoo <nor...@ba...>]

Ο/η Γι ργος σου έχει στείλει ένα μήνυμα...

Το περιεχόμενο του μηνύματος και ο αποστολέας θα είναι ορατά μόνο σε σένα. Μπορείς να διαγράψεις το μήνυμά σου οποιαδήποτε στιγμή ή να απαντήσεις χρησιμοποιώντας το σύστημα ανταλλαγής μηνυμάτων. Για να δεις το περιεχόμενο του μηνύματος, απλά ακολούθησε αυτόν το σύνδεσμο:
http://eu1.badoo.com/0290997345/in/kMCGGzotPS8/?lang_id=19&m=63&mid=5044feb6000000000013000000556bb603bf8c4c01c2

Μερικά ακόμη άτομα από την περιοχή σου που είναι στο Badoo
Panagiotis (Θεσσαλονίκη, Ελλάδα)
Nono (Θεσσαλονίκη, Ελλάδα)
Swami (Θεσσαλονίκη, Ελλάδα)

http://eu1.badoo.com/0290997345/in/kMCGGzotPS8/?lang_id=19&m=63&mid=5044feb6000000000013000000556bb603bf8c4c01c2

Αν ο σύνδεσμος σε αυτό το μήνυμα δεν λειτουργεί, αντίγραψέ τον και επικόλλησέ τον στη γραμμή διευθύνσεων του προγράμματος πλοήγησης.

Αυτό το email αποτελεί μέρος της διαδικασίας για την παράδοση του μηνύματος που εστάλη από τον/την Γι ργος. Αν έχεις λάβει αυτό το email από κάποιο λάθος, παρακαλούμε αγνόησέ το. Μετά από λίγο το μήνυμα θα διαγραφεί από το σύστημά μας.

Να περνάς καλά!
Η Ομάδα του Badoo 

Έχετε λάβει αυτό το email από την Badoo Trading Limited (η ταχυδρομική διεύθυνση εμφανίζεται παρακάτω). 
http://eu1.badoo.com/impersonation.phtml?lang_id=19&email=tm4j-users%40lists.sourceforge.net&block_code=e198c9&m=63&mid=5044feb6000000000013000000556bb603bf8c4c01c2
Η Badoo Trading Limited είναι μία εταιρεία περιορισμένης ευθύνης εγγεγραμμένη σε Αγγλία και Ουαλία με Αριθμό Μητρώου 7540255 και εγγεγραμμένο γραφείο στη διεύθυνση 44a The Green, Warlingham, Surrey, CR6 9NA.

Re: [TM4J-users] question on Hybernate and MySQL

[Kal A. <tec...@gm...>]

Hi Yorgos

I think you will probably find that the version of Hibernate used in
TM4J is very old and so probably assumes a pretty old version of
MySQL. However I would be sort of suprised if that meant that it
wouldn't work with a newer version of MySQL as I don't think that it
does anything particularly version-specific with its MySQL access. I
would definitely recommend trying it out with a new version of MySQL
so that you get the benefit of security/performance fixes in the
database.

Cheers

Kal (reposted from an email address that hopefully the list will recognize
this time!)

On Wed, Dec 8, 2010 at 5:34 PM, Yorgos Tryfon <dra...@gm...> wrote:

> Hello,
> (I posted this question in the forum, but it seems that there is no much
> movement in the forum and I decided to re-post it here)
>  I would like to know if the *Hybernate * that you use with TM4J can work
> with the current *MySQL* or requires some older MySQL version.
> I am interested to use TM4J and store my data on MySQL, but I woudn't want
> to have problems with MySQL version. Could somebody help me with this
> information? Best regards Yorgos Tryfon
>
>
> ------------------------------------------------------------------------------
> This SF Dev2Dev email is sponsored by:
>
> WikiLeaks The End of the Free Internet
> http://p.sf.net/sfu/therealnews-com
> _______________________________________________
> Tm4j-users mailing list
> Tm4...@li...
> https://lists.sourceforge.net/lists/listinfo/tm4j-users
>
>

[TM4J-users] question on Hybernate and MySQL

[Yorgos T. <dra...@gm...>]

Hello,
(I posted this question in the forum, but it seems that there is no much
movement in the forum and I decided to re-post it here)
I would like to know if the *Hybernate * that you use with TM4J can work
with the current *MySQL* or requires some older MySQL version.
I am interested to use TM4J and store my data on MySQL, but I woudn't want
to have problems with MySQL version. Could somebody help me with this
information? Best regards Yorgos Tryfon

Re: [TM4J-users] Problem to create a new topic using the name of a deleted topic

[Dicheva, D. <dic...@ws...>]

Lars - thank you so much!! This is so helpful.

All the very best,
Darina 

> -----Original Message-----
> From: Lars Heuer [mailto:he...@se...] 
> Sent: Wednesday, June 11, 2008 11:10 AM
> To: Dicheva, Darina
> Cc: tm4...@li...; Lars Johnsen; 
> tm4...@li...
> Subject: Re: Problem to create a new topic using the name of 
> a deleted topic
> 
> Hi Darina,
> 
> > Thanks for your idea - it seems good; what do you mean by item 
> > identifiers/source locators - subjectIdentifier? subjectLocator?
> 
> I meant "source locators" which have been renamed into "item 
> identifiers" in the TMDM.
> 
> The "TopicMapObject" base class has the methods 
> "addSourceLocator(Locator)", "removeSourceLocator(Locator)" 
> and "getSourceLocators()".
> 
> I assume that your code (with topic name merging enabled) looks like
> this:
> 
> Fragment A:
> 
>      Topic topicA = tm.createTopic();
>      TopicName nameA = topic.createTopicName("Foo", null);
>      // Here some occurrences, assocs etc.
> 
> 
> Fragment B:
> 
>     Topic topicB = tm.createTopic();
>     TopicName nameB = topic.createTopicName("Foo", null);
> 
> 
> Result: The topics "topicA" and "topicB" are merged since 
> they have the same name "Foo".
> 
> 
> The equivalent code using my solution would look like this 
> (topic name merging NOT enabled!):
> 
> Fragment A:
>      Topic topicA = tm.createTopic();
>      Locator iidA = tm.createLocator("http://www.example.org/#" +
>      "Foo");
>      topicA.addSourceLocator(iidA);
>      TopicName nameA = topic.createTopicName("Foo", null);
>      // Here some occurrences, assocs etc.
> 
> 
> Fragment B:
>     Topic topicB = tm.createTopic();
>     Locator iidB = tm.createLocator("http://www.example.org/#" +
>      "Foo");
>     topicB.addSourceLocator(iidB);
> 
> Result: The topics "topicA" and "topicB" are merged because 
> they have the same source locator (<http://www.example.org/#Foo>).
> 
> Maybe you have to catch the "TopicMustMergeException" if you 
> add the source locator to the topics, that depends on your "automerge"
> setting. If "automerge" is not enabled, you can catch that 
> exception and merge the topics manually via Topic#mergeIn(Topic).
> 
> > In other orders, how the merge algorithm works in case merge by 
> > topicName is false?
> 
> Merging is done, if two topic have:
> * at least one equal locator in their [subject identifiers] 
> properties,
> * at least one equal locator in their [source locators] properties,
> * at least one equal locator in their [subject locators] properties,
> 
> See also: <http://www.isotopicmaps.org/sam/sam-model/#d0e739>
> 
> (In TM4J, the [subject locators] property does not exists, 
> since it can handle max. one subject locator (XTM 1.0 legacy)).
> 
> Best regards,
> Lars
> --
> Semagia
> <http://www.semagia.com>
> 
> 
> 

Re: [TM4J-users] Problem to create a new topic using the name of a deleted topic

[Lars H. <he...@se...>]

Hi Darina,

> Thanks for your idea - it seems good; what do you mean by item
> identifiers/source locators - subjectIdentifier? subjectLocator?

I meant "source locators" which have been renamed into "item
identifiers" in the TMDM.

The "TopicMapObject" base class has the methods
"addSourceLocator(Locator)", "removeSourceLocator(Locator)" and
"getSourceLocators()".

I assume that your code (with topic name merging enabled) looks like
this:

Fragment A:

     Topic topicA = tm.createTopic();
     TopicName nameA = topic.createTopicName("Foo", null);
     // Here some occurrences, assocs etc.


Fragment B:

    Topic topicB = tm.createTopic();
    TopicName nameB = topic.createTopicName("Foo", null);


Result: The topics "topicA" and "topicB" are merged since they have
the same name "Foo".


The equivalent code using my solution would look like this (topic name
merging NOT enabled!):

Fragment A:
     Topic topicA = tm.createTopic();
     Locator iidA = tm.createLocator("http://www.example.org/#" +
     "Foo");
     topicA.addSourceLocator(iidA);
     TopicName nameA = topic.createTopicName("Foo", null);
     // Here some occurrences, assocs etc.


Fragment B:
    Topic topicB = tm.createTopic();
    Locator iidB = tm.createLocator("http://www.example.org/#" +
     "Foo");
    topicB.addSourceLocator(iidB);

Result: The topics "topicA" and "topicB" are merged because they have
the same source locator (<http://www.example.org/#Foo>).

Maybe you have to catch the "TopicMustMergeException" if you add the
source locator to the topics, that depends on your "automerge"
setting. If "automerge" is not enabled, you can catch that exception
and merge the topics manually via Topic#mergeIn(Topic).

> In other orders, how the merge algorithm works in case merge by
> topicName is false?

Merging is done, if two topic have:
* at least one equal locator in their [subject identifiers] properties,
* at least one equal locator in their [source locators] properties,
* at least one equal locator in their [subject locators] properties,

See also: <http://www.isotopicmaps.org/sam/sam-model/#d0e739>

(In TM4J, the [subject locators] property does not exists, since it
can handle max. one subject locator (XTM 1.0 legacy)).

Best regards,
Lars
-- 
Semagia 
<http://www.semagia.com>

Re: [TM4J-users] Problem to create a new topic using the name of a deleted topic

[Dicheva, D. <dic...@ws...>]

Hi Lars,

It seems that I solved my problem by using two TopicMapSystems - one
with merge by topicname set to false (which I normaly use, i.e. when
updating topics) and another one with that feature set to true (which I
only use to merge two files).

Thanks for your idea - it seems good; what do you mean by item
identifiers/source locators - subjectIdentifier? subjectLocator? In
other orders, how the merge algorithm works in case merge by topicName
is false?  

Thanks a lot for your help!

Cheers,
Darina 

> -----Original Message-----
> From: Lars Heuer [mailto:he...@se...] 
> Sent: Wednesday, June 11, 2008 8:31 AM
> To: Dicheva, Darina
> Cc: tm4...@li...; Lars Johnsen; 
> tm4...@li...
> Subject: Re: Problem to create a new topic using the name of 
> a deleted topic
> 
> Hi Darina,
> 
> > So, if in a topic map the merge byTopicName feature is set 
> > 
> (tmfac.setFeature("http://tmapi.org/features/merge/byTopicName",true);
> > ),
> 
> > one cannot delete topics and create them back... It is 
> strange, isn't 
> > it? Do you have an idea what is the logic behind?
> 
> I've no idea, sorry. I can look into the code but that may 
> take some time. Further, I don't think that this "feature" 
> should stay.
> 
> > Obviously, I have to give up on using the merge by topic 
> name feature.
> 
> I'd use simple item identifiers (source locators). It should 
> be very easy to use item identifiers instead of names to 
> merge topics. In addition to the default name, which was 
> previously used to merge topics, you create an item 
> identifier "http://example.org/<default-name-here>".
> 
> If you do that for every topic, your topics will be merged 
> because they have the same item identifier. I think it's a 
> better solution than relying on the "merge by name" (Topic 
> Name Constraint) 'feature'
> which was deprecated during the development of the TMDM.
> 
> Best regards,
> Lars
> --
> Semagia
> <http://www.semagia.com>
> 
> 
> 

Re: [TM4J-users] Problem to create a new topic using the name of a deleted topic

[Lars H. <he...@se...>]

Hi Darina,

> So, if in a topic map the merge byTopicName feature is set
> (tmfac.setFeature("http://tmapi.org/features/merge/byTopicName",true);),

> one cannot delete topics and create them back... It is strange, isn't
> it? Do you have an idea what is the logic behind?

I've no idea, sorry. I can look into the code but that may take some
time. Further, I don't think that this "feature" should stay.

> Obviously, I have to give up on using the merge by topic name feature.

I'd use simple item identifiers (source locators). It should be very
easy to use item identifiers instead of names to merge topics. In
addition to the default name, which was previously used to merge
topics, you create an item identifier
"http://example.org/<default-name-here>".

If you do that for every topic, your topics will be merged because
they have the same item identifier. I think it's a better solution
than relying on the "merge by name" (Topic Name Constraint) 'feature'
which was deprecated during the development of the TMDM.

Best regards,
Lars
-- 
Semagia 
<http://www.semagia.com>

Re: [TM4J-users] Problem to create a new topic using the name of a deleted topic

[Dicheva, D. <dic...@ws...>]

Hello Lars,

Just to report: no luck :-(

I included tmSysFac.setProperty("tm4j.static.merge", "true"); 
but it didn't help... 

So, if in a topic map the merge byTopicName feature is set
(tmfac.setFeature("http://tmapi.org/features/merge/byTopicName",true);),

one cannot delete topics and create them back... It is strange, isn't
it? Do you have an idea what is the logic behind?

Obviously, I have to give up on using the merge by topic name feature.

Thanks for your help anyway - you saved me bunch of time :-)

All the very best,
Darina

> -----Original Message-----
> From: Dicheva, Darina 
> Sent: Monday, June 09, 2008 11:15 AM
> To: 'he...@se...'
> Subject: RE: Problem to create a new topic using the name of 
> a deleted topic
> 
> Lars, 
> 
> > > Unfortunately, I need to merge topic maps ...
> > 
> > Well, just to ensure that we're talking about the same thing here:
> > That feature is not
> > needed if you want to merge topic maps. This feature is 
> needed if you 
> > want that topic A with the name "Darina" is merged with 
> topic B which 
> > has also the name "Darina". But that feature may cause 
> trouble if you 
> > have Paris Hilton and the city Paris in one map. Both 
> topics may have 
> > a name "Paris" and so Paris Hilton will be merged with the city.
> 
> Yes, I understand that - but this is what we wanted for a 
> particular project - we generate automatically small topic 
> maps from webpages of one site and want to merge them - there 
> is no danger of confusion since we collect terms wich belong 
> to a particular subject domain.
> 
> > > How can I do that? I looked in the TMAPITopicMapSystemFactoryImpl 
> > > class and didn't see such a feature and I don't know how to
> > directly
> > > access TM4J features.
> > 
> > TopicMapSystemFactory tmSysFac; // Assumed to be there
> > 
> > tmSysFac.setProperty("tm4j.static.merge", "true");
> 
> Thanks! I will try it and let you know the result.
> 
> Thanks again for your help.
> Cheers,
> Darina
> 
> > --
> > Semagia
> > <http://www.semagia.com/>
> > 

Re: [TM4J-users] Problem to create a new topic using the name of a deleted topic

[Lars H. <he...@se...>]

Hi Darina,

[...]
>> tmfac.setFeature("http://tmapi.org/features/merge/byTopicName",true);
>>
>> This is a very bad feature, I'd call it a bug. ;)
>>
>> You should, if possible, set that to "false".
>
> Unfortunately, I need to merge topic maps ...

Well, just to ensure that we're talking about the same thing here:
That feature is not
needed if you want to merge topic maps. This feature is needed if you
want that topic A with the name "Darina" is merged with topic B which has
also the name "Darina". But that feature may cause trouble if you have
Paris Hilton and the city Paris in one map. Both topics may have a name
"Paris" and so Paris Hilton will be merged with the city.

(Generally, it would not be a big problem if Paris Hilton goes away, though. ;))

>> If that does not help or if that feature is needed: Do you
>> have enabled the "static merging" feature for TM4J?
>
> How can I do that? I looked in the TMAPITopicMapSystemFactoryImpl class
> and didn't see such a feature and I don't know how to directly access
> TM4J features.

TopicMapSystemFactory tmSysFac; // Assumed to be there

tmSysFac.setProperty("tm4j.static.merge", "true");

Best regards,
Lars
-- 
Semagia
<http://www.semagia.com/>

Re: [TM4J-users] Problem to create a new topic using the name of a deleted topic

[Dicheva, D. <dic...@ws...>]

Hi Lars,

Thanks for replying!

> > I have set:
> > 
> tmfac.setFeature("http://tmapi.org/features/merge/byTopicName",true);
> 
> This is a very bad feature, I'd call it a bug. ;)
> 
> You should, if possible, set that to "false".

Unfortunately, I need to merge topic maps ...
 
> If that does not help or if that feature is needed: Do you 
> have enabled the "static merging" feature for TM4J? 

How can I do that? I looked in the TMAPITopicMapSystemFactoryImpl class
and didn't see such a feature and I don't know how to directly access
TM4J features.

Thanks,
Darina
 
> 
> Best regards,
> Lars
> 
> --
> Semagia
> <http://www.semagia.com/>
> 

Re: [TM4J-users] Problem to create a new topic using the name of a deleted topic

[Lars H. <he...@se...>]

Hi Darina,

[...]
> I have set:
> tmfac.setFeature("http://tmapi.org/features/merge/byTopicName",true);

This is a very bad feature, I'd call it a bug. ;)

You should, if possible, set that to "false".

If that does not help or if that feature is needed: Do you have
enabled the "static merging" feature for TM4J? If not, try to enable
static merging and post the results here.

Best regards,
Lars

-- 
Semagia
<http://www.semagia.com/>

[TM4J-users] Problem to create a new topic using the name of a deleted topic

[Dicheva, D. <dic...@ws...>]

Hi Lars and All,

I have a new problem :-(

I discovered that if I delete a topic with a certain name and after that
try to create a topic with the same name I cannot (see the trace below).
The exception is on the line: 

	t.createTopicName(topicName, null);    (I want the name to be
unconstrained)

I also tried:  t.createTopicName(topicName, new HashSet());   

I checked: t is not null; and the topicName ( tested with 't2') is  in
the TopicNamesIndex before the deletion of the topic name and not after
that (so everything looks normal). Below is the code I used to test the
deletion of the topic name when deleting a topic, and the result
(originally the removing of the scoping topics was not present):

TopicNamesIndex tni = UNames.getTopicNamesIndex(UTopicMaps.topicMap); 
System.out.println("tni before reindex");
Iterator i = tni.getTopicNamesByValue("t2").iterator();
while (i.hasNext()) System.out.println(i.next());

Iterator in = t.getTopicNames().iterator();    
while (in.hasNext()){
	TopicName bn = (TopicName) in.next();				
	Iterator itScope = bn.getScope().iterator(); 
	while (itScope.hasNext()) {					
		bn.removeScopingTopic((Topic)itScope.next()); 
	}
	bn.remove();		
}
tni.reindex();		
System.out.println("tni after reindex");
i = tni.getTopicNamesByValue("t2").iterator();
while (i.hasNext()) System.out.println(i.next());
System.out.println("deleted topic: "+t.getObjectId());
..
	
Here is the result
     [java] deleting topic: t2
     [java] tni before reindex
     [java] org.tm4j.tmapi.core.TMAPIBaseNameImpl@6cb8439c
     [java] tni after reindex
     [java] deleted topic: x1pdm557si-28a

I have set:
tmfac.setFeature("http://tmapi.org/features/merge/byTopicName",true);	

When I save the topic map after deleting the topic in the xtm file the
topic is not present, and yet, when I try to create a new topic with
that name, I get the exception.

I am really stuck and don't know what else to try. Please help.

Thanks,
Darina

---
 [java] java.lang.RuntimeException: java.lang.NullPointerException
     [java] 	at
org.tm4j.tmapi.core.TMAPITopicImpl.createTopicName(TMAPITopicImpl.java:8
0)
     [java] 	at
org.tm4l.core.utilities.utilitiesTM.UTopics.returnNewTopic(UTopics.java:
122)
     [java] 	at
org.tm4l.core.ui.dialogs.DialogCreateNewTopic.actionPerformed(DialogCrea
teNewTopic.java:164)
     [java] 	at
javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     [java] 	at
javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
     [java] 	at
javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     [java] 	at javax.swing.DefaultButtonModel.setPressed(Unknown
Source)
     [java] 	at
javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
     ..........
    [java] Caused by: java.lang.NullPointerException
     [java] 	at
org.tm4j.topicmap.memory.TopicImpl.addMergedTopic(TopicImpl.java:1053)
     [java] 	at
org.tm4j.topicmap.memory.TopicMapImpl.scopedNamesChange(TopicMapImpl.jav
a:990)
     [java] 	at
org.tm4j.topicmap.memory.TopicMapImpl.propertyChange(TopicMapImpl.java:1
087)
     [java] 	at
java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
     [java] 	at
java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
     [java] 	at
org.tm4j.topicmap.memory.TopicMapObjectImpl.firePropertyChange(TopicMapO
bjectImpl.java:254)
     [java] 	at
org.tm4j.topicmap.memory.TopicImpl.makeScopedNames(TopicImpl.java:1311)
     [java] 	at
org.tm4j.topicmap.memory.TopicImpl.propertyChange(TopicImpl.java:1459)
     [java] 	at
java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
     [java] 	at
java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
     [java] 	at
org.tm4j.topicmap.memory.TopicMapObjectImpl.firePropertyChange(TopicMapO
bjectImpl.java:254)
     [java] 	at
org.tm4j.topicmap.memory.BaseNameImpl.setData(BaseNameImpl.java:80)
     [java] 	at
org.tm4j.tmapi.core.TMAPITopicImpl.createTopicName(TMAPITopicImpl.java:7
3)
     [java] 	... 59 more

Re: [TM4J-users] Problem with removeSubjectLocator(l)

[Dicheva, D. <dic...@ws...>]

Hi Lars,
 
This solved my problem - everything works now!
 
Thank you so much!
 
All the best,
Darina

________________________________

From: tm4...@li... on behalf of Lars Heuer
Sent: Fri 5/16/2008 2:24 PM
To: Dicheva, Darina
Cc: tm4...@li...
Subject: Re: [TM4J-users] Problem with removeSubjectLocator(l)



Hi Darina,

[...]
> question is, what is the smallest part containing the change that I can
> compile independently in a jar and add it to the other TM4J/TMAPI jars?

BTW, here is the coloured change set:
<http://tm4j.cvs.sourceforge.net/tm4j/tm4j/src/org/tm4j/tmapi/core/TMAPITopicImpl.java?r1=1.23&r2=1.23.2.1&pathrev=TM4J_1_x>
and here the patch:
<http://tm4j.cvs.sourceforge.net/tm4j/tm4j/src/org/tm4j/tmapi/core/TMAPITopicImpl.java?r1=1.23&r2=1.23.2.1&view=patch&pathrev=TM4J_1_x>

HTH,
Lars
--
Semagia
<http://www.semagia.com <http://www.semagia.com/> >



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Tm4j-users mailing list
Tm4...@li...
https://lists.sourceforge.net/lists/listinfo/tm4j-users

Re: [TM4J-users] Problem with removeSubjectLocator(l)

[Dicheva, D. <dic...@ws...>]

Lars,

Thank you so much!

All the best,
Darina

> -----Original Message-----
> From: Lars Heuer [mailto:he...@se...]
> Sent: Friday, May 16, 2008 2:25 PM
> To: Dicheva, Darina
> Cc: tm4...@li...
> Subject: Re: [TM4J-users] Problem with removeSubjectLocator(l)
> 
> Hi Darina,
> 
> [...]
> > question is, what is the smallest part containing the change that I
can
> > compile independently in a jar and add it to the other TM4J/TMAPI
jars?
> 
> BTW, here is the coloured change set:
>
<http://tm4j.cvs.sourceforge.net/tm4j/tm4j/src/org/tm4j/tmapi/core/TMAPI
To
> picImpl.java?r1=1.23&r2=1.23.2.1&pathrev=TM4J_1_x>
> and here the patch:
>
<http://tm4j.cvs.sourceforge.net/tm4j/tm4j/src/org/tm4j/tmapi/core/TMAPI
To
> picImpl.java?r1=1.23&r2=1.23.2.1&view=patch&pathrev=TM4J_1_x>
> 
> HTH,
> Lars
> --
> Semagia
> <http://www.semagia.com>
> 

Re: [TM4J-users] Problem with removeSubjectLocator(l)

[Lars H. <he...@se...>]

Hi Darina,

[...]
> question is, what is the smallest part containing the change that I can
> compile independently in a jar and add it to the other TM4J/TMAPI jars?

BTW, here is the coloured change set:
<http://tm4j.cvs.sourceforge.net/tm4j/tm4j/src/org/tm4j/tmapi/core/TMAPITopicImpl.java?r1=1.23&r2=1.23.2.1&pathrev=TM4J_1_x>
and here the patch:
<http://tm4j.cvs.sourceforge.net/tm4j/tm4j/src/org/tm4j/tmapi/core/TMAPITopicImpl.java?r1=1.23&r2=1.23.2.1&view=patch&pathrev=TM4J_1_x>

HTH,
Lars
-- 
Semagia 
<http://www.semagia.com>

Re: [TM4J-users] Problem with removeSubjectLocator(l)

[Lars H. <he...@se...>]

Hi Darina,

[...]
> doesn't support TOLOG. So, TM4L cannot currently compile :-( Anyway, my
> question is, what is the smallest part containing the change that I can
> compile independently in a jar and add it to the other TM4J/TMAPI jars?

Search for "removeSubjectLocator" in your TMAPITopicImpl and change the
the following lines from:

    if (rawLoc.equals(m_obj.getSubject())) {
       return;
    }

into

    if (!rawLoc.equals(m_obj.getSubject())) {
       return;
    }


Just add a ! in front to the rawLoc.

In the original TMAPITopicImpl file that code appears in the lines
332 - 334.

Best regards,
Lars
-- 
Semagia 
<http://www.semagia.com>

Re: [TM4J-users] Problem with removeSubjectLocator(l)

[Dicheva, D. <dic...@ws...>]

Hi Lars,

Many thanks for this. I checked out the corrected class
(TMAPITopicImpl.java) and recompiled TM4J to get new jars, however, had
a problem - I forgot that I had done some changes beforehand since TMAPI
doesn't support TOLOG. So, TM4L cannot currently compile :-( Anyway, my
question is, what is the smallest part containing the change that I can
compile independently in a jar and add it to the other TM4J/TMAPI jars?

Thanks,
Darina

> -----Original Message-----
> From: tm4...@li... [mailto:tm4j-users-
> bo...@li...] On Behalf Of Lars Heuer
> Sent: Wednesday, May 14, 2008 11:28 AM
> To: Lars Heuer
> Cc: tm4...@li...
> Subject: Re: [TM4J-users] Problem with removeSubjectLocator(l)
> 
> [...]
> > If the locator IS NOT equal to the current locator, the method
should
> > do nothing.
> 
> > I'll try to commit the bug fix. I'll use the "TM4J_1_x" branch. So,
> > you'll have to check out the "TM4J_1_x" branch and compile
everything
> > (at least the TMAPI stuff).
> 
> Fixed in the CVS now. Remember: Use the TM4J_1_X branch!
>
<https://sourceforge.net/tracker/index.php?func=detail&aid=1963893&group
_i
> d=27895&atid=391879>
> 
> Best regards,
> Lars
> --
> Semagia
> <http://www.semagia.com>
> 
> 
> 
>
------------------------------------------------------------------------
-
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Tm4j-users mailing list
> Tm4...@li...
> https://lists.sourceforge.net/lists/listinfo/tm4j-users

Re: [TM4J-users] Problem with removeSubjectLocator(l)

[Lars H. <he...@se...>]

Hi Darina,

[...]
>> I'll try to commit the bug fix. I'll use the "TM4J_1_x" branch. So,
>> you'll have to check out the "TM4J_1_x" branch and compile everything
>> (at least the TMAPI stuff).

> Thank you so much! 
> Could you please let me know when I could check it out?

Should be available (sometimes the anonymous CVS is behind the
developer's CVS, then you have to try it again later).

<http://tm4j.cvs.sourceforge.net/tm4j/tm4j/src/org/tm4j/tmapi/core/TMAPITopicImpl.java?view=markup&pathrev=TM4J_1_x>

Best regards,
Lars
-- 
Semagia 
<http://www.semagia.com>

Re: [TM4J-users] Problem with removeSubjectLocator(l)

[Dicheva, D. <dic...@ws...>]

Lars,

> Seems to be a bug in the TMAPI impl:
>
<http://tm4j.cvs.sourceforge.net/tm4j/tm4j/src/org/tm4j/tmapi/core/TMAPI
To
> picImpl.java?revision=1.23&view=markup>

> I'll try to commit the bug fix. I'll use the "TM4J_1_x" branch. So,
> you'll have to check out the "TM4J_1_x" branch and compile everything
> (at least the TMAPI stuff).

Thank you so much! 
Could you please let me know when I could check it out?

All the very best,
Darina

Re: [TM4J-users] Problem with removeSubjectLocator(l)

[Lars H. <he...@se...>]

[...]
> If the locator IS NOT equal to the current locator, the method should
> do nothing.

> I'll try to commit the bug fix. I'll use the "TM4J_1_x" branch. So,
> you'll have to check out the "TM4J_1_x" branch and compile everything
> (at least the TMAPI stuff).

Fixed in the CVS now. Remember: Use the TM4J_1_X branch!
<https://sourceforge.net/tracker/index.php?func=detail&aid=1963893&group_id=27895&atid=391879>

Best regards,
Lars
-- 
Semagia 
<http://www.semagia.com>

Re: [TM4J-users] Problem with removeSubjectLocator(l)

[Lars H. <he...@se...>]

Hi Darina,

[...]
>> > I have a problem in using the removeSubjectLocator(l) method - it
> just
>> > doesn't work for me ...
>> 

> Well, it just doesn't remove the subject locator: When I do: 

[...]
> Any other idea that I can try?

Seems to be a bug in the TMAPI impl:
<http://tm4j.cvs.sourceforge.net/tm4j/tm4j/src/org/tm4j/tmapi/core/TMAPITopicImpl.java?revision=1.23&view=markup>

  332         if (rawLoc.equals(m_obj.getSubject())) {
  333             return;
  334         }

If the locator to be removed is equals to the current locator, that
method returns. Strange.

Correct impl:

       if (!rawLoc.equals(m_obj.getSubject())) {
          return;
       }

If the locator IS NOT equal to the current locator, the method should
do nothing.

I'll try to commit the bug fix. I'll use the "TM4J_1_x" branch. So,
you'll have to check out the "TM4J_1_x" branch and compile everything
(at least the TMAPI stuff).

Best regards,
Lars
-- 
Semagia 
<http://www.semagia.com>

Re: [TM4J-users] Problem with removeSubjectLocator(l)

[Dicheva, D. <dic...@ws...>]

Hi Lars,

Thanks a lot for replying.

> > I have a problem in using the removeSubjectLocator(l) method - it
just
> > doesn't work for me ...
> 
> What does not work?

Well, it just doesn't remove the subject locator: When I do: 

System.out.println("oldSubjectLocator: "+oldSubjectLocator);
System.out.println("newSubjectLocator: "+newSubjectLocator);
if (!oldSubjectLocator.equals("")) {
	Locator l = (Locator)t.getSubjectLocators().iterator().next();
	System.out.println("loc 1: "+l.getReference());
	System.out.println("loc 1: "+l.getNotation());
	System.out.println("loc 1: "+l.toString());
			
	t.removeSubjectLocator(l);
	Locator l2 = (Locator)t.getSubjectLocators().iterator().next();
	System.out.println("loc 2: "+l2.getReference());
	System.out.println("loc 2: "+l2.getNotation());
	System.out.println("loc 2: "+l.toString());
}
	
I get:
[java] oldSubjectLocator:
c:\\workspace\\TM4L_Plugins\\plugins\\XSLT\\out.xtm
     [java] newSubjectLocator:
c:\\workspace\\TM4L_Plugins\\plugins\\XSLT\\out22.xtm
     [java] loc 1: c:\\workspace\\TM4L_Plugins\\plugins\\XSLT\\out.xtm
     [java] loc 1: URI
     [java] loc 1: org.tm4j.tmapi.core.TMAPILocatorImpl@1048d930
     [java] loc 2: c:\\workspace\\TM4L_Plugins\\plugins\\XSLT\\out.xtm
     [java] loc 2: URI
     [java] loc 2: org.tm4j.tmapi.core.TMAPILocatorImpl@1048d930
	
obviously, the locator doesn't get removed, i.e.
t.removeSubjectLocator(l); doesn't work ... And of course when after
that I try to add the new subject locator, I get the error message that
XTM1.0 doesn't allow more than 1 subject locator.
		
> 
> > I am copying a method to replace a subject locator of a topic with a
new
> > one - have no idea what I am doing wrong...
> 
> Possible problem: I believe that TM4J manages max. one subject locator
> (since XTM 1.0 allows just one). So, if you have a topic with subject
> locator "A" and you call your function with
> 
>         replaceOldSubjectLocator(t, "B", "C");
> 
> the existing subject locator ("A") would not have been matched with
> "B" and if you add "C", the locator "A" goes away since TM4J handles
> just one locator. > (I am not sure if TM4J overrides any existing
> subject locator silently).

Well, as you can see above, the locators "A" and "B" are the same ...

> 
> Maybe you can drop in [tinyTiM] (for testing purposes) as TMAPI
> implementation and see if you get the expected results. tinyTiM
> handles 0..n subject locators and is more TMAPI compatible than TM4J.
> 
> [tinyTiM] <http://sf.net/projects/tinytim>

Thank you, however, if even I get it working there, this will not solve
my problem in TM4L ...

Any other idea that I can try?

I really appreciate your effort to help.

Darina

 
>
------------------------------------------------------------------------
-
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Tm4j-users mailing list
> Tm4...@li...
> https://lists.sourceforge.net/lists/listinfo/tm4j-users

Re: [TM4J-users] Problem with removeSubjectLocator(l)

[Lars H. <he...@se...>]

Hi Darina,

> I have a problem in using the removeSubjectLocator(l) method - it just
> doesn't work for me ...

What does not work?

> I am copying a method to replace a subject locator of a topic with a new
> one - have no idea what I am doing wrong...

Possible problem: I believe that TM4J manages max. one subject locator
(since XTM 1.0 allows just one). So, if you have a topic with subject
locator "A" and you call your function with

        replaceOldSubjectLocator(t, "B", "C");

the existing subject locator ("A") would not have been matched with
"B" and if you add "C", the locator "A" goes away since TM4J handles
just one locator. (I am not sure if TM4J overrides any existing
subject locator silently).

Maybe you can drop in [tinyTiM] (for testing purposes) as TMAPI
implementation and see if you get the expected results. tinyTiM
handles 0..n subject locators and is more TMAPI compatible than TM4J.

[tinyTiM] <http://sf.net/projects/tinytim>

Best regards,
Lars
-- 
Semagia
<http://www.semagia.com>

[TM4J-users] Problem with removeSubjectLocator(l)

[Dicheva, D. <dic...@ws...>]

Hello all,

I have a problem in using the removeSubjectLocator(l) method - it just
doesn't work for me ...
I am copying a method to replace a subject locator of a topic with a new
one - have no idea what I am doing wrong...

Any help is highly appreciated.

Thanks,
Darina
---------------
public static void replaceOldSubjectLocator(Topic t,
	String oldSubjectLocator, String newSubjectLocator, TopicMap tm)
	throws Exception {
	
	Collection sic = t.getSubjectLocators();
	if (!sic.isEmpty()) {
		Iterator it = sic.iterator();
		while (it.hasNext()) {
			Locator l = (Locator) it.next();

			if (oldSubjectLocator.equals(l.getReference()))
{
				t.removeSubjectLocator(l);
			}				
		}
	}
				
	if (!newSubjectLocator.equals("")) {
		Locator siLoc = tm.createLocator(newSubjectLocator,
"URI");  
		 t.addSubjectLocator(siLoc);
	}
}