Skip to main content

Santiago Pericas-Geertsen

Santiago holds a PhD in computer science from Boston University, where he specialized in programming languages and compilers. He has been a staff engineer at Sun/Oracle for 9 years. In his first project, he co-developed XSLTC: an XSLT to bytecode compiler now in the JDK. In the next few years his focus was on XML performance and binary XML and developed the Japex micro-benchmark framework. He participated, and was appointed editor, in a number of initiatives in this area including the W3C XML Binary Characterization WG and the W3C Efficient XML Interchange WG. Before joining the Glassfish Web Tier team at Oracle, he was tech lead for JAXP and also worked on the Glassfish Mobility Platform. Currently, he is the co-spec lead for JAX-RS 2.0 (JSR 339).

 

spericas's blog

W3C Efficient XML Interchange Public Draft Available

Posted by spericas on July 20, 2007 at 9:48 AM PDT

I'm a few days late in reporting that the first public working draft of the Efficient XML Interchange (EXI) format is now available from W3C. And, naturally, the "binary XML" threads have resumed on xml-dev and in a few other places.

Adding Typed Support to the StAX API - Part 2

Posted by spericas on June 14, 2007 at 2:17 PM PDT

In an earlier blog entry I talked about a discussion to extend the StAX API with XML data types. The discussion is still ongoing and we have actually written some Java interfaces to solidify our ideas.

Woodstox rocks Glassfish v2

Posted by spericas on June 1, 2007 at 8:59 AM PDT

This is a great example of how your opinion counts and how a community can work together to improve a product. We kept hearing from many of you about how good the Woodstox XML parser was, especially how well it performed.

W3C EXI Performance Testing Framework

Posted by spericas on June 1, 2007 at 8:10 AM PDT

The W3C Efficient XML Interchange (EXI) Performance Testing Framework is now publicly available for download. This is the testing framework used by the EXI WG to evaluate properties of "binary XML" candidates.

JAXP 1.4.2 RI is available now!

Posted by spericas on May 31, 2007 at 7:38 AM PDT

Two months after releasing JAXP RI version 1.4.1, we are now releasing version 1.4.2.
This is therefore the second update release to the FCS version from last year that is also part of JDK 6.

Adding Typed Support to the StAX API

Posted by spericas on May 21, 2007 at 12:42 PM PDT

A discussion has been started in the stax_builders@yahoogroups.com mailing list about typed extensions to the StAX API. We hope this discussion will serve as the basis for a proposal to be incorporated in the next release of the API. Subscribe to the mailing list (it is moderated) if you are interested in influecing this next-gen API.

JAXP.next Community Discussion Wiki

Posted by spericas on April 20, 2007 at 12:00 PM PDT

As a follow up to a blog I wrote back in December about simplifying the JAXP API, I have created a community wiki page to continue this discussion.

JAXP 1.4.1 is available now!

Posted by spericas on March 21, 2007 at 7:22 AM PDT

The JAXP 1.4.1 RI is now available. This is an update release to the FCS version that we released a few months back, and that is also included in JDK 6.0. The change log shows that approximately 36 issues have been addressed in this release.

Japex 1.1 is now available!

Posted by spericas on March 15, 2007 at 8:06 AM PDT

It's been a while since the last time I blogged about Japex. Over the last year or so there have been many incremental improvements (resulting in 30 different releases) and with the recent addition of combined bar charts, I thought it was time to make this the official 1.1 release.

XML Schema Validation with JAXP 1.4 and JDK 6.0

Posted by spericas on March 1, 2007 at 11:20 AM PST

A few people have found problems validating DOM instances with JAXP1.4/JDK 6.0. I saw this quesion raised in the Java Technology and XML forum, and at least 3 bugs were filed for this in the last few weeks. I'll use this blog entry to explain what the problem is and how to easily fix your code.