java - How is sling:resourceSuperType is impacting sling resolution? -


hi going through how sling resolution works.

i came against scenario mentioned on adobe aem-developer guide

https://docs.adobe.com/docs/en/aem/6-2/develop/the-basics.html

this scenario mentioned- / ( not have resource supertype or resource type)

b (sling:resourcesupertype = a)

c (sling:resourcesupertype = b)

x (sling:resourcetype = c)

y (sling:resourcetype = c, sling:resourcesupertype = a)

the type hierarchy of /x [ c, b, a, ] while /y hierarchy [ c, a, ] because /y has sling:resourcesupertype property whereas /x not , therefore supertype taken resource type.

now understand how /x resolved. not sure /y. first resolved /c. had sling:resourcesupertype b. should sling resolution not go /b well. how supertype overriden , resource resolved instead of b.

as explained in apache sling documentation, if sling:resourcesupertype defined particular resource, used. if it's not present, framework use sling:resourcesupertype defined resource pointed sling:resourcetype.

that said, in case of /y, /b not treated super type. sling:resourcesupertype defined /y points directly /a. hide sling:resourcesupertype property defined @ /c (and pointing @ /b) otherwise taken account.

the example quite described on documentation page linked to.

in experience, custom aem components easier maintain if resource type hierarchy defined set of nodes defining component , present in repository descendants of /apps or /libs (when including ootb components in inheritance hierarchy). specific instances of components (including ones responsible rendering whole pages) present in /content sub-tree can unambiguously define sling:resourcetype determines type (inheritance or not). personally, prefer not define sling:superresourcetype @ level of resource that's part of /content sub-tree makes hierarchy more difficult reason about. off top of head, can't think of use case justify trade-off. perhaps else weigh in if know one.


Comments

Post a Comment

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

i'm using class based views in django , never specify url in ajax calls , omit action parameter in form because know these requests go through post method of class based view. notice view - profile page make many requests depending on user updating on page - post method become convoluted , if/else mess example: def post(self, request, *args, **kwargs): # handle user changing available date if request.post.get('availabledate') != none: self.updateavailabledate(request) return jsonresponse({'result':'success'}) if request.post.get('newprojectname') != none: creative_user = creativeuserprofile.objects.get(id = request.user.id) project = project.create_project(creative_user, request.post['newprojectname']) project.save() return jsonresponse({'projectid': project.id }) if request.post.get('projectimage') != none , request.files['file']: proj
Read more

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

i'm doing micro-optimization on performance critical part of code , came across sequence of instructions (in at&t syntax): add %rax, %rbx mov %rdx, %rax mov %rbx, %rdx i thought had use case xchg allow me shave instruction , write: add %rbx, %rax xchg %rax, %rdx however, dimay found agner fog's instruction tables , xchg 3 micro-op instruction 2 cycle latency on sandy bridge, ivy bridge, broadwell, haswell , skylake. 3 whole micro-ops , 2 cycles of latency! 3 micro-ops throws off 4-1-1-1 cadence , 2 cycle latency makes worse original in best case since last 2 instructions in original might execute in parallel. now... cpu might breaking instruction micro-ops equivalent to: mov %rax, %tmp mov %rdx, %rax mov %tmp, %rdx where tmp anonymous internal register , suppose last 2 micro-ops run in parallel latency 2 cycles. given register renaming occurs on these micro-architectures, though, doesn't make sense me done way. why wouldn't register renamer
Read more

jquery - Responsive Navbar with Sub Navbar -

good day, forgive me nav vocabulary not best. if question confusing apologize. i'm working on navigation bar needs centered on page @ 768px , above. items in nav open (or perhaps toggle) subnav lives directly below. these nav should appear centered on page. i have been able work through responsive portion of nav bar, having main items align vertically , sub nav menu of each item roll out below, , gave them indent separation. working well. however, issue not responsive side, behavior @ width greater 768px. happens toggling menu's sub navigation pushes other main items down page below sub nav. here's code: $(document).ready(function () { //stick in fixed 100% height behind navbar don't wrap $('#slide-nav.navbar-inverse').after($('<div class="inverse" id="navbar-height-col"></div>')); $('#slide-nav.navbar-default').after($('<div id="navbar-height-col"></d
Read more