Hi Dan, thank you for your comments.
> 1. Per another thread, think we should combine: > - LazyPropertyFacet - a hint for lazy loading of properties > - CommonlyUsedFacet - a hint for eager loading of collections Sounds great. > ~~~ > 2. Why is ContentDescription and the describeXxx() method required? > Wouldn't an annotation do? eg: I considered an annotation, but this way we are limiting what can be stored. For example we want to allow storing Adobe Acrobat (application/pdf) and Microsoft Word (application/msword) documents, but with static annotation there is no way of doing it. Though I agree, that the filename can be inferred from attribute name + mime type, for example by using standard Java mechanism (.mime.type files). > 3. per the "pending problem" you've listed (as to knowing whether or not a > blob property is populated), one option might be to do something similar to > the @PersistedTitle annotation that I've proposed in a different thread; in > other words to have Isis automatically maintain a separate "flag" property. Would user add the attribute or would it be silently generated by Isis? In any way, that's probably the way to go. > 4. per the ObjectAdapterMemento issue, I agree with the intent of your > proposed solution. The issue that needs to be addressed is that, normally, > the ObjectAdapter obtained from OneToOneAssociation.get() for a value type > (eg byte[]) has a null Oid. In order to create a lazily evaluated > ObjectAdapter, it'll need to have some sort of way of re-obtaining the > value, ie have a non-null Oid. I will look into this and get back to you if I have more questions. Thank you once again for your time. Giedrius.
