Sun ONE Application Framework (JATO)Version 1.1 Changes |
The following changes were made from JATO 1.0 to JATO 1.1:
Developer Assistance |
---|
Changes | Requires 1.0 App Changes |
---|---|
Added JATO templates and documentation on how to use templates | |
Added JATO tag library plug-in palette for Macromedia Dreamweaver 3.x and higher | |
Added JATO tag library reference document | |
Added Example:
|
Deployment Changes |
---|
Changes | Requires 1.0 App Changes |
---|---|
New deployment descriptor entries needed for proper deployment. See the JATO Deployment Guide for more information. |
Yes
|
Changed the JATO page URL invocation style from query string style to path info style. See the JATO Deployment Guide for more information. |
Yes
|
Tag Library Changes |
---|
Changes | Requires 1.0 App Changes |
---|---|
Fixed hidden tag rendering bug (bug #28) | |
Added TextAreaTag to the taglib package |
Maybe
|
Added PasswordTag to the taglib package |
|
Added GetModelFieldValueTag to the taglib package |
|
Added SetModelFieldValueTag to the taglib package |
|
Added support for URL anchors | |
Added better error handling for situation where an end user mistakenly
enters a URL that calls a JATO JSP directly. JATO 1.0 used to throw a
|
|
Changed the names of the following tags to be more self-describing: 1.0 tags:
1.1 tags:
|
Maybe
|
Changed (relaxed) restrictions for taglib peers. Tag handlers now only require the following peer view/display field types:
|
|
Added ability to turn off tag extra info (TEI) for the taglib. This feature
was necessary to get around JSP translation bugs in certain J2EE containers.
If developers wish, they can reenable the use of TEI to significantly expand
their available JSP development options. This feature can be enabled or
disabled by changing the value of the <JATO package>.taglib.TagBase.USE_TEI
constant. |
|
Added <jato:content> tag. Developers can use this tag
to wrap an arbitrary section of JSP body content and fire display events
for that section. This allows conditional suppression or tweaking of the
content HTML as is possible with display fields. |
|
Changed the default HTML escaping mode to
This change was necessary for security reasons. |
Maybe
|
1.1.1 Change Added escaping of quotes to tag attributes where necessary, to ensure that values including quotes don't cause rendering problems in the browser. |
ViewBean & Request Dispatch Changes |
---|
Changes | Requires 1.0 App Changes |
---|---|
Cleaned up exception handling such that users can throw CompleteRequestException
during JSP rendering and the request will be properly aborted |
|
Improved general exception handling such that users get a much more predictable set of exceptions during event dispatching | |
handle<child>Request() methods never needed a specific
set of thrown exceptions in its signature. The documentation is now consistent
with this fact. |
|
The RequestCompletionListener interface is implemented at
the RequestHandlingViewBase & RequestHandlingTiledViewBase
level, and pushes the notification of the request completion to any child
views that are RequestCompletionListeners . |
|
The ModelManager now sends request complete notification
to all RequestCompletionListeners before it sessions any sessionable
models |
|
Old page URL specification method (...?page=...) is now fallback, and can (should) be disabled |
Yes
|
Addressed issue with cross-module navigation. Now we require a module URL to be specified as a context param, or preload each module servlet (see the JATO Deployment Guide for more information) | |
Added getModuleURL() method to the ViewBean
interface. The implementation of this method in ViewBeanBase
is marked final it should never be overridden |
|
Removed getModuleURL() method from RequestContext
interface |
|
Changed the timing of the initialization of the RequestContext |
|
Changed ApplicationServlet.checkBeanName() method to checkViewBeanClassName() .
Also changed isCheckBeanNames() and setCheckBeanNames()
methods to isCheckViewBeanClassNames() and setCheckViewBeanClassNames() . |
Event Changes |
---|
Changes | Requires 1.0 App Changes |
---|---|
Added new event By default, this event throws an exception. Developers can override
to forward the request somewhere else (and then throw a |
|
Changed the name of the 1.0 Method Signature:
1.1 Method Signature
|
Yes
|
Changed servlet event signatures to take These changes affect the following classes:
1.0 Event Signatures (These have been deprecated and marked
1.1 Event Signatures:
|
Yes
|
Deprecated the The deprecation occurs in
Adjustments may need to be made in the following classes:
Migrate any prior |
Yes
|
Changed the type of the
1.1 Signature
|
Yes
|
View Changes |
---|
Changes | Requires 1.0 App Changes |
---|---|
Fixed check box state bug for first touch requests. In JATO 1.0 there was a bug whereby the checkbox display field values were not being set properly for the first touch request. This was mistakenly being done as part of the special logic that needed to be in place to account for the way in which HTML only returns input values for checkboxes that are checked. This bug has been corrected in JATO 1.1 |
|
Added 3 The following methods are all new to JATO 1.1:
|
|
Added 7
|
|
Added 4 convenience methods to These convenience methods should allow developers to more simply access
commonly needed data structures. In JATO 1.0, developers had to proxy
these requests through the parent
|
|
Added a more formal notion of display fields and revised the view and view.html packages accordingly. These changes should not impact JATO 1.0 applications because the classes have for the most part simply moved package locations. JATO 1.0 had display field constructs but they were still largely abstract
special cases. Due to customer feedback, we now realize that display fields
need to be first class specializations of Changes in the
Changes in the
|
Maybe
|
Added defensive functionality so that HREFs and buttons will always render now, regardless of whether they have a value or not. In JATO 1.0 an HREF or Button child that had a |
|
Changed
1.1 Signatures:
|
Maybe
|
The signatures of the following methods has changed to throw a
|
|
Added ability for developers to specify a qualified view path to the
In the case of referencing children within a tiled view, developers can
also specify the specific tile on which the following child appears. The
syntax for this type of reference is Examples:
|
|
Added a convenience method to
|
|
Changed |
Maybe |
1.1.1 Change Changed the recommended order of code in The 1.0 code was mistakenly invoking The 1.0 Translation style:
1.1 Translation style:
|
Yes |
Model Support Changes |
---|
Changes | Requires 1.0 App Changes |
---|---|
Fixed stored procedure null param issue (bug #22) |
|
Added |
|
Added <JATO package> .model.ContextualModel interface |
|
Added support for default model values. Previously, the value provided in a display field constructor was only
the initial value, which meant that it was pushed into the backing
model one time when the field was instantiated. Subsequent access of that
display field's value would return The use of default values can be disabled by calling the method |
|
Changed
This change formalizes the notion of an executing model, which
is a model that defines an "execution" operation. The execution
context provided to the |
Maybe
|
Changed the Permanently removed the following classes/interfaces:
These implementations and interfaces were superfluous and caused much
confusion. Instead, developers can now use one of the remaining contexts
or simply pass in
|
Maybe
|
Changed <JATO package>.model..DefaultModel . It now
implements <JATO package>.model.ContextualModel . |
|
Added methods to public boolean hasPreviousResults() public boolean hasMoreResults() These methods will return NOTE:
these methods are currently only available in descendents of |
|
Fixed bug in which If a developer provided a |
|
Changed the default dataset size directive from DatasetModelExecutionContext.DATASET_SIZE_ALL_INCREMENTAL
to DatasetModelExecutionContext.DATASET_SIZE_ALL_PREFETCH .
This change removes the need to either provide a JDBC Connection
object or change the directive before using an execution context created
with a default constructor. |
|
Added QueryModelBase.get/setDefaultConnectionUser() and QueryModelBase.get/setDefaultConnectionPassword()
methods. These methods allow developers to specify a username/password combination
that the model will use when it allocates a default connection. |
|
1.1.1 Change Fixed a bug affecting the number of rows returned by the |
|
1.1.1 Change Fixed improper serialization bug in iAS when serializing WHERE criteria
objects for |
Miscellaneous Changes |
---|
Changes | Requires 1.0 App Changes |
---|---|
Fixed runtime include of full JATO pages (translation-time includes of other JATO pages are not supported) | |
Changed the preferred order and content of the 1.0 Order and Content
1.1 Order and Content
The new 1.1 style is required to allow runtime inclusion of JATO pages. The1.0 order can be retained in any already translated JSP's as long as they do not attempt any runtime inclusion of other JATO pages |
Maybe
|
Fixed command dispatching within nested tiled views | |
Added JATO version tag generation | |
Added interface for container exceptions called RootCauseException .
This will help users and the framework detect when an exception wraps another. |
|
Added transparent support for cookieless operation. JATO apps will now maintain session even if cookie support in the browser is disabled. | |
Changed HtmlUtil to make formatting HTML output more robust.
It now checks for empty strings on numeric formatting. |
|
Added capability to StringTokenizer2 to ignore string case
during tokenizing and replace operations |