Is there a way to know which full URL the Spring controller is going to map?

Question

I have a Spring Controller,

@Controller
@RequestMapping(value = "/employee")
public class EmployeeController {

@Autowired
private EmployeeService employeeService;

/**
 * returns all the employees in the datastore.
 * 
 * @return list of all employees.
 */
@RequestMapping(method = RequestMethod.GET)
public @ResponseBody String getAllEmployees() {
    return convertObjectListToJSONArray(this.employeeService.listEmployees());
}

/**
 * adds an employee in the data-store.
 * 
 * @param employee
 *            employee to add in the data-store.
 * @return request status.
 */
@ResponseStatus(value = HttpStatus.CREATED)
@RequestMapping(method = RequestMethod.POST, consumes = "application/json", produces = "application/json")
public ResponseEntity<?> addEmployee(UriComponentsBuilder uriCBuilder, @RequestBody Employee employee) {
    Employee e = this.employeeService.getEmployeeById(employee.getId());
    if(null != e) {
        throw new EmployeeConflictException(); 
    }
    this.employeeService.addEmployee(employee);
    UriComponents uriComponents = uriCBuilder.path("/cmpe281Pratik021/rest/employee/{id}")
            .buildAndExpand(employee.getId());
    HttpHeaders headers = new HttpHeaders();
    headers.setLocation(uriComponents.toUri());
    return new ResponseEntity<Void>(headers, HttpStatus.CREATED);
}

But, when I hit http://localhost:8080/employee it gives an error 404. Is there a way to print to full url which this Spring controller is going to be mapped?

Answer 1

Is there a way to print to full url which this Spring controller is going to be mapped ?

You can enable the below logging property:

log4j.category.org.springframework.web=INFO

Now, if you restart your Tomcat (or any server), then during the start up, when Spring container initializing the DispactherServlet and HandlerMapping, it will print all the identified mappings (from various Controller classes) to the logs so that you can actually verify what mappings are going to be served by the Controller classes.

P.S.: This logging is just to list/log all the controller mappings, which will be helpful to debug/solve the problems