Enhydra 6.2 and beyond

["Madl Alfred - Together AT" <A.Madl@xxxxxxxxxxx>]

Hi to all otter lovers !
 
With Enhydra 6.2-2 (and the upcoming Enhydra Enterprise 6.2-2 based on
the certified version of JOnAS, we still have to find a way to build a
setup that respacts the OW J2EE license by downloading JOnAS during EE
setup or searching for JOnAS tgz-file on the local disk / current
directory) we have reached a lot of goals that we defined some time ago:
 
We completely reworked DODS to have an SQL based (instead of some other
artificial query language like in JDO) O/R mapping tool with support for
very advanced caching, lazyloading and other real world project needs.
 
Enhydra Application Framework is now completely separated and modular.
 
Good old "Multiserver" was updated to Tomcat 5.5 and now supports latest
servlet specs.
 
Axis is included in Enhydra and can be used in combination with EAF,
XMLC, DODS, etc. to easily develop real world webservices.
 
Enhydra XMLC has become a true standalone project and can already be
used with different servlet servers.
 
Enhydra Director now supports native Tomcat 5.0/5.5 and Jetty connectors
and has a lot more features than e.g. Apache mod_jk.
 
Enhydra Kelp now fully supports Eclipse and we even have a prepackaged
version of this bundle called "Enhydra IDE".
 
EAF has full JMX management capabilities and supports other standards
like JNDI for configuration information and datasources.
 
Enhydra Demos were separated for easier maintenance and adopted to the
EJOSA structure.
 
 
Now is a good time to discuss the further development of Enhydra
projects. My current (incomplete) list of ideas looks like:
 
Support for Java 5
 
Synchronized caches for DODS in clustered and balanced app server
scenarios.
 
EAF support (setups) including Enhydra Demos for Jetty, JOnAS, Tomcat,
BEA, Oracle, Websphere and JBoss to provide Enhydra application
portability across all major servlet servers
 
Debian packages in addition to already existing RPMs and Setups.
 
Integration of the Shark workflow engine into the Enhydra distribution
together with a web / XMLC based management application.
 
A better JMX based web admin application instead of Tomcat admin,
Enhydra admin, etc.
 
DODS support for legacy / non-oid datamodels
 
New Barracuda demos and application wizard / Kelp integration
 
....
 
It would now be a great time to tell me your priorities and ideas :-)
 
Greetings.
 
Alfred Madl

Attachment: smime.p7s
Description: S/MIME cryptographic signature