The default superclass, "javax.servlet.http.HttpServlet" error

[ancient dock]

this error is so frustrating i'm creating a rest-API jersey application and i'v done all the settings and configuration to resolve it, i even deleted tomcat 10 and downloaded tomcat 9 and the error is still there

[dusky quest]

<@&987246399047479336> please have a look, thanks.

[dusky quest]

While you are waiting for getting help, here are some tips to improve your experience:

Code is much easier to read if posted with syntax highlighting and proper formatting.

If nobody is calling back, that usually means that your question was not well asked and hence nobody feels confident enough answering. Try to use your time to elaborate, provide details, context, more code, examples and maybe some screenshots. With enough info, someone knows the answer for sure.

Don't forget to close your thread using the command </help-thread close:1027500463647621170> when your question has been answered, thanks.

[ancient dock]

The default superclass, "javax.servlet.http.HttpServlet", according to the project's Dynamic Web Module facet version (2.5), was not found on the Java Build Path. this is the error

[hearty venture]

@ancient dock I'm facing the same issue. I'll let you know if I can find a workaround, but it doesn't seem to affect running it on the server.

Does it run on yours?

[dusky quest]

Closed the thread due to inactivity.

If your question was not resolved yet, feel free to just post a message to reopen it, or create a new thread. But try to improve the quality of your question to make it easier to help you 👍

[ancient dock]

The issue was that I was missing the servlet-API dependency in my pom.xml file and also modified the dynamic web module facet to version 5 and it worked

[hearty venture]

I found an alternative solution if the others did not work, and that was creating a dynamic web project in eclipse with the target runtime set immediately in project creation, and that solved the issue for me. It doesn't seem to clear if I created the project and added the runtime later or even tweaked build path, etc. It could have been something caused by eclipse choosing an incompatible web module version for the version of server running.

@ancient dock

[dusky quest]

Closed the thread due to inactivity.

If your question was not resolved yet, feel free to just post a message to reopen it, or create a new thread. But try to improve the quality of your question to make it easier to help you 👍

[ancient dock]

yeah I think that's the problem with Eclipse and I've seen that solution too, Glad it worked