Re: Persistence?

Hi Chris,

  I have implemented the simple serialization test that I was talking
about. Update your sources from CVS, the test is implemented as
test.serialization.SceneSerializerTest (and SceneSerializer) class.

Regards,
  David


Chris Palmer wrote:
> Hi David!
>
> Thanks alot! I think it could be useful. We may use the library on a
> project and translating the graph to a light weight xml for persiting
> into the database will be a requirement. I imagine other users are out
> there as well so I think the issue is warranted.
>
> I wouldn't mind implementing it for you however time is my issue as
> well. If I can include the time in my project I will ask if we can
> provide the support for it. That way it stays more generic.
>
> Chris
>
>
> David Kaspar wrote:
>> Hi Chris,
>>
>> Oki, this is a good idea for an example. Right now I do not have a time
>> to work on it therefore I have filed an issue #102985:
>>   http://graph.netbeans.org/issues/show_bug.cgi?id=102985
>>
>> Thanks,
>>   David
>>
>>
>> Chris Palmer wrote:
>>   
>>> Hi David!
>>>
>>> You are correct each use case could be quite different. Perhaps just
>>> simple support such as node recreation and x y last seen or something
>>> would be sufficient. However I would imagine its not too high of a
>>> priority.
>>>
>>> Chris
>>>
>>>
>>> David Kaspar wrote:
>>>     
>>>> Hi Chris,
>>>>
>>>> This is not supported since it is hard to define what is the important
>>>> information to be stored. E.g.: usually it is enough to store widget
>>>> preferred location of all nodes and a graph structure itself (node and
>>>> edge objects). But there are other cases which requires more data to
>>>> store. If the library would have built-in serialization support, then it
>>>> would have to define an API for storing the node/edge objects since
>>>> there are represented as "java.lang.Object" and the library does not
>>>> know how to store/recreate them. Also there file format could vary from
>>>> plain text file to XML or binary file, ...
>>>>
>>>> For the reasons above, I was scared that the serialization is so
>>>> different for each use-case that it is hard to write something generic
>>>> enough. Therefore I have decided to exclude the serialization support
>>>> from the library.
>>>>
>>>> Anyway, please, let me know if you have an idea how to make the support.
>>>>
>>>> Regards,
>>>>   David
>>>>
>>>>
>>>> Chris Palmer wrote:
>>>>   
>>>>       
>>>>> Friends!
>>>>>
>>>>> Is there a persistence mechanism available to the graph api that would
>>>>> persist the definition of the graph?
>>>>>
>>>>> If the graph is translated to xml that would be great....
>>>>>
>>>>> Chris
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: 
>>>>> users-unsubscribe-Hi7mZnf3vbIkiw2pgZvNdR2eb7JE58TQ@xxxxxxxxxxxxxxxx
>>>>> For additional commands, e-mail: 
>>>>> users-help-Hi7mZnf3vbIkiw2pgZvNdR2eb7JE58TQ@xxxxxxxxxxxxxxxx
>>>>>
>>>>>     
>>>>>         
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: 
>>>> users-unsubscribe-Hi7mZnf3vbIkiw2pgZvNdR2eb7JE58TQ@xxxxxxxxxxxxxxxx
>>>> For additional commands, e-mail: 
>>>> users-help-Hi7mZnf3vbIkiw2pgZvNdR2eb7JE58TQ@xxxxxxxxxxxxxxxx
>>>>
>>>>
>>>>   
>>>>       
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: 
>> users-unsubscribe-Hi7mZnf3vbIkiw2pgZvNdR2eb7JE58TQ@xxxxxxxxxxxxxxxx
>> For additional commands, e-mail: 
>> users-help-Hi7mZnf3vbIkiw2pgZvNdR2eb7JE58TQ@xxxxxxxxxxxxxxxx
>>
>>
>>   
>