I saw a document today, which provides an example using the Derby database. The development tool is eclipse (3.3.0) and myeclipse (6.0) is used in the project. In order to see its functions, I configured the environment and found several error-prone problems. First, copy the Derby plug-in to the myeclipse plugins package, and then open mylipse IN THE myeclipse directory. ini configuration file:
-Showsplash
Com. genuitec. myeclipse. Product
-- Launcher. xxmaxpermsize
256 m
-Vmargs
-Dosgi. requiredjavaversion = 1.5
-Xms128m
-Xmx512m
-Dosgi. splashlocation = E:/myeclipse 6.0.0 m1/Eclipse/myeclipsesplash.bmp
-Duser. language = EN
-XX: permsize = 128 m
-XX: maxpermsize = 256 m
Add-clean under mb. Note that I added it to MB at the beginning, but I restarted several times of myeclipse, which means I couldn't add it. Then I added it below, I haven't figured it out yet. I hope you can give me some advice! After configuration, restart myeclipse and right-click the project. If the Apache Derby option is displayed, the configuration is successful! Then load it into the project. During running, note that you must first start Tomcat of myeclipse before starting the Derby database, because myeclipse is more aggressive, I always think that I am the first connection to start. If I start the Derby database first, myeclipse Tomcat will not start!
In addition, if it is eclipse, the configuration is basically the same, that is, when running the project, you can start the Derby database and eclipse tomcat in no particular order, because the eclipse Tomcat does not seize the first connection!
Note that the preceding configuration is very important. After you click the myeclipse shortcut, an English prompt is displayed indicating that Java cannot create a VM. This is a shortcut. Click C: /program files/myeclipse 6.0/eclipse to enter the eclipse shortcut.
This article is transferred from
Http://www.javaeye.com/topic/150571