JBoss-IDE 1.2.2 rapid start:
Preface:
JBoss-IDE is a Plugin in Eclipse, which supports the Eclipse 2.1.x series and Eclipse 3.0.x series, first download and install Eclipse (www.eclipse.org).
Start JBoss
JBoss-IDE allows you to boot the JBoss server more easily and quickly in Eclipse or remote remote control, the main features:
l Configure multiple servers simultaneously.
l Start, turn off or terminate the server in Eclipse or remote remote control
l You can obtain the output information of the console in the server and monitor its log file.
Launcher usage
Press' Windows' -> 'SHOW View' -> 'Server Navigator' by pressing 'Windows' -> Show View' -> 'Other' -> 'Server Navigator'.
Server Navigator is a monitoring and control center, in the lower right corner window of Eclipse. In 'Windows' -> 'Preference' -> 'JBoss IDE', choose 'Launcher', in 'Default Server', the installed JBoss Servo The version of the device.
If you want to put the server in the tool column, in 'Windows' -> 'Customize Perspective' -> 'Other', select 'DEFAULT Server' Press 'OK'.
Configure the server
Eclipse To under the Package Explorer environment, press 'Run' -> 'Debug' in the main menu column, or right click on 'Server Navigator', select 'Configuration'
After that, select the version of the JBoss installed, select 'new', then fill in the setting data of JBoss and JDK, press 'Apply', and then press 'Close'.
If you configure 3.x.x version of JBoss, set up the preset JRE will have a warning, preferably in the JDK.
Demonstrate
If you are using Sun's JDPA (Java Platform Debugger Architecture) in JDWP (Java Debugging Wireless Protocol) in a virtual device running Java, it is the same in the Eclipse, which starts in Eclipse. The insect system is that you have an interface to monitor and control the lifecycle of the application system and the input and output of the console.
Start JBoss in the demonstration environment
In a practical application environment, we will not start the JBoss server with Eclipse, so we have to start, and the details can be referred to JDPA DOC3. Here is Java 1.3.x and 1.4.x to start JBoss 3.x.x
l Java 1.3.x: java -djboss.home = {jboss-home} -classpath {jboss-home} /bin/run.jar -xdebug -xrunjdwp: transfer = dt_socket, server = y, suspend = n, address = 10250 Org.jboss.main
l Java 1.4.x: java -djboss.home = {jboss-home} -classpath {jboss-home} /bin/run.jar-xdebug -xrunjdwp: transport = dt_socket, server = y, suspend = n, address = 10250 Org.jboss.main
Address is just any value.
Servo in the application
Java 1.4 Previously, starting an application system in the demonstration environment is to turn off 'JIT' or 'Hotspot', but there is different after 1.4.
The virtual machine of Java Hotspot [TM] is used to 'full-speed debugging'. In the earlier version of Hotspot, when the insectic environment is turned on, the program can only run in the compiler. Now there is no limit, so It will be easier and faster to go to insects. When setting breakpoints, the editor will be blocked, and the compiler will continue to be responsible for the execution program is still in progress, such as the method to enter / exit, observe points, etc. Java 1.4.1 The Java HotSpot client and server can also support the 'full-speted debugging', while Java 1.4.1 can only support the client.
This is a good news run in the application's server, but the limit is only a demoner can be connected to the demonstorm environment in the server.
XDoclet support
XDoclet Support includes 'Code Assist', 'Template' and 'Variables'
Code Assist
When you write Java, you have enabled 'code assist', you can press 'ctrl-space' button (author press: because the Chinese input switch button in my job system is also 'ctrl-space', So I will use '@' and wait for the 'code assist' automatic pop-up). The 'code assist' will automatically appear in the buoy stop in a valid xDoclet structure. If it is invalid, it will automatically pass to the Eclipse automatic completion process. If the buoy is stopped under a valid xdoclet structure but has not automatically completed the processing part, there will be no matter if there will be a 'beep'. Example can be seen below:
The information you entered will affect the content populated by 'code assist', and the content in 'code assist' will be defined in XDoclet 'xtags.xml', so if there are multiple 'xtags.xml' files inside the content If there is contradictory, it will result in 'code assist' errors.
The value of 'code assist' in the property can be variables. If you want to generate an EJB, JNDI-NAME wants to write in the name of the Class, you can set it in 'code assist', please see the following 'variables 'Part.
Templates
You can define your templates in the main menu column 'Windows' ->' preference '->' jboss-> 'assist' -> 'templates'. Note that the content is applied to different In the conditions, such as methods or classes.
Variables
You can define Variables in the main menu column 'Windows' ->' Preference '->' JBoss-> 'Assist' -> 'Variables'. You can set according to some formulas , But be careful is that your settings will have conflicts with variables in the system.
General setting
JBoss-IDE has a very easy XDoclet setting interface, there may be many automatically generated configuration documents in a project to be set, you can select Enable or deactivate these settings in the XDoclet settings of JBoss-IDE. Look at the figure below example:
To define a setting, click on the window to select 'add' (plus self-setting) or 'add standard' (plus preset settings).
All settings will be converted into an Ant's build document, you can run in Eclipse or outside. Right-click on the project, select 'Run XDoclet':
Encapsulation support
JBoss-IDE packaging support can:
l Set the package setting with the image interface
l Define a sealed or scattered package setting
l Package can include all archives or data clips
l can set the planning of the package
l You can simply select enable or deactivate settings (Check Boxes)
Encapsulation setting
JBoss-IDE has a good interface to set the package settings in the project. A project can have multiple packages settings, and each setting you can simply select or deactivate. The following figure is an example: To define When a setting, pick the 'add archive' (plus self-setting), 'add std. Archive' (plus preset setting), 'add file' or 'add folder', etc. .
All settings will be converted to an Ant's build document, you can run in Eclipse or outside. Implement right-click project, select 'Run Packaging':
Deployment support
JBoss-IDE deployment support can:
l Set the deployment setting with the image interface
l JBoss Insect start settings automatically define the target of the archive system
l Define the user's own settings
l You can simply choose Deploy / Red Deploy / Abandon Deployment
l If there is a decorative image displaying resources that you deploy
Deployment setting
JBoss-IDE has a good interface to set the package settings in the project. In the main menu column 'windows' -> 'preferences' -> 'jboss-idE' -> 'deployer' to set:
To set a deployed goal, you can use the key group on the right hand.
To deploy a resource (such as .ear file), right-click this resource, select 'Deploy to ...', select the target to be deployed, as shown below:
After the deployment is complete, you will see the resource that you will see in Workspace will have a decorative image display, as shown below:
Source:
http://prdownloads.sourceforge.net/jboss/quickstart-1.2.2.pdf?download
