You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Ashoka Upadhya <AU...@art.com> on 2012/04/15 17:01:56 UTC

Header contribution from externally loaded markup

I have panel components that gets its markup from external source (CMS).
Component implements IMarkupResourceStreamProvider.

These components are nested and are resolved through component resolver.
Below is the structure of dependency. In below, assume each element
(masterPage, page.. ) as component. 

 

<masterPage>

     <page path="">

            <contentBlocks path="">

            <contentBlocks path="">

            <contentBlocks path="">

    </page>

</masterPage>

 

Markup for each content block component above has "wicket:head" section.
Issue is during page rendering these header section are not processed.

During rendering, HtmlHeaderContainer doesn't process content blocks at
all. Is it because components are not added during the construction of
the component? (For example page adds content block component during the
rendering phase through component resolver) . Is there a way to make
this work?

 

Regards, 

 

Ashoka Upadhya 

Principal Software Engineer

Art.com

Phone: (510) 879-4858

Fax: (510) 588-3930    

 

 

 

  <http://www.art.com/> 

  <http://www.allposters.com/> 

  <http://www.artistrising.com/> 

	

If you have received this e-mail in error, please immediately notify the
sender by reply e-mail and destroy the original e-mail and its
attachments without reading or saving them. This e-mail and any
documents, files or previous e-mail messages attached to it, may contain
confidential or privileged information that is prohibited from
disclosure under confidentiality agreement or applicable law. If you are
not the intended recipient, or a person responsible for delivering it to
the intended recipient, you are hereby notified that any disclosure,
copying, distribution or use of this e-mail or any of the information
contained in or attached to this e-mail is STRICTLY PROHIBITED. Thank
you.


Re: Header contribution from externally loaded markup

Posted by Martin Grigorov <mg...@apache.org>.
Hi,

I'm not 100% certain but I think the reason to not contribute to the header
is that you use IComponentResolver.
Check BrixCms's [1] source to see how they did it.

1. http://brix-cms.org

On Sun, Apr 15, 2012 at 6:01 PM, Ashoka Upadhya <AU...@art.com> wrote:

> I have panel components that gets its markup from external source (CMS).
> Component implements IMarkupResourceStreamProvider.****
>
> These components are nested and are resolved through component resolver.
>  Below is the structure of dependency. In below, assume each element
> (masterPage, page.. ) as component. ****
>
> ** **
>
> <masterPage>****
>
>      <page path=””>****
>
>             <contentBlocks path=””>****
>
>             <contentBlocks path=””>****
>
>             <contentBlocks path=””>****
>
>     </page>****
>
> </masterPage>****
>
> ** **
>
> Markup for each content block component above has “wicket:head” section.
> Issue is during page rendering these header section are not processed.****
>
> During rendering, HtmlHeaderContainer doesn’t process content blocks at
> all. Is it because components are not added during the construction of the
> component? (For example page adds content block component during the
> rendering phase through component resolver) . Is there a way to make this
> work?****
>
> ** **
>
> Regards, ****
>
>  ****
>
> Ashoka Upadhya ****
>
> Principal Software Engineer****
>
> Art.com****
>
> Phone: (510) 879-4858****
>
> Fax: (510) 588-3930    ****
>
> [image: art.com, inc]****
>
>  ****
>
> ** **
>
> [image: art.com] <http://www.art.com/>****
>
> [image: allposters.com] <http://www.allposters.com/>****
>
> [image: artist] <http://www.artistrising.com/>****
>
> If you have received this e-mail in error, please immediately notify the
> sender by reply e-mail and destroy the original e-mail and its attachments
> without reading or saving them. This e-mail and any documents, files or
> previous e-mail messages attached to it, may contain confidential or
> privileged information that is prohibited from disclosure under
> confidentiality agreement or applicable law. If you are not the intended
> recipient, or a person responsible for delivering it to the intended
> recipient, you are hereby notified that any disclosure, copying,
> distribution or use of this e-mail or any of the information contained in
> or attached to this e-mail is STRICTLY PROHIBITED. Thank you.****
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>