EAF 6.4-1 release
What is new in Release 6.4-1
This chapter lists new release changes:
- Changed initialization of 'MultiserverClassloader' for
Enhydra Manager ('HttpPresentationServlet' implementation).
- Application MBean:
- Adapted application MBean naming (name <-> type).
- Changed Application Context parameter (Context MBean initialization).
- Changed 'getAppInfo()' method implementation for
base EAF MBean implementation - calls 'toHtml()'
application method if one exists.
- Resolved problems with PO resources caching (e.g. applet
loading).
- Resolved problem with binaries (loaded by 'MultiClassLoader')
locking after 'HttpPresentationServlet.destroy()' method call.
- Fixed problem with multiple EAF-AxisService instances
deployed (in case o shared EAF binaries) - 'AxisService'
was "static" attribute of 'HttpPresentationServlet'. That cased
successful initialization of first EAF-Axis service but disabled
initialization of others (if any) 'EAF-AxisService' instances
defined.
What is new in Release 6.3-1
This chapter lists new release changes:
- Implemented new 'StandarApplication' MBean logic. All
application MBeans extend basic (abstract) 'org.enhydra.util.EafConfigMBean'
implementation which implements basic set of Dynamic MBean ->
Application Config object operations.
Every application on its startup registers next set of Dynamic
MBean's:
- Context - gives basic information about application context
(full application name, context name an absolute context path),
- SessionManager - enables basic 'SessionManager'
administration (one for every application),
- PresentationManager - enables basic 'PresentationManager'
administration (one for every application),
- DatabaseManager - enables basic 'DatabaseManager'
administration (one for every application - if one is
registered),
- Database-<Database Name> - (one for every logical database
registered to application 'DatabaseManager'),
- Database.Table-<Database Name>.<Table Name> - (one for every
table found),
- ApplicationConfig - administration of the rest (not
SessionManager, PresentationManager or DatabaseManager) of
configuration parameters (one for every application).
- Changed creation of session key for new session in 'StandardSessionManager' in case of director request (support for new director implementation).
- Changed cookie creation in cases when new session is created (no more slash at the end of the path parameter in cookie).
- 'MonologFileLogger' (an extension of a Logger that channels
the logging trough Monolog instead of Tomcat's default 'FileLogger')
renamed to 'TomcatMonologFileLogger' - naming issue only (makes
logger nature more obvious).
- JAVA 1.5 support.
- Included new EAF tool (with purpose to enable JAVA 1.5
support): 'Crimson' -
Java XML
parser.
What is new in Release 6.2-2
This chapter lists new release changes:
- EAF logging configuration process adapted to accept relative
(not only absolute) path to Log4j or Monolog configuration file
('Log4j' or 'Monolog' parameters defined in application configuration
file).
- Implemented 'StandardApplication' session initialization before
first application request redirection.
- Removed existing SessionManager parameter - 'SessionEncodeRandomParameter'
(Peter Stehlik patch).
- Implemented new SessionManager parameter - 'SessionEncodeFirsUrl'.
Parameter indicates whether to (session) encode default application
url ('Application.DefaultUrl' parameter in application configuration
file) or not. This is optional parameter with default value
set to false.
NOTE: This parameter is closely connected to 'SessionEncodeUrlState'
(Always, Auto (default) and Never) parameter. If 'SessionEncodeUrlState'
value is set to 'Always' then 'SessionEncodeFirsUrl' parameter
value will be forced to true and if 'SessionEncodeUrlState'
value is set to 'Never' 'SessionEncodeFirsUrl' parameter value
will be forced to false.
Parameter helps to preserve initial application session during
first request redirection when the URL based session tracking
is used (i.e. either cookies are disabled or the "SessionEncodeUrlState"
is set to "Always" in the application configuration file)
- bug reported by Peter Stehlik.
- XMLC maintenance - version 2.2.6 is included in this release.
IMPORTANT NOTE: New XMLC (version 2.2.6) requires
that DOM3 interfaces are supplied at both buildtime and runtime
(XMLC's compatibility for running under JDK1.4.x). Because
of that we had to include additional DOM Level 3 API binary
(dom3-xml-apis.jar: acquired from last dom3 Xerces release
- version 2.6.2).
- Xerces binaries now included as independent tool (till now
they have bin a part of ANT's binary distribution).
Xerces binaries included:
- xercesImpl.jar - Xerces 2.6.2
- xml-apis.jar - Xerces 2.6.2
- dom3-xml-apis.jar) - DOM3 Xerces 2.6.2-beta2
- Included license and version files for all used tools.
- Included patch - adapted 'StandardSessionManager.deleteSession(sessionKey
)' method to allow deletion of passive (not just active) sessions.
Thanks to Michael Strapp.
What is new in Release 6.1-1
This chapter lists new release changes:
- Fixed problem with memory persistence parameter (Application Configuration
Parameter in web.xml , SessionManager/MemoryPersistence). Sessions
will be held in memory during restart application
- Suport for parameter idle time for sessions (Application Configuration
Parameter in web.xml , SessionManager/MaxIdleTime) for ContainerAdapterSessionManager
and JmxContainerAdapterSessionManager.
- Fixed problem with two same cookies in response when using ContainerAdapterSessionManager
or JmxContainerAdapterSessionManager.
- Implemented ('StandardApplication') unregistration of application
MBean's at applications shutdown (for MBean-s registered during applications
startup).
- Implemented 'ConfConfigurationFactory' class which provides the
possibility of reading application configuration parameters from '<appName>.conf'
file.
- Fixed problem with character encoding. Support for Servlet 2.3/2.4
specifications , method setCharacterEncoding(java.lang.String env).
- New parameter added (Application Configuration Parameter in web.xml,
Application/Encoding ). Specify character encoding which will be used
by server to encode form data.
- Included patch in available() method - com.lutris.mime.MultipartMimeInputStream
class. Many thanks to Michael Strapp.
What is new in Release
6.0-1
This chapter lists new release changes:
- Integrated all implementation changes from Enhydra 5.1-16
(since Enhydra 5.1-1)
EAF
Enhydra Application Framework (EAF) is a collection of Java classes, which
provide the runtime infrastructure for Enhydra applications. It implements the
Enhydra "super-servlet", provides dynamic URL-JSESSIONID rewriting, PO caching,
session-, database-, logging-, configuration- and XMLC API's.
The Enhydra application framework includes:
- 1. Presentation Manager
- 2. Session Manager
- 3. Database Manager
- 4. Configuration
- 5. Logging
In general, the application framework includes all the classes in the com.lutris.appserver.server.* packages, which
provide the infrastructure that Enhydra applications use at runtime.
These release contains next jar files:
1. Core:
-
eaf_api.jar: Enhydra Application Framework API's (Application, Presentation, DatabaseManager, Session, Logging, Configuration)
-
eaf.jar: Enhydra Application Framework implementations
-
util.jar: utility classes - MultiClassLoader, Config etc.
2. Logging:
-
eafcommonlogging.jar: Standad implementation of Enhydra Logger API
-
eaflog4j.jar: Log4j implementation for Enhydra logger API
-
eafmonolog.jar: monolog implementation of Enhydra logger API. Contains CommonLogger and MonologSink Adapters for Monolog logging
-
eafMonologFileLogger.jar: Tomcat File logger adaptre for Monolog logging
3. Session:
-
eafsession-containerAdapter.jar: simple session manager to be used with servlet containers capable of managing their sessions
-
eafstdsessions.jar: simple session manager which interconnects the servlet container sessions and enhydra sessions by using the
same session keys (generated by session container)
4. Configuration
-
eafconfreader.jar: ConfigFile class (implementation of ConfigFileInterface) used for managing of '*.conf' configuration files
-
eafwebxmlreader.jar: XMLConfigFile class (implementation of ConfigFileInterface) used for managing of '*.xml' configuration files
5. External Tools:
-
jivan.jar: Jivan HTML Reparser (version 1.0)
-
log4j.jar: Apache Jakarta Logging Project (version 1.2.8)
-
xercesImpl.jar: Apache Xerces Project (version 2.5.0)
-
xml-apis.jar: Apache Xerces Project (version 2.5.0)
-
xmlc.jar: Enhydra XMLC Project (version 2.2.5)
dbmanager-api.jar: Enhydra DODS Project (version 6.0-1)
6. Servlet
-
cgi_servlet.jar: CGIServlet implementation (HttpServlet extension)
-
enhydra_snoop_servlet.jar: EnhydraSnoopServlet implementation (HttpServlet
extension)
-
file_servlet.jar: FileServerServlet implementation (HttpServlet extension)
-
jar_servlet.jar: JarServerServlet implementation (HttpServlet extension)
This chapter lists tools within EAF used during build, compile and/or
runtime.
- Ant - version 1.5.4
- AntContrib - version 1.5.2
- Axis - version 1.2beta 1320 March 31 2004
- Catalina - Tomcat's jar used for Monolog logging adapter
- Commons-logging - version 1.0.3
- dods - version 6.0-1
- Jetty - Jetty's jar used for Monolog logging adapter
- jivan - version 1.0
- jmx - mx4j implementation version 2.0.1
- log4j - version 1.2.8
- Monolog - version 2.3.1
- XMLC - version 2.2.5
- Servlet - Enhydra 5.1-16 servlet.jar
NOTE: EAF contains only necessary binaries of its tools.
Platform and system information
Through the open-source development process, EAF have been used on a wide
variety of platforms.