Note that there are some explanatory texts on larger screens.

plurals
  1. POsimple HTTP server in Java using only Java SE API
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. COUmm...the short answer is no. If you want something that handles post and get requests without manually writing the http headers then you could use servlets. But thats java ee. If you don't want to use something like that then sockets and manual parsing is the only other option I know of.
      singulars
    2. COI know this isn't in the spirit of SO, but I would urge you to reconsider you distaste for Java EE API's. As some of the answers have mentioned, there are some very straight-forward implementations such as Jetty that allow you to embed a web server in your stand-alone application while still taking advantage of the servlet api. If you absolutely can't use the Java EE API for some reason than please disregard my comment :-)
      singulars
    3. CO"Servlets" are not really "Java EE". They are just a way of writing plugins that can be called by the surrounding application in response to message activity (these days, generally HTTP requests). Providing a servlet hosting environment "using just the Java SE API" is exactly what Jetty and Tomcat do. Of course you may want to *throw out unwanted complexity* but then you may need to decide on a subset of the allowed attributes and configurations of the GET/POST. It's often not worth it though, except for special security/embedded problems.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload