Re: Extending a mountpoint

Hi Tobi,

If you change the content type of a collection, you also have to
redefine the constraints and other properties of the collection. We
don't mix and merge collection properties. To mix and merge as you
suggest would be highly confusing in my opinion, and only work in a
small subset of cases.

hannes

2007/6/24, [email protected] <[email protected]>:
>
> Hello
>
>  I am currently testing Helma's new feature of generic object references and
> collections in Antville.
>
>  So far I have made the Image and LayoutImage prototypes work with the
> mountpoints ImageMgr and LayoutImageMgr:
>
> http://antville.googlecode.com/svn/trunk/code/Image/type.properties
> http://antville.googlecode.com/svn/trunk/code/ImageMgr/type.properties
> http://antville.googlecode.com/svn/trunk/code/LayoutImageMgr/type.properties
>
>  However, I noticed that I need to set all desired mappings in the
> LayoutImage prototype -- although LayoutImage extends Image and some of them
> could be inherited from it.
>
>  If I leave away the mappings in LayoutImageMgr I get all the (layout?)
> images from database, too many, anyway.
>
>  This is confusing because I think all settings below the FIXME in
> LayoutImageMgr should be inherited from ImageMgr; and yet they are not.
>
>  I wonder if inheritance does not work this way regarding mountpoints. Or
> maybe this *should* work and something interferes here, related to the
> changes in Helma?
>
>  Please let me know if you need further information to reproduce the
> behaviour.
>
>  Ciao,
>  tobi
>
> _______________________________________________
> Helma-user mailing list
> [email protected]
> http://helma.org/mailman/listinfo/helma-user
>
>