There a are several migration steps to do, dependent of the application you want to migrate. The steps can be classified by
Most of these steps are relatively simple to carry out. Just replace "this" with "that" and so on. Some of them can be done with regular expressions.
<tx:in label="a" fieldId="b" id="c" />
will be transformed to
<tc:in label="a" id="c" />
.
The id of the input element in HTML is id="c::field".
There is a little conflict between the "label" attribute used in the JSF spec. and the Tobago tx: label: Tobago means it should be displayed, and JSF spec. means that this should be used to display messages. In most cases there is no issue for that. But for the case that the application need a message label, but should not be displayed we need a new attribute:
(preliminary) "labelPosition" or "labelLayout" with value "none" With this attribute we may advise the renderer also the position of the label. Or, using an attribute "renderLable"...
<f:convertDateTime type="time"\/>
inside the <tc:date/>
.
<tc:cell/>
with <tc:panel/>
.
Dependent of the used layout manager, these tags may be dropped completely.
The layout managers are no longer a facet of a container. They are in the tree hierarchy explicitly.
Old:
<tc:panel>
<f:facet name="layout">
<tc:flowLayout/>
</f:facet>
... content ...
</tc:panel>
New:
<tc:flowLayout>
... content ...
</tc:flowLayout>
<tc:image/>
has no longer the attributes width
and height
, please use a
<tc:style/>
child tag instead.
To have typesafe code many Java classes to provide constants are migrated to Java enums,
e. g. org.apache.myfaces.tobago.component.Attributes
.
javax.servlet.http.Part
instead of org.apache.commons.fileupload.FileItem
.
There is no longer a tobago-fileupload.jar.
Remove the dependency to commons-fileupload.jar in your web app, if there is any.
<multipart-config>
Tag to the FacesServlet config in the web.xml
. Since JSF 2.2 this is not needed.
TODO: Because of the changed layout model (no longer on the server, but with browser CSS) there a some classes, methods and parameters removed. * AbstractUIPage.getActionPosition() * AbstractUIPage.setActionPosition() * class Box * class Dimension * class Position * ClientProperties.pageWidth * ClientProperties.pageHeight *<tc:gridLayoutConstraint>
-><tc:span>
(only for attributes columnSpan and rowSpan) *<tc:gridLayoutConstraint>
-><tc:style>
(all other attributes) *<tc:toolBar>
-><tc:buttons>
*<tc:toolBarCommand>
-><tc:button>
* If using<tc:page>
with the attributes state, width, height: remove the attributes * Replace facet 'action' with 'load' for<tc:page>
<f:facet name="load">
contain an instance of UICommand (tc:command). * TODO: attribute renderPartially is replaced by f:ajax * TODO: use ExternalContext.redirect instead of AjaxUtils.redirect * ReplaceAjaxUtils.getRequestPartialIds()
withFacesContext.getPartialViewContext().getExecuteIds()
orFacesContext.getPartialViewContext().getRenderIds()
respectively. * TODO: Move data from ClientProperties to TobagoContext<tc:mediator>
removed If you need a Tobago component to set e. g. some style in a renderer as a replacement, use a simple<tc:panel>
. Tango Icons Tango icon lib is no longer part of Tobago. Replaced by Font Awesome. If you need it, please include it in the application. Dependencies to JS/CSS libs: jQuery UI Tobago uses the jQuery UI library. The library is customizable to limit the amount of JS and CSS content. You will find the used modules in the header of each jQuery UI file. * E. g. Tobago 2.0.10 contains jQuery UI 1.10.4 with these contents: * jquery.ui.core.js * jquery.ui.widget.js * jquery.ui.mouse.js * jquery.ui.position.js * jquery.ui.draggable.js * jquery.ui.datepicker.js * jquery.ui.slider.js * jquery.ui.core.css * jquery.ui.datepicker.css * jquery.ui.slider.css * jquery.ui.theme.css * Tobago 3.0.0 contains jQuery UI 1.12.1 with this component: * widget.js If you are using jQuery UI directly, you may add the required resources via the<tobago-config.xml
and exclude the jQuery UI resource that comes with Tobago.