war

Error while uploading springboot war file to Weblogic 12.2.1.3 server

心不动则不痛 提交于 2020-12-26 08:25:05
问题 I have created a war of springboot project using maven and did some changes to deploy the same on weblogic. While I am uploading the war file to weblogic server its throwing error as shown in screenshot below. I have added configuration details of my project as well. Can you please help me to resolve this. Spring boot main class import org.springframework.boot.SpringApplication; import org.springframework.boot.autoconfigure.SpringBootApplication; @SpringBootApplication public class

Error while uploading springboot war file to Weblogic 12.2.1.3 server

我与影子孤独终老i 提交于 2020-12-26 08:25:05
问题 I have created a war of springboot project using maven and did some changes to deploy the same on weblogic. While I am uploading the war file to weblogic server its throwing error as shown in screenshot below. I have added configuration details of my project as well. Can you please help me to resolve this. Spring boot main class import org.springframework.boot.SpringApplication; import org.springframework.boot.autoconfigure.SpringBootApplication; @SpringBootApplication public class

PropertiesLauncher with Spring Boot 2 (and running a WAR archive)

强颜欢笑 提交于 2020-12-04 03:39:52
问题 I am creating a tomcat/jsp based WAR spring boot 2.0.4 executable which works pretty well when just using bootWar gradle target. But now I want to load local external JARs and WarLauncher doesnt support this (is there a reason for that?). So I switched to PropertiesLauncher via: bootWar { enabled = true manifest { attributes 'Main-Class': 'org.springframework.boot.loader.PropertiesLauncher' } } Now looking inside the generated war file, everything looks ok in the MANIFEST like: Start-Class:

PropertiesLauncher with Spring Boot 2 (and running a WAR archive)

早过忘川 提交于 2020-12-04 03:38:55
问题 I am creating a tomcat/jsp based WAR spring boot 2.0.4 executable which works pretty well when just using bootWar gradle target. But now I want to load local external JARs and WarLauncher doesnt support this (is there a reason for that?). So I switched to PropertiesLauncher via: bootWar { enabled = true manifest { attributes 'Main-Class': 'org.springframework.boot.loader.PropertiesLauncher' } } Now looking inside the generated war file, everything looks ok in the MANIFEST like: Start-Class:

Reasons to use WEB-INF/lib over EAR's lib?

风格不统一 提交于 2020-08-27 21:32:06
问题 I am having second thoughts about something I've been taking for granted. Namely, in an EAR with the following structure: EAR \-- boo-ejb.jar \-- foo-web.war | \--WEB-INF | \--lib \--lib .. I think I understand correctly that the WEB-INF/lib is for jars needed only by the web application and the EAR-level lib for jars needed by the ejb.jar as well. The rationale being to somehow make the dependencies clearer. However, why not just dump everything in the EAR-level lib folder ? Surely if there

Why ClassLoader returns a path with extraneous second exclamation point

走远了吗. 提交于 2020-07-22 21:33:35
问题 I'm trying to grab a resource in ClassLoader . A simplified version of the code looks something like this: String ePath = "rewrite/common/RenameFunctor.groovy" String fPath = ThClType.class.getClassLoader().getResource(ePath); the response I get back as fPath is jar:file:/Users/myName/warPath/warName.war!/WEB-INF/classes!/rewrite/common/RenameFunctor.groovy . The actual path to the resource we want it exactly that, except without the second exclamation point. (Unlike warName.war , classes is

Deploy war file to heroku including additional files

六月ゝ 毕业季﹏ 提交于 2020-06-22 04:00:34
问题 I am deploying a war file to heroku and want to include additional properties file to the slug as described here: Configuring WAR Deployment with the Heroku CLI $ heroku war:deploy application.war --app awesomeapp --jdk 14 --includes app1.properties It deploys war file successfully, but in any subfolder of the expanded application I can't find app1.properties file. At the same time all other files from war archive are on their places, additional tomcat war-tracker file, and nothing more. I