Chuyển đến nội dung chính

[CQ Embedded Form] Add an approach for server side validation in Cq5 to use for CQ embedded form

Issue

While working with cq5 forms you would need to do some validations at server side end. These validations can be very generic like character only validation or may be complex business scenarios.

Solution

The approach we would discuss would incorporate all these scenarios:
The first and foremost thing to do is to override the default server validation file in /libs directory (/libs/foundation/components/form/defaults/field/servervalidation.jsp) into your project like /apps/foundation/components/form/defaults/field/servervalidation.jsp
The file above is called for each form field separately when the form is submitted. Within this default server validation field I suggest you to validate only required constraint. This can be achieved with the help of form api’s available OOTB.
Required validation (available OOTB in the constraint tab on the form field) can be done with this code below.

FieldDescription[] descs = FieldHelper.getFieldDescriptions(slingRequest, resource);
for (final FieldDescription desc : descs) {
if (desc.isRequired()) {
String[] values = request.getParameterValues(desc.getName());
// You can check for length of values in the string array/values whatever
//suits you for required validation.  
}
}

Now, if required validation passes you might want to validate other constraints that can be applicable per form field like numbers/characters/business constraint for the form.
This can be done by creating constraints at location /apps/<your-project-name>/components/form/constraints/<constraint-name>/servervalidation.jsp. Similar to the ones created under /libs at the same location.
The sling:resourceType for the <constraint-name> would be foundation/components/form/constraint.
Now, the question arises how would you call server side validation jsp for specific constraints?
First you have to set the specific constraint in the dialog of the form field. Make sure that the constraint you just created above is available in the dialog. This can be achieved by writing a Servlet that produces a json. When the dialog is set for the respective form field you can call itsserversidevalidation.jsp.
The code for this can be: (A short snippet of my project code, sorry can’t revel more)

final Resource includeResource = new ExtendedResourceWrapper(desc.getFieldResource(), resourceType, FormsConstants.RST_FORM_CONSTRAINT);
FormsHelper.includeResource(slingRequest, slingResponse, includeResource, FormsConstants.SCRIPT_SERVER_VALIDATION);

ExtendedResourceWrapper class is nothing but extends theorg.apache.sling.api.resource.ResourceWrapper and has just a constructor that accepts resource, resourceType and resourceSuperType)
By including these scripts below the required validation (in default server validation file) , you would be able to call the validation (servervalidaiton.jsp) file that has been configured over the form element.
Now, you can retrieve the value of the form fields as we did in required validation and do pattern matchings/ can apply complex business validation rules.
If you face problems in implementing the above approach, please leave a comment and I would be happy to help

From cqwemblog

Nhận xét

Bài đăng phổ biến từ blog này

How to add a new supported language in CQ / WEM (Translator in CQ)

Use case:  You want to add new language to CQ Change display language options in translator grid Change language name and default countries  Solution: You can access translator UI in CQ with following URL http://<HOST>:<PORT>/libs/cq/i18n/translator.html Create new language location for Dictionary Go to CRXDE lite (or your favorite JCR browser) and add this structure (assuming /apps/myapp/i18n as a typical location for custom apps): /apps/myapp/i18n [sling:Folder]     - de [nt:unstructured]         + jcr:mixinTypes = [mix:language]         + jcr:language = de     - fr [nt:unstructured]         + jcr:mixinTypes = [mix:language]         + jcr:language = fr Then reload the translator and the path /apps/ myapp /i18n should show up in the drop-down at the top. Note: the translator will only save translations for languages that are actually present underneath the path (e.g. /apps/myapp/i18n), others will be skipped. Then on jsp pa

Login / Logout on a Publish instance and Closed User Group (CUG)

In CQ5 there is the login logout could be configured using a Closed User Group. Closed User Groups (CUGs) are used to limit access to specific pages that reside within a published internet site. Such pages require the assigned members to login and provide security credentials. http://dev.day.com/docs/en/cq/5-4/howto/create_apply_cug.html The logout using /libs/cq/core/content/login.logout.html always gets redirected to the geometrixx site   http://localhost:4503/content/geometrixx-outdoors/en.html By configuring the Default login page  under the osgi configuration for com.day.cq.auth.impl.LoginSelectorHandler to be – /content/mysite/en/login But still after logout the page goes to the geometrixx site. IIRC, the redirect first goes to to / which then goes through the standard, somewhat complex handling of the root with multiple redirects: 1) / has a resource type of sling:redirect and redirects to /index.html 2) /index.html is handled by the RootMappingServlet [0] which h

[PERFORMANCE] Adobe WEM/CQ performance tuning

Adobe WEM/CQ performance tuning Contents Caching-related configurations CRX Bundle cache CRX Search index handler (Lucene) cache Tar PM index cache Scalability Maintenance Optimizing Tar Files (for Tar Persistence Manager) Data Store Garbage Collection Main documentation you should consult first: http://dev.day.com/docs/en/cq/current/deploying/performance.html http://dev.day.com/content/kb/home/cq5/CQ5Troubleshooting/performancetuningtips.html Caching-related configurations CRX Bundle cache CRX caches bundles, consisting of a node with all its properties. This is used by all bundle-based Persistence Managers. The default size of BundleCache is 8 MB. If this is too small it can cause an excessive number of read-accesses to the underlying persistence layer. Set the bundleCacheSize to something larger than the default. See more here: http://dev.day.com/docs/en/cq/current/deploying/performance.html#CRX%20Bundle%20Cache CRX Search index handler (Lucene