As per the documentation I can see that cq:isContainer is of type
String. Even the latest carousel in the core component is also having
this property. I created a proxy component in my project and tried to
add this property but the crxde lite is not allowing(expecting type
Boolean). I know either I can copy that property and paste it here or
directly export this from eclipse. But why it is not supporting this
Crxde lite. Does this need any update on Crxde in future?
I have seen somewhere in the forum people recommend to use the maven
scope system. if I include my jar location(local maven repo path) in the
system path and embed that in the pom, the jar will be embedded in the
AEM bundle and it would work fine. If I commit that code in the GIT
other developers will need to change the repo path location
corresponding to the local. Is that a good approach? Or do we have a
recommended practice for this?
Thank you jeff.foxx for your response. I got your point of creating a
custom component which give the option to author for multiple devices
and rendering will take place based on client side and server side
logic.I may not need an experience fragment because I am only concerned
about text content. So I don't end up creating multiple text components
for the same page for multiple devices. I would like to know whether we
can leverage the capability of variations in content fragments for this
If I want to display different contents in mobile and desktop, how can I
achieve that?. I am thinking about creating a content fragment with
multiple variations. Is there any option to author one variation of
content fragment for mobile and another variation for desktop for the
Thanks bsloki for the response. I can include multiple parsys
components in the image component inside a layout container. So it would
give authors the flexibility to put other components in any position
where the parsys sit and layout container helps to resize those
component. I think that is the best we can provide. Thank you all for
Thanks for your suggestion arunp99088702. I can only move the components
with in the layout but not above any other components, right? I want to
place some tile component, text component over image component. These
components are already there, I just wanna reuse this. So that I can
drag and drop the existing components over another component. May be in
another page I may only want to put the tile component over the image
component not both. Do we have any similar use case example available?
Thanks arunp99088702 for the response but I am looking for the creation
of a generic component that helps the author to drag & drop components.
They should have the flexibility to select what all components can be
placed over the larger component. I think the customization of layout
container would be best choice because it already provides the option to
resize the components. I think may be if we can merge the parsys we can
Suppose I have a image component, text component and tile component.
Just like we can resize and place any components inside the layout
container, I am thinking of an option to place the large image component
in the background and other components on top of that. So when it is
viewed other components can sit on top of the large image component. To
achieve this on which component should I need to write the custom code.