This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes Web Services Certification (SCDJWS/OCEJWSD) and the fly likes RESTful service with EJB 3.1 endpoint cannot be found (404) Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Certification » Web Services Certification (SCDJWS/OCEJWSD)
Bookmark "RESTful service with EJB 3.1 endpoint cannot be found (404)" Watch "RESTful service with EJB 3.1 endpoint cannot be found (404)" New topic
Author

RESTful service with EJB 3.1 endpoint cannot be found (404)

a sarkar
Ranch Hand

Joined: Aug 05, 2010
Posts: 92
Hi,
I have a Resource configured as a EJB 3.1 Stateless Bean. I also have an overridden Application class to customize the context root. However, the client just cannot seem to find the Resource. What am I doing wrong? The Resource is packaged and deployed as a war.



Resource:


Application class:



Client:


Abhijit
-------
SCJP 5, SCBCD 5, OCWCD 5, OCEWSD 6, CSM
a sarkar
Ranch Hand

Joined: Aug 05, 2010
Posts: 92
I figured this out...the context root is NOT the one specified in the @ApplicationPath annotation. The context root has to be specificed in the vendor-specific dd, glassfish-web.xml for example, or the default needs to be accepted.
The endpoint URI is of the form http://hostname:port/contextRoot/applicationPath/path, where applicationPath is specific with @ApplicationPath and path with @Path.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: RESTful service with EJB 3.1 endpoint cannot be found (404)