Discussion
Cognizant Technology Solutions
GB
Last activity: 6 Apr 2018 19:26 EDT
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.
Pegasystems Inc.
IN
I think still Pega7 allows you to have your own context root defined/
Can you provide more information on how it used to work in 6.1 SP2 and what it got changed Pega7 with example?
Pegasystems Inc.
IN
You might see something like below In web.xml. Can you try commenting out this and see if that helps.
<servlet-mapping>
<servlet-name>WebStandard</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
Cognizant Technology Solutions
GB
Sorry for the delay. This is same reply that we got through SR-A2278
We made the changes and it is working fine now.