Web Clipper Workbench 2.0 - Release Notes

Outline

1. Enhancements
2. Resolved Issues

1. Enhancements

This section lists enhancements added to the Web Clipper Workbench since the last release of the product.

1. Support for Apache Log4J. 

1. Locate the "server/<server>/conf/log4j.xml" located within your JBoss Portal installation directory.


2. Edit the log4j.xml file to include a Web Clipper specific appender and category. The following example will log Web Clipper specific messages to the file "${jboss.server.home.dir}/log/webclipper.log"

 
<!-- ==================== -->
<!-- Web Clipper Appender -->
<!-- ==================== -->

	<!-- A time/date based rolling appender -->
	<appender name="WEB_CLIPPER_FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
		<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
		<param name="File" value="${jboss.server.home.dir}/log/webclipper.log"/>
		<param name="Append" value="false"/>  

		<!-- Rollover at midnight each day -->
		<param name="DatePattern" value="'.'yyyy-MM-dd"/>

		<!-- Rollover at the top of each hour
		<param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
		-->

		<layout class="org.apache.log4j.PatternLayout">

			<!-- The default pattern: Date Priority [Category] Message\n -->
			<param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>

			<!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
			<param name="ConversionPattern" value="%d %-5r %-5p [%c] (%t:%x) %m%n"/>
			-->

		</layout>

	</appender>

<!-- ====================== -->
<!-- Web Clipper categories -->
<!-- ====================== -->      
  
	<!-- Limit the "ICE_LOGGER" category to INFO as its DEBUG is verbose -->
	<category name="ICE_LOGGER">
		<priority value="INFO" />
		<appender-ref ref="WEB_CLIPPER_FILE" />
	</category>
  
	<!-- Limit the "debug.com.redoaksw" category to INFO as its DEBUG is verbose -->
	<category name="debug.com.redoaksw">
		<priority value="DEBUG" />
		<appender-ref ref="WEB_CLIPPER_FILE" />
	</category>
	 
	<!-- Limit the "com.redoaksw" category to INFO as its DEBUG is verbose -->
	<category name="com.redoaksw">
		<priority value="DEBUG" />
		<appender-ref ref="WEB_CLIPPER_FILE" />
	</category>

Back to Top

2. Resolved Issues

This section lists all issues associated with Web Clipper Workbench that have been resolved since the last release. The issues are grouped by the operating system that exhibited the noted behavior. If the resolved issue was present on all operating systems, the issue will be placed under the first section, titled, "All Systems".

All Systems

1. [WC Workbench] Migrated the workbench to execute within Eclipse Galileo (3.5).
2. [WC Workbench] Fixed the Web Clipper browser to display embedded applets.
3. [WC Workbench] Fixed the DOM Viewer so that it will load the DOM for a web page containing an embedded applet.
4. [WC Runtime] Fixed the runtime to display an embedded applet within the Web Clipper portlet.
5. [WC Workbench] No longer including the log4j jar file with generated JBoss portlets. Inclusion of the log4j lib file was causing issues in the form of error statements and warnings regarding improper log4j configuration.
6. [WC Runtime] Tested and verified portlet execution within JBoss 2.7.2 Portal environment.
7. [WC Workbench] Updated Help documentation to include steps to deploy Genric JSR 168 portlet to a Portal that support Generic JSR 168 portlets.
8. [WC Workbench] Fixed error message issue with the License Editor. Proper messages were not displayed.

1. [WC Workbench] Fixed wizard for defining a Generic JSR 168 Portal Server.
2. [WC Workbench] Fixed wizard for editing a Generic JSR 168 Portal Server's specification.
3. [WC Workbench] Fixed deployment functionality for portlets that will be deployed to a Generic JSR 168 supported portal.

1. [WC Runtme] Fixed toArray() implementation issue. Portlets will now work within JBoss Portal Server 2.4 and 2.6, as well as 2.2.

1. [WC Runtme] Fixed parsing issues with HTML comment entries.
2. [WC Runtme] Fixed parsing issue with HTML NOSCRIPT tag that caused invalid rendering.

Back to Top