I am attempting to deploy a Java application from Eclipse (Version: Indigo Release, Build id: 20110615-0604) to Glassfish 3.1 using the Eclipse server adapter. When deploying, Glassfish throws a ClassNotFound exception on one of the classes in my applications.
When I look at the classes folder on my domain (glassfishroot/glassfish/domains/domain1/eclipseApps/myApp/WEB-INF/classes) there are no classes there. There are empty folders for all the packages, but there are no files in them.
Why aren't my classes loaded into Glassfish, and what can I do to fix it?
EDIT:
If I clean and build the projects, the generated .class files are found in the project folder in Eclipse (project_root/build/classes/) so I know the build process is working.
EDIT 2:
Question resolved, see my answer below.
I found the problem, and in hindsight I feel rather stupid.
I had compilation errors in some of my Java classes. Once they were fixed, everything worked smoothly.
Sorry to have bothered you. Carry on with whatever you were doing.
Related
I'm using Netbeans 8.1 with Apache 1.7.1. I've been working on the project for more than a year now, on and off. It's been working perfectly more or less. The majority of project libs are inside server lib folder.
All of a sudden it is decided to remove rich faces libs from the server on Production and include them inside of the project - not my idea, but here we are. So I remove the libs from server on my machine, include them in project libraries, and the aforementioned error appears just like that:
...\build-impl.xml:1066: The module has not been deployed.
See the server log for details.
But the server log is clean and without errors.
I tried restarting server, Netbeans, pc and whatnot, but to no avail. I decided to take a step back: remove libs from project, copy them back to sever. But the problem remains.
I've tried solutions from at least three topics here: disabling network, cleaning Netbeans cache, ending Java task and others, but the problem still remains. Is there anything else that can be done?
This question has been asked many times, but I have yet to see anyone discuss it regarding debugging GWT with Eclipse.
I started getting this error after upgrading from GWT 2.6.0 to 2.6.1 and now 2.7.0.
I can add tomcat-juhli.jar, which is now found in the bin directory, to the classpath and make the error go away, but then I may get a variety of other errors. (Jasper, Permissions, JSTL).
After many hours of moving jars from the classpath into the WEB-INF/lib folder and back again, I no longer can get the eclipse debug perspective to open.
All jars that you use in your server code must be both on the build path and in the WEB-INF/lib folder.
If you get other errors when you do that, you have to deal with those errors.
The tomcat-juli file is required by Tomcat to do its logging, usually not required by either eclipse or your app.
the correct location in that case is the tomcat lib folder, next to jakarta etc.
there should also be a juli adapter jar.
not sure if this is really related to gwt.
Update: Check this page regarding logging in Tomcat: http://tomcat.apache.org/tomcat-7.0-doc/logging.html
If I understand your problem correctly, your chapter is the log4j chapter. Esp. the part with the juli jars. You need to fix the classpath for the tomcat adapter in eclipse to fix it.
if someone could help that would be amazing.
This project is being started in the NetBeans IDE EE version that comes with GlassFish Server. I've used Lucene to make a searchable twitter index of ~5G and am getting the NoClassDefFoundError only when called from the server giving a 500 Page Error.
The problem really confuses me, NetBeans is able to compile and run the code. When I call my functions from the same project in the IDE I'm able to use it perfectly. When I compile to a WebProject and launch it seems like GlassFish isn't able to find the files but I've made sure it has all the jars in the WAR file in the proper directories.
I've tried this both manually adding all the library files and by using Maven. Neither have worked, I've even added classpaths to the files elsewhere and added the files to glassfishes /lib folder.
Here is my setup.
http://imgbin.org/images/22748.PNG
I guess the problem is that you are mixing two different versions of lucene together (3.4 and 4.0).
I don't know why this works on your local Glassfish instance but you should update your dependencies so that they all have the same version.
When I'm changing some Java source code and my server is running, hot deploy fails, giving the following error message:
"Delete method not implemented"
How can I find out the root of this evil? My project has been recently deployed, so the sources on the server should be up to date.
The project uses JSF 1.2, if that's of any use for you.
I deploy the project as an exploded war.
Won't work with a zipped war either.
It's strange that the sources of dependencies are also not resolved in the debug mode. They're correctly read from the jar in the Eclipse Java view.
if you 'touch' the file (war/ear) in the deploy directory, this should trigger the deployment cycle, is this happening?
I've already asked a similar question more than one year ago. And my answer to it solved this problem too.
Uninstall all JDKs
Install only on JDK
Configure every program (Eclipse and JBoss) to use this JDK.
I couldn't find any info in google on this one, someone changed properties on a project and I'm not sure why the project can no longer deploy to jar. It compiles ok, but won't build into a jar file even though the dependencies do so just fine.
Has anyone run into this issue in JDeveloper before?
I can rename the jar to a different name (it's a dependency as well) but I need that specific name to match up with the other project.
I'm working with JDeveloper 10g and the project has been building fine for the last few months, and just now I'm getting this error which I can find no source or help on.
I've fixed it, it plagued me for 3 days.
The project itself had some deploy profile stuck in it, directly in the properties file of the project, not the external "blah blah.deploy".
When looking under the "Miscellaneous Files" area I noticed an extra deploy file, i.e. two deploy files in that area even though I hadn't deployed yet. This is how I figured out it was stuck in the project properties not in the external files. Removing one of these from the project fixed the issue, although I imagine ridding the project of both and creating a new deploy profile (still need to do this) would also fix it.
10g for the lose :p