[Evolution] Java interfaces for Message Server and so on?

[Miles Lane <miles speakeasy org>]

I am not sure if this is relevant.  You feedback is appreciated.
The quoted article mentions Java APIs that might be useful for
integrating Evolution within enterprise IT systems.

Quoted from:
http://www.anchordesk.co.uk/anchordesk/commentary/columns/0,2415,7102840-3,00.html

>  The J2EE (Java 2 Enterprise Edition) vision is to provide standard, Java language
>  interfaces to every component that is likely to be used in an enterprise context, such
>  as webservers, mailservers, directory servers, message queues, databases, etc. Users'
>  application code then never has to change even if the underlying branded products
>  change. 
>
>  In an interesting approach, Sun itself does not provide more than "reference"
>  implementations of any of these APIs. Sun's Java strategy is to avoid competing with
>  its technology partners who support the J2EE standard in their products (in a striking
>  contrast to another large software company we know). It is an effective strategy that
>  has won Sun many willing allies. 
>
>  And so, users are free to buy (say) databases from Oracle, Informix, IBM or even
>  Microsoft, as long as those vendors support the relevant J2EE API in their databases,
>  namely JDBC. The same goes for other technologies. JNDI (Java Naming and
>  Directory Interface) is the defined way to communicate with a directory server,
>  whether it is LDAP, Novell's NDS or even Microsoft's Active Directory. In similar
>  fashion, the JavaMail API defines the interface to mail servers such as SendMail and
>  even Microsoft Exchange. JMS (Java Messaging Service) is the defined way to
>  communicate with message queues and with publish/subscribe mechanisms. JTA (Java
>  Transaction Architecture) and JTS (Java Transaction Service) define the high-level and
>  low-level interfaces to distributed transaction services, and so on.