锘??xml version="1.0" encoding="utf-8" standalone="yes"?>
]]>
鍦ㄦ柊寤篔Boss Server鏃訛紝鍥犱負(fù)鏈満涓婂凡鏈塗omcat鍗犵敤浜?080绔彛錛堟湭鍚姩錛夛紝鎵浠ュ皢鐩戝惉绔彛鐢遍粯璁ょ殑8080鏀規(guī)垚浜?081錛岀粨鏋滆繍琛屾湇鍔″櫒鍚庯細(xì)JBoss榪涚▼鏄庢槑姝e父鍚姩錛堟牴鎹瓹onsole寰楀嚭錛夛紝浣哤TP鐨凷ervers瑙嗗浘鍗存彁紺衡淭imeout waiting for JBOSS 3.2.3 to start. Server did not start after 50000s鈥濓紝鏈嶅姟鍣ㄧ殑鐘舵佷篃鏄劇ずStopped銆備絾鏀規(guī)垚榛樿鐨?080灝變竴鍒囨甯搞傛庝箞鑳藉嚭榪欑闂鍛紵闅鵑亾WTP灝辨槸閫氳繃鏌ヨ8080鏈夋病鏈塉Boss鍦ㄧ洃鍚紝浠庤屽垽鏂璊Boss鏄惁鍚姩鎴愬姛錛熷己鐑堟鐤戣繖鏄竴涓狟ug錛屼笉鐭ラ亾鍦ㄦ渶鏂扮増Eclipse鍜學(xué)TP鏀硅繃鏉ユ病鏈?img height="19" src="http://www.tkk7.com/Emoticons/confused_smile.gif" width="19" border="0" />
PS: 鐢ㄨ佺増鐨凟clipse3.1.1鏉ュ紑鍙戜篃鏄揩涓嶅緱宸詫紝鏈潵宸插畨瑁呬簡Callisto鏈鏂?strong>瀹屾暣鐗堬紙Eclipse3.2M5錛夛紝浣嗗湪J2EE閫忚鍥句腑灝辨槸鐪嬩笉鍒癊JB欏圭洰鍒嗙被錛屾柊寤篍JB欏圭洰涔熸姏鍑鴻嫢騫蹭釜寮傚父錛岀湅Log鍙戠幇鏄疛Face鎻掍歡閲屾姏鍑轟簡NullPointerException錛屾諱箣鏄仛涓嶄笅鍘諱簡錛屼笉鐭ラ亾榪欐牱鐨凜allisto鎬庝箞浼?xì)绠桵ileStone錛? (
閭d釜50000s搴旇鏄?0000ms鍚э紝50000s鍙槸13鏃?3鍒嗗晩錛乛_^
There are two traversal shortcuts I use all the time: Ctrl-O and Ctrl-T.
Ctrl-O shows the methods of the class in the current editor in a popup.
Hit Ctrl-O when the popup is up, and you'll see all the inherited
methods as well. This is incredibly useful, as it allows me to bounce
between methods even when I'm not sure which class is implementing
which method.
Ctrl-T shows the type hierarchy of a selected type in a popup. This is the
complement to Ctrl-O. When I'm sure of what
interface I'm looking at, but I really want to pick a particular implementation
and want to go trawling through that
implementation for a bit, Ctrl-T will show me all the subclasses or
implementors for that type.
There is a third option which I haven't used much. Ctrl-F3 shows the
methods of a selected type in a popup. I can see how this can be useful,
but in practice I have a pretty good idea of which methods are attached
to which classes and Ctrl-Space fills most of my needs there.
However, I have been missing a couple of things. These are the shortcuts
I just found recently, and are very good for hitting up random files:
Ctrl-E shows a popup list of all the open files.
Ctrl-Shift-T creates a dialog box that you can use to navigate to any class.
Ctrl-Shift-R creates a dialog box that shows any resource in the project
(basically any file.)
Alternately, there's an Eclipse plugin called GotoFile which seems to behave
a little more "IDEAish".
Finally, I found a plugin which actually integrates Eclipse with Windows!
Eclipse Platform Extensions is actually functional and useful, although
you wouldn't guess it by looking at the website. Although it says that
it provides a "System GC" functionality, it actually does far more,
like provide a "Open in Windows Explorer" and
"Open Command Window here" dialog to the Package Explorer.
You can allow your users to access the help system over the Internet or an intranet, by
installing the infocenter and the documentation plug-ins on a server. Clients view help
by navigating to a URL, and the help system is shown in their web browser. The
infocenter help system can be used both for client applications and for web
applications, either of which can have their help accessed remotely. All features
of help system except infopops and active help are supported.
The infocenter help system allows passing number of options that can be used to
customize various aspects of the infocenter. The following options are supported:
-nl en -locales de en es fr it ja ko pt_BR zh_CN zh_TWwill cause infocenter operating in 10 locales. All other locales will receive content
-vmargs -Xmx256M
increases memory available to the infocenter and will allow serving a larger book collection. These steps are for the help system integrator and are not meant to address all the possible scenarios.
It is assumed that all your documentation is delivered as Eclipse plug-ins and, in general, you are
familiar with the eclipse help system.
The org.eclipse.help.standalone.Infocenter class has a main method that you can use to
launch infocenter from a command line. The command line arguments syntax is:
-command start | shutdown | [-eclipsehome eclipseInstallPath]
[-data instanceArea] [-host helpServerHost] [-locales localeList]
[-port helpServerPort] [-dir rtl] [-noexec] [platform options]
[-vmargs JavaVMarguments]
To start an infocenter on port 8081 issue a start command by running
java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_3.1.0.jar
org.eclipse.help.standalone.Infocenter -command start -eclipsehome
d:\myApp\eclipse -port 8081
To shut the infocenter down issue a shutdown command by running
java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_3.1.0.jar
org.eclipse.help.standalone.Infocenter -command shutdown -eclipsehome
d:\myApp\eclipse
Start the web server. Point a web browser to the path "help" web application running on a port
specified when starting the infocenter. On the machine the infocenter is installed, this would be
http://localhost:8081/help/.
When including infocenter as part of another application, it may be more convenient to start it
and stop using Java APIs instead of using system commands. Follow the steps if it is the case:
String[] options = new String[] { "-eclipsehome", "d:\\myApp\\eclipse" ,
"-port", "8081" };
Infocenter infocenter = new Help(options);
helpSystem.start();
To shut the infocenter down:
helpSystem.shutdown();
Eclipse contains a complete infocenter and does not require other server software to run.
However, in unsecure environment like Internet, it is recommended infocenter is not accessed
directly by clients, but is made available through an HTTP server or an application server.
Most servers come with modules or servlets for delegating certain request to other web
resources. For example, one may configure a proxy module of Apache HTTP Server to
redirect requests made to http://mycompany.com/myproduct/infocenter to
http://internalserver:8081/help that runs an infocenter. Adding the lines
LoadModule proxy_module modules/ApacheModuleProxy.dll ProxyPass /myproduct/infocenter http://internalserver:8081/help ProxyPassReverse /myproduct/infocenter http://internalserver:8081/helpto conf/httpd.conf file of Apache server running mycompany web site accomplishes this.
Some versions of Apache HTTP server, may contain AddDefaultCharset directive enabled in
configuration file. Remove the directive or replace with
AddDefaultCharset Offto have browsers display documents using correct character set.
Multiple instances of infocenter can be run on a machine from one installation. Each started
instance must use its own port and be provided with a workspace, hence -port
and -data
options must be specified. The instances can serve documentation from different set of plug-ins,
by providing a valid platform configuration with -configuration
option.
If -configuration
is not used and configuration directory is shared among multiple infocenter
instances, with overlapping set of locales, it must be ensured that all search indexes are created
by one infocenter instance before another instance is started. Indexes are saved in the configuration
directory, and write access is not synchronized across infocenter processes.
The infocenter does not require the entire Eclipse Platform package. It is possible to run the
infocenter with the following plug-ins (located in the eclipse\plugins directory):
org.apache.lucene
org.eclipse.core.runtime
org.eclipse.help
org.eclipse.help.appserver
org.eclipse.help.base
org.eclipse.help.webapp
org.eclipse.osgi
org.eclipse.tomcat
org.eclipse.update.configurator
Some documentation plug-ins may have dependencies on other plug-ins, usually by specifying required
plug-ins in their plugin.xml. The dependent plug-ins need to be installed on the infocenter as well.
Additionally, plug-ins that were designed for earlier than 3.0 version of Eclipse implicitly require an org.eclipse.core.runtime.compatibility
being present plug-in to work.
Infocenter plug-ins can be updated without restarting the infocenter, using commands explained
in Updating a running infocenter from command line topic. To use this functionality, the minimal
set of plug-ins must include org.eclipse.update.core
plug-in.
See Help System Preferences for more information on customizing help system.
schedule鍚庯紝浠誨姟鍦ㄥ鉤鍙扮嚎紼嬬瓑寰呴槦鍒椾腑鎺掗槦錛岀瓑寰呰皟搴︽墽琛屻?BR>璋冪敤鏂瑰紡1錛?/P>
璋冪敤鏂瑰紡2錛?/P>
To do this right click the project in Package Explorer or Navigator view and got to either Java Code Style or Java Compiler options. Check the Enable project specific settings.
This will create a .settings folder in the project root. Eclipse will add and maintain the project specific configuration in this folder. Commit this folder to the version control. Thats it. Now the project settings are shared with the team. When the other team members synchronize with the repository they will get the project settings too. Any team member can update and check in the settings. Cool!
This code is a simple SWT wizard page. The most interesting characteristic of this class is in the handleBrowse method. This method uses Eclipse's ContainerSelectionDialog for displaying the folders in the workspace.
鍦ㄦ垜浠皬緇勭殑璁捐涓紝Plugin鍜屾帶鍒墮昏緫鏄垎鎴愪袱涓伐紼嬪崟鐙紑鍙戠殑錛孭lugin涓昏瀹炵幇鐣岄潰鍔熻兘錛岄氳繃璋冪敤鎺у埗閫昏緫瀹炵幇鏁版嵁瀛樺偍銆丅log鍙戝竷銆佹墦鍗扮瓑鍔熻兘錛屾墍浠ユ帴瑙﹀埌浜嗗埗浣滃簱鎻掍歡榪欎釜榪囩▼錛岀幇鍦ㄥ啓涓嬫潵錛屽笇鏈涙湁鐐瑰府鍔┿?/P>
濡備綍鍒朵綔搴撴彃浠訛細(xì)
灝嗗簱宸ョ▼杞崲涓篜lugin宸ョ▼錛屽湪MANIFEST.MF鐨刼verview閲屽畾涔塈D錛屽湪Runtime閲屽姞鍏ヤ綘瑕佸叕寮鐨勫寘錛圗xported Packages錛夈侽K
濡備綍浣跨敤搴撴彃浠訛紝涓昏鍒嗕負(fù)涓夋錛?BR>1銆佸湪Dependencies Tab鐨凴equired Plug-ins涓姞鍏ヤ綘鐨勫簱鎻掍歡錛堜繚璇佽緭鍑洪」鐩椂瀵煎嚭鐩稿簲鐨勫簱鎻掍歡錛?BR>2銆佺劧鍚嶤ompute build path錛堜嬌欏圭洰鑳藉欏哄埄閫氳繃緙栬瘧錛?BR>3銆佸湪榪愯瀵硅瘽妗嗙殑Plugin Tab閲屽崟鍑籄dd required plugins錛岃繖鏍烽」鐩墠鑳芥甯歌繍琛?BR>
鏈変竴鐐瑰繕浜嗗氨浼?xì)鎸洪儊闂风殑锛?BR> RCP Eclipse Plugin
璇︾粏鐨勫埗浣淗elp榪囩▼鎴戝氨涓嶈浜嗭紝鍦?A >榪欓噷鍙互鎵懼埌銆?/P>
瑕佹敞鎰忎笁涓棶棰橈細(xì)
1銆佹坊鍔犵殑鎻掍歡瑕侀綈鍏紝浣跨敤Help瑕佸鍔犱互涓嬪嚑涓彃浠訛細(xì)org.apache.ant
org.apache.lucene
org.eclipse.help.appserver
org.eclipse.help.base
org.eclipse.help.ui
org.eclipse.help.webapp
org.eclipse.tomcat
2銆佸湪Build閲屾坊鍔爃tml鏂囦歡鐨勪俊鎭紝浣縣tml鏂囦歡鑳芥紜鍑猴紝濡傦細(xì)
bin.includes = plugin.xml,\
*.jar,\
plugin.properties,\
book.xml,\
html/,\
icons/
3銆佸湪html鏂囦歡涓笉鑳芥湁涓枃鐨勯摼鎺ワ紙鏄劇ず涓轟貢鐮侊紝鏈嶅姟鍣ㄤ細(xì)鎻愮ず鎵句笉鍒拌鏂囦歡錛夛紝鎵浠tml鍜屽浘鐗囩殑鍚嶇О灝介噺鐢ㄨ嫳鏂囷紝鍐呭鐢ㄤ腑鏂囧掓病鏈夐棶棰樸?/P>
鍙兘鐨勫師鍥狅細(xì)浠婂ぉ鐪婨clipse鐨凴CP Tutorial鏃舵敞鎰忓埌Eclipse RCP鎵闇鐨凱lugin鏈灝忛泦鏄痮rg.eclipse.core.runtime鍜宱rg.eclipse.ui錛屽張璁拌搗鏄ㄥぉ浣跨敤浜哖DE鐨勮皟璇曞姛鑳斤紝鎵浠rg.eclipse.debug.core錛宱rg.eclipse.debug.ui鍙兘鏄皟璇曟椂鐢熸垚鐨勶紝鎴栬呮槸浠ュ墠鍒殑欏圭洰鐢ㄨ繃鍑洪敊宸ョ▼鐨剋orkspace鐩綍錛岀敓鎴愪簡涓浜涘埆鐨凱lugin鐩綍錛岃屽鍑虹殑Plugin鍦≒lugin.xml鏂囦歡閲屾敞鍐岀殑menu鍦ㄦ垜鐨勭▼搴忛噷娌℃湁琚坊鍔狅紙鎴栬呮病鏈夊畾涔夊搴旂殑MenuPath錛夛紝浜庢槸灝辨姏鍑轟簡錛欼nvalid Menu Extension (Path is invalid)
涓嶈繃榪樻湁涓涓棶棰橈細(xì)鎬庝箞workspace鐨?Plugin鏂囦歡澶歸噷鍙湁org.eclipse.ui.workbench鑰屾病鏈塷rg.eclipse.core.runtime錛屾湁璋佺煡閬撹繖鏄負(fù)浠涔堝悧錛?/P>
銆奀ontributing to Eclipse銆嬪垎涓哄洓涓驚鐜紝絎竴涓驚鐜槸絎浂涓驚鐜紙hahaha錛夈?BR>
絎浂涓驚鐜粙緇嶄簡Eclipse鐨勫熀紜鏋舵瀯錛岀劧鍚庨氳繃緙栧啓涓涓渶綆鍗曠殑HelloWorld Plugin甯︽垜浠蛋榪汣ontributing鐨勫ぇ闂ㄣ?/P>
鍏堣璇磋繖閲屽垪鍑虹殑姣旇緝閲嶈鐨勬蹇碉細(xì)
Eclipse鍒嗕負(fù)涓夊眰錛歅latform銆丣DT銆丳DE銆傚叾涓璓DE鏄JDT鐨勬墿灞曪紝鎻愪緵浜嗘彃浠跺紑鍙戞敮鎸併?/P>
Platform鍙堝垎涓轟袱灞傦細(xì)Core錛圵orkspace銆丷untime錛夈乁I錛圵orkbench銆丣Face銆丼WT錛夈?BR>涓嬮潰鍒嗗埆浠嬬粛涓涓嬶細(xì)
Runtime --- 瀹氫箟浜嗘彃浠剁殑鍩虹璁炬柦銆傚惎鍔ㄦ椂鍙戠幇鎵鏈夊彲鐢ㄦ彃浠跺茍綆$悊鎻掍歡鐨勫姞杞姐?BR>Workspace --- 綆$悊涓涓垨澶氫釜欏剁駭欏圭洰銆?BR>SWT錛圫tandard Widget Toolkit錛?-- 鎻愪緵鍥懼艦鏄劇ず鍔熻兘錛屽畾涔変簡涓緇勬爣鍑嗙獥浣撶粍浠躲?BR>JFace --- 寤虹珛鍦⊿WT涓婄殑涓緇勬瘮杈冨皬鐨刄I妗嗘灦錛屾彁渚涘甯哥敤UI浠誨姟鐨勬敮鎸併?BR>Workbench --- Eclipse鐨刄I鑱氬悎浣擄紝鏍稿績瑕佺礌鏄紪杈戝櫒銆佽鍥撅紙View錛夊拰瑙嗚錛圥erspective錛夈?BR>鍏朵腑瑙嗚錛圥erspective錛夊畾涔変簡鍚勫伐浣滃彴閮ㄤ歡鐨勫彲瑙嗗寲鎺掑垪鏂瑰紡銆?/P>
All Right. That's how you get it.
Go on, be a tiger.
涓妔oftware.hit.edu.cn鐪婩lash娌℃湁闂錛屾墦寮涓涓猈ord鏂囨。涔烵K錛屽簲璇ユ槸鍐呭祵浜咺E鍚с?/P>
鐪嬩簡浠g爜涔熷彧鍙戠幇涓涓猻etLocation(URL)錛屾病鏈夎窡鏈湴緋葷粺鑱旂郴鐨勪唬鐮侊紝闅鵑亾SWT閲岀殑Browser鏈韓灝卞唴宓屼簡IE銆?/P>
浠ュ墠涔熷惉璇磋繃SWT鏄笉鐢ㄨ櫄鎷熸満鐨勶紙鏄悧錛燂級(jí)錛岄兘鏄皟鐢ㄦ湰鍦扮殑dll錛屽彧鏄幇鍦ㄤ翰鐪肩洰鐫逛簡銆?/P>
榪欎笉鏈夌偣鍍廇WT鍚楋紵錛?/STRONG>