[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Access to Tamino from Java environments

• To: "'Sandor Spruit'" <sandor@c...>,<xml-dev@l...>
• Subject: RE: Access to Tamino from Java environments
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Thu, 25 Apr 2002 15:28:57 +0100
• Importance: Normal
• In-reply-to: <16914447904.20020425134923@c...>
• Reply-to: <michael.h.kay@n...>

> My current focus is on Tamino. I'm looking for others to confirm my
> initial findings, and help me find the relevant stuff to look into.
>
> I've a hard time wading through docs, figuring out how to position
> the various techologies, solutions, components. Especially: those
> related to both client and server-side programming. As far as I can
> tell after close-reading sessions this morning, there're three ways:
>
> (1) Tamino API for Java
> (2) X-Application (application framework)
> (3) X-Tension (server extensions)
>
> Number (1) looks like a client-side way to access Tamino, wrapping-up
> each call to a DOM/SAX API in HTTP requests with parameters.
>
> Number (2) is based on Java modules addressed through some JSP tag
> libraries and is definately a server-side approach;
>
> Number (3) looks like another server technology to do non-standard
> processing of XML documents similar to the options offered by, for
> example, XSLT extension functions. I assume this is relevant to an
> application that transforms some external data to an XML-format. The
> docs mention "(...) access to legacy processes through EntireX, ..."
>
> Any comments from regular Tamino developers?

You should raise this on the Tamino developer forum at
http://www.tamino.com/ - that's where all the Tamino experts congregate.

You've got it roughly right. The terms "client" and "server" here are
confusing; if you think of a three-tier architecture (browser, application
tier, database server), then (1) and (2) are both primarily
application-tier, though (1) could also be used in a desktop Java
application or from an applet, while (3) is a database back-end technology.
I think of X-Application as a higher-level toolkit for building visual
applications based on JSP, while the Java API is lower-level. X-Tension is
for writing things that execute behind the scenes in response to database
queries, e.g. fetching data from a remote application and returning it in
the XML results of a query.

EntireX is Software AG's middleware for distributed computing.

Michael Kay
Software AG
home: Michael.H.Kay@n...
work: Michael.Kay@s...

• References:
  • Access to Tamino from Java environments
    • From: Sandor Spruit <sandor@c...>

• Prev by Date: RE: lots of WS reading material
• Next by Date: RE: W3C Successes (RE: W3C Culture and Aims )
• Previous by thread: Re: Access to Tamino from Java environments
• Next by thread: Can a DTD itself be validated
• Index(es):
  • Date
  • Thread