luigidemasi opened a new issue, #48: URL: https://github.com/apache/camel-kit/issues/48
> Imported from [luigidemasi/camel-kit#84](https://github.com/luigidemasi/camel-kit/issues/84), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-05-15. > Closed by [luigidemasi/camel-kit#85](https://github.com/luigidemasi/camel-kit/pull/85), merged on 2026-05-15. --- ## Description When running a migration from MuleSoft (or BizTalk), if `project-graph.json` exists and contains vendor-specific nodes (e.g., `MULE_FLOW`, `BIZTALK_ORCHESTRATION`), the graph-accelerated analysis path is skipped because the skill guides only check for `CAMEL_ROUTE` nodes. The user sees: > The project graph exists but contains MuleSoft nodes (not Camel routes), so graph-accelerated analysis doesn't apply here. I'll proceed with the standard file scanning approach. The Java infrastructure already supports vendor-specific graph analysis: - `MuleXmlFlowParser` correctly produces `MULE_FLOW`, `MULE_SUB_FLOW`, `MULE_ENDPOINT`, `MULE_CONNECTOR`, `MULE_TRANSFORM`, `MULE_ERROR_HANDLER`, and `DATAWEAVE_SCRIPT` nodes - `BizTalkParser` produces `BIZTALK_ORCHESTRATION`, `BIZTALK_SHAPE`, `BIZTALK_MAP`, etc. - Generic graph CLI commands (`graph find --type MULE_FLOW`, `graph neighbors`, `graph stats`) work with any node type The gap is purely in the skill guides: 1. **`camel-brainstorm/guides/migration-graph-analysis.md`** — only uses Camel-specific commands (`graph route-topology`, `graph neighbors route:<routeId>`) and expects `CAMEL_ROUTE`/`CAMEL_ENDPOINT` nodes 2. **`camel-migrate/SKILL.md` Step 0** — explicitly checks for `CAMEL_ROUTE` nodes and falls back if not found 3. **`camel-brainstorm/guides/migration-discovery.md` Step 1** — loads graph analysis without vendor-aware dispatch ## Proposed Fix Skill guide changes only — no Java changes needed: 1. **Create `migration-mule-graph-analysis.md`** — mirrors `migration-graph-analysis.md` but uses MuleSoft node/edge types (`MULE_FLOW`, `MULE_FLOW_CONTAINS`, `MULE_CALLS_SUBFLOW`, etc.) with generic CLI commands to build flow topology, connector inventory, and migration ordering 2. **Create `migration-biztalk-graph-analysis.md`** — same pattern for BizTalk node types (`BIZTALK_ORCHESTRATION`, `BIZTALK_USES_MAP`, etc.) 3. **Update `migration-discovery.md` Step 1** — detect vendor from `graph stats` node types and load the correct vendor-specific guide 4. **Update `camel-migrate/SKILL.md` Step 0** — extend the dispatch logic to handle `MULE_FLOW` and `BIZTALK_ORCHESTRATION` nodes alongside `CAMEL_ROUTE` ## Affected Files - `camel-kit-core/src/main/resources/skills/camel-brainstorm/guides/migration-graph-analysis.md` (reference for new guides) - `camel-kit-core/src/main/resources/skills/camel-brainstorm/guides/migration-discovery.md` (update Step 1) - `camel-kit-core/src/main/resources/skills/camel-migrate/SKILL.md` (update Step 0) - New: `camel-kit-core/src/main/resources/skills/camel-brainstorm/guides/migration-mule-graph-analysis.md` - New: `camel-kit-core/src/main/resources/skills/camel-brainstorm/guides/migration-biztalk-graph-analysis.md` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
