Justin Deoliveira ha scritto:
...
>> and then leave ReadOnlyDataStore as is, but I don't see how this can
>> be implemented using the java dynamic proxies.
> Yeah, the case for datastore is a little hard to sell proxies. However
> for regular java beans its like the classes in the new configurati
>
> Yeah, I was tempted by this approach as well, that would
> have spared me quite some pure forwarding delegation calls... but
> at the same time it would have made the decorated calls handling
> a a bit cumbersome, since I have no generic rule for decoration.
> See for example:
>
> http://svn
Justin Deoliveira ha scritto:
> Hi Andrea,
>
> I recently ran into some of the same concerns with the new catalog
> implementation. As you know there is currently no real DTO layer, which
> means that changes made via the UI or wherever else are instantly made
> live. Now.. this if course has i
Hi Andrea,
I recently ran into some of the same concerns with the new catalog
implementation. As you know there is currently no real DTO layer, which
means that changes made via the UI or wherever else are instantly made
live. Now.. this if course has issues with synchronization, beign able
to
Hi,
in the security implementation work I have to create a ton of wrappers.
These classes are needed in order to make the current user do only
what he's supposed to do, that is, if the current user can only read
a feature type, the wrappers make sure the service really see a read
only object, be i
