You don't.
First, placing SQL into JSP, even via tags, is indicative of a horrible design choice. The JSP page is the "view" in the Model View Controller pattern. Its job is to display your model, not actually do anything with it other than display it.
In your controller class, execute your SQL and retrieve actual Java objects that can be displayed via the JSP. Then, in your JSP, display them. Leave your SQL to your controller, and let the JSP focus on simply displaying the data. Not only do you gain clean separation of concerns, but your JSP becomes a lot simpler as a result, and it is much easier to refactor Java code than JSP code later on if it needs to be done (it is a lot simpler to test Java code as well).
