war

I've an issue with logback. I set it up (using maven) and everything seems fine except that Logback reports it can't find the configuration file (but I'm able to log to the console using the default logger configuration). [#|2013-07-03T07:55:30.843+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=124;_ThreadName=Thread-2;|07:54:39,844 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 07:54:39,844 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 07

I'm having a problem trying to deploy Jenkins war to Tomcat. I'm using CentOS with Java 1.6.0_28, Tomcat 6.0.24 and last version of jenkins as of January 21, 2014. I think the problem is more related to Jenkins because of the log but not sure. When I google the error only find the classes that fire the exception but no solution. Here is the log. Any help is appreciated. Jan 21, 2014 9:30:26 PM hudson.util.BootFailure publish SEVERE: Failed to initialize Jenkins hudson.util.NoHomeDir at hudson.WebAppMain.contextInitialized(WebAppMain.java:126) at org.apache.catalina.core.StandardContext

In eclipse, when exporting a web project to war/ear file there is this option "Optimize for a specific server runtime" What does happen under the hood when this option is selected? Couldn't find an explanation about that so far. I am running Eclipse Indigo 3.7 . Eclipse itself doesn't do anything with that option. What happens is dependent on a particular server adapter. Many of the adapters don't do anything with this option either, but they might in the future. If a server adapter does support export optimization, it has the option of displaying custom options beneath that pop-up list of

I have a Maven project with a parent-pom project and 3 maven-module projects in it. 2 of the modules are Java-EE web apps that compile into WAR files. 1 of the modules contains common JAVA code which is shared between the 2 other projects. Sharing the JAVA code was easy. The question I have is how to a share common static resources such as JavaScript, CSS, and image files without duplicating them in each web module? I would also like to do it in such a way that I can continue running the web app from Eclipse and have changes I make to the static-files automatically available to the Eclipse's

It used to take 3 minutes to deploy our WAR to WebSphere 8.5.5.0. It takes 3 hours to deploy the same WAR to WebSphere 9.0.0.2. Is that a manifestation of a bug in WebSphere 9.0.0.2? Did anybody have similar experience? UPDATE: Results of my experiments with settings suggested by IBM: http://www-01.ibm.com/support/docview.wss?uid=swg21983564 Our WAR file contains 160 JAR files with total size of 160MB. Time is measured for the "New Application" wizard, from first screen, until the next screen is shown. WebSphere 8.5.5 - 3 minutes WebSphere 9 - 3 hours Added "Ignore-Scanning-Packages: org, net,

I would like to have a symbolic link in tomcat's webapps directory that points to a war file at another place in my file system, and I would like that war file to be served as the default webapp. I have pieced together the following solution, but the app is not accessible from the browser. I have a folder in my home directory ~/tomcat/webapps. The owner is tomcat7. In this folder, I have my war file, myapp-1.0.war. In my /var/lib/tomcat7/webapps directory, I have a symbolic link: myapp -> /home/[me]/tomcat/webapps/myapp-1.0.war. In my /etc/tomcat7/server.xml, I have: <Context docBase="/var/lib

I have in my main config something like: grails.config.locations = ["file:grails-app/config/Jawr.groovy"]. When running the application with grails run-app, everything is OK. But, on deployment (creating the war archive) this does not work anymore, as the file "Jawr.groovy" is not kept anymore on the filesystem (it should be only in the war). Do you have a solution for that? Hw do you include external files into the grails main configuration file? Thanks. Okay, a few things here. First, because you don't have a leading slash on your config path, that is a path relative to who knows where. I