Deploying REST API produces warnings "unable to load class ..."
Deploying OSCM including the REST API produces the following warning for every REST related class:
[glassfish 4.1] [WARNING] [AS-WEB-UTIL-00035] [javax.enterprise.web.util] [tid: _ThreadID=49 _ThreadName=admin-listener(4)] [timeMillis: 1490886036513] [levelValue: 900] [[ Unable to load class org.oscm.rest.trigger.RestTriggerResource, reason: java.lang.ClassNotFoundException: org.oscm.rest.trigger.RestTriggerResource]]
I can only advise to package sample rest api application into jar and then into ear (as we have it with oscm.ear) to get working solution without exceptions and then apply the same packaging to our application.
To get rid of the warnings war with rest trigger api has to be deployed separately after oscm.ear is deployed. Both applications needs to be deployed on the same domain as trigger war uses EJB from oscm.ear. If there is a need to deploy the applications separately trigger rest needs to be reworked to use SOAP instead of EJB or remote JNDI lookup of that EJB. BasicAuthFilter class needs to be refactored because it looks like beggining of our AuthorizationFilter. This is wrong direction.