??xml version="1.0" encoding="utf-8" standalone="yes"?>
]]>
在新建JBoss ServerӞ因ؓ本机上已有Tomcat占用?080端口Q未启动Q,所以将监听端口由默认的8080Ҏ?081Q结果运行服务器后:JBossq程明明正常启动Q根据Console得出Q,但WTP的Servers视图却提C“Timeout waiting for JBOSS 3.2.3 to start. Server did not start after 50000s”,服务器的状态也昄Stopped。但Ҏ默认?080׃切正常。怎么能出q种问题呢?NWTP是通过查询8080有没有JBoss在监听,从而判断JBoss是否启动成功Q强烈怀疑这是一个BugQ不知道在最新版Eclipse和WTP改过来没?img height="19" src="http://www.aygfsteel.com/Emoticons/confused_smile.gif" width="19" border="0" />
PS: 用老版的Eclipse3.1.1来开发也是迫不得Ԍ本来已安装了Callisto最?strong>完整版(Eclipse3.2M5Q,但在J2EE透视图中是看不到EJB目分类Q新建EJB目也抛q个异常Q看Log发现是JFace插g里抛ZNullPointerExceptionQM是做不下MQ不知道q样的Callisto怎么会算MileStoneQ? (
那个50000s应该?0000ms吧,50000s可是13?3分啊Q^_^
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后,d在^台线E等待队列中排队Q等待调度执行?BR>调用方式1Q?/P>
调用方式2Q?/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.
在我们小l的设计中,Plugin和控刉辑是分成两个工E单独开发的QPlugin主要实现界面功能Q通过调用控制逻辑实现数据存储、Blog发布、打印等功能Q所以接触到了制作库插gq个q程Q现在写下来Q希望有点帮助?/P>
如何制作库插Ӟ
库工程转换为Plugin工程Q在MANIFEST.MF的overview里定义IDQ在Runtime里加入你要公开的包QExported PackagesQ。OK
如何使用库插Ӟ主要分ؓ三步Q?BR>1、在Dependencies Tab的Required Plug-ins中加入你的库插gQ保证输出项目时导出相应的库插gQ?BR>2、然后Compute build pathQə目能够利通过~译Q?BR>3、在q行对话框的Plugin Tab里单击Add required pluginsQ这样项目才能正常运?BR>
有一点忘了就会挺郁闷的! RCP Eclipse Plugin
详细的制作Helpq程我就不说了,?A >q里可以扑ֈ?/P>
要注意三个问题:
1、添加的插g要齐全,使用Help要增加以下几个插Ӟ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里添加html文g的信息,使html文g能正导出,如:
bin.includes = plugin.xml,\
*.jar,\
plugin.properties,\
book.xml,\
html/,\
icons/
3、在html文g中不能有中文的链接(昄Zؕ码,服务器会提示找不到该文gQ,所以html和图片的名称量用英文,内容用中文倒没有问题?/P>
可能的原因:今天看Eclipse的RCP Tutorial时注意到Eclipse RCP所需的Plugin最集是org.eclipse.core.runtime和org.eclipse.uiQ又记v昨天使用了PDE的调试功能,所以org.eclipse.debug.coreQorg.eclipse.debug.ui可能是调试时生成的,或者是以前别的目用过出错工程的workspace目录Q生成了一些别的Plugin目录Q而多出的Plugin在Plugin.xml文g里注册的menu在我的程序里没有被添加(或者没有定义对应的MenuPathQ,于是抛ZQInvalid Menu Extension (Path is invalid)
不过q有一个问题:怎么workspace?Plugin文g多w只有org.eclipse.ui.workbench而没有org.eclipse.core.runtimeQ有谁知道这是ؓ什么吗Q?/P>
《Contributing to Eclipse》分为四个@环,W一个@环是W零个@环(hahahaQ?BR>
W零个@环介l了Eclipse的基架构Q然后通过~写一个最单的HelloWorld Plugin带我们走qContributing的大门?/P>
先说说这里列出的比较重要的概念:
Eclipse分ؓ三层QPlatform、JDT、PDE。其中PDE是对JDT的扩展,提供了插件开发支持?/P>
Platform又分Z层:CoreQWorkspace、RuntimeQ、UIQWorkbench、JFace、SWTQ?BR>下面分别介绍一下:
Runtime --- 定义了插件的基础设施。启动时发现所有可用插件ƈ理插g的加载?BR>Workspace --- 理一个或多个目?BR>SWTQStandard Widget ToolkitQ?-- 提供囑Ş昄功能Q定义了一l标准窗体组件?BR>JFace --- 建立在SWT上的一l比较小的UI框架Q提供对常用UId的支持?BR>Workbench --- Eclipse的UI聚合体,核心要素是编辑器、视图(ViewQ和视角QPerspectiveQ?BR>其中视角QPerspectiveQ定义了各工作台部g的可视化排列方式?/P>
All Right. That's how you get it.
Go on, be a tiger.
上software.hit.edu.cn看Flash没有问题Q打开一个Word文档也OKQ应该是内嵌了IE吧?/P>
看了代码也只发现一个setLocation(URL)Q没有跟本地pȝ联系的代码,NSWT里的Browser本n内嵌了IE?/P>
以前也听说过SWT是不用虚拟机的(是吗Q)Q都是调用本地的dllQ只是现在亲眼目睹了?/P>
q不有点像AWT吗?Q?/STRONG>