For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 10 replies, 2 voices, and was last updated 19 years, 8 months ago by
.
-
Posts
-
MyEclipse Workbench 5.0.1 GA
JRE 1.5.0_06When I try to add JSF capablility to a web project, I get “this operation is not available.”
relevant log entries:
!MESSAGE Plug-in “com.genuitec.eclipse.jsf” was unable to instantiate class “com.genuitec.eclipse.jsf.core.JSFCore”.
Caused by: java.lang.NoClassDefFoundError: org/apache/xml/serializer/OutputPropertiesFactory
(I was also getting this when using Workbench 4.1.1 just before I upgraded, but I had successfully added JSF capablility in one previous project a few months ago)
What’s the deal, and how do I correct it?
Thanks
Can you explain in detail how you upgraded? There is no direct upgrade path from 4.1 to 5.0, it’s a full reinstall, so if you did this by unzipping a new copy ontop of an existing one or some other method short of a clean reinstall that would explain why the plugin is failing.
The fastest way to work around an install problem (which this seems to be) is to use our new All-In-One installer for Windows (assuming you are on Windows). It includes the latest stable JDK, Eclipse and MyEclipse, all pre-configured to run with eachother after it’s installed. It’s very handy and is a great/stable starting point for a MyEclipse install if you are running into trouble.
Also since all your preferences and information is stored in your workspace, it’s usually just an issue of installing to a new dir using the installer, then reopening your existing workspace and you are all set.
I don’t consider this an upgrade or installation issue because I was having the same problem and getting the same error before I upgraded.
While using 4.1.1 I was able to add JSF capabilities, then I wasn’t (a couple of months later); and then I upgraded (hoping that it would take care of the issue, but alas, it didn’t).
GP
I want to clarify that using the All-In-One installer to a brand new directory isn’t meant to invalid your previous efforts or anything like that. The idea is to get an install that we know works, installed and then to open your project with it. If you are still having problems then the issue may lie in the Project, or more likely, the Workspace. At which point our methods for troubleshooting those issues can be different.
It’s just the fastest way for me to remotely provide you a way to get a best-case scenario setup while removing all the possible variables in the equation that can cause things to go south on us.
I did a clean re-install. The new workbench is associated with Eclipse 3.2.
I’m using the old workspace except that I deleted the JasperAssistant samples project before re-installing.
But the re-install did not resolve the issue.
I’ll create a clean workspace tomorrow and see what happens.
GP
GP,
Did you use the FullStack “All-In-One” installer that is about 270MB from our download area to perform the reinstall and then use the shortcuts it created to launch the install? I’m asking because of the “the new workbench is associated with Eclipse 3.2” made me think you possibly did another manual install with your own copies of things and I wanted to be absolutely sure of all the details** I’m cautious to a fault because doing this for enough years, I’ve spent almost a week before helping users with a problem that in the end turned out to be nothing more than the tiniest little detail.
No, I had installed Eclipse separately.
I’ll go back and do the “full stack” install.
I didn’t really think that would make a difference (I’ve always done it that way), but I understand the concept of controlling the variables.
Thanks
GP
No, I had installed Eclipse separately.
I’ll go back and do the “full stack” install.
I didn’t really think that would make a difference (I’ve always done it that way), but I understand the concept of controlling the variables.
Thanks
GP
Well that did it (and I was able to keep my old workspace).
Shouldn’t the standalone work with Eclipse 3.2, however?
Thanks for your help
GP
GP,
Yes you are right the standalone install can work with Eclipse 3.2.1 (Our 5.1 release is based on Eclipse 3.2.1, if you were installing it against 3.2.0 it’s possible for some weirdness to ensue). Using the full stack just allowed us to get everything into a “known” configuration. Thank you for doing that, I’m glad it’s working now.
