Amy,
Yes, by adding an instance, you should be able to add that resource as a
target of a property, if that property range and that resource type
match or if the property has no range.
What I think is happening is that, somehow, your index and your
application got out of sync. After you deleted the luceneIndex folder,
TBL created a new one, and the old instances should not be present there
anymore, if they are not in the ontology file.
Are you using TBL/TBE or are you using it through TBC?
Here's what you can do:
* stop TBL
* delete the index again
* make sure the test instances are not in the model (you can use TBC
for that)
* restart TBL (or TBC, if that's the case)
This should put all the components in sync again.
Andre
Amy Guthormsen wrote:
> Hi Andre,
>
> It's the autocomplete that's giving me the trouble. If I add a new
> instance, I'd like to be able to select that resource as a target of a
> property. My autocomplete does not refresh with newly added intances,
> nor can I get rid of these old ones even after deleting the
> luceneIndex file.
>
> Amy
>
> On Fri, Aug 21, 2009 at 12:47 PM, Andre Rubin<[email protected]> wrote:
>
>> Amy,
>>
>> You can go ahead and delete the whole .luceneIndex folder. This folder
>> holds an index of the instances in your ontology and is used for a quick
>> lookup while using any of the autocomplete features in TBE. It's only
>> used for this purpose and they do not represent the instances per se.
>>
>> Where were you seeing these old instances? In the grid or in the
>> autocomplete? Did you delete them using TBE or by other means?
>> (Answering these questions will help us determine what happened in your
>> case).
>>
>> Having said that, we're currently working, among other things, on
>> several improvements with the Lucene index for the next release.
>>
>> Thanks,
>>
>>
>> Andre
>>
>>
>> Amy wrote:
>>
>>> I am a new user trying to use TBLive and Ensemble to make a web
>>> application based on an ontology. My intention is to save all
>>> instance data to a sesame repository, and I have been successful in my
>>> initial attempts to do so. Yesterday I made some test instances.
>>> Today I deleted all instances from the ontology and started fresh with
>>> an empty sesame repository. Yet when I run the web app, the old
>>> instances are still there. The ONLY place I can find these instances
>>> appearing is in the _0.cfs file which is autogenerated in a folder
>>> [mynamespade].luceneIndex. Where is this coming from and how do I get
>>> rid of those old instances?
>>>
>>>
>>>
>>
>
> >
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TopBraid Composer Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---
