Problem: Such exception is thrown during code gen(under Windows).
Solution: move the wsdl file to a path without special character(i.e. Document and Settings, Program Files).
Friday, March 13, 2009
Thursday, March 12, 2009
java.lang.reflect.InvocationTargetException at Axis2 Codegen Wizard
Problem: java.lang.reflect.InvocationTargetException
1. An exception is thrown:
2. Identify the errors by
2.1 workspace/.metadata/.log OR
2.2 turn the console log on if there is no file at the above path by running "eclipse -consoleLog"
3. in my case, one of many exceptions is:
Caused by: java.lang.ClassNotFoundException: edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap
...
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
... 60 more
4. Find the missing jars at Axis2_Codegen_Wizard_1.3.0\plugin.xml
5. Mines include:
backport-util-concurrent-3.1.jar
jibx-bind-1.1.5.jar
jibx-run-1.1.5.jar
neethi-2.0.4.jar
woden-1.0M8.jar can't be found anywhere, needs to download the interface and implementations separately and add them to the plugin.xml.
woden-api-1.0M8.jar
woden-impl-dom-1.0M8.jar
woden-impl-om-1.0M8.jar
6. run "eclipse -clean"
7. Voila!
1. An exception is thrown:
2. Identify the errors by
2.1 workspace/.metadata/.log OR
2.2 turn the console log on if there is no file at the above path by running "eclipse -consoleLog"
3. in my case, one of many exceptions is:
...
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
... 60 more
4. Find the missing jars at Axis2_Codegen_Wizard_1.3.0\plugin.xml
5. Mines include:
backport-util-concurrent-3.1.jar
jibx-bind-1.1.5.jar
jibx-run-1.1.5.jar
neethi-2.0.4.jar
woden-1.0M8.jar can't be found anywhere, needs to download the interface and implementations separately and add them to the plugin.xml.
woden-api-1.0M8.jar
woden-impl-dom-1.0M8.jar
woden-impl-om-1.0M8.jar
6. run "eclipse -clean"
7. Voila!
Tuesday, March 10, 2009
A fatal error has occurred while upgrading your device's software. Device communications error encountered.
Problem:
Upgrading the handset OS with Desktop Manager via USB connection, and it crashed.
Then it became unusable: Reload software: 507
Solution(for my case): Don't run anything on the serial/communication ports while upgrading, seems like the RIM software wants to talk to these ports and because they are occupeid, it threw exception.
P.S.: It takes more than 20 minutes for my OS to reboot afterward, be patient!
Upgrading the handset OS with Desktop Manager via USB connection, and it crashed.
Then it became unusable: Reload software: 507
Solution(for my case): Don't run anything on the serial/communication ports while upgrading, seems like the RIM software wants to talk to these ports and because they are occupeid, it threw exception.
P.S.: It takes more than 20 minutes for my OS to reboot afterward, be patient!
Subscribe to:
Posts (Atom)