TeamDev Support : Document List - All Communities

JxBrowser hotfixes

roman.lymar@teamdev.com — Fri, 22 Jan 2010 11:54:44 GMT

JxBrowser 2.0

2.0 Download (Jan 22, 2010)

Fixed issue when ScriptErrorListener doesn't work under BrowserType.Mozilla
Fixed issue when StatusListener doesn't work when mouse cursor move over link for BrowserType.Mozilla

2.1 Download (Feb 12, 2010)

Fixed issue with localization of operating system withBrowserType.IE

2.2 Download(Mar 30, 2010)

JxBrowser 2.2 Released

2.3.23014 Download (Jun 14, 2010)

Official release build of JxBrowser 2.3

2.3.23016 Download (Jun 21, 2010)

Fixed issue when Mozillaengine browser component cannot get focus
Fixed issue when Mozillaengine browser component can not be initialized in Java Applet

2.3.23022 Download (Jun 23, 2010)

Fixed issue when executeScript method in Mozilla engine is failed in case of "window.close();" JavaScript code
Fixed issue when Mac style native menu is disappeared after creating a new Mozilla engine browser instance
Fixed issue when navigation method does not work for local PDF file
Fixed issue when Mozilla engine crashes after multiple JavaScript executions
Added Flash Player 10 support for IE engine

2.3.23038 Download (Jul 16, 2010)

Fixed issue when SilentPromptService doesn't work for IE engine
Fixed issue when Mozilla engine cannot unpack XULRunner at first time in Linux platform

2.4.24058 Download(Sep 3, 2010)

Fixed issue when JVM crashes when JVM terminates with desktop application which has Mozilla engine component.

Hotfixes

yuriy.privezentsev@teamdev.com — Wed, 20 Aug 2008 17:03:09 GMT

This page contains pre-released updates for our products. Though they are not official releases, you can safely use them in your production.

JxFileWatcher

ftp://ftp.teamdev.com/updates/jxfilewatcher-1.0.1-cross-desktop-win_mac_linux.22164.zip - this update fixes the issue with running JxFileWatcher on Mac OS X 10.4 (Tiger).

ftp://ftp.teamdev.com/updates/jxfilewatcher-1.0.2.jar - removed false delete event after renaming on Mac OS X.

ftp://ftp.teamdev.com/updates/jxfilewatcher-1.0.2.partial.jar - removed false delete event after renaming on Mac OS X.

JxCapture 2

ftp://ftp.teamdev.com/updates/jxcapture-2.0.23566.zip - Fixed audio & video sync. issue, restored back jxcapture.image.operation package and its contents for backward compatibility with previous version of JxCapture.

ComfyJ

ftp://ftp.teamdev.com/updates/comfyj-generator-2.7.22074.jar - Updated "Codegen for ComfyJ" applicaiton. Fixed the issue with generation of incompilable wrappers for dispinterfaces.

ftp://ftp.teamdev.com/updates/comfyj-generator-2.7.22980.jar - Updated "Codegen for ComfyJ" applicaiton. Preventing usage of Java keywords as parameter names.

ftp://ftp.teamdev.com/updates/comfyj-generator-2.7.22999.jar - Updated "Codegen for ComfyJ" applicaiton. Fixed issue with using interfaces instead of their implementation for return types in automated stubs.

ftp://ftp.teamdev.com/updates/comfyj-generator-2.7.23105.jar - Updated "Codegen for ComfyJ" applicaiton. SafeArray return type initialized with the containing type class.

ftp://ftp.teamdev.com/updates/comfyj-generator-2.7.23427.jar - Updated "Codegen for ComfyJ" applicaiton. Solved compilition issues for UInt8/Int8 default initializers.

JExplorer

ftp://ftp.teamdev.com/updates/jexplorer-1.9.1.956.zip - build #956. Added the WebBrowser.getDocumentSource() method that allows receiving original HTML of a document. Like the "View source" command in context menu of Internet Explorer application.

ftp://ftp.teamdev.com/updates/jexplorer-1.9.1.959.zip - build #959. Fixed encoding issue in the WebBrowser.getContent(true) method. Changed the WebBrowser.getDocumentSource() method on WebBrowser.getContent(true).

Hotfixes for JExplorer 2.0 are published here: http://support.teamdev.com/docs/DOC-1072

JxBrowser

http://www.teamdev.com/downloads/jxbrowser/jxbrowser-1.4-cross-desktop-win_mac_linux.zip - JxBrowser 1.4 release. For the full list of resolved issues and improvements, please read the JxBrowser 1.4 Release Notes page.

Hotfixes for JxBrowser 2.0 are published here: http://support.teamdev.com/docs/DOC-1169

JExcel

ftp://ftp.teamdev.com/updates/jexcel-1.4.full.jar - full version of JExcel library that contains all stubs for Excel COM type library.

ftp://ftp.teamdev.com/updates/jexcel-1.4.23383.full.jar - full version of JExcel library withfix of the in-cell data validation dropdowns.

ftp://ftp.teamdev.com/updates/jexcel-1.4.23383-windows-32-bit.zip - fix of the in-cell data validation dropdowns.

ftp://ftp.teamdev.com/updates/jexcel-1.4.23627-windows-32-bit.zip - fixed event fireing when the new worksheet is created via copy.

WinPack

winpack-3.8.22317.jar - build #22317. Fixed the issue in low level keyboard and mouse hooks, so another installed low level hooks can work properly.

winpack-3.8.23224.jar - build #23224. Added functions to identify WinVista,Win7 and Win2008.

We will continue posting the links to the new updates on this page.

What's New in Nightly Builds

forum-admin@teamdev.com — Tue, 01 Dec 2009 18:35:16 GMT

This document summarizes the changes that haven't been released yet, but are already available in the nightly builds. Please note that we're updating this document when committing the appropriate changes to SVN, so you might need to wait for the nearest successful nightly build to see the recent changes added to this document. You can also follow the OpenFaces_JSF Twitter channel to receive notifications on the most notable new features as they are being implemented.

The nightly builds are usually published by 5:00am GMT+0 if successful.

Build number is not available on the site yet, though you can find it in openfaces.jar/META-INF/manifest.mf file – see the Build-Label field.

New Components

SelectOneMenu -- an extended version of the standard SelectOneMenu component with autocompletion support.
LevelIndicator -- a component that shows a numeric value in graphic style, similar to the LED volume meter and resource meter used in Windows Task Manager.

Enhancements

Ajax framework:
- Added AjaxRequest class that provides programmatic aspects for various aspects of OpenFaces Ajax requests.
- It's now possible to load application-specific data with Ajax requests. See the "Loading Data with Ajax" sections in "Ajax Framework" and "Ajax Component" documentation pages.
- It's now possible to specify components for reloading programmatically during the Ajax request. See the "The AjaxRequest Class" section in the "Ajax Framework" documentation.
- The render attribute of <o:ajax> is not required anymore, which simplifies the use cases when performing Ajax request just for loading data from the server.
- Added a new executeRenderedComponents attribute that allows skipping the "execute" lifecycle phases for components specified in the render attribute of such components as <o:ajax>, <o:commandButton>, etc.
- It's now possible to reload components in different forms simultaneously using the "absolute" id syntax, for example render=":form1:out1 :form2:out2".
Chart:
- Added interactive selection support for charts. It can be enabled by adding the <o:chartSelection> tag <o:chart> tag turns on an ability for interactive chart item selection. This means that a user can select a chart item (sector in pie charts, bar in bar charts, or shape in line charts) by clicking on it, and application developer has an ability to detect the selected item and optionally update the dependent content with Ajax on selection change. By default, chart's context menu have Save and Print menu item included that allows to download chart's image or easily display print dialog in order to print the chart's content.
- Now it is possible to add custom popups to the charts to allow displaying extended content for each chart item, which can be useful for example when implementing a drill down functionality. Custom item popups can be enabled by specifying the <o:chartPopup> tag as a child of chart view tags. As a container, the ChartPopup lets you place any kind of JSF components inside it to build its content. You can use the "sector" (for pie charts) and "point" (for bar and line charts) request scope variables when defining the child components of <o:chartPopup> tag to specify the item-dependent content.
- Implemented built in context menu support. Now it is possible to enable the standard chart context menu to allow performing useful actions on chart, like saving and printing the chart. The context menu support can be turned on by adding the <o:chartMenu> tag inside of the <o:chart> tag. It is possible to customize the content and appearance of the standard menu by customizing the <o:chartMenu> tag's attributes and child tags.
- Line Area Fill - Line charts has an advanced customization that enables an ability to fill the area below the line with a gradient or a flat color. This functionality can be enabled by adding either <o:gradientLineAreaFill> or <o:solidLineAreaFill> tag as a child of <o:lineChartView> tag. The <o:gradientLineAreaFill> tag is used to fill the area with a gradient from current line's color to the chart's background color.
- Added support for 3D mode in charts. 3D mode can be turned on/off using enable3D attribute of corresponding chart view tag.
- Added domain and range markers support for Bar and Line chart types. <o:marker> tag can be added as a child tag to <o:domainMarkers> and <o:rangeMarkers> tags. These tag should be added as a child tags of corresponding chart view tag.
- It's now possible to customize labels position for Bar and Line chart types.It can be done using defaultLabelsPosition, positiveLabelsPosition and negativeLabelsPosition attributes of <o:barChartView> and <o:lineChartView> tags.
- It's now possible to turn off gradients in Bar charts using showGradient attribute of <o:barChartView> tag
- Added support for bars' gradient customization. Gradient parameters allows customizing how the "shiny" part of the bar gradient is displayed. This is customized with three attributes: g1WhitePosition, g2FullIntensityPosition, g3LightIntensityPosition. These attributes should be specified as numbers in range [0..1], which correspond to the position of the appropriate gradient portion.
- Added support for shadow customization for both Bar and Pie chart views.
- Added support for outlines customization for Bar and Line chart types. Use defaultOutlineStyle and outlines attributes of <o:barChartView> or <o:lineChartView> tags.
- It's now possible to customize line styles for Line chart view using defaultLineStyle or lineStyles attributes of <o:lineChartView> tag.
Command components:
- Added onajaxstart/onajaxend/onerror events for CommandButton, CommandLink, CaptionButton, MenuItem and selection tags (<o:singleRowSelection>, <o:multipleNodeSelection>, etc.)
DataTable and TreeTable:
- Added disabled attribute for <o:checkboxColumn> and <o:selectAllCheckbox> tags.
- Added autoSaveState attribute to <o:columnResizing> tag for on-the-fly resizing state saving with Ajax (turned on by default).
- Added autoScrollbars attribute to <o:scrolling> tag that allows automatic hiding of scrollbars when the displayed data entirely fits in the visible area.
- Added rendered attribute to all selection tags to support scenarios where selection kind should be chosen at run-time.
- Greatly improved performance for DataTable and TreeTable components with scrolling and/or column resizing enabled under Internet Explorer.

Fixes

Ajax:
- Fixed Ajax "execute" functionality when "render" components are located in a different form (applicable to all components with Ajax execute and render attributes).
DataTable and TreeTable:
- Fixed the missing column resizing behavior when the sub-header row (aka filter row) is hidden with the "display:none" style.
- Selection functionality shouldn't be applied for the "no data" row.
- Fixed the problem of non-expanding TreeTable rows in IE quirks mode after adding any CSS styles dynamically.
- Fix for command components in TreeTables on deep hierarchy levels (2+ level).
- Fixed using the "subHeader" facet for <o:columns> tag.
- Fixed an issue with double-height nodes in case of empty node text under IE quirks mode.
- Fixed java.io.NotSerializableException exception on filterable DataTable/TreeTable components under MyFaces JSF implementation.
- Fixed "Unsupported binding type: class java.util.ArrayList" exception when binding multiple selection tags to a property of type ArrayList instead of List.
- Fixed "Unspecified error" in IE when reordering columns.
- Fixed declaring the resizingState attribute for <o:columnResizing> tag in JSP.
- Fixed ClassCastException when declaring "header"/"footer" facet without declaring "header"/"footer" facets for columns on a scrollable table.
- Fixed inability to select DataTable/TreeTable contents for copying to clipboard under IE.
- Fixed erroneous displaying of "Sort ascending" and "Sort descending" menu items for non-sortable columns.
- Fixed row heights mismatch when exanding nodes in horizontally-scrollable TreeTables in some cases.
- Fixed misplaced loading of child rows when expanding nodes in scrollable TreeTable in IE 6/7.
- Fixed writing column resizing state into a bound property.
- Fixed not saving collapsed nodes in TreeTable's expansion state.
- Fixed error on DataTable with zero-item model and column filters.
Chart:
- Fixed actionListener attribute for chart view tags which worked only when the tooltip attribute was declared.
DropDownField and SuggestionField:
- Fixed using the string-to-string converters.
- Fixed typing comma char in <o:dropDownField> and <o:suggestionField> with suggestionMode="custom".
Window
- Fixed an issue with <select> elements protruding through Window's modal area.
- Fixed an issue of empty window content when showing a window with Ajax call.
- Fixed the "Can't move focus to the control..." JavaScript error when opening a modal window under IE in some cases.
- Fixed an inability to specify draggable="false" for the Window component.
Other:
- Fixed automatic BorderLayoutPanel resizing when using it as a root component.
- Fixed attaching PopupMenu to FoldingPanel.
- Fixed client validation for required fields with a prompt text.
- Solved excessive "enclosing form cannot be found for component" log warnings when using <rich:tabPanel> with OpenFaces client validation enabled.
- Fixed adding the util-2.x.js file to the pages without OpenFaces components/functionality, though it can still be included on such pages by setting the org.openfaces.forceIncludingUtilJs init parameter if you'd like to have the O$ function on such pages (see the Common Concepts documentation section).
- Fixed "java.lang.InstantiationException: java.util.Arrays$ArrayList" exception during state restoring in some configurations.
- Specifying disabled images for image-based SelectManyCheckbox is now optional.
- Fixed using converter for <o:inputText> component.

Roadmap

forum-admin@teamdev.com — Thu, 23 Apr 2009 16:34:14 GMT

To know when the next version of OpenFaces will come out and what features or components will be available in it, use the OpenFaces roadmap. Note, however, that these are only preliminary plans for future releases and, therefore, they may change over time. Please also note that the roadmap lists only major features of these releases.

If you want to see more new features in the OpenFaces roadmap, let us know. Visit our forum, submit requests to our issue tracking system, or e-mail us directly at info@openfaces.org. You can also follow the current development news in OpenFaces twitter.

OpenFaces 3.0 Early Access 2 (released)

This release is going to have the following modifications since EA1 release:

A part of OpenFaces infrastructure transitioned to JSF 2.0 API instead of old JSF 1.2 ones.
Ajax state handling fixes, which resolves EA1 issues such as Ajax features of DataTable and TreeTable components.
A fix for a conflict with JSF 2.0 Ajax functionality (OF-34)

This version can be downloaded here. See the release notes.

OpenFaces 3.0 (September)

OpenFaces version 3.0 will be maintained in parallel with OpenFaces version 2.0 while there is still interest in JSF 1.2. Both of these versions will have the same set of features but they will be targeted at JSF 2.0 and JSF 1.2 respectively.

OpenFaces 2.1/3.1

Enhanced SelectOneMenu component.
WeekTable component, analogous to DayTable but showing events for a week.
MonthTable component, analogous to DayTable but showing events for a month.
Timetable component -- displays a schedule of events with multiple views (DayTable/WeekTable/MonthTable components combined).
DataTable extensions.

Future releases

MenuBar component.
Panel component.
ProgressBar component.
Interactive column list customization in DataTable and TreeTable components.
Add the nodeDataByKey attribute to the TreeTable (similar to rowDataByKey in the DataTable component for enhanced handling of concurrent data modifications).
Support for displaying a checkbox/selection column with images instead of check boxes.
Nesting of DataTable/TreeTable inside other DataTable/TreeTable.
Flexible paginator customization.
Additional chart types.
Validation groups.
Support for IDEs (NetBeans, IBM Rational Application Developer, Sun Java Studio Creator, JDeveloper, etc.).

Migrating from QuipuKit 1.6.2

forum-admin@teamdev.com — Thu, 30 Apr 2009 16:06:49 GMT

This document describes how to upgrade your application from QuipuKit 1.6.2 to OpenFaces 2.0.

General

OpenFaces 2.0 requires Java version 5 or higher.
OpenFaces 2.0 requires JSF 1.2.x (Mojarra or MyFaces).
As with QuipuKit 1.x, OpenFaces can be used with JSP and Facelets. Though if you are working with Facelets, please ensure that you are using a version 1.1.14 or higher.
Support for Ajax4jsf framework of versions that existed prior to integrating Ajax4jsf into RichFaces has been dropped. Use RichFaces 3.3.0 or later instead of Ajax4jsf.
Support for RichFaces library earlier than version 3.3.0 has been dropped. Upgrade to RichFaces 3.3.0 or later.
Suppor for JBoss Seam framework of versions earlier than 2.0 has been dropped.
OpenFaces 2.0 comes as a single Jar file named openfaces.jar . License jar file that was required for QuipuKit 1.x is not required anymore and should be removed. Other jar dependencies remained the same (see the Installation and Configuration section in OpenFaces Developer's Guide).

Changes Dependent on the New Product Name

Since version 2.0 QuipuKit has been renamed to OpenFaces. Hence all of the names that depended on the old product name must be changed. Here's the full list of changes that might require updates in your application:

Renamed the root package from teamdev.jsf to org.openfaces. Therefore you need to update paths to imported packages in your code appropriately. Please also pay special attention to renaming the resource filter class in web.xml from teamdev.jsf.util.ResourceFilter to org.openfaces.util.ResourceFilter . The teamdev.jsf.portlet.QuipuKitPortlet class for configuring portlet applications has also been renamed to org.openfaces.portlet.OpenFacesPortlet.
Changed prefixes of component-type and component-family strings from teamdev.jsf to org.openfaces .
The prefixes for application parameters specified in web.xml file were changed from teamdev.jsf to org.openfaces .
The /qk_internalResource/* resource mapping that can optionally be specified in web.xml for performance optimization has been renamed to /openFacesResources/* .
Changed validation message key prefixes for message bundles from teamdev.jsf to org.openfaces .
Namespace for OpenFaces component tags was changed from http://teamdev.com/quipukit to http://org.openfaces/ . Although it is not required to change the namespace prefix in your page files, we recommend to use the "o" prefix when using OpenFaces tags, for example <o:dataTable>.

Library Changes

OpenFaces now requires Commons-Collections library (commons-collection.jar) as a runtime dependency.
OpenFaces was upgraded to work with the new versions of the CSSParser and JFreeChart libraries.

IMPORTANT: since the new versions of these libraries have some incompatible changes, you have to replace the old versions of these libraries with the new ones when upgrading from OpenFaces EAP2 or earlier. Here's the list of files that must be updated with their new versions which can be found in OpenFaces distribution package:

For JFreeChart library, just update jfreechart.jar and jcommon.jar to the new versions.
For CSSParser library, remove the old ss_css2.jar file, and add cssparser.jar and sac.jar instead.

Removal of Deprecated API

In version 2.0 we have removed the API that was marked as deprecated in QuipuKit 1.x. Below is the list of changes, with the description of how to retain the appropriate functionality using the new API.

The list of removed attributes, and the appropriate replacements:

Component	Old Attribute Name	Replacement
HintLabel	title	hint
DataTable, TreeTable	rowOnclick, rowOndblclick, rowOnmousedown, rowOnmousemove, rowOnmouseout, rowOnmouseover, rowOnmouseup	Place <o:row onclick="..."/> inside of your <o:dataTable> or <o:treeTable> tag (applicable for all listed events).
TabSet	submitOnChange	Use onchange attribute with manual form submission code, e.g. onchange="document.forms[0].submit()"; or use the <o:reloadComponents> tag to introduce Ajax interaction for the onchange event

The list of removed tags and their replacements:

Tag	Replacement
<q:cellStyle>	Rename all <q:cellStyle> tags to <o:cell> and enclose them into empty <o:row> tags with no additional attributes.
<q:rowStyle>	<o:row>

Renamed, Moved API

Moved/renamed packages:

Old Package Name	New Package Name
teamdev.jsf.component.ajaxsettings	org.openfaces.component.ajaxsettings
teamdev.jsf.component.calendar.daterange	org.openfaces.component.calendar
teamdev.jsf.component.confirmation	org.openfaces.component.window
teamdev.jsf.component.chart.impl.view	org.openfaces.component.chart
teamdev.jsf.component.chart.impl.model	org.openfaces.component.chart
teamdev.jsf.component.chart.impl.event	org.openfaces.component.chart
teamdev.jsf.component.chart.view	org.openfaces.component.chart
teamdev.jsf.component.datatable	org.openfaces.component.table
teamdev.jsf.component.datechooser	org.openfaces.component.input
teamdev.jsf.component.dropdownfield	org.openfaces.component.input
teamdev.jsf.component.dynamicImage	org.openfaces.component.output
teamdev.jsf.component.focus	org.openfaces.component.util
teamdev.jsf.component.foldingpanel	org.openfaces.component.panel
teamdev.jsf.component.graphicText	org.openfaces.component.output
teamdev.jsf.component.hintlabel	org.openfaces.component.output
teamdev.jsf.component.message	org.openfaces.component.validation
teamdev.jsf.component.inputText	org.openfaces.component.input
teamdev.jsf.component.inputTextarea	org.openfaces.component.input
teamdev.jsf.component.loadbundle	org.openfaces.component.util
teamdev.jsf.component.popuplayer	org.openfaces.component.window
teamdev.jsf.component.scrollposition	org.openfaces.component.util
teamdev.jsf.component.spinner	org.openfaces.component.input
teamdev.jsf.component.suggestionField	org.openfaces.component.input
teamdev.jsf.component.tabbedpane	org.openfaces.component.panel
teamdev.jsf.component.tabset	org.openfaces.component.select
teamdev.jsf.component.treetable	org.openfaces.component.table
teamdev.jsf.component.twolistselection	org.openfaces.component.select

Moved/renamed classes:

Old Class Name	New Class Name
teamdev.jsf.component.chart.impl.model.PlainModelImpl	org.openfaces.component.chart.PlainModel
teamdev.jsf.component.chart.impl.model.PlainSeriesImpl	org.openfaces.component.chart.PlainSeries
teamdev.jsf.component.chart.impl.model.TupleImpl	org.openfaces.component.chart.Tuple
teamdev.jsf.component.dropdown.DropDownField	org.openfaces.component.input.DropDownField
teamdev.jsf.component.dropdown.HorizontalAlignment	org.openfaces.component.Side
teamdev.jsf.component.message.FloatingIconMessage	org.openfaces.component.validation.FloatingIconMessage
teamdev.jsf.component.output.HintLabel	org.openfaces.component.output.HintLabel
teamdev.jsf.component.popuplayer.Confirmation	org.openfaces.component.window.Confirmation
teamdev.jsf.component.popuplayer.ButtonType	org.openfaces.component.window.ButtonType
teamdev.jsf.component.util.LoadingMode	org.openfaces.component.LoadingMode
teamdev.jsf.component.util.FacesUtil	org.openfaces.util.Faces
teamdev.jsf.renderkit.validation.validator.ClientValidationEnum	org.openfaces.component.validation.ClientValidationMode

Renamed tags:

Old Tag Name	New Tag Name
<q:customValidator>	<o:validateCustom>
<q:emailValidator>	<o:validateEmail>
<q:equalValidator>	<o:validateEqual>
<q:regExpValidator>	<o:validateRegex>
<o:tabbedPaneItem>	<o:subPanel>
<o:tabbedPaneItems>	<o:subPanels>
<q:urlValidator>	<o:validateUrl>

Renamed attributes. These are applicable to both property names in the actual component classes and the appropriate attribute names.

DataTable and TreeTable

Component/Tag	Old Attribute Name	New Attribute Name
Chart	style	textStyle
Confirmation	captionText	caption
Confirmation	invokerId	for
Confirmation	invokerEventName	event
Confirmation	middleAreaClass	contentClass
Confirmation	middleAreaStyle	contentStyle
Confirmation	rolloverMiddleAreaClass	rolloverContentClass
Confirmation	rolloverMiddleAreaStyle	rolloverContentStyle
DataTable and TreeTable	allRecordsFilterName	allRecordsFilterText
DataTable and TreeTable	emptyRecordsFilterName	emptyRecordsFilterText
DataTable and TreeTable	`nonEmptyRecordsFilterName`	nonEmptyRecordsFilterText
DataTable and TreeTable	filterRowStyle	subHeaderRowStyle
DataTable and TreeTable	filterRowClass	subHeaderRowClass
DataTable and TreeTable	filterRowSeparator	subHeaderRowSeparator
GraphicText	style	textStyle
PopupLayer, Confirmation	closeOnOuterClick	hideOnOuterClick
TwoListSelection	allowSorting	sortingAllowed
TwoListSelection	allowItemsOrdering	reorderingAllowed
all column tags	filterCellStyle	subHeaderStyle
all column tags	filterCellClass	subHeaderClass

Renamed methods:

Class	Old Method Name	New Method Name
org.openfaces.component.chart.PlainSeries	setId	setKey
org.openfaces.component.chart.PlainSeries	setSeriesKey	setKey
org.openfaces.component.chart.PlainSeries	getSeriesKey	getKey
org.openfaces.component.chart.Series	getId	getKey

Component/Tag/Class	Change Description
<o:confirmation>	Changed event attribute usage for <o:confirmation> tag: now there shouldn't be "on" prefix in event names, e.g. you should use "click" instead of "onclick".
<o:foldingPanel> and <o:tabbedPane>	The value "ajax" of loadingMode attribute has been renamed to "ajaxLazy". The appropriate enumeration constant in theorg.openfaces.component.LoadingMode enumeration has also been renamed from AJAX to AJAX_LAZY.
<o:scrollPosition>	The `scrollX` and `scrollY` attributes of `<o:scrollPosition>` tag were combined into one `value` attribute that should be specified as a binding to a property of type `java.awt.Point`.
<o:tabbedPaneItem>	Renamed tag <o:tabbedPaneItem> -> <o:subPanel> Renamed "tag" facet to "caption"
Confirmation, FoldingPanel	Renamed getCaption/setCaption methods to getCaptionFacet/setCaptionFacet
org.openfaces.util.FacesUtil	Renamed class: FacesUtil -> Faces Replaced getRequestMapValue(String varName) method with var(String varName) method, which is more universal as it can fetch not just request-scope variables. Renamed method: getRequestParameterMapValue(String paramName) -> requestParam(String paramName). Removed getRequestParameterMapValueAsDate(String paramName) method. Its invocations should now be replaced with requestParam(String paramName, Date.class).
Classes in org.openfaces.component.table package (former teamdev.jsf.component.datatable) classes	The following classes were renamed to match the appropriate tag names: TableColumnGroup -> ColumnGroup, TableColumn -> Column, DynamicTableColumn -> DynamicColumn, TableColumns -> Columns, TableCell -> Cell, TableRow -> Row . The appropriate COMPONENT_TYPE and COMPONENT_FAMILY strings were changed accordingly.

Client-Side API Changes

The New `O$(id)` Function

OpenFaces 2.0 introduces a new JavaScript function named "O$(id)" (capital letter O and a dollar sign) that locates a DOM element by its identifier. Locating element by id is a very common scenario, where the "document.getElementById(id)" function is usually invoked. The O$(id) function works in the same way and can be used as a short replacement for this expression. See the documentation for usage example.

Unified Client-Side API

In QuipuKit 1.x each method of component's client-side API was available in two ways:

As a "global" function prefixed with "q_" and receiving component identifier as the first parameter, for example q_showPopupLayer(popupId);
As a component instance method without a prefix and component id parameter, for example popup.show().

In OpenFaces 2.0, the first way of using the component's client-side API is not available anymore. Therefore you should replace invocations of all "global" functions, the functions that start with the "q_" prefix, with usages of the appropriate instance methods. We recommend using the new O$(id) function to simplify this process. Here are some examples of replacing the old invocations with the new ones:

Old-Style Invocation	New-Style Invocation
`q_showPopupLayer("form:popup1")`	`O$("form:popup1").show()`
`q_showPopupLayerAtXY("form:popup1", 150, 100)`	`O$("form:popup1").showAtXY(150, 100)`
`q_isTableSelectionEmpty("form:dataTable1")`	`O$("form:datatable1").isSelectionEmpty()`

Client-Side Validation Functions

Validation functions have undergone a change similar to the one described above. The notation for validation function names was changed. The "q_" prefix was removed, and all functions were placed into the "O$" namespace instead. That means that now you should invoke such functions as methods of the "O$" variable. Here are the examples:

Old-Style Invocation	New-Style Invocation
`q_validate(myComponent)`	`O$.validate(myComponent)`
`q_validateForm(document.forms[0])`	`O$.validateForm(document.forms[0])`

Migrating to the New Filtering API

All of the filtering-related attributes were removed from <o:column> (former <q:column>) tag and should now be specified inside of one of the new filter tags, depending on type of the filter (formerly specified with thefilterKind attribute). There's the new "subHeader" facet in <o:column> tag, where the filter tag should be placed. Here are the instructions that you can use to migrate to the new API:

1. Place the filter tag inside of the column's "subHeader" facet depending on a value of filterKind attribute and remove the filterKind attribute from column tag as follows:

`filterKind` value	Tag name
`"searchField"` or no `filterKind` attribute	`<o:inputTextFilter>`
`"dropDownField"`	`<o:dropDownFieldFilter>`
`"comboBox"`	`<o:comboBoxFilter>`

2. Move all of the filtering-related attributes from the column tag to the filter tag and rename them as follows:

Old attribute name	New attribute name
`filterExpression`	`expression`
`filterValue`	`value`
`filterValues`	`options`
`filterPromptText`	`promptText`
`filterPromptTextStyle`	`promptTextStyle`
`filterPromptTextClass`	`promptTextClass`

Here's an example of migrating to the new API.
Old-style code:


<o:column filterKind="dropDownField" filterExpression="#{product.category}" filterValues="#{Products.categories}">
...

New-style code:


<o:column>
    <f:facet name="subHeader">
        <o:dropDownFieldFilter expression="#{product.category}" options="#{Products.categories}"/>
    </f:facet>
...

3. [Required if you are using custom data providing or filter criterion classes in Java code]

3.1. The type of the filterCriteria request-scope variable was changed from List to org.openfaces.component.filter.CompositeFilterCriterion. TheCompositeFilterCriterion class has the getCriteria() method that returns a list of criterion objects.

3.2. The EmptyFilterCriterion, NonEmptyFilterCriterion and TextFilterCriterion classes were replaced with a genericorg.openfaces.component.filter.ExpressionFilterCriterion class, that is parameterized with filter condition to address different filtering scenarios (see the getCondition()and isInverse() methods). See the following items for detilas.

3.3. The usage getColumnId() method of TextFilterCriterion is now replaced with the usage of getExpressionStr() method of ExpressionFilterCriterion class, and it now returns filter's expression string instead of column id. Replacement of column Id with filter's expression string is required because a filter is not required to be placed inside of table's column now, and can even be placed outside of the table, hence filter's expression is now the filter's identifier when using the custom data providing mode. So besides replacing getColumnId() invocations with getExpressionStr(), be sure to specify the appropriate string (a-la column id) in the filter's expression attribute.

3.4. The usage of getText() method of TextFilterCriterion is now replaced with usage of getArg1() method. Unlike the getText() method which returns java.lang.String, getArg1() returns java.lang.Object to allow non-string comparisons, so you should convert the result of invoking the getArg1() method using the toString() method to match the old behavior.

3.5. The checks for instances of EmptyFilterCriterion and NonEmptyFilterCriterion classes should now be replaced with checks of the ExpressionFilterCriterion's condition and inverse properties. The condition is an enumeration of org.openfaces.component.filter.FilterCondition type, which distinguishes between different types of filtering, and in particular the value of FilterCondition.EMPTY means that empty records should be accepted (and this is a replacement for checking the EmptyFilterCriterion class instance), and ifisInverse() method returns true at the same time this is the case for filtering the non-empty records (and this is a replacement for checking the NonEmptyFilterCriterion class instance).

Here's a simple example of how the appropriate code is to be changed as a result of this change.

Old-style code:

<o:column id="name" filterKind="searchField">

...

List<ColumnFilterCriterion> criteria = (List) Faces.var("filterCriteria");

for (ColumnFilterCriterion criterion: criteria) {

String columnId = criterion.getColumnId();

String searchString = ((TextFilterCriterion)criterion).getText();

...

New-style code:

<o:column>

<f:facet name="subHeader">

<o:inputTextFilter expression="name"/>

</f:facet>

...

CompositeFilterCriterion criteria = Faces.var("filterCriteria", CompositeFilterCriterion.class);

for (FilterCriterion c: criteria.getCriteria) {

ExpressionFilterCriterion criterion = (ExpressionFilterCriterion) c;

String columnId = criterion.getExpressionStr();

String searchString = criterion.getArg1().toString();

...

Please see the "Handling Large Datasets" section in the DataTable documentation for the general description of the new API.

4. [Optional] Drop-down field filters are now configured to provide input suggestions by default, though you can turn this behavior off if you'd like the filters to behave exactly as before. This can be done by declaring the following attributes on the <o:dropDownFieldFilter> tag: suggestionMode="none" autoComplete="false"

5. [Optional] Input text filters now automatically perform filtering as the user types in the field. This behavior can be turned off to match the old behavior by specifying the following attribute for<o:inputTextFilter> tag: autoFilterDelay="-1"

6. [Optional] The default filtering condition for non-string values is now "equals" instead of "contains". If you'd like to retain the old behavior of always searching by substring anyway (e.g. if you'd like for filtering integer values "1" to match both "1" and "10"), declare the condition="contains" attribute on the appropriate filter tags.

The `q_refreshTable` and `q_refreshTreeTable` Functions

In OpenFaces 2.0, the q_refreshTable and q_refreshTreeTable functions were removed in favor of the new API that allows reloading any components and provides a wider set of possibilities. OpenFaces 2.0 introduces the new ReloadComponents component that allows reloading one or more components with Ajax. This component provides programmatic access to its functionality using the O$.reloadComponents function. q_refreshTable and q_refreshTreeTable function invocations should be replaced with O$.ajax.request invocations as shown below.

Old-Style Invocation New-Style Invocation Notes

q_refreshTable("form:dataTable1") O$.ajax.request(this, event, {render:"form:dataTable1"}) Refreshing the table without additional options

Old-Style Invocation	New-Style Invocation	Notes
`q_refreshTable("form:dataTable1")`	`O$.ajax.request(this, event, {render:"form:dataTable1"})`	Refreshing the table without additional options
q_refreshTable("form:dataTable1", ["f`orm:field1","form:field2"])`	`O$.ajax.request(this, event, {render:"form:dataTable1",` `execute: "form:field1 form:field2"})`	Refreshing the table with submitting data for two additional form fields
`q_refreshTable("form:dataTable1",` `["form:field1","form:field2"],` `"MyBean.action1")`	`O$.ajax.request(this, event, {render:"form:dataTable1",` `execute: "form:field1 form:field2",` `listener: "MyBean.action1Listener"})`	Refreshing the table with submitting data for two additional form fields and invoking the "MyBean.action1Listener" server action. Note that the action listener function action1Listener should take the additional ActionEvent parameter, so it'll be declared like this: public void action1Listener(ActionEvent event) { // execute the action }

q_refreshTable("form:dataTable1",

["form:field1","form:field2"])

O$.ajax.request(this, event, {render:"form:dataTable1",
execute: "form:field1 form:field2"})

Refreshing the table with submitting data for two additional form fields

q_refreshTable("form:dataTable1",

["form:field1","form:field2"],

"MyBean.action1")

O$.ajax.request(this, event, {render:"form:dataTable1",
execute: "form:field1 form:field2",
listener: "MyBean.action1Listener"})

Refreshing the table with submitting data for two additional form fields and invoking the "MyBean.action1Listener" server action. Note that the action listener function action1Listener should take the additional ActionEvent parameter, so it'll be declared like this:

public void action1Listener(ActionEvent event) {

// execute the action

}

The same replacements are applicable for the q_refreshTreeTable function. See the documentation for the ReloadComponents component for more information.

API Changes

Component	Change Description
Confirmation	The `q_runConfirmedFunctionByName`/`runConfirmedFunctionByName` client-side function was removed. Use `runConfirmedFunction` function instead and pass an appropriate closure (aka anonymous function) there instead.

Other

Component/Attribute	Note
All components	All methods that received ValueBinding/MethodBinding arguments now receive ValueExpression/MethodExpression
Calendar, FoldingPanel, TabbedPane, TabSet	These components have been made focusable by default in OpenFaces 2.0. You can make them non-focusable as they were in QuipuKit 1.x by specifying the `focusable="false"` attribute.
Calendar, DateChooser	The `showWeekNumber` and `weekText` attributes were removed because of their counterintuitive display and meaning. An alternative implementation can be expected in future versions if needed.
Confirmation	The `event` attribute of `<o:confirmation>` tag now defaults to `"onclick"`, so you can remove it for declarations where it equals to the default value.
Confirmation	Confirmation components that previously were declared without the `for` (former name is `invokerId`) attribute for explicit usage via JavaScript should now include the explicit `standalone="true"` attribute declaration. Otherwise these components will automatically be attached to the parent component.
Confirmation	`closeButtonImageUrl` and `showCloseWindowButton` attributes were replaced with a notion of caption areas that is a generic way of customizing caption buttons and is used in FoldingPanel and Window components in addition to the Confirmation component. Here's an example of migrating to the new API: Old-style code: <q:confirmation closeButtonImageUrl="close.gif" ... /> New-style code: <o:confirmation ...> <o:captionArea> <o:closeWindowButton imageUrl="close.gif"/> </o:captionArea> </o:confirmation> The new `<o:closeWindowButton>` tag also provides additional attributes for customizing other aspects of button's appearance such as a style and a hint. The window closing button is displayed by default, but you can hide it just by placing an empty `<o:captionArea/>` tag inside of `<o:confirmation>` tag. See the documentation for Confirmation component for more details about customizing the caption buttons.
FoldingPanel	Adding StateChangeListener to FoldingPanel doesn't trigger form submission on expanding/collapsing FoldingPanel anymore. Use onstatechange event with manual form submission script if necessary.
FoldingPanel	Changed the way of customizing toggle button's image and hint. Now there's the possibility to specify so called caption areas, which allows specifying additional buttons in the panel's caption. As a part of this, a new tag for the toggle button was created: `<o:expansionToggleButton>`, which now includes all of the image URL properties that were previously specified through `<q:foldingPanel>` (names were unchanged), the `hint` attribute instead of `foldingPanel`'s `buttonHint` attribute and other new attributes. Usages of <q:foldingPanel> tag's buttonPlacement attribute should be replaced with using the `alignment` attribute of `<o:captionArea>` tag. Note that if you don't need customization of the toggle button itself, you should include an empty declaration of the `<o:expansionToggleButton/>` tag into the `<o:captionArea>` tag for the area to be non-empty. Here's an example of migrating to the new API: Old-style code: <q:foldingPanel collapsedImageUrl="collapsed.gif" expandedImageUrl="expanded.gif" buttonHint="Click here" buttonPlacement="left" ...> ... </q:foldingPanel> New-style code: <o:foldingPanel ...> <o:captionArea alignment="left"> <o:expansionToggleButton collapsedImageUrl="collapsed.gif" expandedImageUrl="expanded.gif" hint="Click here"/> </o:captionArea> ... </o:foldingPanel> See FoldingPanel documentation for a detailed description of how to use caption areas and the `<o:expansionToggleButton>` tag.
ScrollPosition	Changed the way of specifying the "for" attribute to be consistent with other components. It should now be specified in the same way as a "for" attribute of <h:outputLabel>, <h:message> or <o:confirmation> components. Previously the whole tree was searched for the short id specified in this attribute. Now it's either an "absolute" id if it starts with a colon symbol, or a "relative" id otherwise. See ScrollPosition documentation for details.
Validation	The <q:message> and <q:messages> tags were removed. Since they are identical in API with the standard counterparts, you just need to replace them with the standard <h:message> and <h:messages> tags respectively.
Validation	Validator IDs were renamed to match the traditional convention: `org.openfaces.CustomValidator` -> `org.openfaces.Custom` `org.openfaces.EmailValidator` -> `org.openfaces.EMail` `org.openfaces.EqualValidator` -> `org.openfaces.Equal` `org.openfaces.RegexValidator` -> `org.openfaces.RegularExpression` `org.openfaces.URLValidator` -> `org.openfaces.URL` The following message bundle keys were amended to match the updated validator names: `org.openfaces.EmailValidatorMessage` -> `org.openfaces.EMailValidatorMessage` `org.openfaces.RegExpValidatorMessage` -> `org.openfaces.RegexValidatorMessage`

Browser component embedded within JPanel

roman.lymar@teamdev.com — Fri, 19 Jun 2009 08:19:45 GMT

The sample demonstrates how to create instance of JxBrowser library, add JxBrowser component to Swing container (JPanel) and navigate to a resource specified by a URL.

/*
 * Copyright (c) 2000-2010 TeamDev Ltd. All rights reserved.
 * TeamDev PROPRIETARY and CONFIDENTIAL.
 * Use is subject to license terms.
 */
import com.teamdev.jxbrowser.WebBrowser;
import com.teamdev.jxbrowser.WebBrowserFactory;
import com.teamdev.xpcom.Xpcom;
 
import javax.swing.*;
import java.awt.*;
 
public class BrowserSample {
    public static void main(String args[]) {
        Browser browser = BrowserFactory.createBrowser();
 
        // add browser component to JPanel
        JPanel panel = new JPanel(new BorderLayout());
        panel.add(browser.getComponent(), BorderLayout.CENTER);
 
        JFrame frame = new JFrame("JxBrowser Sample");
        frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        frame.getContentPane().add(panel, BorderLayout.CENTER);
        frame.setSize(640, 480);
        frame.setLocationRelativeTo(null);
        frame.setVisible(true);
 
        browser.navigate("http://www.google.com");
    }
}

JxBrowser Technical Questions and Answers

roman.lymar@teamdev.com — Thu, 19 Feb 2009 12:55:17 GMT

Get answers to most commonly asked technical questions about JxBrowser. If you cannot find the answer here, please send us your question using the support request form, and we will add it to this FAQ after answering you.

Also you can find a lot of useful information about using JxBrowser in JxBrowser Programmer's Guide

1. How to work with Browser engines?

Answer: You can find answer on this question in our JxBrowser Programmer's Guide

2. I can not run my application via Java Web Start. I have "Unsigned application requesting unrestricted access to system" error in JWS console.

Answer: This error occurs because JWS does not accept files with more than one signature. It is also mandatory that all application JAR files are signed with the same signature. Please read about how to resolve your issue in the сhapter Using JxBrowser with Java Web Start

3. I'm using JxBrowser 1.x and would like to upgrade to 2.x. Do I need to purchase an upgrade or will my 1.x license work?

Answer: JxBrowser 2.x will not work with JxBrowser 1.x licenses, thus you need upgrade to JxBrowser 2.x license. If you already our customer then you can upgrade your current version with a 25% discount. Please contact our sales department with your upgrade requests.

4. I found that JxBrowser 2.x distribution package doesn't contain JNIWrapper JAR and native libraries. Where can I find them because I use JNIWrapper for other things in my application?

Answer: To decrease the amount of files in JxBrowser 2.x distribution package we moved JNIWrapper library into jxbrowser.jar and all native libraries into jniwrap-native.jar. This means that you do not need to have separate JNIWrapper JAR file in your project to work with JNIWrapper API.

5. Where should I put the JxBrowser 2.x license file (teamdev.license)?

Answer: You should put the license file into META-INF folder of your application JAR file or any JAR file included into your application class path. In JxBrowser 2.0 we have disabled functionality that allows finding license file in the application working directory.

6. I have a Mac package and a Windows package. I don't want to include unnecessary files. What jars should each package (Windows & Mac) include?

Answer: It depends on which browser engine you want to use on each platform (Mozilla, Internet Explorer or Safari). Please read about how to resolve your issue in the сhapter Libraries Dependency

7. Can I implement my own print dialog?

Answer: Yes you can implement your own print dialog. You can build your own print dialog GUI and invoke appropriate print actions using JxBrowser printing API. The sample that demonstrates how to print the loaded web page and receive print progress events you can find here: PrintingSample

8. Can I programmatically turn on/off JavaScript execution, plug-ins or images downloading?

Answer: Yes, JxBrowser provides this functionality. The following sample demonstrates how to perform these operations you can find at: ConfigureContentSettingsSample

9. Can I pre-install or install at runtime firefox plugins/extensions?

Answer: JxBrowser allows you to enable or disable Mozilla plugins, but it doesn't provide functionality that allows controlling Mozilla plugins installation process programmatically.

As for the extensions - JxBrowser's Mozilla browser component is based on Mozilla engine and it doesn't support Firefox extensions, because these extensions are designed only for Firefox application and unfortunately Mozilla engine doesn't know about installed Firefox extensions at all.

10. Can I control of link execution? For an example when a user selects a link on the page, I want control if the link will be executed. I need the ability to examine the link (where it's going to) and make a decision whether allow or not allow the browser to perform this action. What I need to do?

Answer: With JxBrowser API you can implement any navigation rules. For example you can find how to decide whether to allow navigation or cancel it at the following sample:CancelNavigationSample

11. I purchased JxBrowser license. Where I should (and how ) put Development and Runtime license?

Answer: The license file (Development or Runtime) should be placed in your application's JAR file, in its META-INF folder or in META-INF folder of any JAR file included into your application class path: http://support.teamdev.com/docs/DOC-1051

You need to have the Development License Key installed to use JxBrowser for development purposes. For example you can create a license.jar with the following structure and include it into your application project class path:

license.jar/
META-INF/
teamdev.licenses

The Runtime License Key should be used when you distribute your software with JxBrowser enclosed. For example you can include Runtime License Key into your application JAR file during build process.

12. Before initialization of JxBrowser instance on Windows platform I have got "Error Dialog" with following message: "The application has failed to start because MSVCR80.dll was not found. Re-installing the application may fix this problem." What can I make for disappearing this error dialog?

Answer: You should try to use JxBrowser2.3 version or later with JDK/JRE 1.6.0_07 or higher.

Samples

All available JxBrowser samples you can find here:

http://support.teamdev.com/community/java_platform_integration_solutions/jxbrowser/demo_samples?view=documents

All smaples were bundled together with JxBrowser distibution.

QuipuKit Hotfixes

forum-admin@teamdev.com — Tue, 27 Apr 2010 15:19:19 GMT

This document contains the QuipuKit hotfixes released after the last release of QuipuKit 1.x version family -- QuipuKit 1.6.2. We recommend upgrading to the new major version of QuipuKit named OpenFaces 2.0 -- read the details on the OpenFaces site: http://openfaces.org/. See also what's new has been added in OpenFaces 2.0 the and the migration guide.

QuipuKit 1.6.2 Update 1

Full package: quipukit-1.6.2_u1.zip

Jar file: quipukit-1.6.2_u1.jar

Fixes in this update:

- Fixed duplicating the content of <h:messages> content when opening DateChooser.

- Fixed disappearing of a "required" validation message when opening DateChooser's drop-down.

- Fixed Ajax functionality when using several QuipuKit-based portlets on the same page.

- Fixed intermittent errors on concurrent Ajax requests and form submissions.

- Fixed the occasional inability to expand TreeTable node after Ajax request for reloading another TreeTable/DataTable.

- Fixed double-height TreeTable nodes in case of empty node texts under IE.

QuipuKit 1.6.2 Update 2

Full package: quipukit-1.6.2_u2.zip

Jar file: quipukit-1.6.2_u2.jar

Fixes in this update:

- Fixed binding multiple selection tags to List/Set type descendants rather than List/Set types themselves.

QuipuKit 1.6.2 Update 3

Full package: quipukit-1.6.2_u3.zip

Jar file: quipukit-1.6.2_u3.jar

Fixes in this update:

- Fixed inability to select DataTable/TreeTable contents for copying to clipboard under IE.

Recording sound from 'Stereo Mix' device with JxCapture 2 on Vista and Windows 7 systems

sergei.piletsky@teamdev.com — Tue, 06 Jul 2010 13:17:31 GMT

JxCapture 2 provides the ability to record sound from various recording devices available in a system.

To enable audio recording during video capture just two steps are required:

1. Open "Video Capture Options" dialog and select "Enable Audio Recording" option in it;
2. Then select a required audio source device (which is a microphone by default).

This is also can be done programmatically at runtime using the following code:

List<AudioSource> audioSources = AudioSource.getAvailable();
if (audioSources.isEmpty()) {
    System.err.println("No audio sources available");
} else {
    AudioSource audioSource = audioSources.get(0);
    videoCapture.setAudioSource(audioSource);
}

Apart from recording sound from a microphone you may also want to record "what you hear" sound. This also can done with JxCapture 2 - all you need to do is to select the 'Stereo Mix' device instead of a microphone:

However, on some Vista and Windows 7 systems such device is not available at all. This issue can be explained by the fact that this device is not supported by default Microsoft sound card drivers. Fortunately this issue can be solved by installing the manufacture's sound card drivers. The guide below demonstrates how to make it available:

1) Install sound card drivers. In this example I have used driver for Realtek HD audio device.

2) To configure recording devices, right click on Speakers icon in system tray and click on "Recording devices" menu item:

The "Sound" properties dialog should appear:

The same dialog can activated via Control Panel:

3) To display required 'Stereo Mix' device right click on Microphone device and select "Show Disabled Devices" and "Show Disconnected Devices" menu items:

4) Then, enable 'Stereo Mix' device via its popup menu:

After performing all these steps you will be able to select this device in the list of available ones in the Video Capture Options dialog.

When 'Stereo Mix' device is selected, it's still possible simultaneously to record audio from a microphone by enabling its "Listen to this device" option, for example:

JxBrowser License Instruction

forum-admin@teamdev.com — Thu, 17 Jun 2010 09:20:27 GMT

Installing License File

The JxBrowser library requires a valid license (teamdev.licenses) file for operations.

You can request a fully-functional 30-day evaluation license (http://www.teamdev.com/jxbrowser) or purchase a commercial license of JxBrowser (http://www.teamdev.com/store/jxbrowser).

The license file should be placed in META-INF folder in one of your application's JAR file or in META-INF folder of any JAR file included into your application class path.

Note: When you request a license file, you get a license.jar library which already contains required teamdev.licenses file. You need just to include this library into your application class path.

Warning: Do NOT rename the license file or it will not be recognized.

License Information

In order to get information about license that JxBrowser could find you can use the "teamdev.license.info" system property. The following code demonstrates how to enable license info printing in your application.

System.setProperty("teamdev.license.info", "true");
Browser browser = BrowserFactory.createBrowser();

JxBrowser Installation Instruction

forum-admin@teamdev.com — Thu, 08 Jan 2009 12:45:22 GMT

Installing Library JAR File

All the JAR files from the lib directory of JxBrowser distribution package should be in your application class path.

Also in your application class path should be included JAR file with license file (teamdev.licenses) in its META-INF folder. More information about license installation process you can read in JxBrowser License Instruction

TeamDev Support : Document List - All Communities

JxBrowser hotfixes

Hotfixes

JExplorer

What's New in Nightly Builds

New Components

Enhancements

Fixes

Roadmap

OpenFaces 3.0 Early Access 2 (released)

OpenFaces 3.0 (September)

OpenFaces 2.1/3.1

Future releases

Migrating from QuipuKit 1.6.2

General

Changes Dependent on the New Product Name

Library Changes

Removal of Deprecated API

Renamed, Moved API

Client-Side API Changes

The New O$(id) Function

Unified Client-Side API

Client-Side Validation Functions

Migrating to the New Filtering API

The q_refreshTable and q_refreshTreeTable Functions

API Changes

Other

Browser component embedded within JPanel

JxBrowser Technical Questions and Answers

QuipuKit Hotfixes

QuipuKit 1.6.2 Update 1

QuipuKit 1.6.2 Update 2

QuipuKit 1.6.2 Update 3

Recording sound from 'Stereo Mix' device with JxCapture 2 on Vista and Windows 7 systems

JxBrowser License Instruction

Installing License File

License Information

JxBrowser Installation Instruction

Installing Library JAR File

The New `O$(id)` Function

The `q_refreshTable` and `q_refreshTreeTable` Functions