Eclipse Quick EJB - 1. Lomboz + JBoss-IDE Configuration 2

xiaoxiao2021-03-06 14

Connected article http://blog.9cbs.net/javamxj/archive/2005/01/13/251982.aspx II, develop a Hello instance

For the diagram of Lomboz, please refer to my previous article, not more here.

1. New project

● Right-click on the blank of "Pack Explorer", select "New" in the pop-up menu -> "Lomboz J2EE Project"

· Project Name: Helloejb

· EJB MODULES: HELLOEJB

· Targeted Server: JBoss 4.0.0

The effect is as follows: (Using the small down triangle button in the picture below will filter the introduced JBoss library file)

2. Modifications to XDoclet.xml:

Open Build.xml and XDoclet.xml, take a closer look.

If you have seen an article about xdoclet, you should compare Lomboz development of EJB operation. In fact, Ant XDoclet, focus on xDoclet.xml files.

XDoclet.xml

xml

Version = "1.0"

Www.eteration.com

Project name =

XDocletBuild

"default =

ejbdoclet

"Basedir =

10:

Init

11:

Target Name =

init

12:

Property file =

Build.properties

13:

14:

Property Name =

ejb.dd.dir

Value =

../Meta-inf

15:

Property Name =

Web.dd.dir

Value =

. .Web-inf

16:

Property Name =

XDoclet.Force

Value =

True

17:

Property Name =

Container.Type

Value =

EJB-JAR

18:

19:

Set up java.class.path

20:

Path id =

Project.class.path

twenty one:

PATHELEMENT LOCATION =

$ {project.dir} / $ {bin.dir}

twenty two:

twenty three:

twenty four:

FILESET DIR =

$ {Eclipse.home} / plugins

25:

INCLUDE NAME = "

** / Ant.jar

26:

INCLUDE NAME =

** / sf.net.xdoclet * / *. jar

27:

INCLUDE NAME =

** / org.apache.log4j * / ** / *. jar

28:

INCLUDE NAME =

** / org.apache.commons * / ** / *. jar

29:

Fileset

30:

31:

Append The External ClassPath Lastly

32:

PATHELEMENT PATH =

$ {java.class.path}

33:

34:

Append the path Sent Through Eclipse to ClassPath

35:

PATHELEMENT PATH =

$ {Project.path}

36:

37:

Path

38:

39:

40:

Target

41:

42:

Run Ejbdoclet

43:

Target Name =

ejbdoclet

Depends =

init

44:

45:

Taskdef name =

ejbdoclet

"ClassName =

XDoclet.modules.ejb.ejbdoclettask

46:

Classpath Refid =

Project.class.path

47:

Taskdef

48:

49:

50:

ejbdoclet

51: destdir =

$ {project.dir} / $ {ejbsrc.dir}

52: mergedir =

$ {ejb.dd.dir}

53: ExcludedTags =

@ Version, @ Author, @ TODO

54: AddedTags =

@Lomboz generated

55: EJBSPEC =

2.0

56: force =

$ {xdoclet.Force}

57: verbose =

True

58:

59:

Please Keep The Bean Marker Comments if you modify the file.

60:

Contents Between the Markers Are Auto Inserted with Each

61:

BUILD.

62:

Beans start

63:

FileSet Dir = "

. ../../src

"defaultexcludes =

YES

64:

Patternset Includesfile =

EJBS.XML

65:

Fileset

66:

Beans end

67:

68:

DataObject

69:

DAO PATTERN =

{0}

DESTDIR =

$ {project.dir} / $ {ejbsrc.dir}

70:

71:

VALUEOBJECT

72:

UtilObject cachehomes =

True

"includeguid =

True

"Kind =

Physical

73:

74:

RemoteInterface

75:

LocalInterface

76:

HOMEINTERFACE

77:

LocalhomeInterface

78:

79:

Entitypk

80:

EntityCMP

81:

EntityBMP

82:

session

83:

84:

DeploymentDescriptor

85: destdir =

$ {ejb.dd.dir}

86: ValidateXML =

False

87: mergedir =

$ {ejb.dd.dir}

88:

89:

90:

91:

Have Struts Form Objects Generated Based on Entity Beans'

92:

Data Objects. Will Require struts.jar to compile.

93:

Strutsform

94:

95:

96:

97:

Have a mapping.xml file generated for castor classes.

98:

99:

Castormapping destdir =

$ {ejb.dd.dir}

"validatexml =

False

100:

101:

102:

WebLogic

103: Version =

6.1

104: Xmlencoding =

UTF-8

105: destdir =

$ {ejb.dd.dir}

106: ValidateXML =

False

107: DataSource =

Please_modify_this

108: mergedir = "

$ {ejb.dd.dir}

109: Persistence =

WebLogic

110:

111:

JBoss

112: Version =

3.0

113: UnauthenticatedPrincipal =

NoBody

114: Xmlencoding =

UTF-8

115: destdir =

$ {ejb.dd.dir}

116: ValidateXML =

False

117: DataSource =

Please_modify_this

118: DataSourceMapping =

Please_modify_this

119: preferredRelationMapping =

Please_modify_this

120:

121:

122:

JRUN

123: Version =

4.0

124: xmlencoding =

UTF-8

125: Destdir =

$ {ejb.dd.dir}

126: ValidateXML =

False

127:

128:

129:

WebSphere destdir =

$ {ejb.dd.dir}

130:

Jonas

131: Version =

3.2

132: xmlencoding =

UTF-8

133: destdir =

$ {ejb.dd.dir}

134: ValidateXML =

False

135: mergedir =

$ {ejb.dd.dir}

136:

137:

138:

Orion

139: destdir =

$ {ejb.dd.dir}

140:

141:

142:

ApachesoAP

143: destdir =

$ {ejb.dd.dir}

144:

145:

146:

ejbdoclet

147:

Target

148:

149:

PROJECT

· Use the LINKS way to install the lomboz plugin Causes and remedies for the XDoclet:

24: 25: 26: 27: 28: 29: · From 2nd lines and 26 lines, Lomboz is looking for" sf.net.xdoclet_1.2.1 "from the" Eclipse installation directory / plugins / " The * .jar file in the subdirectory is running XDoclet. Since the LINKS mode is installed, the "sf.xdoclet_1.2.1" directory cannot be found, and the XDoclet library file cannot be loaded.

● Modify method:

· Do not install the LOMBOZ plug-in by links;

· If you use a links method to install the plugin, copy the three directories in the Lomboz plug-in directory (ie, the above three directorys) to the "Eclipse installation directory / plugins /";

· Directly modify the xdoclet.xml file, replace "$ {eclipse.home} / plugins" in the plug-in directory in the LINKS mode; -3.0.1 / Eclipse / Plugins>

· Or

Add a version 1.2.2 library file path to classpaths.

Note that there is no, this version is 1.2.1, and the current version is 1.2.2; so it is best to replace the library file in the XDoclet in the XDoclet you download, otherwise some functions It may not be used in JBoss 4.0.0.

● Other modified places

· Look at 55, the generation is the 2.0 version of the EJB, of course, it is necessary to change to "2.1", people want to go high.

55: EJBSPEC = "2.0"

· From 102 lines to 140 lines, you can see that Lomboz can use servers such as WebLogic, JBoss, WebSphere, because I only use JBoss to develop EJB, so you only need to keep JBOSS items enough to avoid generating too many server profiles.

Since I use JBoss, I don't use it, modify it, make it more suitable for yourself.

(About the configuration of the database, the next article details, is to develop entity bean settings)

● Modified XDoclet file

XDoclet.xml

Naci Dai and other.

Parts Developed Under Contract Ref: FT / R & D / MAPS / AMS / 2004-09-09 / Al Are

Are Made Available Under The Terms of The Eclipse Public License V1.0

Which Accompanies this Distribution, and is available at

http://www.eclipse.org/legal/epl-v10.html

Contributors:

Eteration Bilisim A.s. - Initial API and Implementation

Naci Dai

For more information on eteration, please see

Correctly point to the Lomboz directory, it is also recommended to use the library in the 1.2.2 version of the XDoclet directory.

File instead of the library file in the sf.net.xdoclet * directory

Destdir = "$ {project.dir} / $ {ejbsrc.dir}"

MergeDir = "$ {ejb.dd.dir}"

ExcludedTags = "@ version, @ Author, @ TODO"

AddedTags = "@ imboz generated"

EJBSPEC = "2.1"

Force = "$ {xdoclet.force}"

Verbose = "True">

Contents Between the Markers Are Auto Inserted with Each

Destdir = "$ {ejb.dd.dir}"

Validatexml = "false"

MergeDir = "$ {ejb.dd.dir}"

Have Struts Form Objects Generated Based on Entity Beans'

Data Objects. Will Require Struts.jar to Compile. ->

Have a mapping.xml file generated for castor classes.

Version = "4.0"

UnauthenticatedPrincipal = "noBody"

Xmlencoding = "GBK"

Destdir = "$ {ejb.dd.dir}"

Validatexml = "false"

DataSource = "java: / mysqlds"

DataSourceMapping = "mysql"

PreferredRelationMapping = "Foreign-key"

Destdir = "$ {ejb.dd.dir}"

Tips:

I will use this file in the future to perform XDoclet, if you have modified it every time you create a project, some troublesome. Here is a method, find

The "com.objectlearn.jdt.j2ee_3.0.1" subdirectory in the Lomboz plug-in directory, found a "Lomboz.jar" file, unzip this file, "COM / ObjectLearn / JDT / J2EE / Templates in the decompressed file) / EJB "directory has a" xdoclet.xml ", open it, is it like xDoclet.xml in the project. You can replace the XDoclet.xml here after the modified xdoclet.xml, then you don't have to modify xdoclet.xml each time.

I spent such a big strength to talk about xDoclet.xml because it is the core of Lomboz developing EJB, I hope that it will not be too Luo.

3. Write a program

●

Continue in the Helloejb project, right-click "SRC" -> New-> Lomboz EJB CREATION WIZARD:

· Package (K): javamxj.ejb.StateLes

· Name (M): Hello

· EJB TYPE: Select STATELESS

Finally click to complete.

● In the Package Resource Manager window, right-click Hellobean.java -> Lomboz J2EE ... -> Add EJB To Module ...: Check HelloEJB Module.

remind

At this time, the following statement will be added to XDoclet.xml:

At the same time, will join in Beans.xml

javamxj.ejb.Stateless.Hellobean session joined the Hellobean.java to the EJBDoclet task.

● Right-click Hellobean.java -> Lomboz J2EE ... -> Add Ejb To Method:

· Method Signature: Public STRING SAYHELLO (String Message)

· Method Type: Business Method

· Interface Type: Remote Interface

● Modify Hellobean.java, add the following statement as shown in the 45-47 row, and save it.

● Right-click HelloEJB module -> Lomboz J2EE ... -> Generate EJB Classes.

Do you see it? 6 files are generated under the EJBSRC folder.

4. Some tips for jboss-ide

In fact, there is no need to generate these two files in Hellolocal.java HellolocalHome, and can remove these two files by modifying the EJB.Bean tag.

JBoss-IDE has now renamed JBoss Eclipse IDE. For convenience, I still refer to JBoss-IDE below.

For detailed usage of JBoss-IDE, please refer to the tutorial on its homepage. Simply say some tips here.

· Switch the inverted window:

· Turn down the scroll bar, select "View-Type" attribute, then click, as shown below:

Here you choose to click "Remote".

This way for view-type = "remote" is entered, it is convenient! Mainly eliminate the memory and look up.

· Save, then delete the EJBSRC this folder, once again Generate EJB CLASSES, this, then find only 4 files under the generated EJBSRC folder.

· There is no need to delete the two files, inserting such a paragraph is mainly to introduce the convenience of using JBoss-IDE. In fact, the benefits of jboss-identity are still a lot, I will experience it slowly.

remind

Open the subdirectory D: /eclipse/myplugins/jboss-ide-1.40/eclipse/plugins/org.jboss.ide.eclipse.xdoclet.core.eclipse.xdoclet.core_1.4.0 (I use the Links mode installation), found there in The xdoclet library file is 1.2.1 version, and it is best to replace it with a library file corresponding to version 1.2.2, and other files do not move.

In addition, you can add other library files such as IBM, BEA to this directory, so that JBoss-IDEs can not only support JBoss, but also support other servers, even write library files you can join.

Also, what is "Alt /", you can view: Eclipse's main window -> Help -> Tips and Tips -> Eclipse Java development tools, very nice.

5. Run the server

There is almost the abuse, and I will enter the topic again.

5. Run the server

There is almost the abuse, and I will enter the topic again.

· Start the server first

As shown in the figure, there are many ways to start the JBoss server. Other operations are the same, it is best to practice more, right-click. · Then right-click HelloEJB and select Deployment Modules in the pop-up menu. If everything is normal, the console will output similar statements:

21: 51: 46, 2013 Info [EJBModule] Deploying Hello

21: 51: 47,656 Info [EjBDeployer] Deployed: file: / f: /java/jboss/server/default/deploy/helloejb.jar

Ok, the server is ready.

6. Develop clients:

· Right-click SRC folder -> New -> Lomboz EJB Test Client Wizard:

Among them, "Packages" and "Name" should be manually entered, "EJB Home" and "EJB Interface" can be selected by selecting.

· An "helloclient.java" file will be generated, open it, add two statements as shown.

· Save, then run HelloClient.java, you can see the output results at the console:

· At this time, the server output:

22: 25: 45, 156 Info [stdout] I am in the EJB server side, the client is calling the 'SayHello' method. 22: 25: 45,156 Info [stdout] Hello JavaMxj (9CBS)

Ok, I finally finished writing, enough.

This is just a beginning, the main talks of the main talks about how to develop entity EJBs, and not talk about the interface and configuration, will focus on development.

Workers must be good, and must first make a tool.

Is your tool equipped?

5. Run the server

There is almost the abuse, and I will enter the topic again.

· Start the server first

As shown in the figure, there are many ways to start the JBoss server. Other operations are the same, it is best to practice more, right-click.

· Then right-click HelloEJB and select Deployment Modules in the pop-up menu. If everything is normal, the console will output similar statements:

21: 51: 46, 2013 Info [EJBModule] Deploying Hello

21: 51: 47,656 Info [EjBDeployer] Deployed: file: / f: /java/jboss/server/default/deploy/helloejb.jar

Ok, the server is ready.

6. Develop clients:

· Right-click SRC folder -> New -> Lomboz EJB Test Client Wizard:

Among them, "Packages" and "Name" should be manually entered, "EJB Home" and "EJB Interface" can be selected by selecting.

· An "helloclient.java" file will be generated, open it, add two statements as shown.

· Save, then run HelloClient.java, you can see the output results at the console:

· At this time, the server output:

22: 25: 45, 156 Info [stdout] I am in the EJB server side, the client is calling the 'SayHello' method. 22: 25: 45,156 Info [stdout] Hello JavaMxj (9CBS)

Ok, I finally finished writing, enough.

This is just a beginning, the main talks of the main talks about how to develop entity EJBs, and not talk about the interface and configuration, will focus on development.

Workers must be good, and must first make a tool. Is your tool equipped?

remind

In addition, you can add other library files such as IBM, BEA to this directory, so that JBoss-IDEs can not only support JBoss, but also support other servers, even write library files you can join.

Also, what is "Alt /", you can view: Eclipse's main window -> Help -> Tips and Tips -> Eclipse Java development tools, very nice.

5. Run the server

There is almost the abuse, and I will enter the topic again.

5. Run the server

There is almost the abuse, and I will enter the topic again.

· Start the server first

As shown in the figure, there are many ways to start the JBoss server. Other operations are the same, it is best to practice more, right-click.

· Then right-click HelloEJB and select Deployment Modules in the pop-up menu. If everything is normal, the console will output similar statements:

21: 51: 46, 2013 Info [EJBModule] Deploying Hello

21: 51: 47,656 Info [EjBDeployer] Deployed: file: / f: /java/jboss/server/default/deploy/helloejb.jar

Ok, the server is ready.

6. Develop clients:

· Right-click SRC folder -> New -> Lomboz EJB Test Client Wizard:

Among them, "Packages" and "Name" should be manually entered, "EJB Home" and "EJB Interface" can be selected by selecting.

· An "helloclient.java" file will be generated, open it, add two statements as shown.

· Save, then run HelloClient.java, you can see the output results at the console:

· At this time, the server output:

22: 25: 45, 156 Info [stdout] I am in the EJB server side, the client is calling the 'SayHello' method. 22: 25: 45,156 Info [stdout] Hello JavaMxj (9CBS)

Ok, I finally finished writing, enough.

This is just a beginning, the main talks of the main talks about how to develop entity EJBs, and not talk about the interface and configuration, will focus on development.

Workers must be good, and must first make a tool.

Is your tool equipped?

5. Run the server

There is almost the abuse, and I will enter the topic again.

· Start the server first

As shown in the figure, there are many ways to start the JBoss server. Other operations are the same, it is best to practice more, right-click.

· Then right-click HelloEJB and select Deployment Modules in the pop-up menu. If everything is normal, the console will output similar statements:

21: 51: 46, 2013 Info [EJBModule] Deploying Hello

21: 51: 47,656 Info [ejbDeployer] Deployed: file: / f: /java/jboss/server/default/deploy/helloejb.jar is good, the server is already ready.

6. Develop clients:

· Right-click SRC folder -> New -> Lomboz EJB Test Client Wizard:

Among them, "Packages" and "Name" should be manually entered, "EJB Home" and "EJB Interface" can be selected by selecting.

· An "helloclient.java" file will be generated, open it, add two statements as shown.

· Save, then run HelloClient.java, you can see the output results at the console:

· At this time, the server output:

22: 25: 45, 156 Info [stdout] I am in the EJB server side, the client is calling the 'SayHello' method. 22: 25: 45,156 Info [stdout] Hello JavaMxj (9CBS)

Ok, I finally finished writing, enough.

This is just a beginning, the main talks of the main talks about how to develop entity EJBs, and not talk about the interface and configuration, will focus on development.

Workers must be good, and must first make a tool.

Is your tool equipped?

remind

In addition, you can add other library files such as IBM, BEA to this directory, so that JBoss-IDEs can not only support JBoss, but also support other servers, even write library files you can join.

Also, what is "Alt /", you can view: Eclipse's main window -> Help -> Tips and Tips -> Eclipse Java development tools, very nice.

5. Run the server

There is almost the abuse, and I will enter the topic again.

5. Run the server

There is almost the abuse, and I will enter the topic again.

· Start the server first

As shown in the figure, there are many ways to start the JBoss server. Other operations are the same, it is best to practice more, right-click.

· Then right-click HelloEJB and select Deployment Modules in the pop-up menu. If everything is normal, the console will output similar statements:

21: 51: 46, 2013 Info [EJBModule] Deploying Hello

21: 51: 47,656 Info [EjBDeployer] Deployed: file: / f: /java/jboss/server/default/deploy/helloejb.jar

Ok, the server is ready.

6. Develop clients:

· Right-click SRC folder -> New -> Lomboz EJB Test Client Wizard:

Among them, "Packages" and "Name" should be manually entered, "EJB Home" and "EJB Interface" can be selected by selecting. · An "helloclient.java" file will be generated, open it, add two statements as shown.

· Save, then run HelloClient.java, you can see the output results at the console:

· At this time, the server output:

22: 25: 45, 156 Info [stdout] I am in the EJB server side, the client is calling the 'SayHello' method. 22: 25: 45,156 Info [stdout] Hello JavaMxj (9CBS)

Ok, I finally finished writing, enough.

This is just a beginning, the main talks of the main talks about how to develop entity EJBs, and not talk about the interface and configuration, will focus on development.

Workers must be good, and must first make a tool.

Is your tool equipped?

5. Run the server

There is almost the abuse, and I will enter the topic again.

· Start the server first

As shown in the figure, there are many ways to start the JBoss server. Other operations are the same, it is best to practice more, right-click.

· Then right-click HelloEJB and select Deployment Modules in the pop-up menu. If everything is normal, the console will output similar statements:

21: 51: 46, 2013 Info [EJBModule] Deploying Hello

21: 51: 47,656 Info [EjBDeployer] Deployed: file: / f: /java/jboss/server/default/deploy/helloejb.jar

Ok, the server is ready.

6. Develop clients:

· Right-click SRC folder -> New -> Lomboz EJB Test Client Wizard:

Among them, "Packages" and "Name" should be manually entered, "EJB Home" and "EJB Interface" can be selected by selecting.

· An "helloclient.java" file will be generated, open it, add two statements as shown.

· Save, then run HelloClient.java, you can see the output results at the console:

· At this time, the server output:

22: 25: 45, 156 Info [stdout] I am in the EJB server side, the client is calling the 'SayHello' method. 22: 25: 45,156 Info [stdout] Hello JavaMxj (9CBS)

Ok, I finally finished writing, enough.

This is just a beginning, the main talks of the main talks about how to develop entity EJBs, and not talk about the interface and configuration, will focus on development.

Workers must be good, and must first make a tool.

Is your tool equipped?

remind

In addition, you can add other library files such as IBM, BEA to this directory, so that JBoss-IDEs can not only support JBoss, but also support other servers, even write library files you can join.

Also, what is "Alt /", you can view: Eclipse's main window -> Help -> Tips and Tips -> Eclipse Java development tools, very nice. 5. Run the server

There is almost the abuse, and I will enter the topic again.

5. Run the server

There is almost the abuse, and I will enter the topic again.

· Start the server first

As shown in the figure, there are many ways to start the JBoss server. Other operations are the same, it is best to practice more, right-click.

· Then right-click HelloEJB and select Deployment Modules in the pop-up menu. If everything is normal, the console will output similar statements:

21: 51: 46, 2013 Info [EJBModule] Deploying Hello

21: 51: 47,656 Info [EjBDeployer] Deployed: file: / f: /java/jboss/server/default/deploy/helloejb.jar

Ok, the server is ready.

6. Develop clients:

· Right-click SRC folder -> New -> Lomboz EJB Test Client Wizard:

Among them, "Packages" and "Name" should be manually entered, "EJB Home" and "EJB Interface" can be selected by selecting.

· An "helloclient.java" file will be generated, open it, add two statements as shown.

· Save, then run HelloClient.java, you can see the output results at the console:

· At this time, the server output:

22: 25: 45, 156 Info [stdout] I am in the EJB server side, the client is calling the 'SayHello' method. 22: 25: 45,156 Info [stdout] Hello JavaMxj (9CBS)

Ok, I finally finished writing, enough.

This is just a beginning, the main talks of the main talks about how to develop entity EJBs, and not talk about the interface and configuration, will focus on development.

Workers must be good, and must first make a tool.

Is your tool equipped?

5. Run the server

There is almost the abuse, and I will enter the topic again.

· Start the server first

As shown in the figure, there are many ways to start the JBoss server. Other operations are the same, it is best to practice more, right-click.

· Then right-click HelloEJB and select Deployment Modules in the pop-up menu. If everything is normal, the console will output similar statements:

21: 51: 46, 2013 Info [EJBModule] Deploying Hello

21: 51: 47,656 Info [EjBDeployer] Deployed: file: / f: /java/jboss/server/default/deploy/helloejb.jar

Ok, the server is ready.

6. Develop clients:

· Right-click SRC folder -> New -> Lomboz EJB Test Client Wizard:

Among them, "Packages" and "Name" should be manually entered, "EJB Home" and "EJB Interface" can be selected by selecting.

· An "helloclient.java" file will be generated, open it, add two statements as shown.

· Save, then run HelloClient.java, you can see the output results at the console:

· At this time, the server output:

22: 25: 45, 156 Info [stdout] I am in the EJB server side, the client is calling the 'SayHello' method. 22: 25: 45, 156 Info [stdout] Hello JavaMxj (9CBS) is ok, finally finished writing, enough.

This is just a beginning, the main talks of the main talks about how to develop entity EJBs, and not talk about the interface and configuration, will focus on development.

Workers must be good, and must first make a tool.

Is your tool equipped?

转载请注明原文地址:https://www.9cbs.com/read-48217.html

9cbs

New Post(0)