Posted by Venkatt Guhesan on November 29, 2016
Most likely you’ve landed on this page because you’ve searched for the error in a search engine and it brought you here.
Symptom: When you run “grails” under an existing project that you previously had (either on a different PC or from a source-control like GIT or SVN and you’ve mistakenly included the “build” directory).
The associated error would have been one of the following:
Grails No profile found for name [web]
java.lang.IllegalStateException: No profile found for name [web].
| Error Error occurred running Grails CLI: No profile found for name [web]
Either way, here’s how you can quickly resolve this issue and get back in business.
Step-1: Remove “.grails” under your “home” directory.
rm -rf ~/.grails/
Step-2: Create a temporary *new* project
grails create-app bookstore
# This will create a new scafolding and download the dependencies
Step-3: Remove the “build” directory under your *original* Grails project where you had the problem to begin with.
rm -rf ./build/
# Remove the old "build" directory
Step-4: Run Grails once again under your *original* Grails project
You should see a whole bunch of dependencies being downloaded for this project like the following and you will end up with the Grails prompt:
| Enter a command name to run. Use TAB for completion:
Now you’re all set and ready to go.
|Today’s inspirational quote:
- When you need encouragement, think of the qualities the people around you have: this one’s energy, that one’s modesty, another’s generosity, and so on. Nothing is as encouraging as when virtues are visibly embodied in the people around us, when we’re practically showered with them. It’s good to keep this in mind.
- You have power over your mind—not outside events. Realize this, and you will find strength.
Posted in Gradle, Grails, Java, Spring, Spring Framework | Tagged: Grails, Grails Profile, IllegalStateException, Java, No profile found, web | Leave a Comment »
Posted by Venkatt Guhesan on November 3, 2016
If you’re implementing any projects with Spring and Gradle (for build), as your project grows you may run into this issue. Or you’ve landed on this page by searching on Google for “Unable to locate Spring NamespaceHandler for XML schema namespace” (your actual XML that it’s error-ing out may vary).
Either way, you’re in luck! Most likely, you’re using the fatjar gradle plugin to create a single JAR for executing as “java -jar one-big-bundle.jar”. The problem that happens is that if two or more dependent jar libraries contain the same file/artifact, then the last one wins the race in the fatjar bundle.
Let me illustrate this with an example:
Let’s say that your project depends on Spring-Context and Spring-Core. Within each jar, there maybe resources that have a common name such as META-INF/spring.schemas and/or META-INF/spring.handler (To learn more about the two individual files and their purpose in Spring, click on the links). When the fatjar combines the two JAR file, depending upon who goes last, the version of the above two files may belong to one or the other library. What should happen in reality is that it merges the two files contents. They maybe good for some files. But if you have a specific file in a format where you simply cannot concatenate the two files (such as a nested XML or JSON), simply combining the two files will not work. You may need to extend the Gradle plugin tasks to perform something selective and unique to your situation.
But if you ended up here after searching for “Unable to locate Spring NamespaceHandler for XML schema namespace” message, there is hope. You can simply, add the following to the fatJar Gradle plugin and problem is solved:
A second option is to use a newer plugin called shadow. [User Guide]
apply plugin: 'com.github.johnrengelman.shadow'
//For building a single jar with all dependencies run "gradlew shadowJar"
// Configure the shadow jar task
attributes 'Implementation-Title': 'application name',
Today’s Inspirational Quote:
…Bliss is not something to be got.
On the other hand you are always Bliss.
This desire [for Bliss] is born of the sense of incompleteness.
To whom is this sense of incompleteness? Enquire.
In deep sleep you were blissful.
Now you are not so.
What has interposed between that Bliss and this non-bliss?
It is the ego.
Seek its source and find you are Bliss.
– Ramana Maharishi|2nd link (Spiritual Teacher & one of the great minds of this century)
Posted in Gradle, Grails, Spring, Spring Framework | Tagged: fatJar, Gradle, shadowJar, Spring Framework, spring.handlers, spring.schemas | Leave a Comment »
Posted by Venkatt Guhesan on July 1, 2011
I’m sure if you have been developing with Java and Tomcat for sometime, you are likely to run into the infamous debug error.
SEVERE: Error listenerStart
You will most likely start Googling it trying to find out what the heck is going on. And in trying to see the extended logging on what that “listenerStart” error means. After some lucky searches, you will see links asking you to drop a “log4j.properties” file under ‘/WEB-INF/classes’ directory inside your WAR to help debug which one of the listeners is throwing this crazy error.
Well, this advise will most likely work for you if you are developing under an earlier version of Tomcat. If you are using versions 6.0 or above then continue to read on…
In Tomcat 6 or above, the default logger is the”java.util.logging” logger and not Log4J. So if you are trying to add a “log4j.properties” file – this will NOT work. The Java utils logger looks for a file called “logging.properties” as stated here:
So to get to the debugging details create a “logging.properties” file under your”/WEB-INF/classes” folder of your WAR and you’re all set.
And now when you restart your Tomcat, you will see all of your debugging in it’s full glory!!!
Sample logging.properties file:
org.apache.catalina.core.ContainerBase.[Catalina].level = INFO
org.apache.catalina.core.ContainerBase.[Catalina].handlers = java.util.logging.ConsoleHandler
and you will most likely see a “class-not-found” exception. 😉
Look at the bright side, you’re now one step closer to the solution.
Posted in Grails, Groovy, GWT, Java, Spring, Spring Framework, Tomcat, web development | Tagged: Error listnerStart, exception, Java, listenerStart, severe, Tomcat | 21 Comments »
Posted by Venkatt Guhesan on April 19, 2010
Sometimes it’s good to look at the svn repository for the reference sample that Spring Framework provides.
Here’s a quick link for that URL:
You can traverse through it via a HTTP(s) browser or you can download the latest samples via tools like TortiseSVN.
Here is a list of some of the projects samples that are available today:
spring-samples – Revision 431: /
Hopefully this article will be beneficial for someone who is trying to get familiar with Spring Framework.
Posted in Java, Programming, Spring, Spring Framework | Tagged: samples, Spring, Spring Framework | Leave a Comment »