[개발 환경]

서버: Spring Boot 3.2.4

프론트: Vite + React + TypeScript

<MyController.java>

import jakarta.servlet.http.HttpServletRequest;
import org.springframework.stereotype.Controller;
import org.springframework.web.bind.annotation.RequestBody;
import org.springframework.web.bind.annotation.RequestMapping;

@Controller
public class MyController {

    @RequestMapping(value = "/gnbmenu")
    public String gnbMenu(@RequestBody Object request) {
        String str = "{\"message\" : \"메뉴 요청 url.\"}";
        return str;
    }

}

<MyFront.tsx>

import { useEffect } from "react";

function MyFront() {
  const dataToSend = {
    key1: "value1",
    key2: "value2",
  };
  useEffect(() => {
    fetch("/api/gnbmenu", {
      method: "POST",
      headers: { "Content-Type": "application/json" },
      body: JSON.stringify(dataToSend),
    }).then((response) => console.log(response.json()));
  }, []);

  return <></>;
export default MyFront;

<Server Console>

2024-04-18T20:10:29.643+09:00 ERROR 26416 --- [****] [nio-8080-exec-2] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed: org.thymeleaf.exceptions.TemplateInputException: Error resolving template [{"message" : "메뉴 요청 url."}], template might not exist or might not be accessible by any of the configured Template Resolvers] with root cause

org.thymeleaf.exceptions.TemplateInputException: Error resolving template [{"message" : "메뉴 요청 url."}], template might not exist or might not be accessible by any of the configured Template Resolvers
	at org.thymeleaf.engine.TemplateManager.resolveTemplate(TemplateManager.java:869) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
	at org.thymeleaf.engine.TemplateManager.parseAndProcess(TemplateManager.java:607) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
	at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1103) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
	at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1077) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
	at org.thymeleaf.spring6.view.ThymeleafView.renderFragment(ThymeleafView.java:372) ~[thymeleaf-spring6-3.1.2.RELEASE.jar:3.1.2.RELEASE]
	at org.thymeleaf.spring6.view.ThymeleafView.render(ThymeleafView.java:192) ~[thymeleaf-spring6-3.1.2.RELEASE.jar:3.1.2.RELEASE]
	at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1431) ~[spring-webmvc-6.1.5.jar:6.1.5]
	at org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1167) ~[spring-webmvc-6.1.5.jar:6.1.5]
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1106) ~[spring-webmvc-6.1.5.jar:6.1.5]
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:979) ~[spring-webmvc-6.1.5.jar:6.1.5]
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1014) ~[spring-webmvc-6.1.5.jar:6.1.5]
	at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:914) ~[spring-webmvc-6.1.5.jar:6.1.5]
	at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:590) ~[tomcat-embed-core-10.1.19.jar:6.0]
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:885) ~[spring-webmvc-6.1.5.jar:6.1.5]
	at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:658) ~[tomcat-embed-core-10.1.19.jar:6.0]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:205) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:149) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) ~[tomcat-embed-websocket-10.1.19.jar:10.1.19]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:174) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:149) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100) ~[spring-web-6.1.5.jar:6.1.5]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:116) ~[spring-web-6.1.5.jar:6.1.5]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:174) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:149) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:93) ~[spring-web-6.1.5.jar:6.1.5]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:116) ~[spring-web-6.1.5.jar:6.1.5]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:174) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:149) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201) ~[spring-web-6.1.5.jar:6.1.5]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:116) ~[spring-web-6.1.5.jar:6.1.5]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:174) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:149) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:167) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:115) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:391) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:896) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1744) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63) ~[tomcat-embed-core-10.1.19.jar:10.1.19]
	at java.base/java.lang.Thread.run(Thread.java:842) ~[na:na]

<Client console>

MyFront.tsx:36 
 POST http://localhost:5173/api/gnbmenu 500 (Internal Server Error)
(anonymous)	@	MyFront.tsx:36
Show 10 more frames

[예상 문제 1]

경로 설정 문제?

"/abc"로 시작하는 경로에서 "/"을 제거하고 "abc"형태로 수정 ☞ AWS나 배포 환경에서 발생하는 문제로 해당 문제가 아님

[문제 2]

Controller Annotaion 종류의 문제

@Controller는 반환값으로 view를 찾음. view가 아닌 json형태를 반환하기 때문에 @RestController로 설정 ☞ 해결

package com.study.controller;

import org.apach.commons.io.FileUtils;
import org.springFamework.http.HttpHeaders;
import org.springFamework.http.HttpStatus;
import org.springFamework.http.MediaType;
import org.springFamework.http.ResponseEntity;


@Controller
public class AttachFileController {

	@RequestMapping("/pdfView")
    public ResponseEntity<byte[]> pdfView(HttpServletRequest request, HttpServletResponse) throws Exception{
    	request.setCharacterEncoding("utf-8");
        String fileId = new String(request.getParameter("fileId".getBytes("8859_1", "KSC5601");
        // fileId 없는 경우 예외처리
        // fileId에 해당하는 파일 없는 경우 예외처리
              
        String filePath = ${FILES_ROOT_PATH} + fileId;
        String tempFile = new File(filePath);
        byte[] pdfBytes;
        
        try {
        	pdfBytes = org.apache.commons.io.FileUtils.readFileToByteArray(tempFile);
        } catch (Exception e){
        	e.printStackTrace();
            String error = "<script tye='text/javascript'> alert('File Not Found');</script>";
            byte[] arrorBytes = error.getBytes(StandardCharsets.UTF_8);
            return ResponseEntity.status(HttpStatus.INTERNAL_SERVER_ERROR).body(errorBytes);
            }
            
        HttpHeaders = headers = new HttpHeaders();
        headers.setContentType(MediaType.APPLICATION_PDF);
        headers.setContentDispositionFormData("filename", "example.pdf");
        headers.setContentLength(pdfBytes.length);
        //파일이 다운로드 되지 않고 브라우저 내에 보이도록 함
        headers.set("Content-Disposition", "inline; filename=example.pdf"
        
        return new ResponseEntity<>(pdfBytes, headers, HttpStatus.OK);
    }

}

프로젝트를 클라우드 환경에 배포하는 과정 중에 모르는것, 문제들에 대해서 다시 찾아보는 시간을 줄이기 위해 작성

groupId,  artiactedId, version 각 프로젝트별로 있고 의존성주입을 한 프로젝트들에도 모두 있다는 것을 알 수 있다.

최상단의 내용은 내가 작성한 프로젝트에 대한 groupId,  artiactedId, version을 의미한다.

[공식 문서의 설명 + 찾아본 정보]

groupId: 모든 프로젝트에서 각 프로젝트를 고유하게 식별하는 것

- Java의 패키지 이름 규칙을 따라야 한다.

(강제 규칙은 아니지만 역도메인이름(즉, Java 패키지 이름)을 사용하지 않고 단어하나로 쓰면

  Maven Central 저장소에서 프로젝트의 ID로 승인 받기 어려울 것)

- Java 패키지 이름 규칙을 따라서 하위그룹을 생성할 수 도 있음

artifactId: 버전 없이 jar 파일의 이름

- 소문자로 된 문자만 사용해야 함

- 다른 사람이 만든 jar 파일인 경우 배포되는 이름을 그대로 사용해야 함
예: maven, commons-math

- 웹 프로젝트의 Context root로 자동 설정된다. → 이 Context root는 배포할때 url 설정과 관련 있..는거 같음

pom.xml에  artifactId가 controller로 되어있어서 Context root도 /controller 로 되어 있음.

왜 저렇게 해놨는지는 당연히 모름... 그냥 프로젝트에 대한 setting을 복사해서 써서 그런것 같음. 그래서 artifactId와 함께 바꿈

version: 말그대로 배포하는 프로젝트의 버전

- 일반적인 형태 (1.0, 1.1, 1.0.1 등)를 사용할수 있지만,

날짜는 보통 SNAPSHOT 빌드와 연관되기 때문에 사용하지 않도록 함.

- 다른사람의 artifact인 경우 버전 번호 원래 적힌 그대로 사용해야 함.

출처 : https://maven.apache.org/guides/mini/guide-naming-conventions.html

Guide to naming conventions on groupId, artifactId, and version

• groupId uniquely identifies your project across all projects. A group ID should follow Java's package name rules. This means it starts with a reversed domain name you control. For example,org.apache.maven, org.apache.commonsYou can create as many subgroups as you want. A good way to determine the granularity of the groupId is to use the project structure. That is, if the current project is a multiple module project, it should append a new identifier to the parent's groupId. For example,
• org.apache.maven, org.apache.maven.plugins, org.apache.maven.reporting
• Maven does not enforce this rule. There are many legacy projects that do not follow this convention and instead use single word group IDs. However, it will be difficult to get a new single word group ID approved for inclusion in the Maven Central repository.
• artifactId is the name of the jar without version. If you created it, then you can choose whatever name you want with lowercase letters and no strange symbols. If it's a third party jar, you have to take the name of the jar as it's distributed.eg. maven, commons-math
• version if you distribute it, then you can choose any typical version with numbers and dots (1.0, 1.1, 1.0.1, ...). Don't use dates as they are usually associated with SNAPSHOT (nightly) builds. If it's a third party artifact, you have to use their version number whatever it is, and as strange as it can look. For example,2.0, 2.0.1, 1.3.1

+ 위의 정보들을 통해서 아래와 같이 여러 프로젝트들이 트리 형태를 만든다고 함.

    ⇒다른 프로젝트에서 나의 프로젝트를 사용할때 사용하는 식별자라고 생각하면될 것 같음

packaging : 패키징 할 형식

빌드 후 프로젝트 파일의 이름과 형식이 이렇게 생성된다.

출처 : https://youtu.be/KNGQ9JBQWhQ