Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Sameera De Silva (SameeraSilva) Associate Engineer
Virtusa
LK
SameeraSilva Member since 2017 62 posts
Posted: Jun 1, 2017
Last activity: Jun 9, 2017
Posted: 1 Jun 2017 0:16 EDT
Last activity: 9 Jun 2017 0:37 EDT
Closed

JSP generation selected without any JSP tags present

I am getting the following warning,jsp tags are also given.What will be the solution?

To see attachments, please log in.
Low-Code App Development
User Experience

Posted: 7 years ago
Posted: 5 Jun 2017 6:45 EDT
Santanu Bhattacherjee (Santanu) Senior Manager, Cloud Engineering, Management Plane Services
Pegasystems Inc.
IN

Hi

Is it an upgraded environment ? 

Generally this kind of warning appears if your rules are using old ruleform and there under the generate for field, the value is still set to JSP rather than HTML.

Watch out for any old legacy rule in your application.

To see attachments, please log in.
Posted: 7 years ago
Posted: 5 Jun 2017 6:55 EDT
Basavaraj Kadakol (BASAVARAJ)
PEGA
Senior Manager of Technical Support Engineering
Pegasystems Inc.
AU

Hi Sameer,
This is coming from the CheckForWarnings Rule Stream, from the first step pxMissingJSPTags. Can you perform the customization of this rule Rule-Stream!CheckForWarnings and remove this condition and see if you still get this?
Regards,
Basavaraj

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice