Skip to main content

Registering custom REST resources to access through Webcenter API's

Hi All,

You may have developed your custom RESTful services which you might want to consume by extending the native WebCenter application, Consuming services this way will also secure your services if you can extend the uToken capabilities provided by the Webcenter framework itself which is an interesting implementation which i will save for a different blog post however to consume your custom rest services oracle made it very easy in 12c with just one change in web.xml (Of-course, you should have your rest services built and deployed). Please make the following change within your web.xml to list your resources in the resourceIndex.

Add this <context-param>:

 <context-param>
        <param-name>oracle.jaxrs.config.property.resources.studyResources</param-name>
        <param-value>com.mycompany.rest.services.LibraryResource,
                                com.mycompany.rest.services.PeopleResource,
                                com.mycompany.rest.services.CardManagementResource,
       </param-value>
    </context-param>

So with just one simple change as mentioned above your resources should be available in the resourceIndex. This change will work because webcenter will be loading all the needed Jersey configuration for you so that part is abstracted from your extended library.

*In case you need help on developing and deploying your shared libraries oracle has a really good documentation in this location

Environment:
JDeveloper 12.2.1.3.0
Webcenter Extension 12.2.1.3.0
Jersey 2.0

Happy Coding ✌
Labels:

Comments

Post a Comment

Popular posts from this blog

Spring Boot - RestTemplate PATCH request fix

  In Spring Boot, you make a simple http request as below: 1. Define RestTemplate bean @Bean public RestTemplate restTemplate () { return new RestTemplate (); } 2. Autowire RestTemplate wherever you need to make Http calls @Autowire private RestTemplate restTemplate ; 3. Use auto-wired RestTemplate to make the Http call restTemplate . exchange ( "http://localhost:8080/users" , HttpMethod . POST , httpEntity , String . class ); Above setup works fine for all Http calls except PATCH. The following exception occurs if you try to make a PATCH request as above Exception: I / O error on PATCH request for \ "http://localhost:8080/users\" : Invalid HTTP method: PATCH ; nested exception is java . net . ProtocolException : Invalid HTTP method: PATCH Cause: Above exception happens because of the HttpURLConnection used by default in Spring Boot RestTemplate which is provided by the standard JDK HTTP library. More on this at this  bug Fix: This can b...
Post a Comment
Read more

Settings.xml for Maven, JFrog

For development and deployment of applications we always use an artifactory in real-time world to host artifacts needed for your build and also as a target to deploy artifacts generated in the build process. For Maven, to communicate with artifactory we need a settings.xml file which is usually located at "/User/rake/.m2/settings.xml" this file consists of how to authenticate to the artifactory servers and authorizations to read/ write to different locations like release, snapshots e.t.c... Settings.xml can be generated using the artifactory you're using which in my case is JFrog , but here's a sample settings file for your reference incase you're feeling lazy☺ <?xml version="1.0" encoding="UTF-8"?> <settings xsi:schemaLocation= "http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd" xmlns= "http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi= "http://www.w3.org/2001/XM...
Post a Comment
Read more

RADUS#4 - Caching the response in REST API's

  Caching in spring boot app: Caching can be used to provide a performance boost to your application users by avoiding the business logic processing involved again and again, load on your DB, requests to external systems if the users request data that's not changed frequently Different types of caching: We'll be focusing more on in-memory caching in this post i listed other options available to have an idea. In-memory caching You'll have a key-value data stores that stores the response of the request after it is served for the first time There are multiple systems like Redis, Memcached that do this distributed caching very well By default Spring provides concurrent hashmap as default cache, but you can override CacheManager to register external cache providers. Database caching Web server caching Dependencies needed: Maven < dependency > < groupId > org . springframework . boot </ groupId > < artifactId > spring - boot - starter - cache ...
Post a Comment
Read more