My Oracle Support Banner

RESTful Web Service Application Using web.xml Without Application Subclass does not Work as Expected (Doc ID 2695151.1)

Last updated on SEPTEMBER 16, 2020

Applies to:

Oracle WebLogic Server - Version 12.2.1.3.0 to 12.2.1.4.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

The context path of RESTful web service using web.xml without Application subclass is created from default "resources" value if it follows the below WebLogic document. That is not expected behavior. Expected behavior is the context path should be based on Servlet Mapping value.

Regarding to how to packaging about the RESTful web service using web.xml without Application subclass has been documented below:

Developing and Securing RESTful Web Services for Oracle WebLogic Server
https://docs.oracle.com/en/middleware/fusion-middleware/weblogic-server/12.2.1.4/restf/deploy-restful-service.html#GUID-251D4FD9-CBB6-4D7D-952D-7DB873B6451C
Packaging the RESTful Web Service Application Using web.xml Without Application Subclass

Example 4-3 Updating web.xml for Servlet 3.0 If Application Subclass is Not in Package

Expected Behavior:
Can access to http://<WLS HOST>:<PORT>/<WebAppContext>/sampleresources/<Path>

Actual Behavior:
Can access to http://<WLS HOST>:<PORT>/<WebAppContext>/resources/<Path> 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.