Description Li Ding 2005-09-28 17:55:21 EDT

This feature actaully asks for two enhancements of Import Log Wizard so that it
can be integrated with other tooling easily :
1. Separate UI and underline processing code
2. Provide a configurable import log wizard archtecuture.

Details:

1. In current Import log wizard, UI and processing code are very tightly
coupled. Both are resides in import wizard class. This causes problem for third
parties to integrate log import ability in their tooling. Third party may have
programtical way to get the necessary parameters for importing log instead of
using import log wizard interactively. What third party needs is to call the
import log processing API. In current design, there is no such API can be
called. For example, in my case to import iSeries job log, WDSc ( iSeries
tooling based on RAD/RWD ) has UI where I can get the job information and I want
to call import log API to start the importing. Currently I have to extend the
whole import wizard.


2. The import log wizard ( or parser ? )predefines all the tabs: host, details,
destination and filter. It would be nice for third party to contribute
additional tab or remove tab. For example, they may want to logically divide the
 input fields to different tabs other than put all in "details" tab.  Ideally,
import log wizard predefined tabs should be common APIs so that third party can 
reuse them.