How eltonriva1/customers-administration works
Project type and purpose
• This is a Spring Boot–based SOAP web‐service for “Customers Administration.”
• It exposes CRUD operations over SOAP (WSDL/XSD), backed by Spring Data JPA and a MySQL database.
• There is no front-end; it’s strictly a backend microservice exposing SOAP endpoints.
File structure
Top-level
• pom.xml, mvnw(.cmd), .mvn/… → Maven wrapper and build config
• docker-compose.yml → defines MySQL service (and potentially the service)
• SOAP/, files-xml/ → SOAP-UI project files and example request/response XML & XSD
• src/main/java/…/br/com/klayrocha → JAXB‐generated request/response/domain classes from XSD
• src/main/java/com/klayrocha/soap/webservices/customersadministration/…
– bean/Customer.java
– repository/CustomerRepository.java (Spring Data JPA)
– service/CustomerDetailService.java (business logic)
– soap/CustomerDetailEndpoint.java, WebServiceConfig.java (SOAP endpoints + config)
– soap/exception/CustomerNotFoundException.java
• src/main/resources/application.properties, customer-information.xsd
• src/test/java → unit/integration test scaffolding
README for additional insights
• Tech stack: Java 8, Spring Boot 2.7.9, Spring Data JPA, Hibernate, MySQL, Maven
• Deployment: configure JDBC URL + credentials, “mvn spring-boot:run,” HTTP on port 8080
• Future work: JWT auth, React/Angular front‐end, automated tests
Essential details to capture
• The XSD → JAXB generation step
• The layered separation: SOAP binding vs. business logic vs. persistence
• Any exception→fault mapping in the endpoint
• The Docker-Compose dependency on MySQL
• The Maven build process generating WAR/JAR and launching via Spring Boot