For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 14 replies, 7 voices, and was last updated 21 years, 9 months ago by
Riyad Kalla.
-
AuthorPosts
-
weetabixMemberHi there
Does anyone faced a “java.lang.reflect.InvocationTargetException” while trying to save the MyEclipse-XDoclet properties of an EJB Module Project ?
See Eclipse’s error log below…
[Eclipse2.1.1 + MyEclipse2.7RC2]
Thanx
—
Franck!ENTRY org.jboss.ide.eclipse.xdoclet.ui 4 0 janv. 14, 2004 17:57:16.265 !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) .....January 14, 2004 at 6:02 pm #201858
Scott AndersonParticipantThis is caused by a problem in the XML environment of the JDK used
to run Eclipse. Have you used the ‘endorsed’ dirs mechanism of the JDK?
Can you please post your full configuration?January 15, 2004 at 2:53 am #201882
weetabixMemberScott,
Eclipse is currently configured to run with the JRE included in Sun JDK v1.3.1_08.
Actually, the suprising thing is that MyEclipse’s XDoclet configuration used to work with v2.6.4.
The “java.lang.reflect.InvocationTargetException” appeared right after an upgrade of MyEclipse to v2.7RC2 (in order to test Struts wizards).[BTW, Struts supports looks great]
This is the only thing that have changed on my Java environment…
Any help is welcome 🙂
—
FranckJanuary 15, 2004 at 5:52 pm #201950
Scott AndersonParticipantFrank,
Can you try running Eclipse with JDK 1.4.1/2 to see if that resolves the issue? All problems like
this that we’ve seen in the past have been due to errors in JDK 1.3.1’s XML libraries. The new
Struts stuff makes extensive use of XML / XSLT so it may be aggravating a bug that 2.6.4 did not.BTW, Struts supports looks great
Thanks alot. The team has been working really hard on it. 🙂
January 19, 2004 at 6:05 am #202068
weetabixMemberIn order to sort things out, i have tryed the following :
– new Eclipse installation (still running with the JRE included in Sun JDK v1.3.1_08)
– no additionnal plugins
– new MyEclipse2.7RC2 installationGuess what ? It worked.
So, i came to conclusion that MyEclipse2.7RC2 is a bit un-compatible with some of the plugin I was using (In particular, EasyStruts & Lomboz).—
FranckJanuary 19, 2004 at 7:08 am #202075
Riyad KallaMemberYou were upsetting the MyEclipse environment when it saw you had competing plugins installed 😉
January 24, 2004 at 2:01 pm #202411
mdebruijnMemberI’ve got the same problem. I’m running Eclipse 2.1.2 with MyEclipse 2.7RC2 with no additional plugins installed.
I’ve tried and JDK 1.3.1 and JDK 1.4.1_05 but with no success.
Output of eclipse log file:java.net.MalformedURLException: unknown protocol: e at java.net.URL.<init>(Unknown Source) at java.net.URL.<init>(Unknown Source) at java.net.URL.<init>(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.startDocumentEntity(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl.setInputSource(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:972) at org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:788) 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)Why is org.jboss included? I’m not using JBoss and did not configure something for JBoss?
January 24, 2004 at 2:35 pm #202412
Riyad KallaMemberI believe this is because the xdoclet functionality comes from the jbosside plugin that has been integrated into MyEclipse. Can you explain what you are doing when this error occurs? Does this thread help?
https://www.genuitec.com/forums/topic/unable-to-run-xdoclet-configuration/&highlight=xdoclet+runJanuary 25, 2004 at 6:22 am #202417
mdebruijnMemberThe InvocationTargetExecption occurs after press the ‘Apply’ button on the screen where you can change the MyEclipse-XDoclet properties in the project properties screen. I’ve added the Standard EJB config.
January 25, 2004 at 6:34 am #202418
mdebruijnMemberThe problem occurs because I was switching to an other JDK in the wrong way. I selected an other JDK in the Eclipse preferences dialog but of cause I had to change the JDK before starting Eclipse.
January 25, 2004 at 9:04 am #202420
Riyad KallaMemberSo everything is working for you now?
February 5, 2004 at 12:22 pm #202950
mymytempMemberi am having the same problem when i save the configuration. please help.
jdk 1.3.10
eclipse 2.1.2 and no other pluginFebruary 5, 2004 at 8:40 pm #202980
support-michaelKeymasterCan you post a segment of your Eclipse log file relating to this problem?
August 8, 2004 at 8:37 pm #211675
bmy78MemberHi! I’m having the same problem that’s being described in this thread. I’m running Eclipse 2.1.3 and MyEclipse 2.7.101. I right-click on my EJB project, click on “Properties”, go to “MyEclipse-XDoclet”, add “Standard EJB”, then under “ejbdoclet” I add “JBoss”, select a few properties, and when I hit Apply or Ok I get an InvocationTargetException.
Window->Preferences->Java->Installed JREs points to C:\j2sdk1.4.2_04 and Window->Preferences->MyEclipse->JBoss 3->JDK also points to the same JDK.
I can’t seem to figure this one out. Can anyone help me out?
Thanks.
August 8, 2004 at 11:33 pm #211676
Riyad KallaMemberbmy78,
Can you post the exact exception from your log file? The InvocationException problem was fixed in later builds (I believe the Beta 1 build), but I want to make sure that is the error you are getting instead of something else. -
AuthorPosts
