java
jcabi
A few years ago, I created two Java wrappers for W3C validators: (HTML and CSS). Both wrappers seemed to be working fine and were even listed by W3C on their website in the API section. Until recently, these wrappers have always been part of ReXSL library.
A few days ago, though, I took the wrappers out of ReXSL and published them as a standalone library—jcabi-w3c. Consequently, now seems to be a good time to write a few words about them.
Below is an example that demonstrates how you can validate an HTML document against W3C compliance rules:
import com.jcabi.w3c.ValidatorBuilder;
assert ValidatorBuilder.html()
.validate("<html>hello, world!</html>")
.valid();
The valid() method is a black or white indicator that returns false when the document is not valid. Additionally, you can obtain more information through a list of “defects” returned by the W3C server:
Collection<Defect> defects = ValidatorBuilder.html()
.validate("<html>hello, world!</html>")
.errors();
The same can be done with CSS:
Collection<Defect> defects = ValidatorBuilder.css()
.validate("body { font-family: Arial; }")
.errors();
Personally, I think it is a good practice to validate all of HTML pages produced by your application against W3C during integration testing. It’s not a matter of seeking perfection, but rather of preventing bigger problems later.
These dependencies are mandatory when using jcabi-w3c (get their latest versions in Maven Central):
<dependency>
<groupId>com.jcabi</groupId>
<artifactId>jcabi-w3c</artifactId>
</dependency>
<dependency>
<groupId>org.glassfish</groupId>
<artifactId>javax.json</artifactId>
</dependency>
<dependency>
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-client</artifactId>
</dependency>
<dependency>
<groupId>org.hamcrest</groupId>
<artifactId>hamcrest-core</artifactId>
</dependency>
