Provide a public getter for the list and it's available in the JSP.
Note that you're creating a new ArrayList then promptly replacing it with another one--you might as well skip the unused constructor call.
I'd also consider doing something different than instantiating the ListDB() directly, although it may not be very important yet--it can impede testability and flexibility, though.
(And is an empty list actually an error? It might be--but if not, maybe a different result name would express intent better?)