Skip to content

feat: upgrade to ESPI 4.0 schema and complete Spring Boot 3.5 migration fixes#7

Merged
dfcoffin merged 1 commit into
mainfrom
feature/continue-jpa-mapping-investigation
Jul 16, 2025
Merged

feat: upgrade to ESPI 4.0 schema and complete Spring Boot 3.5 migration fixes#7
dfcoffin merged 1 commit into
mainfrom
feature/continue-jpa-mapping-investigation

Conversation

@dfcoffin
Copy link
Copy Markdown
Contributor

Summary

This PR completes the Spring Boot 3.5 migration work by upgrading to ESPI 4.0 schema and resolving remaining JPA mapping issues.

Key Changes:

  • ESPI 4.0 Schema Upgrade: Migrated from ESPI 3.3 to ESPI 4.0 schema files
  • JPA Mapping Fix: Updated OrganisationRole entity for ESPI 4.0 compatibility
  • Migration Documentation: Added comprehensive 2025-07-15 migration plan update

Schema Changes:

  • ✅ Added openespi-common/src/main/resources/schema/ESPI_4.0/customer.xsd
  • ✅ Added openespi-common/src/main/resources/schema/ESPI_4.0/espi.xsd
  • ✅ Removed legacy ESPI 3.3 schema files

JPA Entity Updates:

  • ✅ Updated OrganisationRole.java with proper JPA mapping annotations
  • ✅ Resolved attribute override mappings for ESPI 4.0 compatibility

Documentation:

  • ✅ Added 2025-07-15_Claude_Code_Spring_Boot_3.5_Migration_Plan.md with current status

Test Plan

  • Verify schema files are valid ESPI 4.0 format
  • Test JPA entity mappings compile without errors
  • Validate application startup with new schema
  • Confirm backward compatibility where needed

Related Issues

  • Resolves remaining Spring Boot 3.5 migration tasks
  • Addresses ESPI 4.0 compliance requirements
  • Completes JPA mapping standardization

🤖 Generated with Claude Code

- Add ESPI 4.0 schema files (customer.xsd, espi.xsd)
- Remove legacy ESPI 3.3 schema files
- Update OrganisationRole JPA mapping for ESPI 4.0 compatibility
- Add updated Spring Boot 3.5 migration plan (2025-07-15)

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant