Cameleon OSP What's New
Since Version 3:
- Applet / Servlet Concept for Browser Applications
Since Version 2.8:
- Context Menu in TextFields
- Multiple Change
- Inquriy-History
Since Version 2.6:
- Barcode Printing
- Table Row Sorting
- Table Printing
- UI Term Replacement
- MS SQL Server supported
- Generics
- Java 6 Compatibility
Since Version 2.5:
- Prepared Statements
- Java 1.5 compatibility
Since Version 2.3:
- Tomcat 5 support
- More features
Since Version 2.2:
- Advanced Linux support
- Advanced JRE 1.4 compatibility
Since Version 2.1:
Since Version 2:
- Maturation due to the use in many projects
- Advanced Oracle support
- Advanced Internationalization
Since Version 1.1.9:
- Tabbed panes in de.must.markup.DataPropertyAdministration
- de.must.markup.ColumnDataList and de.must.markup.SimpleDataList
- don't extend DataList directly any more now.
Since Version 1.1.8:
- File upload components. Required changes in your
applications: JSP
(butler) beans implement protected void handle(GeneralizedRequest
request)
instead of protected void
handle(javax.servlet.http.HttpServletRequest
request). Thus, you may access parameters in the same way, no
matter
if the form declared enctype="multipart/form-data" or not. Since the
upload
functionality is realized through existing foreign components,
additional
donwload from www.servlets.com is necessary to use it. See de.must.markup.MustMultipartRequest.
- Performance increase.
- Subclasses of de.must.wuic.MustFrame should override free()
instead of finalize() now. Thus, system resource may be
freed,
no matter if the object is hold by another reference and independant
from
System decisision when to collect garbage.
Since Version 1.1.7:
- No Java JDK 1.4.0 compilation errors.
- Connection Pooling. Existing server applications need to
implement
getGlobal in class Session and JspSession. Existing Swing applications
should check how mkt.Main.Main() and mkt.FrParamBas.act()
open and change databases now. Instead of createBasics() createOrCheckConnections()
is now used.
- Identifying database records via class Identifier. Thus,
there
is
no switch case needed for different types of primary keys any more.
Required
changes in your applications: DataTableAdministration extending
classes:
Method isInUse uses Identifier instead of int:
import de.must.dataobj.Identifier;
. . .
protected boolean isInUse(Identifier identifier) {
return false;
}
Since Version 1.1.6:
- New components and sample application parts for JavaServerPage
technology
see various\cookbookCompanions\jsp
© Copyright 2001-2011 Christoph
Müller, Kärntner Str. 56, D-70469 Stuttgart, Germany, http://www.must.de