For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 3 replies, 2 voices, and was last updated 21 years, 8 months ago by
Riyad Kalla.
-
AuthorPosts
-
gogineniMemberHI,
I am getting an invocationtargetexception when I try to save/apply the xdoclet properties. I have seen the 2 mail threads regarding the same one but neither of those applied in my case. I.e. I DONT have any other plugins other than MYECLIPSE. Also My JDK is being set correctly through the VM properties or directly through Java_Home.
The below is my system information:
– What operating system and version: Windows 2000 5.00.2195 Service Pack 4
– What Eclipse version and build id are you using? 2.1.2 BuildID: 200311030802
– Was Eclipse freshly installed for MyEclipse? yes
– Are any other external plugins installed? no
– How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.* 7– What MyEclipse version are you using?
– What JDK version are you using to run Eclipse? Tried 1.3.1_08 as well as 1.4.2 (1.4.2 was a new install just in case 1.3.1 was corrupted)– What JDK version are you using to launch your application server? – Havent yet launched the appserver
– What steps did you take that resulted in the issue? Created a Session Bean using the wizard. added 1 business method. Went to Project>>Properties>>MyEclipse-XDoclet & configured it. Clicked on OK button. A dialog saying invocationtargetexception came up
What application server are you using? havent started using any yet but planning to use JBOSS
-Are there any errors in the Eclipse log? (<workspace>/.metadata/.log)
!MESSAGE Internal Error
!STACK 0
javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: java.net.MalformedURLException: unknown protocol: c
at org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:805)
at org.jboss.ide.eclipse.xdoclet.run.configuration.ProjectConfigurations$1.run(ProjectConfigurations.java:160)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
———
javax.xml.transform.Trans[/b]June 2, 2004 at 2:35 pm #207815
Riyad KallaMembergogineni,
This does look like it might be an issue with supplemental XML libraries used by the JDK. Can you check the jre/lib/ext/ directory under each of your JDK installations, probably something like:c:\jdk1.3.1_08\jre\lib\ext AND c:\j2sdk1.4.2_04\jre\lib\extand tell us if there are any files in there? If so, what are they?
Also when you said you are sure you are running Eclipse with the correct VM, what command line are you using to launch Eclipse, and also what does Help > About > Configuration Details say you are running?
June 2, 2004 at 2:48 pm #207818
gogineniMemberHi,
Thanks for your help! Im not quite certain how I fixed it but it seems to be fixed now. See below for changes made.
INFO FOR TRACKING BUG:
Nothing under the ext folders for either 1.3.1_08 or 1.4.2(a) I was setting JAVA_HOME to 1.3.8
(b) I read somewhere that you can override this by setting the -vm option so I downloaded 1.4 & tried to use
“eclipse.exe -vm C:\j2sdk1.4.2\bin\java” to force it to use 1.4STEPS THAT SEEM TO HAVE FIXED IT:
The changes made included the following – even though I had set jdk1.4 in my java home the project itself was using JRE from 1.3 I guess it still holds on to the old settings I changed this to JRE1.4 for each of my project modules.
Another change I made was in the XDOCLET properties dialog I wasnt selecting the top level “ejbdoclet” checkbox but choosing only some of the ones below that. If I Selected the toplevel (& deselected some of the things that I dont require) it works fine now.
Pratima
June 2, 2004 at 3:45 pm #207822
Riyad KallaMemberPratima,
Thank you for closing the loop with us, I believe this was a JDK issue that you got worked out when you cleaned up all your JRE settings and updated all your project settings. The only other times we’ve seen this error is when someone has an older JDK, or has played with their ext dir and placed different versions of the Xalan (or Xerces) libraries.Nice job figure out how to fix it!
-
AuthorPosts
