|
|||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Class Summary | |
IXBDocumentPlaceHolder |
The following figure shows the essential participants and interactions involved with the export process.
· Export Application – serves as access point to export functionality.
· IxbHandlersManager – instantiates Export Handler for the object based on the object class and IX handlers registry. For each export session, there is only one instance of Export handler for all objects of the given class
· Exporter – invokes Export Handlers; serves as the context of export operation
· Export Handler - creates xml DOM document representing the object
The following figure shows the essential participants and interactions involved with the import process.
The following figure shows class hierarchy for IX handlers. Most of the existing IX handlers implement both ClassExporters and ElementImporters. However, this is not required.
Windchill IXB functionality can be customized in three different ways.
wt.ixb.publicforapps
. wt.ixb.publicforhandlers
.
Subpackages
wt.ixb.actor –contains actor classes which support ‘import as’ and restore use cases. In terms of java patterns, actors are decorators for IX class handlers
wt.ixb.applications - contains templates for export and import applications
wt.ixb.archive – contains helper classes for archive and restore specific functionality
wt.ixb.clientAccess – contains classes for client-server communication, including service classes and some utilities which assist in creating/reading data file and sending result to/from client
wt.ixb.conflictframework – contains classes related to conflict reporting and resolution
wt.ixb.epm – contains IX handlers and helper classes for CAD (EPM) objects
wt.ixb.handlers.forclasses – contains IX class handlers for ‘core’ objects
wt.ixb.handlers.forattributes – contains IX attribute handlers
wt.ixb.handlers.netmarkets – contains Netmarkets handlers and utility classes, which are used by container templates and PJL import/export
wt.ixb.impl – contains wrapper classes for xml DOM documents/elements and DTD manager.
wt.ixb.mapping - contains classes to support ufid mapping. Ixb uses ufid mapping to allow import of the same foreign object into different namespaces on the target system. Can be eliminated if standard ufid package becomes container aware
wt.ixb.objectset – contains classes which support collecting objects for export. Object collection is customizable, i.e. you can add custom navigators.
wt.ixb.pdx - contains classes for export in PDX format (the code was not released so currently is not supported)
wt.ixb.publicforapps - provides APIs to develop IXB application
wt.ixb.publicforhandlers - provides APIs to develop IXB plugable components.
wt.ixb.tuner – contains classes which support ‘tuning’ xml files prior to import with the mapping files. Tuning can be done with XSL or with xml ‘mapping’ files of special format. Examples of mapping files can be found in ..\codebase\registry\ixb\samples.
wt.ixb.util – contains various utility classes
|
|||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |