I just converted a JSF web app to a maven based project.
I've just compiled it and deployed it to glassfish 4.0. Nothing loads on my page and I get the following log message:
[2013-10-03T15:21:24.736+1000] [glassfish 4.0] [WARNING] [realmAdapter.noWebSecMgr] [javax.enterprise.system.container.web.com.sun.web.security] [tid: _ThreadID=21 _ThreadName=http-listener-1(3)] [timeMillis: 1380777684736] [levelValue: 900] [[
WEB9100: No WebSecurityManager found for context WEB/WEB]]
I'm also using PrettyFaces and Primefaces in my project
Does anyone know what this means or what I need to do to fix it?
Not sure if you ever found a solution here, but I just had the same error when testing out a clustering setup. My solution was to add a web.xml, even though it is optional, it didn't work with out one. I would get the same WARNING and my responses were always empty.
Hope this helps!
I've had the same warning "No WebSecurityManager found for context" and empty html page and in my case the solution was - change the project directory tree:
It was:
hello\
hello\META-INF\
hello\META-INF\ ...some files
hello\src
hello\src\ ...some files
hello\web
hello\web\WEB-INF
hello\web\ *.xhtml files
hello\web\ ...other files
and after I've changed it to that one it started to work:
hello\
hello\META-INF\
hello\META-INF...some files
hello\src
hello\src...some files
hello\WEB-INF
hello\ *.xhtml files
hello\ ... other files
So, I eliminated "web" folder
Related
For my android project I upgraded play-services-auth library version from 15.0.0 to 16.0.1
Since then I see following error during the build and it also produces
ajcore files
I have removed my .gradle caches and done build and still see this error.
Anybody else seen this before, how do I fix it?
java.lang.IllegalStateException: Expecting .,<, or ;, but found authapi while unpacking Lcom/google/android/gms/common/api/internal/BaseImplementation$ApiMethodImpl;
at org.aspectj.util.GenericSignatureParser.parseClassTypeSignature(GenericSignatureParser.java:204)
at org.aspectj.util.GenericSignatureParser.parseFieldTypeSignature(GenericSignatureParser.java:155)
at org.aspectj.util.GenericSignatureParser.parseTypeArgument(GenericSignatureParser.java:267)
In my case, removing the Hugo logging plugin fixed the issue.
Check in your gradle file if you have it configured.
classpath 'com.jakewharton.hugo:hugo-plugin:1.2.1'
It happens because some plugin (added by you) use libs:
org.aspectj:aspectjtools
or
org.aspectj:aspectjrt for codegeneration
The Sync failed when tried to add the dependency for google play service. The problem seem to its looking for the jar in C:/Program/Files/Android/Android Studio however my SDK is placed in C:\Android\sdk. However I also have Android Studio in Program Files where there are no jar for Google play services.
Information:Gradle tasks [clean, :app:generateDebugSources, :app:compileDebugSources]
Error:A problem occurred configuring root project 'XXXXXX'.
Could not resolve all dependencies for configuration ':classpath'.
Could not find com.google.gms:google-services:9.0.0.
Searched in the following locations:
file:/C:/Program Files/Android/Android Studio/gradle/m2repository/com/google/gms/google-services/9.0.0/google-services-9.0.0.pom
file:/C:/Program Files/Android/Android Studio/gradle/m2repository/com/google/gms/google-services/9.0.0/google-services-9.0.0.jar
https://jcenter.bintray.com/com/google/gms/google-services/9.0.0/google-services-9.0.0.pom
https://jcenter.bintray.com/com/google/gms/google-services/9.0.0/google-services-9.0.0.jar
Required by:
:XXXXX:unspecified
Information:BUILD FAILED
Information:Total time: 6.148 secs
Information:1 error
Information:0 warnings
Information:See complete output in console
Also my ANDROID_HOME is set to C:\Android\sdk.
Please advise.
By checking other SO question. You can find that Google Play Service updating to version 9.0.0 has a bug issue.
Some solution is by checking if you have enabled offline work for gradle, deselect Offline Work if it's checked. Then, confirm if you have latest version of Google services mentioned as dependencies in project level build.gradle: classpath 'com.google.gms:google-services:3.0.0'. Clean and build the project after the gradle sync completes.
Also, some people fixed it by just deleting the debug.keystore file found in the android folder.
Check this SO question for more information.
I am tearing my hair out trying to figure out how to run the simplest Apache Mina tutorial.
I am running the tutorial on Netbeans 6.9 on Ubuntu and it keeps saying the following error
even I have added the necessary jar files to the compile-time libraries folders in Netbeans.
Exception in thread "main"
java.lang.ExceptionInInitializerError
at minatimeserver.MinaTimeServer.main(MinaTimeServer.java:29)
Caused by: java.lang.RuntimeException:
Uncompilable source code - package
org.slf4j does not exist
at org.apache.mina.core.service.AbstractIoService.(AbstractIoService.java:51)
... 1 more
I have downloaded slf4j-log4j12-1.6.1.jar and slf4j-api-1.6.1.jar and placed them in the compile-time libraries folder too but the error still remains. I have also tried with slf4j-1.5.11
Any person who has solved this problem? Please help me or I'm going bald in no time!
Thanks in advance!
Yakult121
slf4j-log4j12-1.6.1.jar and slf4j-api-1.6.1.jar are runtime libraries.
Add them to your class path not to your compile-time libraries else it will try to compile your jar files.
Also See
What's the difference of compile time libraries and run time libraries in java?
Apache mina uses slf4j-api-1.6.1.jar, adding slf4j-api-1.6.1.jar to class path will resolve the issue.
Well, I also had faced same problem. What I did was, I unjarred the mina-core-2.x that is on the main page of the apache project. When things failed, I changed downloaded mina-core-1.1.7 and everything worked fine. Of course, you have to make sure that you set the claspath correctly.
Note - I will really appreciate a quick and complete answer to this question. I can't offer a bounty yet because I just published this question a few hours ago, but if someone answers this question fully, I will issue a total bounty of 150 (100 from me + 50) and award it to them.
I have tried to work my way through the GWT Archtype, but failed. Currently, I'm getting an error finding entry point class, when doing "mvn clean package"
INFO] auto discovered modules [org.test.TestGwt]
INFO] Compiling module org.test.TestGwt
INFO] Finding entry point classes
INFO] [ERROR] Unable to find type 'org.test.MyEntryPoint'
INFO] [ERROR] Hint: Previous compiler errors may have made this type unavailable
I uploaded the source code to my dropbox, would appreciate your help. This is a very stripped down project, it only contains the bare essentials - please help me figure out a working example.
My goal is to get mvn gwt:run to work, and to get a deployable war that actually works.
the property:
<source path="org/test"/>
refers to the path relative to your TestGwt.gwt.xml file itself. Also don't put server side code in your code base because GWT tries to compile it to JavaScript and will fail because it contains classes not available to compile.
I suggest you add 2 folders to you package structure:
org.test.client
org.test.server
Leave the TestGwt.gwt.xml file in the org/test folder.
and change the gwt.xml to:
<source path="client"/>
We have our local Maven repository which was working fine till yesterday.
Today we are getting the following error while building any project.
Failed to load late-bound plugin: org.apache.maven.plugins:maven-resources-plugin
We haven't change any settings. Any idea?
It's hard to say because you skipped the next line that prints the Reason. A typical output looks like:
[WARN] Failed to load plugin: org.apache.maven.plugins:maven-resources-plugin. Adding to late-bound plugins list.
Reason: Failed to load plugin. Reason: The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not exist or no valid version could be found
It would have been interesting to join this line to find a fix for the root cause of the problem.
I resolved it.
I had to delete the plugins folder on my local repository then Maven downloaded the plugins again.
It works fine now.