Learn and Be Curious

2월 14, 2017 12:44:26 오전 org.apache.tomcat.util.digester.SetPropertiesRule begin

경고: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:first' did not find a matching property.

2월 14, 2017 12:44:26 오전 org.apache.tomcat.util.digester.SetPropertiesRule begin

경고: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:jqwidgets-spring' did not find a matching property.

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: Server version:        Apache Tomcat/9.0.0.M15

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: Server built:          Dec 5 2016 13:44:25 UTC

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: Server number:         9.0.0.0

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: OS Name:               Windows 10

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: OS Version:            10.0

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: Architecture:          amd64

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: Java Home:             C:\Program Files\Java\jre1.8.0_111

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: JVM Version:           1.8.0_111-b14

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: JVM Vendor:            Oracle Corporation

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: CATALINA_BASE:         C:\Users\myung\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: CATALINA_HOME:         C:\dev\tomcat

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: Command line argument: -Dcatalina.base=C:\Users\myung\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: Command line argument: -Dcatalina.home=C:\dev\tomcat

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: Command line argument: -Dwtp.deploy=C:\Users\myung\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\wtpwebapps

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: Command line argument: -Djava.endorsed.dirs=C:\dev\tomcat\endorsed

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: Command line argument: -Dfile.encoding=UTF-8

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.VersionLoggerListener log

정보: Command line argument: -Xbootclasspath:C:\Program Files\Java\jre1.8.0_111\lib\resources.jar;C:\Program Files\Java\jre1.8.0_111\lib\rt.jar;C:\Program Files\Java\jre1.8.0_111\lib\jsse.jar;C:\Program Files\Java\jre1.8.0_111\lib\jce.jar;C:\Program Files\Java\jre1.8.0_111\lib\charsets.jar;C:\Program Files\Java\jre1.8.0_111\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_111\lib\tools.jar

2월 14, 2017 12:44:26 오전 org.apache.catalina.core.AprLifecycleListener lifecycleEvent

정보: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre1.8.0_111\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:/Program Files/Java/jre1.8.0_111/bin/server;C:/Program Files/Java/jre1.8.0_111/bin;C:/Program Files/Java/jre1.8.0_111/lib/amd64;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Git\cmd;C:\Program Files\nodejs\;C:\Users\myung\AppData\Local\Microsoft\WindowsApps;C:\Users\myung\AppData\Roaming\npm;C:\WINDOWS\system32;;.

2월 14, 2017 12:44:26 오전 org.apache.coyote.AbstractProtocol init

정보: Initializing ProtocolHandler ["http-nio-8080"]

2월 14, 2017 12:44:26 오전 org.apache.tomcat.util.net.NioSelectorPool getSharedSelector

정보: Using a shared selector for servlet write/read

2월 14, 2017 12:44:26 오전 org.apache.coyote.AbstractProtocol init

정보: Initializing ProtocolHandler ["ajp-nio-8009"]

2월 14, 2017 12:44:26 오전 org.apache.tomcat.util.net.NioSelectorPool getSharedSelector

정보: Using a shared selector for servlet write/read

2월 14, 2017 12:44:26 오전 org.apache.catalina.startup.Catalina load

정보: Initialization processed in 1025 ms

2월 14, 2017 12:44:26 오전 org.apache.catalina.core.StandardService startInternal

정보: Starting service Catalina

2월 14, 2017 12:44:26 오전 org.apache.catalina.core.StandardEngine startInternal

정보: Starting Servlet Engine: Apache Tomcat/9.0.0.M15

2월 14, 2017 12:44:30 오전 org.apache.jasper.servlet.TldScanner scanJars

정보: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

2월 14, 2017 12:44:30 오전 org.apache.catalina.core.ApplicationContext log

정보: No Spring WebApplicationInitializer types detected on classpath

2월 14, 2017 12:44:30 오전 org.apache.catalina.core.ApplicationContext log

정보: Initializing Spring root WebApplicationContext

2월 14, 2017 12:44:32 오전 org.apache.catalina.core.ApplicationContext log

정보: Initializing Spring FrameworkServlet 'action'

2월 14, 2017 12:44:35 오전 org.apache.jasper.servlet.TldScanner scanJars

정보: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

2월 14, 2017 12:44:35 오전 org.apache.catalina.core.ApplicationContext log

정보: No Spring WebApplicationInitializer types detected on classpath

2월 14, 2017 12:44:35 오전 org.apache.catalina.core.ApplicationContext log

정보: Initializing Spring FrameworkServlet 'mvc-dispatcher'

2월 14, 2017 12:44:35 오전 org.springframework.web.servlet.DispatcherServlet initServletBean

정보: FrameworkServlet 'mvc-dispatcher': initialization started

2월 14, 2017 12:44:35 오전 org.springframework.web.context.support.XmlWebApplicationContext prepareRefresh

정보: Refreshing WebApplicationContext for namespace 'mvc-dispatcher-servlet': startup date [Tue Feb 14 00:44:35 KST 2017]; root of context hierarchy

2월 14, 2017 12:44:35 오전 org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions

정보: Loading XML bean definitions from ServletContext resource [/WEB-INF/mvc-dispatcher-servlet.xml]

2월 14, 2017 12:44:36 오전 org.springframework.web.servlet.handler.SimpleUrlHandlerMapping registerHandler

정보: Mapped URL path [/resources/**] onto handler 'org.springframework.web.servlet.resource.ResourceHttpRequestHandler#0'

2월 14, 2017 12:44:36 오전 org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping registerHandlerMethod

정보: Mapped "{[/chart/getProducts],methods=[POST],params=[],headers=[],consumes=[],produces=[],custom=[]}" onto public java.util.List<com.jqwidgets.Product> com.jqwidgets.ChartController.getProducts() throws java.lang.ClassNotFoundException

2월 14, 2017 12:44:36 오전 org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping registerHandlerMethod

정보: Mapped "{[/chart],methods=[GET],params=[],headers=[],consumes=[],produces=[],custom=[]}" onto public java.lang.String com.jqwidgets.ChartController.chart(org.springframework.ui.ModelMap)

2월 14, 2017 12:44:36 오전 org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping registerHandlerMethod

정보: Mapped "{[/datatable/getEmployees],methods=[POST],params=[],headers=[],consumes=[],produces=[],custom=[]}" onto public java.util.List<com.jqwidgets.Employee> com.jqwidgets.DataTableController.getEmployees() throws java.lang.ClassNotFoundException

2월 14, 2017 12:44:36 오전 org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping registerHandlerMethod

정보: Mapped "{[/datatable],methods=[GET],params=[],headers=[],consumes=[],produces=[],custom=[]}" onto public java.lang.String com.jqwidgets.DataTableController.dataTable(org.springframework.ui.ModelMap)

2월 14, 2017 12:44:36 오전 org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping registerHandlerMethod

정보: Mapped "{[/dgrid/getEmployees],methods=[POST],params=[],headers=[],consumes=[],produces=[],custom=[]}" onto public java.util.List<com.jqwidgets.Employee> com.jqwidgets.DynamicController.getEmployees() throws java.lang.ClassNotFoundException

2월 14, 2017 12:44:36 오전 org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping registerHandlerMethod

정보: Mapped "{[/dgrid],methods=[GET],params=[],headers=[],consumes=[],produces=[],custom=[]}" onto public java.lang.String com.jqwidgets.DynamicController.dataTable(org.springframework.ui.ModelMap)

2월 14, 2017 12:44:36 오전 org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping registerHandlerMethod

정보: Mapped "{[/grid/getEmployees],methods=[POST],params=[],headers=[],consumes=[],produces=[],custom=[]}" onto public java.util.List<com.jqwidgets.Employee> com.jqwidgets.GridController.getEmployees() throws java.lang.ClassNotFoundException

2월 14, 2017 12:44:36 오전 org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping registerHandlerMethod

정보: Mapped "{[/grid],methods=[GET],params=[],headers=[],consumes=[],produces=[],custom=[]}" onto public java.lang.String com.jqwidgets.GridController.grid(org.springframework.ui.ModelMap)

2월 14, 2017 12:44:36 오전 org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping registerHandlerMethod

정보: Mapped "{[/test/getEmployees],methods=[POST],params=[],headers=[],consumes=[],produces=[],custom=[]}" onto public java.util.List<com.jqwidgets.Employee> com.jqwidgets.TestController.getEmployees() throws java.lang.ClassNotFoundException

2월 14, 2017 12:44:36 오전 org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping registerHandlerMethod

정보: Mapped "{[/test],methods=[GET],params=[],headers=[],consumes=[],produces=[],custom=[]}" onto public java.lang.String com.jqwidgets.TestController.grid(org.springframework.ui.ModelMap)

2월 14, 2017 12:44:37 오전 org.springframework.web.servlet.DispatcherServlet initServletBean

정보: FrameworkServlet 'mvc-dispatcher': initialization completed in 1921 ms

2월 14, 2017 12:44:37 오전 org.apache.coyote.AbstractProtocol start

정보: Starting ProtocolHandler [http-nio-8080]

2월 14, 2017 12:44:37 오전 org.apache.coyote.AbstractProtocol start

정보: Starting ProtocolHandler [ajp-nio-8009]

2월 14, 2017 12:44:37 오전 org.apache.catalina.startup.Catalina start

정보: Server startup in 10704 ms



The article lists down two most commonly used folder structure for a Spring MVC/Hibernate based web application project. In fact, this folder structure could be used with any other MVC framework like Spring. Following are different two folder structures described later in this article:

  • Eclipse-based Web Application (Dynamic Web Project)
  • Maven-based Web Application Project
Eclipse-based Web Application (Dynamic Web Project)

As per this Eclipse page, Dynamic web projects contain dynamic Java EE resources such as servlets, JSP files, filters, and associated metadata, in addition to static resources such as images and HTML files. Following is how the folder structure looks like on the disk:

  • src
    • packages (com.orgid.abc)
  • WebContent
    • CSS/JS Folders (Publicly accessible; DO NOT Put them within WEB-INF)
    • META-INF (Manifest.mf)
    • WEB-INF
      • lib (Consists of Spring, Hibernate and dependent libraries)
      • views (depends upon the configuration in spring-servlet.xml)
      • web.xml
      • spring-servlet.xml (Spring related configuration)
      • hibernate.cfg.xml (Hibernate related configuration)

Following is the sample screenshot of how it looks within Eclipse:

Dynamic Web Project Folder Structure

Maven-based Web Application Project

Following is the standard folder structure one would find in many of the web applications. It is  also the directory layout expected by Maven and the directory layout created by Maven. The details about this folder structure could be found on the Maven Apache page. The directory structure is primarily laid down based on two code groupings:

  • src/main: Main build artifact consisting of Java code, configuration files, filters, scripts, application libraries etc. All these artifacts are placed within “src/main” and sub-folders as java, webapp, resources, filters, configs, scripts. It looks like following:”
  • src/test: Test build artifact consisting of unit test code. The unit tests code is placed within folder such as “src/test/java”.

Following is the minimum folder structure based on above description that would be enough to run your hello world Spring MVC/Hibernate application:

  • src/main/java: Consists of source code
  • src/main/webapp: Consists of libraries, configuration files, resources etc.
    • CSS/JS Folders (Publicly accessible; DO NOT put them within WEB-INF)
    • META-INF (Manifest.mf)
    • WEB-INF
      • lib  (Consists of Spring, Hibernate and dependent libraries)
      • views (Depends upon the configuration in spring-servlet.xml)
      • web.xml
      • spring-servlet.xml (Spring related configuration)
      • hibernate.cfg.xml (Hibernate related configuration)
  • src/test/java: Consists of unit test code

If you are working on Maven based project, you could adopt the Maven-based folder structure. Build tools such as Gradle work like charm. However, Gradle could easily be configured to work with Eclipse-based dynamic web project folder structure. This will be discussed in later articles. Rookies could start with Eclipse-based folder structure.


'dev > spring framework' 카테고리의 다른 글

정상 로그  (0) 2017.02.14
Spring Legacy Project 에서 MVC Project가 안보일때 해결방법  (0) 2017.01.04

https://stackoverflow.com/questions/13533123/spring-tool-suite-missing-spring-mvc-project-template/40698374



Try this , it solved my issue.

  1. Go to New Project -> Spring Legacy Project. For first use, only show "Simple Project" folder.
  2. Select Configure templates.. (blue link).
  3. In Template Projects window, delete "spring-data-gemfire" and "spring-integration", and check "Show self-hosted templates ..." (at bottom), and then press Apply -> OK
  4. Just wait while refreshing process, and "Spring MVC Project" should be showed.


'dev > spring framework' 카테고리의 다른 글

정상 로그  (0) 2017.02.14
Web Application Folder Structure for Spring MVC Web Projects  (0) 2017.02.13