How pancoded/sistematableros works
Project type and purpose
• This is a standalone Java Swing desktop application (“Sistema de prestación de tableros en Java”).
• It implements a classic 3-tier architecture (UI, business logic, persistence) and uses JPA for database interactions.
File structure
• Top-level files:
• README.md – project description
• pom.xml – Maven build and dependency management
• Package breakdown under src/main/java/ar/edu/ottokrause/sistemaTableros:
• gui – Swing forms and frames (Principal, Registro, Pedidos)
• logica – core domain model (Tablero, Usuario, Prestamo, EstadoTablero, EstadoPrestamo, TipoUsuario) and Controladora
• persistencia – JPA controllers (UsuarioJpaController, TableroJpaController, PrestamoJpaController) and persistence unit (persistence.xml)
• src/main/resources/META-INF/persistence.xml – JPA configuration
README for additional insights
• Confirms project goal: manage lending (“prestación”) of boards.
• No explicit architecture section, but persistence.xml implies a relational database managed by JPA.
Details to capture
• Persistence unit (name, DB connection settings in persistence.xml)
• Entity classes (Tablero, Usuario, Prestamo) inside Persistence or Domain layer
• Exception hierarchy (NonexistentEntityException, PreexistingEntityException) as part of DAO error handling
• Maven as the build orchestrator (pom.xml)