Update Javadoc, versioning, and community standards for 1.5.0

CODE_OF_CONDUCT.md

@@ -0,0 +1,92 @@
+
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, **pasinduogdev@gmail.com**
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+
+## Addressing and Repairing Harm
+
+****
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+    1) Event: A violation involving a single incident or series of incidents.
+    2) Consequence: A private, written warning from the Community Moderators.
+    3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+    1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+    2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+    3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+    1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+    2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+    3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+    1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+    2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+    3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
+

README.md

@@ -21,10 +21,10 @@
 <img src="https://img.shields.io/badge/Java-17+-orange.svg" alt="Java">
 </a>
 <a href="https://spring.io/projects/spring-boot">
-<img src="https://img.shields.io/badge/Spring%20Boot-4.0.3-brightgreen.svg" alt="Spring Boot">
+<img src="https://img.shields.io/badge/Spring%20Boot-4.0.5-brightgreen.svg" alt="Spring Boot">
 </a>
 <a href="https://github.com/OG4Dev/og4dev-spring-response">
-<img src="https://img.shields.io/badge/Version-1.4.0-brightgreen.svg" alt="Version">
+<img src="https://img.shields.io/badge/Version-1.5.0-brightgreen.svg" alt="Version">
 </a>
 </p>
 
@@ -125,6 +125,7 @@ Unlike other response wrapper libraries, this one offers:
 * ✅ **Native Spring Boot 3.x/4.x Auto-Configuration** - No manual setup required
 * ✅ **Zero-Boilerplate @AutoResponse** - Return raw objects, let the library wrap them automatically while preserving your HTTP Status codes. **Supports both Class-level and Method-level granularity.**
 * ✅ **Intelligent String Handling** - Safely wraps raw `String` returns into JSON without throwing `ClassCastException`.
+* ✅ **Dynamic Exception Registry** - Seamlessly map 3rd-party exceptions (SQL, Security) to standard HTTP responses with a simple builder pattern.
 * ✅ **RFC 9457 ProblemDetail Support** - Industry-standard error responses (latest RFC)
 * ✅ **Opt-in Security Features** - Fine-grained control via field and **class-level** annotations (`@XssCheck`, `@AutoTrim`)
 * ✅ **Zero External Dependencies** - Pure Java implementation, won't conflict with your application
@@ -134,29 +135,26 @@ Unlike other response wrapper libraries, this one offers:
 
 ## 🚀 Installation
 
-### Maven (Latest - v1.4.0)
+### Maven (Latest - v1.5.0)
 
 ```xml
 <dependency>
     <groupId>io.github.og4dev</groupId>
     <artifactId>og4dev-spring-response</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
-
 ```
 
-### Gradle (Latest - v1.4.0)
+### Gradle (Latest - v1.5.0)
 
 ```gradle
-implementation 'io.github.og4dev:og4dev-spring-response:1.4.0'
-
+implementation 'io.github.og4dev:og4dev-spring-response:1.5.0'
 ```
 
-### Gradle Kotlin DSL (Latest - v1.4.0)
+### Gradle Kotlin DSL (Latest - v1.5.0)
 
 ```kotlin
-implementation("io.github.og4dev:og4dev-spring-response:1.4.0")
-
+implementation("io.github.og4dev:og4dev-spring-response:1.5.0")
 ```
 
 ---
@@ -165,7 +163,7 @@ implementation("io.github.og4dev:og4dev-spring-response:1.4.0")
 
 The library is organized into six main packages:
 
-```
+```text
 io.github.og4dev
 ├── advice/
 │   └── GlobalResponseWrapper.java           # Automatic response wrapper interceptor
@@ -175,14 +173,14 @@ io.github.og4dev
 │   └── XssCheck.java                        # Opt-in annotation for XSS validation
 ├── config/
 │   └── ApiResponseAutoConfiguration.java    # Spring Boot auto-configuration
-├── dto/
+├─�� dto/
 │   └── ApiResponse.java                     # Generic response wrapper
 ├── exception/
 │   ├── ApiException.java                    # Abstract base for custom exceptions
+│   ├── ApiExceptionRegistry.java            # Dynamic mapping for 3rd-party exceptions
 │   └── GlobalExceptionHandler.java          # RFC 9457 exception handler
 └── filter/
     └── TraceIdFilter.java                   # Request trace ID generation
-
 ```
 
 ## 🎯 Quick Start
@@ -201,7 +199,6 @@ public class UserController {
         return ApiResponse.success("User retrieved successfully", user);
     }
 }
-
 ```
 
 ### Method 2: Automatic Wrapping (New in v1.4.0) 🎁
@@ -232,34 +229,31 @@ public class UserController {
     @GetMapping("/greeting")
     public String greeting() {
         // Raw strings are safely converted to JSON ApiResponse too!
-        return "Hello World"; 
+        return "Hello World";
     }
 }
-
 ```
 
 **Both methods produce the exact same JSON:**
 
 ```json
 {
   "status": 200,
-  // or 201 for POST
   "message": "Success",
   "content": {
     "id": 1,
     "name": "John Doe"
   },
   "timestamp": "2026-02-28T10:30:45.123Z"
 }
-
 ```
 
 ## ⚙️ Auto-Configuration
 
 The library features **Spring Boot Auto-Configuration** for truly zero-config setup!
 
-✅ **GlobalExceptionHandler** - Automatic exception handling
-✅ **GlobalResponseWrapper** - Automatic payload wrapping via `@AutoResponse`
+✅ **GlobalExceptionHandler** - Automatic exception handling  
+✅ **GlobalResponseWrapper** - Automatic payload wrapping via `@AutoResponse`  
 ✅ **Security Customizers** - Jackson configuration for `@AutoTrim` and `@XssCheck`
 
 **No configuration needed!** Just add the dependency.
@@ -284,7 +278,7 @@ Introduced in **v1.4.0**, you can eliminate boilerplate code by letting the libr
 
 The library provides fine-grained security and data processing features through field-level annotations. By default, **fields are NOT modified** unless explicitly annotated.
 
-*New in v1.4.0:* You can now apply `@AutoTrim` and `@XssCheck` to **entire classes** to protect all string fields at once!
+*Introduced in v1.3.0:* You can apply `@AutoTrim` and `@XssCheck` to **entire classes** to protect all string fields at once!
 
 ### 1. Strict Property Validation 🛡️ (Automatic)
 
@@ -297,7 +291,6 @@ Fail-fast HTML tag detection and rejection using regex pattern `(?s).*<\s*[a-zA-
 ```java
 @XssCheck
 private String comment; // Rejects "<script>alert(1)</script>"
-
 ```
 
 ### 3. Opt-in String Trimming with @AutoTrim ✂️
@@ -307,12 +300,11 @@ Automatic whitespace removal for specific fields.
 ```java
 @AutoTrim
 private String username; // "  john_doe  " -> "john_doe"
-
 ```
 
-### 4. Class-Level Protection (New in v1.4.0) 🛡️
+### 4. Class-Level Protection for `@AutoTrim`/`@XssCheck` (Added in v1.3.0) 🛡️
 
-Apply annotations to the class level to automatically protect **ALL** string fields within that class!
+Starting in v1.3.0, these annotations can also be applied at the class level to automatically protect **ALL** string fields within that class.
 
 ```java
 @AutoTrim
@@ -323,14 +315,13 @@ public class SecureRegistrationDTO {
     private String email;
     private String bio;
 }
-
 ```
 
 *(See full Security details in the Javadocs and examples above).*
 
 ## 🛡️ Built-in Exception Handling
 
-The library includes a **production-ready `GlobalExceptionHandler**` that automatically handles 10 common exceptions using Spring Boot's **ProblemDetail (RFC 9457)** standard.
+The library includes a **production-ready `GlobalExceptionHandler`** that automatically handles 10 common exceptions using Spring Boot's **ProblemDetail (RFC 9457)** standard.
 
 * **Automatic Logging:** SLF4J integration for all errors.
 * **Trace ID Consistency:** Logs and responses always have matching trace IDs.
@@ -342,9 +333,30 @@ public class ResourceNotFoundException extends ApiException {
         super(String.format("%s not found with ID: %d", resource, id), HttpStatus.NOT_FOUND);
     }
 }
+```
+
+### 🔄 Dynamic Exception Registry (New in v1.5.0)
 
+Seamlessly map 3rd-party or framework-specific exceptions (like `SQLException`, `MongoException`, or `AuthenticationException`) to standard `ProblemDetail` responses without writing custom `@ExceptionHandler` methods!
+
+Simply define a configuration bean to register your external exceptions:
+
+```java
+@Configuration
+public class ApiExceptionConfig {
+    @Bean
+    public ApiExceptionRegistry apiExceptionRegistry() {
+        return new ApiExceptionRegistry()
+            // Map Database Exceptions
+            .register(SQLException.class, HttpStatus.INTERNAL_SERVER_ERROR, "A database error occurred.")
+            // Map Security Exceptions
+            .register(AuthenticationException.class, HttpStatus.UNAUTHORIZED, "Invalid authentication token.");
+    }
+}
 ```
 
+All registered exceptions will automatically be caught by the `GlobalExceptionHandler` and formatted into RFC 9457 compliant JSON responses with trace IDs.
+
 ## 🌍 Real-World Examples
 
 ### Example 1: Clean CRUD Controller (Using Class-Level @AutoResponse)
@@ -381,7 +393,6 @@ public class ProductController {
         // Returns empty content with 200 OK automatically
     }
 }
-
 ```
 
 ## 📚 API Reference
@@ -390,33 +401,35 @@ public class ProductController {
 
 ## 📈 Version History
 
-### 1.4.0 (February 2026) - Current Release
-
-✨ **New Features & Improvements:**
+### 1.5.0 (April 2026) - **Current Release**
 
-* **@AutoResponse Annotation & GlobalResponseWrapper**
-* Opt-in automatic response wrapping to eliminate boilerplate code.
-* **Improved Granularity:** Fully supports both Class-level (`ElementType.TYPE`) and Method-level (`ElementType.METHOD`) placement for precision control over which endpoints are wrapped.
-* Returns raw DTOs from controllers and automatically wraps them in `ApiResponse<T>`.
-* Preserves HTTP status codes from `@ResponseStatus`.
-* Intelligently skips `ResponseEntity`, `ApiResponse`, and `ProblemDetail` to prevent double-wrapping.
-* **Intelligent String Handling:** Uses Spring's `ObjectMapper` to safely serialize raw `String` returns to JSON, avoiding `ClassCastException` with native converters.
+✨ **Highlights & Improvements:**
 
+* **Dynamic Exception Registry (`ApiExceptionRegistry`)**
+    * Centralized mapping for 3rd-party exceptions (e.g., SQL, Mongo, Spring Security) without writing custom handlers.
+    * Thread-safe registry preserving insertion order for hierarchy-based exception catching.
 
-* **Class-Level Security Annotations**
-* `@AutoTrim` and `@XssCheck` can now be applied at the Class level (`ElementType.TYPE`) to automatically protect all String fields within the DTO at once.
+* **Documentation**
+    * `package-info.java` documentation added for the new `advice` package.
 
 
-* **Documentation**
-* `package-info.java` documentation added for the new `advice` package.
+### 1.4.0 (March 2026)
 
+* **@AutoResponse Annotation & GlobalResponseWrapper**
+    * Opt-in automatic response wrapping.
+    * **Granularity:** Supports both Class-level (`ElementType.TYPE`) and Method-level (`ElementType.METHOD`) placement.
+    * Returns raw DTOs from controllers and automatically wraps them in `ApiResponse<T>`.
+    * Preserves HTTP status codes from `@ResponseStatus`.
+    * Intelligently skips `ResponseEntity`, `ApiResponse`, and `ProblemDetail` to prevent double-wrapping.
+    * **Intelligent String Handling:** Uses Spring's `ObjectMapper` to safely serialize raw `String` returns to JSON, avoiding `ClassCastException` with native converters.
 
 
 ### 1.3.0 (February 2026)
 
 * **Security Philosophy Change:** Complete redesign from automatic to opt-in approach for JSON sanitization.
 * Added **@AutoTrim** annotation for explicit string trimming.
 * Added **@XssCheck** annotation for explicit fail-fast XSS validation.
+* Added **Class-level support** for `@AutoTrim` and `@XssCheck` (`ElementType.TYPE`).
 * Extensive Javadoc and README updates regarding the new security model.
 
 ### 1.2.0 (February 2026)
@@ -450,4 +463,4 @@ Licensed under the Apache License 2.0.
 
 ---
 
-**⭐ If you find this library helpful, please give it a star on GitHub!**
+**⭐ If you find this library helpful, please give it a star on GitHub!**