You would want to define classes for WeatherLocation, WeatherForecast, and WeatherCurrent. Then the question is, what exactly are you trying to achieve in this SQL? You can certainly achieve the same thing in Hibernate -- the HQL transliteration of this SQL would look something like:
Code:
select l.zip_code, l.city, l.state, f.sky24, c.temperature, c.wind_speed, c.relative_humidity
from WeatherLocation l, WeatherForecast f, WeatherCurrent c
where l.zip_code = 30346 and l.station = f and l.location = c
and f.day_of_week = 2 order by l.zip_code;
Of course, Hibernate is buying you very little if you do this... you are just pulling fields (projecting columns) out of your objects. Hibernate only really starts paying dividends when you build your application around it and start thinking more in terms of the objects than in terms of the columns you are pulling out of them. Without knowing more about your application it's hard to know what this query *means* and hence how to make it more Hibernate-ish.
Now, when it comes to creating objects, Hibernate will certainly help right away -- it's much nicer to do 'session.save(new WeatherLocation("San Francisco", "CA", "94105"))' than to do whatever JDBC you are doing now....
Cheers,
Rob