Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 4
    Umm...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. Commented Sep 17, 2010 at 1:32
  • 6
    I 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 :-) Commented Sep 17, 2010 at 3:05
  • 1
    "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. Commented Nov 19, 2013 at 17:48
  • 1
    It might be worth going through this list of http servers before making a decision. java-source.net/open-source/web-servers Commented Mar 19, 2014 at 10:52