views:

516

answers:

1

I am working on a Java project using spring2 and Maven.

I have already incorporated JSLint4Java into Maven, but now find myself needing to do some further validation.

There are a number of core pages in the build i.e. home page, search page etc. that I want to automatically test the final HTML output for specification validity i.e. Valid XHTML 1.1 strict from the Maven build. The html template files that generate the final HTML output are all modularised and separated so validating the components individually will not work as they do not become valid until executed as one.

I do not want to test each of the pages in the build as this would slow it down considerably, my preference would be to have an XML config file with a list of the URL's I wish to run through the validation process.

I have found the Jtidy project, but am unsure of how to incorporate this into the Maven build and get it call specific URLS to validate against.

Has anybody ever done this before? Could someone provide a brief walkthrough of the stages I would need to do this?

Cheers

+1  A: 
Pascal Thivent
ah ok, that sounds like what I want. Problem is though that the JSP templates in the project are all broken out into separate components with server code in them, they probably won't be valid until compiled and called by a URL. Maybe there is some process where I can call the URLs and temporaily save down the contents and check them?
Simon Kenyon Shepard