Merge pull request #347 from k01zero/part2-김경린

[김경린] sprint 7

Author: youngxpepp

.github/img_4.png

@@ -0,0 +1,31 @@
+25-03-28 14:34:43.799 [main] INFO  c.s.m.discodeit.DiscodeitApplication - Starting DiscodeitApplication using Java 17.0.12 with PID 70960 (C:\Users\User\OneDrive\Desktop\codeit\1-sprint-mission\build\classes\java\main started by User in C:\Users\User\OneDrive\Desktop\codeit\1-sprint-mission)
+25-03-28 14:34:43.801 [main] INFO  c.s.m.discodeit.DiscodeitApplication - The following 1 profile is active: "prod"
+25-03-28 14:34:46.614 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Bootstrapping Spring Data JPA repositories in DEFAULT mode.
+25-03-28 14:34:46.798 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Finished Spring Data repository scanning in 169 ms. Found 6 JPA repository interfaces.
+25-03-28 14:34:48.014 [main] INFO  o.s.b.w.e.tomcat.TomcatWebServer - Tomcat initialized with port 8080 (http)
+25-03-28 14:34:48.036 [main] INFO  o.a.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-8080"]
+25-03-28 14:34:48.041 [main] INFO  o.a.catalina.core.StandardService - Starting service [Tomcat]
+25-03-28 14:34:48.041 [main] INFO  o.a.catalina.core.StandardEngine - Starting Servlet engine: [Apache Tomcat/10.1.33]
+25-03-28 14:34:48.201 [main] INFO  o.a.c.c.C.[Tomcat].[localhost].[/] - Initializing Spring embedded WebApplicationContext
+25-03-28 14:34:48.202 [main] INFO  o.s.b.w.s.c.ServletWebServerApplicationContext - Root WebApplicationContext: initialization completed in 4324 ms
+25-03-28 14:34:48.448 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
+25-03-28 14:34:48.946 [main] INFO  com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Added connection org.postgresql.jdbc.PgConnection@2fdf22f7
+25-03-28 14:34:48.950 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
+25-03-28 14:34:49.192 [main] INFO  o.h.jpa.internal.util.LogHelper - HHH000204: Processing PersistenceUnitInfo [name: default]
+25-03-28 14:34:49.360 [main] INFO  org.hibernate.Version - HHH000412: Hibernate ORM core version 6.5.3.Final
+25-03-28 14:34:49.449 [main] INFO  o.h.c.i.RegionFactoryInitiator - HHH000026: Second-level cache disabled
+25-03-28 14:34:50.179 [main] INFO  o.s.o.j.p.SpringPersistenceUnitInfo - No LoadTimeWeaver setup: ignoring JPA class transformer
+25-03-28 14:34:52.324 [main] INFO  o.h.e.t.j.p.i.JtaPlatformInitiator - HHH000489: No JTA platform available (set 'hibernate.transaction.jta.platform' to enable JTA platform integration)
+25-03-28 14:34:52.476 [main] INFO  o.s.o.j.LocalContainerEntityManagerFactoryBean - Initialized JPA EntityManagerFactory for persistence unit 'default'
+25-03-28 14:34:53.625 [main] WARN  o.s.b.a.o.j.JpaBaseConfiguration$JpaWebConfiguration - spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
+25-03-28 14:34:53.656 [main] INFO  o.s.b.a.w.s.WelcomePageHandlerMapping - Adding welcome page: class path resource [static/index.html]
+25-03-28 14:34:55.632 [main] INFO  o.a.coyote.http11.Http11NioProtocol - Starting ProtocolHandler ["http-nio-8080"]
+25-03-28 14:34:55.678 [main] INFO  o.s.b.w.e.tomcat.TomcatWebServer - Tomcat started on port 8080 (http) with context path '/'
+25-03-28 14:34:55.697 [main] INFO  c.s.m.discodeit.DiscodeitApplication - Started DiscodeitApplication in 12.781 seconds (process running for 21.381)
+25-03-28 14:35:23.964 [http-nio-8080-exec-1] INFO  o.a.c.c.C.[Tomcat].[localhost].[/] - Initializing Spring DispatcherServlet 'dispatcherServlet'
+25-03-28 14:35:23.964 [http-nio-8080-exec-1] INFO  o.s.web.servlet.DispatcherServlet - Initializing Servlet 'dispatcherServlet'
+25-03-28 14:35:23.967 [http-nio-8080-exec-1] INFO  o.s.web.servlet.DispatcherServlet - Completed initialization in 2 ms
+25-03-28 14:35:26.004 [http-nio-8080-exec-2] INFO  o.s.api.AbstractOpenApiResource - Init duration for springdoc-openapi is: 1115 ms
+25-03-28 14:44:14.631 [SpringApplicationShutdownHook] INFO  o.s.o.j.LocalContainerEntityManagerFactoryBean - Closing JPA EntityManagerFactory for persistence unit 'default'
+25-03-28 14:44:14.633 [SpringApplicationShutdownHook] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated...
+25-03-28 14:44:14.642 [SpringApplicationShutdownHook] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed.

.github/pull-request-template.md

@@ -3,6 +3,7 @@ plugins {
     id 'application' // application 플러그인 추가
     id 'org.springframework.boot' version '3.3.6'
     id 'io.spring.dependency-management' version '1.1.7'
+    id 'com.gorylenko.gradle-git-properties' version '2.4.1' // git 정보 읽기
 }
 
 group = 'com.sprint.mission'
@@ -39,6 +40,12 @@ dependencies {
     // Spring Boot Web 의존성 (Spring MVC, REST 등)
     implementation 'org.springframework.boot:spring-boot-starter-web'
 
+    // Spring Validation 의존성
+    implementation 'org.springframework.boot:spring-boot-starter-validation'
+
+    // Spring Actuator 의존성
+    implementation 'org.springframework.boot:spring-boot-starter-actuator'
+
     // Lombok 의존성 (간결한 코드 작성)
     compileOnly 'org.projectlombok:lombok'             // 컴파일 타임에만 Lombok을 사용
     annotationProcessor 'org.projectlombok:lombok'    // Lombok 애노테이션 프로세서
@@ -49,9 +56,14 @@ dependencies {
 
     // PostgreSQL 의존성
     runtimeOnly 'org.postgresql:postgresql'            // 런타임에만 PostgreSQL 드라이버
+    // h2 의존성
+    runtimeOnly 'com.h2database:h2'
 
     // Spring Boot Test 의존성
-    testImplementation 'org.springframework.boot:spring-boot-starter-test'   // 테스트 관련 의존성
+    testImplementation 'org.springframework.boot:spring-boot-starter-test'
+
+    // Mockito 의존성
+    implementation "org.mockito:mockito-core:4.6.1"
 
     // JUnit 플랫폼 런처 (JUnit 테스트 실행)
     testRuntimeOnly 'org.junit.platform:junit-platform-launcher'
@@ -61,6 +73,23 @@ dependencies {
 }
 
 
+gitProperties {
+    dateFormat = "yyyy-MM-dd'T'HH:mm:ssZ"
+    dateFormatTimeZone = "UTC"
+}
+
+tasks.register('writeBuildProperties') {
+    doLast {
+        def props = new Properties()
+        props.setProperty('version', project.version.toString())
+        props.setProperty('time', new Date().format("yyyy-MM-dd'T' HH:mm:ss'Z'", Timezone.getTimeZone("UTC")))
+
+        def file = file("$buildDir/resources/main/build.properties")
+        file.parentFile.mkdir()
+        props.store(file.newWriter(), null)
+    }
+}
+
 tasks.named('test') {
     useJUnitPlatform()
 }

.logs/app.2025-03-28.log

@@ -0,0 +1,77 @@
+문제 상황 :
+
+    Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean
+    with name 'dataSourceScriptDatabaseInitializer' defined in class path
+    resource [org/springframework/boot/autoconfigure/sql/init/DataSourceInitializationConfiguration.class]:
+    Unsatisfied dependency expressed through method 'dataSourceScriptDatabaseInitializer' parameter 0:
+    Error creating bean with name 'dataSource' defined in class path
+    resource [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]: Failed
+    to instantiate [com.zaxxer.hikari.HikariDataSource]: Factory method 'dataSource' threw exception
+    with message: Failed to load driver class org.h2.Driver in either of HikariConfig class loader or
+    Thread context classloader
+
+Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean
+with name 'dataSourceScriptDatabaseInitializer' defined in class path
+
+클래스 경로에 'dataSourceScriptDatabaseInitializer'라는 이름으로 정의된 빈을 생성할 수 없는 오류가 발생했다.
+UnsatisfiedDependencyException = 불만족스러운 종속성 예외
+
+Failed to load driver class org.h2.Driver in either of HikariConfig class loader or
+Thread context classloader
+H2 드라이버(org.h2.Driver)를 로드할 수 없다.
+
+해결 : 의존성 추가, 설정 파일에 설정 추가
+
+1. 의존성 추가
+   ![img_1.png](img_1.png)
+
+새로운 의존성을 추가한 후 다운로드할 수 있게 build.gradle 을 통해 org.h2.Driver 클래스가 인식되도록 했다.
+
+2. yml 설정 파일에 설정 추가
+   ![img_2.png](img_2.png)
+
+공통 설정 파일에 spring:profiles:active: dev, datasource:driver-class-name: org.h2.Driver 를 설정했다.
+
+![img_3.png](img_3.png)
+
+
+-----
+
+문제 상황2 :
+
+      2025-03-27T16:14:02.827+09:00 ERROR 18156 --- [discodeit] [           main]
+      j.LocalContainerEntityManagerFactoryBean : Failed to initialize JPA
+      EntityManagerFactory: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested
+      exception is org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing
+      table [message]
+      2025-03-27T16:14:02.830+09:00 WARN 18156 --- [discodeit] [           main]
+      ConfigServletWebServerApplicationContext : Exception encountered during context initialization -
+      cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating
+      bean with name 'entityManagerFactory' defined in class path
+      resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: [PersistenceUnit: default]
+      Unable to build Hibernate SessionFactory; nested exception is
+      org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [message]
+
+Schema-validation: missing table [message]
+스키마 검증 단계에서 message 라는 테이블이 없어서 발생한 문제이다.
+
+해결 : H2 DB에 테이블 생성
+
+DB에 message 테이블이 없거나, 아예 테이블을 생성하는 SQL(schema.sql)이 실행되지 않았거나 둘 중 하나라고 생각했다.
+때문에 H2 DB에 데이터테이블을 생성하는 방법을 찾자, 두 가지 방법이 나왔다.
+
+1. 스프링 부트의 DB 테이블 만들기
+    - spring.sql.init.mode 사용
+2. 하이버네이트가 테이블을 자동 생성해주기
+    - jpa:hibernate:ddl-auto : 를 create, update 로 지정
+
+이때, 이 두가지 설정을 동시에 이용하면 안 된다. 스프링 부트에서 테이블을 생성하려고 하는 동작과 하이버네이트가 자동 테이블을 자동 생성하려는 동작에 충돌이 있다.
+![img_6.png](img_6.png)
+실제로 jpa:hibernate:ddl-auto를 validation으로 지정한 후 테이블을 생성하려고 하자, 여전히 message 테이블이 존재하지 않는다는 오류가 동일하게
+떴다.
+이후 jpa:hibernate:ddl-auto를 none으로 설정하자, 애플리케이션이 실행될 수 있었다.
+
+[[Spring Boot] DB Schema 및 Data 초기화 schema.sql data.sql
+](https://chaewsscode.tistory.com/174)
+[[Spring] org.springframework.beans.factory.UnsatisfiedDependencyException 에러](https://yn98.tistory.com/84#%EC%A3%BC%EC%9A%94%20%EC%9B%90%EC%9D%B8-1)
+[SQL 데이터베이스](https://docs.spring.io/spring-boot/reference/data/sql.html#data.sql.h2-web-console)

.logs/app.2025-03-30.log

@@ -0,0 +1,58 @@
+### 문제 상황 :
+
+Strict stubbing argument mismatch. Please check:
+
+- this invocation of 'toDto' method:
+  userMapper.toDto(
+  com.sprint.mission.discodeit.entity.User@743c6ce4
+  );
+  -> at com.sprint.mission.discodeit.service.basic.BasicUserService.createUser(
+  BasicUserService.java:92)
+- has following stubbing(s) with different arguments:
+    1. userMapper.toDto(
+       com.sprint.mission.discodeit.entity.User@30669dac
+       );
+       -> at com.sprint.mission.discodeit.service.UserServiceTest.createUser_Success(
+       UserServiceTest.java:77)
+       Typically, stubbing argument mismatch indicates user mistake when writing tests.
+       Mockito fails early so that you can debug potential problem easily.
+       However, there are legit scenarios when this exception generates false negative signal:
+- stubbing the same method multiple times using 'given().will()' or 'when().then()' API
+  Please use 'will().given()' or 'doReturn().when()' API for stubbing.
+- stubbed method is intentionally invoked with different arguments by code under test
+  Please use default or 'silent' JUnit Rule (equivalent of Strictness.LENIENT).
+  For more information see javadoc for PotentialStubbingProblem class.
+  org.mockito.exceptions.misusing.PotentialStubbingProblem:
+  Strict stubbing argument mismatch. Please check:
+- this invocation of 'toDto' method:
+  userMapper.toDto(
+  com.sprint.mission.discodeit.entity.User@743c6ce4
+  );
+
+### 문제가 일어난 이유 : User 객체가 테스트 코드에서 예상한 것과 다른 인수로 호출됐다.
+
+Strict stubbing argument mismatch. Please check:
+Strict stubbing argument mismatch. Please check:
+
+- this invocation of 'toDto' method:
+  userMapper.toDto(
+  com.sprint.mission.discodeit.entity.User@743c6ce4
+  );
+  -> at com.sprint.mission.discodeit.service.basic.BasicUserService.createUser(
+  BasicUserService.java:92)
+- has following stubbing(s) with different arguments:
+    1. userMapper.toDto(
+       com.sprint.mission.discodeit.entity.User@30669dac
+       );
+       -> at com.sprint.mission.discodeit.service.UserServiceTest.createUser_Success(
+       UserServiceTest.java:77)
+
+실제로 호출된 userMapper.toDto() 메서드는 com.sprint.mission.discodeit.entity.User@743c6ce4 객체를 인자로 받았지만,
+테스트에서 stubbing한 호출은 com.sprint.mission.discodeit.entity.User@30669dac 객체를 인자로 기대했습니다.
+
+테스트에서 생성된 user 객체와 BasicUserService.createUser() 메서드 내부에서 생성되는 User 객체가 서로 다른 인스턴스이기 때문에 발생한 문제입니다.
+
+### 해결 : user 객체가 expected 값과 동일한 값으로 stub될 수 있도록 설정해야 한다.
+
+user 을 전달받던 userMapper.toDto() 메서드에 `any(User.class)` 를 전달한다.
+테스트 의의에 맞게 변경했다.

.logs/app.2025-03-31.log

@@ -0,0 +1,11 @@
+### 상황 :
+
+![img_7.png](img_7.png)
+jakarta.validation.UnexpectedTypeException: HV000030: 'jakarta.validation.constraints.NotBlank' 제약
+조건에 대한 유효성 검사기를 찾을 수 없습니다. 'java.util.UUID' 유형을 유효성 검사합니다. 'authorId'에 대한 구성을 확인합니다
+
+### 문제가 일어난 이유 : @NotBlank 제약 조건은 문자열(String) 유형에 적용해야 한다.
+
+UUID 유형에 @NotBlank 제약 조건을 걸어놔 발생한 문제였다.
+
+### 해결 :  @NotBlank -> @NotNull

.logs/app.2025-04-01.log

@@ -5,7 +5,6 @@
 import org.springframework.data.jpa.repository.config.EnableJpaAuditing;
 
 @SpringBootApplication
-@EnableJpaAuditing
 public class DiscodeitApplication {
 
   public static void main(String[] args) {

.logs/app.log

@@ -10,7 +10,7 @@
 public class AppConfig {
 
   @Bean
-  @ConditionalOnProperty(name = "discodeit.stroage.type", havingValue = "local")
+  @ConditionalOnProperty(name = "discodeit.storage.type", havingValue = "local")
   public BinaryContentStorage binaryContentStorage() {
     return new LocalBinaryContentStorage();
   }

build.gradle

@@ -0,0 +1,10 @@
+package com.sprint.mission.discodeit.config;
+
+import org.springframework.context.annotation.Configuration;
+import org.springframework.data.jpa.repository.config.EnableJpaAuditing;
+
+@Configuration
+@EnableJpaAuditing // @WebMvcTest 와의 충돌을 고려해 분리
+public class JpaConfig {
+
+}

error-log/DB연결 오류.md

@@ -1,5 +1,6 @@
 package com.sprint.mission.discodeit.controller;
 
+import com.sprint.mission.discodeit.controller.api.AuthApi;
 import com.sprint.mission.discodeit.dto.user.UserLoginRequest;
 import com.sprint.mission.discodeit.entity.User;
 import com.sprint.mission.discodeit.service.basic.AuthService;
@@ -13,7 +14,7 @@
 @RestController
 @RequestMapping("/api/auth")
 @RequiredArgsConstructor
-public class AuthController {
+public class AuthController implements AuthApi {
 
   private final AuthService authService;
 

error-log/img_1.png

@@ -5,12 +5,15 @@
 import com.sprint.mission.discodeit.service.BinaryContentService;
 import com.sprint.mission.discodeit.storage.BinaryContentStorage;
 import lombok.RequiredArgsConstructor;
+import lombok.extern.slf4j.Slf4j;
+import org.springframework.http.HttpStatus;
 import org.springframework.http.ResponseEntity;
 import org.springframework.web.bind.annotation.*;
 
 import java.util.List;
 import java.util.UUID;
 
+@Slf4j
 @RestController
 @RequestMapping("/api/binaryContents")
 @RequiredArgsConstructor
@@ -26,12 +29,11 @@ public ResponseEntity<BinaryContentDto> binaryContentFindById(
 
   @GetMapping(value = "/{binaryContentId}/download")
   public ResponseEntity<?> downloadBinaryContent(@PathVariable UUID id) {
-    // BinaryContentStorage 를 직접 들고와서 쓰라는 것(클래스 다이어그램)으로 이해는 했지만,
-    // 그러면 컨트롤러 단에서 Mapper를 통한 변환(id로 BinaryContent 를 부르고, BinaryContent <-> DTO)이 이뤄이지 때문에
-    // 저는 우선 binaryContentService 에 download 관련 메서드를 추가했습니다.
-    // 내부적으로는 binaryContentStorage 의 downlaod 메서드가 호출됩니다.
-    // 즉, 다운로드 API -> (컨트롤러 - 서비스 - 스토리지) 단에서 기능 구현
-    return binaryContentService.downloadBinaryContent(id);
+    log.info("파일 다운로드 요청(Request)");
+
+    ResponseEntity<?> downloadBinaryContent = binaryContentService.downloadBinaryContent(id);
+    log.info("파일 다운로드 응답(Response): HttpStatus={}", HttpStatus.OK);
+    return downloadBinaryContent;
   }
 
   @GetMapping