© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM® Corp.
Page Designer does not support non visual type CSS properties, for example speak.
Page Designer does not support the following visual type CSS properties:
border-collapse,border-spacing,caption-side,clip,content,counter-increment,counter-reset,cursor,empty-cells,font-variant,letter-spacing,max-height,max-width,min-height,min-width,orphans,outline-color,outline-style,outline-width,outline,overflow,page-break-after,page-break-before,page-break-inside,quotes,table-layout,visibility,widows and word-spacing.Page Designer does not fully support the following visual type CSS properties:
- Negative values of margin, margin-top, margin-bottom, margin-left and margin-right are not supported.
- Relative and fixed values of position are not supported.
- Values specified by percentage or length of vertical-align are not supported.
- Top and bottom values of vertical-align are not supported.
- Pre-wrap and pre-line values of white-space are not supported.
When a horizontal or vertical menu with the menu depth of greater than 3 is created , if the keepSelection property is true then hovering the mouse on the menu items should keep the sub-menu items expanded, but the third level menu items will not be kept expanded.
Drag and drop of a page from the WebContent folder of the Project Explorer view to the Navigation page of Web Site Navigation throws a null pointer exception.
If you select the Web Site Navigation project facet when you create a Web project , in the Select a page template for the Web site page in the wizard, you can select the Use a default Page Template for the Web site check box and select a sample template, but you can only select a design time template. You cannot select a dynamic page template.
If you make changes to the web.xml file, Web Site Navigation does not reflect your changes. For example, if the servlet mapping for a page in web.xml is changed, Web Site Navigation does not reflect this change on the Details page immediately or after you save the web.xml file.
Whenever a button name is translated from English to Russian (or some other language), the length of the translated string may be more than the length in the English string. If the button size remains the same then the name of the button appears truncated.
In English and other languages, a menu item will appear as Undo <Action> , for example Undo Adding Web Page but in Korean , the menu item should appear as <Action> Undo (for example Adding Web Page Undo). Currently these menu items display as Undo <Action>.
When you insert a navigation trail on one of the pages of the site, then changing the site does not reflect the changes in the Design page of Page Designer. You must refresh your screen, for example, by switching to the Preview page and then switching back to the Design page of Page Designer, to see the changes.
You may not be able to edit a file in Page Designer if the file is newly created by splitting a frame on the same Page Designer and if it is managed under SCM.
Workaround: Close the Page Designer and reopen the file.
When the caret appears in the outside of Free Layout table in the Design page of Page Designer, you can not insert Free Layout table from main menu.
Workaround: Insert Free Layout table from palette in the case.
When you use Page Designer along with resident screen reader software, the layout of Properties view may collapse.
Workaround: Do not use the Properties view with such software. Use All Attributes mode from "Show All Attributes" on local toolbar menu of the Properties view.
When you edit a Web diagram, context-sensitive help is available in a dynamic help view, but not in an infopop. To set a preference for displaying context-sensitive help in a dynamic help view: click Window > Preferences > Help, and then under Open window context help, click the in a dynamic help view radio button. If you click the in an infopop radio button, only general help is available when you edit a Web diagram.
Mixing HTML and JSP tags (including custom tags) may cause the HTML syntax validator to incorrectly report missing start and end tag errors. For example, in the following code:
<c:when test="${status.first}">
<div class="topNavRight"><ul>
</c:when>
...
<c:if test="${status.last}">
</ul></div>
</c:if>The <div> and <ul> start tags are within the <c:when> tags and the end </ul></div> tags are within the <c:if> tags. This is valid code; however, the HTML syntax validator reports that the </ul> and </div> tags are missing start tags.
Workaround #1: When possible, do not overlap the HTML and JSP tags. In the example above, the workaround would be to change the code to:
<div class="topNavRight"><ul>
<c:when test="${status.first}">
</c:when>
...
<c:if test="${status.last}">
</c:if>
</ul></div>Workaround #2: If overlapping is required, the workaround would be to disable HTML syntax validation. To disable HTML syntax validation in a project, invoke the Properties dialog for the project, select the Validation property page, check "Override validation preferences", uncheck "HTML Syntax Validator".
If migrating an application via J2EE Migration Wizard (available from a Project's context menu under Migrate), some facets that have dependencies on a specific Dynamic Web Version may not be properly updated.
Workaround: After migration is complete, go to the project's Properties page (select Properties from the Project context menu) and go to the Project Facets property page. Click Add/Remove Project Facets. You may see error messages saying that some facets require a specific Dynamic Web Module version, such as JSTL, JDBC Mediator, and WebSpher®e Web (Co-existence) and (Extended). For most facets, you can simply select the appropriate required version from the drop-down and then click Finish. For the JDBC Mediator facet you will need to manually unselect the old facet and click Finish, and then reopen the facet page and select the appropriate facet version in order for the appropriate JDBC Mediator jars to be added to your classpath.
When only one element is in a text cell, you cannot display the pop-up menu for the element within the text cell by right-clicking the element.
Workaround: To display the correct pop-up menu for the element of the text cell, press the Shift+F10 key instead of clicking the right mouse button.
When updating the runtime details of a JDBC connection (from the project's properties) this will create a new connection in your extended EAR file and update the resource reference to point to the new JNDI name for this new data source. However the authentication alias will not get updated.
Workaround: Select the resource reference in the web.xml file that has the same name as your JDBC connection. The resource reference name is based on the original connection that was selected for update (from the Name pulldown) and not the name of the connection specified on update. Set the authentication alias to the one just created (the new authentication alias will include the name of the connection specified on update) which can be found in the Deployment section of your EAR deployment descriptor or in the server configuration if using a WebSphere Application Server v5.1 Test Environment server.
When you work with Page Designer, you may see a prompt saying SWTError suggesting you to close the workbench. This is likely to happen when your Web page is opened or when you try to open a pop-up menu in Page Designer. If you encounter this problem, your system load may be high, running a lot of applications.
Workaround:
- Open Windows® Task Manager.
- Go to the Processes tab.
- Find processes which have large values in the Handles, User Objects, and GDI Objects columns.
If you do not see the columns, please select View > Select Columns from the menu. Check the Handles Count, User Objects, and GDI Objects in the Select Columns window.
- These processes consume a lot of system objects and this product can not run together with these applications. Try to close some of these applications and start the workbench again.
When connecting to a Derby network database, problems can occur when using the Relational Record and Record List wizards. This can occur when you have a table in your database that has a foreign key relationship to a table that has a multi column primary key and you try to add a relationship from the former table to the latter one.
Workaround: Open the Database Explorer view, expand any tables that you will be using, and make sure that the primary key constraints are loaded correctly, before running your Relational Record or Relational Record List wizards.
When you create a dynamic Web project with the JDBC Mediator facet, the runtime JAR files will be set up on the basis of your target server, regardless of the facet version that you choose. For example, if you target WebSphere Application Server V5.1 but choose the 6.1 version of the JDBC Mediator facet , the 5.1 appropriate JAR files are added to your project. If you then set the target runtime of your Web project to WebSphere Application Server v6.1, however, your JDBC Mediator runtime will not be updated.
Workaround: Uninstall the JDBC Mediator facet from the project and then re-install it. To do so, right-click the Web project and click Properties. Click Project Facets and then click the Add/Remove Project Facets button. Clear the JDBC Mediator check box and then click Finish. Click the Add/Remove Project Facets button again, select the JDBC Mediator check box, and click Finish. Click OK.
When accessing Relational Records or Relational Record Lists using the JDBC Mediator, a resource reference for the data source is created in the project's web.xml. If the project is exported to a WAR or EAR file and then later re-imported, the resource reference may be deleted causing the data access to fail at runtime. If the resource reference is deleted on import you can do one of two things to correct the problem. The first is to use the data access tooling to recreate the data source connection. This is also necessary if you want to modify any Relational Records or Lists on Web pages you have created. An alternative is to unzip the WAR file to a directory and copy the resource reference from the web.xml file into the web.xml file in the imported project in your workspace. If you do this, you must also remove the resource reference description, otherwise the resource reference will be deleted again when the project is built. The resource reference description will be, "Auto Generated - SDO Datasource connection to XXXX".
If you import a dynamic Web project that was created in WebSphere Studio Application Developer or WebSphere Studio Site Developer v5.1.2 that included a sample Web site navigation control (for example., a vertical or horizontal tab). the following error appears in the Problems view against the sample JSP file that gets added to the user's project:
Invalid identifier, "${siteid.id}".
Cause :
In V512 , whenever JSF tag "h:outputLink" is used in site navigation bars , its "id" attribute is generated and used. Where as in V7 , this "id" attribute is neither generated nor used , and hence the faces validator does not understand those statements introduced in Web Site Navigation, but it needs to mark the duplicated ids as errors (Otherwise the runtime will complain).
Workaround :
Manually, delete the "id" attribute (i.e., the text id="${siteid.id}" should be removed) of JSF tag "h:outputLink" present in site navigation bars in the JSP page code.
For example , if a .jsp file in a V512 project has the following line that causes the above error:
<td nowrap valign="middle" style="background-image: url('${sitenav.navtabSelImg[4]}')"><h:outputLink id="${siteid.id}" style="${sitenav.navstyle}" styleClass="${sitenav.navclass}" value="${item.href}"><h:outputText value="${item.label}"></h:outputText></h:outputLink></td>it should be modified to as follows:
<td nowrap valign="middle" style="background-image: url('${sitenav.navtabSelImg[4]}')"><h:outputLink style="${sitenav.navstyle}" styleClass="${sitenav.navclass}" value="${item.href}"><h:outputText value="${item.label}"></h:outputText></h:outputLink></td>