Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>>> Drawing some parallel with the way Hibernate works, what
>>> about a:
>>> Catalog.attach(Info info)
>>> that does reconnect the impl with the catalog after it
>>> has been deserialized. This has the advantage of not having
>>> the UI code expli
Justin Deoliveira ha scritto:
>> Drawing some parallel with the way Hibernate works, what
>> about a:
>> Catalog.attach(Info info)
>> that does reconnect the impl with the catalog after it
>> has been deserialized. This has the advantage of not having
>> the UI code explicitly know about what needs
Justin Deoliveira ha scritto:
>> In some cases. You cannot use a loadable/detachable model
>> if there is nothing to detach, in particular, you cannot
>> detach a catalog object that has not been saved 'cause
>> there is nothing to reload from the catalog.
>> In this case, you're basically forced i
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> Andrea Aime wrote:
>>> Hi,
>>> I'm having some troubles with the catalog objects I'd like
>>> to discuss.
>>>
>>> There are a few catalog objects that do require some access
>>> to GT2 provided information. For example, FeatureTypeInfo
>>> can r
Andrea Aime wrote:
> Andrea Aime ha scritto:
>> Works for me, we just have a handful of these cases, so I guess
>> we can create reusable loadable/detachable models that know
>> how to re-instate the lost attribute programmatically on reload?
>> The candidates would be ResourceInfo and subclasses,
Andrea Aime ha scritto:
> Works for me, we just have a handful of these cases, so I guess
> we can create reusable loadable/detachable models that know
> how to re-instate the lost attribute programmatically on reload?
> The candidates would be ResourceInfo and subclasses, by
> extension LayerInfo
Justin Deoliveira ha scritto:
> Andrea Aime wrote:
>> Hi,
>> I'm having some troubles with the catalog objects I'd like
>> to discuss.
>>
>> There are a few catalog objects that do require some access
>> to GT2 provided information. For example, FeatureTypeInfo
>> can return a FeatureType, Attribut
Andrea Aime wrote:
> Hi,
> I'm having some troubles with the catalog objects I'd like
> to discuss.
>
> There are a few catalog objects that do require some access
> to GT2 provided information. For example, FeatureTypeInfo
> can return a FeatureType, AttributeTypeInfo an AttributeDescriptor.
> Th
Hi,
I'm having some troubles with the catalog objects I'd like
to discuss.
There are a few catalog objects that do require some access
to GT2 provided information. For example, FeatureTypeInfo
can return a FeatureType, AttributeTypeInfo an AttributeDescriptor.
The way things are done now, that inf
