Bug 886599

Summary: RHQ on as7: REST api complete failure
Product: [Other] RHQ Project Reporter: Heiko W. Rupp <hrupp>
Component: RESTAssignee: Lukas Krejci <lkrejci>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: lzoubek
Target Milestone: ---   
Target Release: RHQ 4.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-03 12:41:42 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Heiko W. Rupp 2012-12-12 11:25:01 EST
When you hit the rest-api at
e.g.

http://localhost:7080/rest/index.html you will see

--------
Error

app/rhq-enterprise-server-ejb3/RootHandlerBean -- service jboss.naming.context.java.app.rhq-enterprise-server-ejb3.RootHandlerBean
---------

Same for other rest api endpoints

The failure is triggered by 

org.rhq.enterprise.server.core.StartupBean#secureNaming

If that is commented out, the rest-api again works as expected.
Comment 1 Heiko W. Rupp 2012-12-12 11:33:22 EST
Basically what seems to happen is that resteasy scans for the rest-classes and knows (from the @Path annotation) that the RootHandlerBean -- an *interfaceless* stateless session bean is a rest endpoint implementation. 
When a request hits the servlet, resteasy tries to find the RootHandlerBean in JNDI and fails.
Comment 2 Lukas Krejci 2012-12-20 07:43:49 EST
This should be fixed in master by commits:
b62fb191a178d06fe48b47b2508fd4cb0aa039ca
e00d4e22f5e32593b366a23f908fc521be1a8f44