OHDSI Home | Forums | Wiki | Github

shiroFilter error occured when I deploy 'Webapi.war' file in tomcat

webapi

(Park,CHANGHYUN) #1

Hi. I am a beginner in OHDSI Tools.
I want to install OHDSI Tools in my local PC. I’m already success build ‘WebAPI’ through ‘maven’.

But when I try deploy ‘Webapi.war’ file in tomcat, it show error like below.
So how can I solve this error.

P.S
this is my environment SPEC
-Oracle 11g realease2,
-Webapi 2.6,

Also It’s really strange. Now I’m trying to ‘CDM’ data update in my office Server. So we make a new ‘CDM Schema’ & ‘CDM_Result Schema’ in our Sever.
By the way It’s occured same error below.
it’s well working previous ‘CDM Schema’ & ‘CDM_Result Schema’.
So I am suspicious that this error is occured by ‘Grant’ in oracle.

Please let me know how can I solve this error.


ΓΓ
14-Jan-2019 12:24:44.210 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.37
14-Jan-2019 12:24:44.217 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Dec 12 2018 12:07:02 UTC
14-Jan-2019 12:24:44.218 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.37.0
14-Jan-2019 12:24:44.219 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows 7
14-Jan-2019 12:24:44.220 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 6.1
14-Jan-2019 12:24:44.221 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
14-Jan-2019 12:24:44.222 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:\Program Files\Java\jre1.8.0_191
14-Jan-2019 12:24:44.223 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_191-b12
14-Jan-2019 12:24:44.224 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
14-Jan-2019 12:24:44.225 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: D:\apache-tomcat-8.5.37
14-Jan-2019 12:24:44.225 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: D:\apache-tomcat-8.5.37
14-Jan-2019 12:24:44.227 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=D:\apache-tomcat-8.5.37\conf\logging.properties
14-Jan-2019 12:24:44.227 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
14-Jan-2019 12:24:44.229 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
14-Jan-2019 12:24:44.231 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
14-Jan-2019 12:24:44.233 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=
14-Jan-2019 12:24:44.236 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=D:\apache-tomcat-8.5.37
14-Jan-2019 12:24:44.238 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=D:\apache-tomcat-8.5.37
14-Jan-2019 12:24:44.239 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=D:\apache-tomcat-8.5.37\temp
14-Jan-2019 12:24:44.241 정보 [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based Apache Tomcat Native library [1.2.19] using APR version [1.6.5].
14-Jan-2019 12:24:44.242 정보 [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
14-Jan-2019 12:24:44.243 정보 [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]
14-Jan-2019 12:24:44.262 정보 [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.1.1a 20 Nov 2018]
14-Jan-2019 12:24:44.456 정보 [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler [“http-nio-8070”]
14-Jan-2019 12:24:44.725 정보 [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
14-Jan-2019 12:24:44.753 정보 [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler [“ajp-nio-8009”]
14-Jan-2019 12:24:44.763 정보 [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
14-Jan-2019 12:24:44.765 정보 [main] org.apache.catalina.startup.Catalina.load Initialization processed in 3917 ms
14-Jan-2019 12:24:44.827 정보 [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
14-Jan-2019 12:24:44.828 정보 [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.37
14-Jan-2019 12:24:44.864 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [D:\apache-tomcat-8.5.37\webapps\WebAPI.war]
14-Jan-2019 12:24:44.880 경고 [localhost-startStop-1] org.apache.catalina.startup.SetContextPropertiesRule.begin [SetContextPropertiesRule]{Context} Setting property ‘antiJARLocking’ to ‘true’ did not find a matching property.
14-Jan-2019 12:25:18.359 심각 [localhost-startStop-1] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/WebAPI]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:754)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:730)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:985)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘shiroFilter’ defined in class path resource [org/ohdsi/webapi/ShiroConfiguration.class]: Unsatisfied dependency expressed through method ‘shiroFilter’ parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘flyway’ defined in class path resource [org/ohdsi/webapi/FlywayConfig.class]: Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Schema “OHDSI” contains a failed migration to version 1.0.0.1 !
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:749)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:467)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1173)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1067)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:513)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
at org.springframework.context.support.PostProcessorRegistrationDelegate.registerBeanPostProcessors(PostProcessorRegistrationDelegate.java:235)
at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:702)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:527)
at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:737)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:370)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:314)
at org.springframework.boot.web.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:151)
at org.springframework.boot.web.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:131)
at org.springframework.boot.web.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:86)
at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:169)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5267)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 10 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘flyway’ defined in class path resource [org/ohdsi/webapi/FlywayConfig.class]: Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Schema “OHDSI” contains a failed migration to version 1.0.0.1 !
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1628)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:296)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:208)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1138)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1066)
at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:835)
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:741)
… 32 more
Caused by: org.flywaydb.core.api.FlywayException: Schema “OHDSI” contains a failed migration to version 1.0.0.1 !
at org.flywaydb.core.internal.command.DbMigrate$2.call(DbMigrate.java:193)
at org.flywaydb.core.internal.command.DbMigrate$2.call(DbMigrate.java:146)
at org.flywaydb.core.internal.dbsupport.DbSupport$1.call(DbSupport.java:223)
at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:75)
at org.flywaydb.core.internal.dbsupport.DbSupport.lock(DbSupport.java:219)
at org.flywaydb.core.internal.metadatatable.MetaDataTableImpl.lock(MetaDataTableImpl.java:174)
at org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:146)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:1010)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:971)
at org.flywaydb.core.Flyway.execute(Flyway.java:1464)
at org.flywaydb.core.Flyway.migrate(Flyway.java:971)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1758)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1695)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1624)
… 45 more

14-Jan-2019 12:25:18.372 심각 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive [D:\apache-tomcat-8.5.37\webapps\WebAPI.war]
java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/WebAPI]]
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:758)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:730)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:985)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

14-Jan-2019 12:25:18.378 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [D:\apache-tomcat-8.5.37\webapps\WebAPI.war] has finished in [33,512] ms
14-Jan-2019 12:25:18.380 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [D:\apache-tomcat-8.5.37\webapps\Atlas]
14-Jan-2019 12:25:18.440 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [D:\apache-tomcat-8.5.37\webapps\Atlas] has finished in [60] ms
14-Jan-2019 12:25:18.441 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [D:\apache-tomcat-8.5.37\webapps\docs]
14-Jan-2019 12:25:18.474 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [D:\apache-tomcat-8.5.37\webapps\docs] has finished in [33] ms
14-Jan-2019 12:25:18.476 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [D:\apache-tomcat-8.5.37\webapps\examples]
14-Jan-2019 12:25:18.878 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [D:\apache-tomcat-8.5.37\webapps\examples] has finished in [402] ms
14-Jan-2019 12:25:18.879 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [D:\apache-tomcat-8.5.37\webapps\host-manager]
14-Jan-2019 12:25:18.918 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [D:\apache-tomcat-8.5.37\webapps\host-manager] has finished in [39] ms
14-Jan-2019 12:25:18.920 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [D:\apache-tomcat-8.5.37\webapps\manager]
14-Jan-2019 12:25:18.953 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [D:\apache-tomcat-8.5.37\webapps\manager] has finished in [33] ms
14-Jan-2019 12:25:18.955 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [D:\apache-tomcat-8.5.37\webapps\ROOT]
14-Jan-2019 12:25:18.980 정보 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [D:\apache-tomcat-8.5.37\webapps\ROOT] has finished in [25] ms
14-Jan-2019 12:25:18.988 정보 [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler [“http-nio-8070”]
14-Jan-2019 12:25:19.012 정보 [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler [“ajp-nio-8009”]
14-Jan-2019 12:25:19.026 정보 [main] org.apache.catalina.startup.Catalina.start Server startup in 34257 ms
14-Jan-2019 12:25:53.833 경고 [http-nio-8070-exec-5] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [WebAPI] registered the JDBC driver [oracle.jdbc.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.」」


(Kwang Soo Jeong) #2

Hello.
(안녕하세요)

It seems to me that the maven command uses the P option to parameterize oracle.
(제가 보기에는 mvn 명령어에 P 옵션을 사용해 oracle을 파라미터로 준 것 같습니다.)

<datasource.ohdsi.schema>OHDSI</datasource.ohdsi.schema>

I do not know what the default schema is because I do not use Oracle DB, but the pom.xml file seems to have the above settings.
(제가 오라클 DB를 사용하지 않아서 기본 스키마가 무엇인지는 잘 모르겠지만, 현재 돌리시고 있는 pom.xml 파일에 위와 같은 설정이 있는 것 같습니다.)

Please enter the name of the schema you want to use in the code, and please make the schema in the database in the DBMS so that you can go ahead again.
(해당 코드에 본인이 사용하기 원하는 스키마의 이름을 넣어주시기 바라며 동시에, DBMS에서 해당 데이터베이스에 스키마를 만들어주시고 다시 한 번 진행해주시기 바랍니다.)


(Park,CHANGHYUN) #3

Thanks for your favor.
(우선 이렇게 친절히 답변해주셔서 감사합니다.)

I’m already do action like you said, matched DBMS Schemas, manipulate pom.xml file through settings.xml
(저는 답변자님이 말씀해주신 것 처럼 DBMS에 OHDSI라는 스키마를 구성했고, settings.xml 파일을 통해 pom.xml 파일의 설정을 변경하도록 세팅했습니다.)

But it still occured error. (그러나 여전히 에러가 발생합니다.)

So I want to try that you said "
It seems to me that the maven command uses the P option to parameterize oracle.
(그래서 답변자님이 언급하신 " mvn 명령어에 P 옵션을 사용해 oracle을 파라미터로 준 것" 이라는 의미를 알아내서 문제를 해결하고 싶습니다.)

When I build WebAPI.war file, I type the command Line like
“mvn clean package -s WebAPIConfig/settings.xml -P webapi-oracle”.
Is it any problem?
(제가 WebAPI.war파일을 빌드 할때 다음과 같은 명령어를 썼는데 여기에 혹시 문제가 있을까요?)


(Kwang Soo Jeong) #4

At the bottom of the Maven configuration file called pom.xml, there will be profiles set up for each DBMS.
(pom.xml 혹은 질문자님께서 s 옵션으로 지정한 settings.xml 안에 맨 밑쪽을 보면 각 DBMS별로 설정한 Profile들이 존재할 것입니다.)

<profile>
      <id>webapi-postgresql</id>
      <properties>
        <datasource.driverClassName>org.postgresql.Driver</datasource.driverClassName>
        <datasource.url>jdbc:postgresql://dbHost:dbPort/databaseName</datasource.url>
        <datasource.username>USER</datasource.username>
        <datasource.password>PASS</datasource.password>
        <datasource.dialect>postgresql</datasource.dialect>
        <datasource.ohdsi.schema>ohdsi</datasource.ohdsi.schema>
        <flyway.datasource.driverClassName>${datasource.driverClassName}</flyway.datasource.driverClassName>
        <flyway.datasource.url>${datasource.url}</flyway.datasource.url>
        <flyway.datasource.username>userWithWritesToOhdsiSchema</flyway.datasource.username>
        <flyway.datasource.password>PASS</flyway.datasource.password>
        <flyway.schemas>${datasource.ohdsi.schema}</flyway.schemas>
        <flyway.placeholders.ohdsiSchema>${datasource.ohdsi.schema}</flyway.placeholders.ohdsiSchema>
        <flyway.locations>classpath:db/migration/postgresql</flyway.locations>
        <spring.batch.repository.tableprefix>${datasource.ohdsi.schema}.BATCH_</spring.batch.repository.tableprefix>
        <hibernate.dialect>org.hibernate.dialect.PostgreSQL9Dialect</hibernate.dialect>
        <security.db.datasource.url>${datasource.url}</security.db.datasource.url>
        <security.db.datasource.driverClassName>${datasource.driverClassName}</security.db.datasource.driverClassName>
        <security.db.datasource.username>${datasource.username}</security.db.datasource.username>
        <security.db.datasource.password>${datasource.password}</security.db.datasource.password>
        <security.db.datasource.authenticationQuery>select password from ${security.db.datasource.schema}.users_data where \
          lower(email) = lower(?)</security.db.datasource.authenticationQuery>
      </properties>
    </profile>

For example, in PostgreSQL, it looks like the code above. Looking at the code, we have defined the name webapi-postgresql using the profile tag.
(예를 들어서 PostgreSQL의 경우 위의 코드와 같습니다. 코드를 보면 profile 하위의 id태그를 이용해 webapi-postgresql 이라는 이름이 정의되어 있습니다.)

This tag is the name to put in the P option when you use the mvn command later.
(이 태그는 차후에 mvn 명령어를 사용할 때 P 옵션에 들어갈 이름을 말합니다.)

mvn package -P webapi-postgresql

Then the questioner can build WebAPI through the above command.
(그러면 질문자님께서는 위 명령어를 통해 WebAPI를 빌드하실 수 있습니다.)


(Park,CHANGHYUN) #5

Currently, I still face same error.
As you(NEONKID) told me, I’m already did setting.
(Frankly speaking, that’s a miss typing that " -P webapioracle".)

Also I did WebAPI build success. But while webapi deploy in tomcat, it still ouccured Same matter “shiroFilter Error”.

please help me.


t