On Oct 1, 2004, at 5:03 PM, Michael Kay wrote:
Consider implementing the transformation as a web service and invoking
it
from the client application via HTTP calls. The client need never know
that
the transformation is done using XSLT, let alone that it's done using
an
XSLT processor written in Java.
Interesting idea. Any examples I can point people to?
As I see it, it'd just involve passing the document and a single
parameter to the web service, and getting back the formatted document.
Contexts in which it would likely be used? Web applications (often
written in PHP), as well as desktop applications like OpenOffice.
As a possibly relevant aside, the OpenOffice bibliographic project
which I hope to see this become part of is being designed around a web
service record query model (for sucking in records from remote
databases).
And does such a service get around the JVM startup problem?
Bruce