Hi David, my hierarchy will contain building parts (actually content) for web portal - news,articles, interviews. maybe blogs. Every type of content has related type of node. So end users will not work with repository directly - they will use usual functions of web portal - searching and viewing certain type of content.
With jcr functionality will work facade (for example - session bean), wich will provide for web layer needed functions. So if I put all node types under one main root - it will be mistake? Or better choice is providing related parent nodes for each category? Will affect the structure of repository on prefomance of searching? 2007/8/15, David Nuescheler < [EMAIL PROTECTED]>: > > hi anton, > > sorry for the delay. > > i would be interested to understand the actual business > requirement that you are trying solve... > the hierarchy of nodes does not so much depend on property > types used, but really on how can the hierarchy be of value for > the business problem that you are trying to solve for your users. > > so if you can explain a little bit more in detail what it is that your > application > does and how your users are going to use it. from a hierarchy perspective > i think it is important that you structure things as intuitively as > possible > for the end user. > > a good hierarchy, is self explanatory to the user of the application. so > if you end users should ever see the content hierarchy directly, they > should > say: "i get it..." without any further explanations. > they should feel at home, just like with the filesystem structure on their > local harddisks... > > regards, > david > > On 8/12/07, Anton Gavazuk < [EMAIL PROTECTED]> wrote: > > Hi David, > > > > I am going to save a lot of different type nodes in repository. > > The nodes will have 2 main property - name and body - both are String > type. > > And search will be carried out on these properties. > > The differences between types - comments allowed or not. > > > > So, I'm searching a faster scheme . > > > > P.S. What can I add to make my description more precise? > > > > > > > > 2007/8/11, David Nuescheler <[EMAIL PROTECTED]>: > > > > > > hi anton, > > > > > > this all depends on the actual usecase... > > > can you be more specific about what you are trying to achieve > > > and explain your application a little bit in details? > > > > > > regards, > > > david > > > > > > On 8/10/07, Anton Gavazuk < [EMAIL PROTECTED]> wrote: > > > > Hello all! > > > > I have the question about optimal structure of repository > > > > > > > > root > > > > nodeTypeA > > > > ... > > > > nodeTypeB > > > > ... > > > > nodeTypeC > > > > > > > > > > > > or > > > > > > > > root > > > > rootForA > > > > nodeTypeA > > > > ... > > > > rootForB > > > > nodeTypeB > > > > ... > > > > rootForC > > > > nodeTypeC > > > > ... > > > > > > > > > > > > Is there anything which can impact on prefomance or on > maintainability? > > > > > > > > > >
