Search: concept

keywords. Note: could reuse the "Types" concept here maybe, with a built-in type "SPAM" that would

particular keywords. Note: could reuse the "Types" concept here maybe, with a built-in type "SPAM" that would

) This concept is to replace (in a lazy way) initial HTML by a richer HTML. What I mean by richer? In order

, expanding the DocumentName concept) Annotation model changes to store such a reference to a field

? === ==== Solution n°1 : Richer HTML (not used) ==== This concept is to replace (in a lazy way) initial HTML

will be devised (for example, expanding the DocumentName concept) * Annotation model changes to store

, PatchId toPatch) /** do we need to introduce a concept of dependencies between patches? */ Iterator

if we cannot somehow merge the concepts together. I guess I'd need to see some examples

. * Skin extensions sounds like an afterthought. I wonder if we cannot somehow merge the concepts together

architecture using a Component Manager * Each component group (set of components for implementing a concept

) further introduces the concept of shareable nodes which allows multiple paths of access to a node

the concept of journaled listeners which can ask the repository to re-play all events after a certain

. JSR283 hence introduces the (optional) concept of shareable nodes. This allows implementing multiple

://whiteboardjunkie.wordpress.com/2008/11/24/where-am-i-using-jcr-and-why/] * JSR 283 (JCR 2.0) further introduces the concept

navigations through content * JSR 283 further introduces the concept of journaled listeners which can ask

) concept of shareable nodes. This allows implementing multiple URIs for a given model object