Discussion

4
Replies
196
Views
Mridul Kumar (MRIDULKUMAR)
Cognizant Technology Solutions
Team Lead
Cognizant Technology Solutions
GB
MRIDULKUMAR Member since 2011 5 posts
Cognizant Technology Solutions
Posted: June 18, 2015
Last activity: April 6, 2018
Posted: 18 Jun 2015 5:40 EDT
Last activity: 6 Apr 2018 19:26 EDT
Closed

BarCode image not visible post Upgrade from PRPC 6.1SP2 to PRPC 7.1ML7

It seems that PEGA 7 has put in restrictions on custom URL patterns (example /barcode/*).
Further check in the web.xml revealed that any custom URL needs to be defined as a servlet else would be routed through existing servlets.

There is a section in the new web.xml with the following statement:
“We have to explicitly define these as servlets because we need to map them later, we don't have these requests to go into WebStandard which has a default mapping for all requests.”
Under this section, existing URL patterns are mapped which are not accessed through standard PRServlets

Could someone please let us know what all steps needs to be done to put in a custom mapping for a request.
Example I need to map <URL>/<Context Root>/<Custom URL>. What changes are needed in web.xml for that?

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

System Administration Upgrades
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion.