使用NetBeans6.1 进行Spring RCP开发!【转载】
? NetBeans 现在是越来越强大了! 今天又看到了 Geertjan Wielenga 写的一篇关于如何开始开发SpringRCP
?的文章感觉非常的棒,于是就把它给转载过来了!呵呵! 英文太多了,也就没有翻译了!大家就凑合这看吧,
图文并茂的,我想大家应该不会觉得难了吧! ? (不知道这篇文章能否发到论坛里,让大家讨论一下关于在NetBeans下开发SpringRCP ,如果不行就麻烦管理员将这个帖子删除了吧!顺便通知一声,下次就不再发到论坛来了.谢谢!)
PS: 原来SpringRCP的开发这么好玩啊!
插件下载? NetBeans Spring RCP 插件
原文连接:http://java.dzone.com/news/spring-rcp-tutorial?page=0%2C0
作者: Geertjan Wielenga
?Let's familiarize ourselves with the Spring RCP.New life seems to have been blowing into this project: after almost twoyears of hiatus, the 1.0.0 release came out a few months ago. Let'sleave aside the question about its direction and so on and, instead,let's look purely at the technology itself to see exactly what itoffers. In that light, I've made available a simple plugin for NetBeansIDE that provides samples and templates to get things started. Below, Iwalk through a basic scenario using the plugin. However, even those whoare not NetBeans users could learn a lot about Spring RCP by readingthe steps in this tutorial and the explanations that accompany them.
Table of Contents
Getting Started Creating a View Adding Customer Data Adding Docking Views Enabling Actions Adding Context Sensitivity Changing the Look & Feel Getting StartedInstall the Spring RCP Tooling plugin into NetBeans IDE 6.1.
In the New Project wizard (Ctrl-Shift-N), you will find a new project template:
A brief overview of the files that you see above:
File ExplanationSimpleApp.java
Provides the application's "main" method and launches the application
via the Spring RCP "ApplicationLauncher" class. That class loads the
application context XML file and the startup context XML file, where application-level concerns such as the splash screen, initialization sequences, and views are defined. SimpleLifecycleAdvisor.java Provides lifecycle management for the application. This class is
registered in the application context XML file. It provides methods such
as "onWindowOpened" and "onCommandsCreated", so that you have
entry points to customize what happens when the application starts. (For example, you can adjust the application's size in the "onPreWindowOpen" method.)richclient-application-context.xml Provides the application context XML file, which configures the Spring RCP
components and services.
richclient-startup-context.xml Provides the startup context XML file, which defines the splash screen, but could define anything that you want to have happen specifically at startup.
images.properties Provides the image resource. It is registered in the application context
XML file.
splash-screen.jpg Provides the splash screen image that is used in the startup context XML
file.
commands-context.xml Provides the application's commands, organized within menu bars and toolbars, and the items within them. This file is declared in the application context XML file.
messages.properties Provides the display texts in a centralized location. For example, texts for titles and descriptions are found here.
Note: The template also put most of the Spring RCP JARs on your application's classpath. Look in the Libraries node to see which ones are there. Potentially, more JARs could be included in the plugin as the complexity of the provided tooling increases.
?
Creating a ViewNow we will create a new window in our application.
- Right-click the project node and choose New | Spring View, as shown here:
???
?import?javax.swing.JComponent;??
?import?javax.swing.JPanel;??
?import?org.springframework.richclient.application.support.AbstractView;??
????
???public?class?CustomerView?extends?AbstractView?{??
???
?????@Override??
?????protected?JComponent?createControl()?{??
??????????JPanel?panel?=?new?JPanel();??
??????????return?panel;??
?????}??
?}
Open the richclient-application-context.xml file. At the end of thefile, notice that your view has been automatically registered for youas follows:
????????????<property?name="viewClass"?value="simple.CustomerView"></property>??
??</bean>?
Finally, open ui/messages.properties and notice the new entry for the menu item that will open the view:
? 4 . Run the application and go to Window | Show View, from where you can open the new Customer View:
??
? 5.? Let's make our new view open by default wheneverthe application starts. In other words, our Customer View will be theapplication's initial view. To do that, open therichclient-application-context.xml file and find the bean that has"lifecycleAdvisor" as its "id" attribute. Add this property to thatbean's list of properties:<!---->
<!----><property?name="startingPageId"?value="CustomerView"?/>Notice that the "name" attribute can be completed automatically ifyou call up code completion (which is Ctrl-Space, by default):
Therefore, the whole bean definition is now as follows:
<!----><bean?id="lifecycleAdvisor"?class="simple.SimpleLifecycleAdvisor">????<property?name="startingPageId"?value="CustomerView"?/>
????<property?name="windowCommandBarDefinitions"?value="ui/commands-context.xml"?/>
????<property?name="windowCommandManagerBeanName"?value="windowCommandManager"?/>
????<property?name="menubarBeanName"?value="menuBar"?/>
????<property?name="toolbarBeanName"?value="toolBar"?/>
</bean>
?6 . Run the application again and notice that the Customer View now appears when the application starts.?
Adding Customer DataNext, we'll use our new Spring View to display customer data to ourusers. Nothing in this section is specific to Spring RCP. Nothing morethan its seamless integration with standard Swing development isdemonstrated below, together with the related benefit of being able touse the associated development tools provided by NetBeans IDE. We'lluse one of the databases bundled with the IDE, but we could be usingany database at all.
- Right-click the project node and choose New | JPanel Form. Name the panel "CustomerPanel" and choose "simple" in the package drop-down so that your panel will be created in the same package as where the other classes are found. Click Finish. Open "CustomerView.java". Change the line that instantiates the JPanel so that your new CustomerPanel is created instead:<!---->public?class?CustomerView?extends?AbstractView?{
????@Override
????protected?JComponent?createControl()?{
????????JPanel?panel?=?new?CustomerPanel();
????????return?panel;
????}
}
Now, whenever you run the application, the CustomerPanel will define the initial view.
Open the Services window (Ctrl-5). In the Services window, expand the Databases node, right-click the jdbc:derby node, and choose Connect. The IDE now connects to its bundled Derby database. Expand the jdbc:derby node, expand the Tables node, and notice that there is a table called "CUSTOMER". That's the table we'll show in our application. Open the CustomerPanel in Design mode. Next, drag and drop a table from the Palette onto the CustomerPanel's Design view. Finally, drag and drop the CUSTOMER node onto the table. You should now see this:
Note: Make sure that you click the two arrow buttons on the top right of the screenshot above. Doing that will result in the JTable resizing automatically at runtime, to fit snugly into the size of the JPanel.
The related JAR files should automatically be added to your project. If they're not and you see a lot of error messages in the generated code, right-click the Libraries node, choose Add Library, and then add "Beans Binding" and "TopLink Essentials", as well as "derbyclient.jar" from your JDK's db/lib folder. Back in the Projects window, you should see that JPA-related artifacts have been added to your project:
?
Adding Docking ViewsAt the moment, we only have one view (i.e., one window). One of thecentral reasons for desktop developers choosing to use an RCP is theneed for a windowing system. As soon as a desktop application startsbecoming non-trivial, you need to be able to deal with multiplewindows. More than simply showing multiple windows, you alsoneed to provide functionality for maximizing and minimizing them, foropening and closing them, for docking and undocking them. Not much funto code all of that. Let's see how Spring RCP can help us with thisbasic requirement.
- First, we need to add a new view, so that we have two windows. Use the Spring View template, as described earlier in this tutorial, and add a new view with whatever name you like, in the same package as before (or anywhere else). As before, the view is registered for you in the richclient-application-context.xml file, as well as in the messages.properties file. When you run the application, you'll have two menu items under Window | Show View. On selection, the second view replaces the first view, and vice versa. That's not docking, that's replacing. So let's now change that so that both are displayed at the same time, i.e., so that both windows dock within the Spring RCP. Begin by adding this bean to the richclient-application-context.xml file:
?
<!----><bean?id="applicationPageFactory"?depends-on="serviceLocator"??????class="org.springframework.richclient.application.docking.vldocking.VLDockingApplicationPageFactory">
</bean>
? 4. Run the application. When you open both views, you should see the following:
?5 . Next, find the beans that declare the two views and changethe class that they use in the richclient-application-context.xml tothe following:
????? org.springframework.richclient.application.docking.vldocking.VLDockingViewDescriptor
So now the bean for the Customer View should be as follows, while the same should be true for the other view you created:
<!----><bean?id="CustomerView"?class="org.springframework.richclient.application.docking.vldocking.VLDockingViewDescriptor">????<property?name="viewClass"?value="simple.CustomerView"?/>
</bean>
?6 . Let's now look more carefully at how our views are defined. Find theCustomerView bean, place the cursor at the start of the propertyelement's "name" attribute's value, and call up code completion(Ctrl-Space). You should now see the list of possible values displayed:
??? Go ahead and take a whole bunch of those names, specifically, the ones shown below, setting them all to "true":
<!----><bean?id="CustomerView"?class="org.springframework.richclient.application.docking.vldocking.VLDockingViewDescriptor">??
?
?? 7. You can do the same for the other view, depending on which of theproperties above you would like to make available to that particularwindow. The names of the above properties are self explanatory, exceptfor "autoHideEnabled", which will add minimize functionality to yourview.
? 8. Run the application again and notice some small new buttons in the top right of the view:
??? If you right-click inside the title bar, you see the sameoptions, this time as menu items together with the keystroke that can???invoke them:
? 9. Try out a few of those new features in yourapplication. For example, click the "Detach" button and then you'reable to move the whole view out of the application (handy if your userhas multiple monitors, for example), as shown below:
Note: To be able to drag a detached window, your cursor needs to become a hand, which is what happens when you move the mouse over the dotted line at the top of the window's title bar.
10.? Finally, drag the title bar of a view to a positionwhere it could conceivably be dropped and then you will see a shadowwhere it will appear when you release the view:
? 11. Once you have more windows, you can move them around andyou can even end up with tabs, if you drag the window to the correctposition, as shown below:
Note: One thing I haven't been able to figure out is how to save window positions at shutdown. In other words, at startup the user would like to have the window positions be restored to where they were when the application last closed. I don't know how this is handled in Spring RCP. I believe it should be done automatically, which doesn't seem to be the case since the application reverts to its default state when I rerun it.
?
Enabling ActionsLet's now look at the menubar. Several menu items are available bydefault. Where do they come from? Our simple application contains noJava classes that have anything to do with menu items. So, what's goingon here?
Menus and toolbars are all declared in the"command-context.xml" file. That file and its contents, in turn, aredeclared in the "richclient-application-context.xml" file, which is theapplication context XML file that is loaded at startup.
- Open the "richclient-application-context.xml" file and take note of the declaration of the command-context.xml file, as follows:
????<property?name="startingPageId"?value="CustomerView"?/>
????<property?name="windowCommandBarDefinitions"?value="ui/commands-context.xml"?/>
????<property?name="windowCommandManagerBeanName"?value="windowCommandManager"?/>
????<property?name="menubarBeanName"?value="menuBar"?/>
????<property?name="toolbarBeanName"?value="toolBar"?/>
</bean>
?
Note: The menubar and the toolbar are also declared above and are then further spelled out in the "command-context.xml" file.
? 2.? Notice the third line above and then open thatfile, i.e., the commands-context.xml file. Let's start by looking atthe Help menu:
So, the "Help Contents" item is disabled, while the "About" item is enabled. Why?
?3. Look at the "menuBar" bean incommands-context.xml, where you'll find that one of its members is"helpMenu". Hold down the Ctrl key and move your mouse over the"helpMenu" text and you will see a hyperlink:
Click it and you will jump to the "helpMenu" bean, which is defined as follows:
?
<!----><bean?id="helpMenu"???class="org.springframework.richclient.command.CommandGroupFactoryBean">
????<property?name="members">
????????<list>
????????????<value>helpContentsCommand</value>
????????????<value>separator</value>
????????????<ref?bean="aboutCommand"?/>
????????</list>
????</property>
</bean>
??
<bean?id="aboutCommand"?
??class="org.springframework.richclient.command.support.AboutCommand"?/>
?4. Now you can see why the "Help Contents" item is disabled, while the"About" item is enabled. In the first case, only a value has beendeclared, while in the second case there is a reference to a bean, forwhich a class has been defined that handles the invocation of the menuitem. Let's do the same for the "Help Contents" item, starting bycreating a new bean for the "Help Contents" item:
????<property?name="helpSetPath"?value="help/simple-hs.xml"?/>
</bean>
?
Note: We refer above to "help/simple-hs.xml". That's theJavaHelp helpset file that is the entrypoint to our helpset. You couldcreate that by hand, as well as all the files that are needed to set upa JavaHelp helpset. Instead of that, save yourself some time andtrouble by going back to the New Project wizard (Ctrl-Shift-N) and inthe "Samples" category you will find some Spring Rich Client samples.Complete the wizard for one of them and then copy its "help" packageinto the "Resource Packages" node of your own application. Hurray younow have the start of your own helpset.
? 5. Finally, we need to hook the bean up to our helpmenu, replacing the value with a reference to the bean, as shown below,in the same way as is done by default for the About item:
<!----><bean?id="helpMenu"???class="org.springframework.richclient.command.CommandGroupFactoryBean">
????<property?name="members">
????????<list>
????????????<ref?bean="helpContentsCommand"/>
????????????<value>separator</value>
????????????<ref?bean="aboutCommand"?/>
????????</list>
????</property>
</bean>
?6. Run the application and now the "Help Contents" item is enabled.When you click the item, the JavaHelp from the sample appears.
As your application increases in size, fewer actions remain relevantto all views. Not every menu item should be available to every window,for example. This aspect of large applications is referred to as"context sensitivity" or "selection management". Depending on thecurrent context, certain features should be available while otherfeatures are hidden or greyed out or disabled.
So, in this section, we will set things up so that the "New"command is only available if the current view is the Customer view. Ifthe current view is not the Customer view, the "New" menu item andtoolbar button (first button in the toolbar in the two followingscreenshots) will be disabled:
Otherwise, both will be enabled. Below you see the "New" toolbar button enabled because the current view is the Customer view:
To achieve the above result, one simply needs to modify the CustomerView class, as follows:
<!---->public?class?CustomerView?extends?AbstractView?{????/**
?????*?Handler?for?the?"New"?action.
?????*/
????private?ActionCommandExecutor?newContactExecutor?=?new?NewExecutor();
????@Override
????protected?JComponent?createControl()?{
????????JPanel?panel?=?new?CustomerPanel();
????????return?panel;
????}
????/**
?????*?Register?the?local?command?executor?to?be?
?????*?associated?with?named?commands.?This?is?called?by?
?????*?Spring?RCP?prior
?????*?to?making?the?view?visible.
?????*/
????@Override
????protected?void?registerLocalCommandExecutors(PageComponentContext?context)?{
????????context.register("newCommand",?newContactExecutor);
????}
????/**
?????*?Private?inner?class?to?create?a?new?customer.
?????*/
????private?class?NewExecutor?implements?ActionCommandExecutor?{
????????@Override
????????public?void?execute()?{
????????????JOptionPane.showMessageDialog(null,?"new?customer
");????????}
????}
????
}
Notice lines 20-23 in the code above:
<!---->@Override??protected?void?registerLocalCommandExecutors(PageComponentContext?context)?{??
????context.register("newCommand",?newContactExecutor);??
}
Reference is made here to "newCommand". Where's that defined? Asalways, all commands in Spring RCP are defined in "command-context.xml"file. There, note that the "windowCommandManager" bean declares"newCommand", among other commands, under "sharedCommandIds". In eachview, a different target executor could be defined for the samecommand. In the code above, an "ActionCommandExecutor" is defined inthe CustomerView, which produces a JOptionPane with a message as aplaceholder for real code. In the OtherView, there could be a differentway of handling the "newCommand". In other words, though the"newCommand" is globally visible, it is implemented differently perview.
In addition to commands that are defined in"command-context.xml", there are several that are predefined, which youcan simply declare in your code:
As a result, for the view above, the commands declared abovewill be available and implemented as defined in the second argument to"GlobalCommandIds" (all of which are handled by "newContactExecutor",though that's not very likely in real life). Potentially, you couldhave all or some of these displayed as toolbar buttons in the toolbar,assuming you declare the related tags in the "command-context.xml"file. They would be enabled if the view in which they're declared isactive:
...while being disabled in the context of other views:
?
Changing the Look & FeelSince the end result is a standard Swing application, we should beable to change the look and feel. Open the"richclient-application-context.xml" and find the bean that is definedas follows, thanks to the NetBeans project template that created thesource structure used in this tutorial:
<!----><bean?id="lookAndFeelConfigurer"????class="org.springframework.richclient.application.config.JGoodiesLooksConfigurer">
????<property?name="popupDropShadowEnabled"?value="false"?/>
????<property?name="theme">
??????<bean?class="com.jgoodies.looks.plastic.theme.ExperienceBlue"?/>
????</property>
</bean>
Let's change the look and feel to Metal:
????class="javax.swing.plaf.metal.MetalLookAndFeel">
</bean>
?
Now run it again, with this result:
If you remove the bean altogether, you can set the look and feel via the VM option:
-Dswing.defaultlaf=net.sourceforge.napkinlaf.NapkinLookAndFeel
The result, assuming the Napkin look and feel is on your classpath, is then as follows:
There are several other topics that could be discussed in thecontext of Spring RCP. However, the topics discussed so far shouldserve as a pretty good basis and give you an understanding of whatSpring RCP can do for you and how various pieces fit together. At thispoint, you certainly should have enough information to build somepretty solid applications on top of Spring RCP.
It is tempting to attempt to compare Spring RCP with similarofferings in the desktop framework domain. It is also tempting to makevalue judgements. However, that's not the purpose of this article andwill be broached at another point in time.
1 楼 kenlee14 2008-07-01 NetBeans 现在功能真是越来越强大了，据说，NetBeans 6.5发布中还直接包含Groovy/Grails支持呢。从我用过的IDE里面，IDEA应该是对Groovy/Grails支持最到位的IDE。详情可以参考：http://www.javaread.com/article/show/91 2 楼 gml520 2008-07-01 kenlee14 写道NetBeans 现在功能真是越来越强大了，据说，NetBeans 6.5发布中还直接包含Groovy/Grails支持呢。从我用过的IDE里面，IDEA应该是对Groovy/Grails支持最到位的IDE。
详情可以参考：http://www.javaread.com/article/show/91
不要拿收费的工具和免费的工具比! 3 楼 gml520 2008-07-01 你给的那个连接里的一句话:
引用据小道消息，NetBeans 6.5发布中直接包含Groovy / Grails支持
还要小道消息吗?我想这个人一定没有读过 NetBeans的wiki . 4 楼 fxbird 2008-07-05 就是传说中的插件开发？ 5 楼 kldwq2002 2008-11-22 人家辛苦发点东西，不要一上来就跟吃了大粪似的，拿些微不足道的东西在这纠缠。
现在的程序员脑袋里都在想啥？