I kinda had a similar route, although not because I was in college, but because my career of many years involved standalone application development using Java, with no web component involved. Java-based web development basically seemed to pass me by, and I didn't find it easy when I tried to move into the mainstream.
Recognize first that web-based development is a pretty large field. From an employment point of view, opportunities tend to drift towards one or other subsections of the field in general. Roughly speaking, front-end and back-end development tend to be viewed as specific enough skills that you might be expected to have expertise in one versus the other, more so now that JavaScript is more central to frontend development.
And the surfeit of frameworks in Java makes it difficult for the newcomer to choose what to begin out with. There's just way too many JavaScript libraries, Web frameworks and application servers or frameworks. Even though your background is in Java, I'd still suggest you try out Rails or maybe Grails to get a better idea of the entire stack, as they have a more coherent story. In Java, there's dominant libraries for sure, but you'll still find your efforts to master them interrupted by constant comparisons to other competing frameworks or so. Or GWT and Wicket, being more based on the Java development style, may mean an easier transition to web technologies. Spring framework is also a good starting point as it has a more or less consistent story from the back- to the front-end, although it is still overwhelming.