That means, that during theh dump of the index definition the JSON
serializer fails because the blob which is supposed to be dumped exceeds
1 Megabyte (it's actually around 3 Megabyte). Can you check on the
running AEM 6.4 instance, if you can dump the index information (using
OSGI Webconsole -> "Status" -> "Oak Index Definitions")? That should use
the same functionality.
Hi @divyas70997717!Is there any specific reason why you would need to
have a ".jsp" extension on the public URL?In general, AEM supports
multiple scripting languages, such as HTL, JSP, (server-side)
resource and script resolution is not as simple as requesting a resource
with a ".jsp" extension to have the according JSP file render the
resource. In AEM, there are dedicated handlers based on the extension of
the incoming reques...
that's correct. you have to customize it as per your presentation need,
and the best way to achieve it through styling system as OOTB component
already have it available. refer this conversation for help reg styling
Hi, i have a requirement as following.I am running profile import
workflow where my cvs file will have columns likeEmail; Name;
DesignationRolesxx@a.con;Divya;TM,AEyy@a.com;Sekar;AE in this we have
designationroles will have multiple values as comma separated. The
values will be in short form so I have been asked to create a custom
resource cusDesigRoles which will have two columns (key, value) where
key is the short form and value is abbreviated form. cusDesigRoles table
will have some 100 desi...
if you do add them as test1,test2,... it would rather get complex to
define amd also not too easy to add new values later on. So I would
rather approach it as: * No custom attributes on the profile* instead a
new custom resource called cusPrrogram or so - 1 object exists per
unique record (e.g. test1)* New custom resource to link profile with the
cusProgram resource (i.e. per "yes" assigned to a profile, there would
be 1 instance of the link resource)
In this case you can override manage publication and add
granite:rendercondition node and create custom simple renderer. e.g.
In this servlet you can get user and groups from request e.g.