Webservice delete error

Question

I have a problem in my webservice. It is giving this error:

Requestfailed Requestfailed --> Status: (405)

The code I’m using:

@DELETE
@Produces("text/plain")
@Path("ExcluirLista/{usuario}")
public boolean excluirTodos(@PathParam("usuario") String usuario)
{
    ProdutoDAO dao = new ProdutoDAO();
    return dao.excluir(usuario);
}

public boolean excluir(String usuario)
{
    String sql = "delete * from listaproduto where uclogin=?";
    Boolean retorno = false;
    PreparedStatement pst = Conexao.getPreparedStatement(sql);
    try {
        pst.setString(1,usuario);
        if(pst.executeUpdate()>0)
        {
            retorno = true;
        }   
    } catch (SQLException ex) {
        Logger.getLogger(ProdutoDAO.class.getName()).log(Level.SEVERE, null, ex);
        retorno = false;
    }
    return retorno;
}   

Answer 1

Error 405 is the Method not allowed. This error indicates that there was a request in a given URL using an HTTP verb that was not suitable.

The @DELETE makes it clear that the request should be made using the HTTP DELETE method. If this error was produced, it is because some other HTTP method (such as POST) was used instead.

---

And although it’s not what you asked, it’s possible to improve your code like this:

@DELETE
@Produces("text/plain")
@Path("ExcluirLista/{usuario}")
public void excluirTodos(@PathParam("usuario") String usuario) {
    ProdutoDAO dao = new ProdutoDAO();
    dao.excluir(usuario);
}

public void excluir(String usuario) {
    String sql = "delete * from listaproduto where uclogin = ?";

    try (PreparedStatement pst = Conexao.getPreparedStatement(sql)) {
        pst.setString(1, usuario);
        if (pst.executeUpdate() == 0) throw new RuntimeException();
    } catch (SQLException ex) {
        Logger.getLogger(ProdutoDAO.class.getName()).log(Level.SEVERE, null, ex);
        throw new RuntimeException(ex);
    }
}

Do not use booleans to indicate errors, this is bad programming practice. The exceptions were designed exactly so that programmers didn’t have to do this, and so take advantage of this feature that language offers you.

And never let PreparedStatementopen up for nothing. The best way to manage them is through Try-with-Resources.