Read Parasolid for JT conversion
A Parasolid-to-JT workflow combines the Parasolid reader with the JT writer. Use it when the receiving application needs JT data from an existing Parasolid model.
Read Parasolid X_T or X_B files through the commercial Parasolid interface into OCCT BRep shapes. Use the XDE import layer when supported names and colors must remain associated with the model items.
Build a JT visualization model
Keep the imported BRep for precise CAD output. For polygonal output, generate a surface mesh with tolerances selected for the receiving application. Check any healing settings against the geometry used in production.
Use the OCAF-to-JT converter for supported hierarchy, names, colors and mesh representations. Configure tessellation and any required levels of detail around the viewing task. This output route creates a visualization representation; it does not promise Parasolid BRep export inside JT.
Validate the JT result
This route starts from a Parasolid export, not an arbitrary native file from a Parasolid-based application. Parasolid writing is not provided by the documented import component.
Select a JT version accepted by the recipient and check part positions, geometry coverage and appearance there. Compare both the full assembly and selected parts. If later processing requires precise CAD surfaces, retain the source BRep alongside the visualization derivative.
For a production pipeline, keep a representative source file and its expected geometry and attributes with the conversion settings. Discuss conversion integration with the source and destination applications, or compare the supported format interfaces.