Books
in black and white
Main menu
Share a book About us Home
Books
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics
Ads

convergent architecture Building model driven J2EE Systems with UML - Hubert R.

Hubert R. convergent architecture Building model driven J2EE Systems with UML - Wiley publishing , 2002. - 289 p.
ISBN: 0-471-10560-0
Download (direct link): convergentarchitecturebu2002.pdf
Previous << 1 .. 124 125 126 127 128 129 < 130 > 131 132 133 134 135 136 .. 142 >> Next

E

Proier! Cnnntliursllo-I b WcSM* ^jamplE-slei'IendscfllBankiçi'’ s.pleri_CGE Uti H 3 nkJNl 1
Dirnaiu Î ûtifjflüralt&n fc VvjrtSfylericfchasrose ifg
OK Apply Fr-eser bisliel
Figure 8.17: The Tools panel.
Now that you have configured the code generator, save the configuration using the Rose menu Tools ^ ArcStyler ^ Save Configuration.
Running the Code Generator
Now run the code generator. In the Rose browser, select the entire Logical View package, and use its ArcStyler ^ Generate context menu to generate all artifacts. These artifacts include the following at this point. The JSP and other Web artifacts will be generated in later section using an accessor cartridge.
Java sources (home interface, remote interface, bean implementation
class).
The Java sources are generated in the %SRC%/<container_id>_gen/ibank directory, where %SRC% is the
source-code output directory you configured in the Generate panel.
Default test client.
-251-
Team-Ffy®
Convergent Architecture
Chapter 8: Tutorial Example
The default test client, modelTestClientjava, is generated in the %SRC%/components/Mbs/model directory.
Standard deployment descriptor.
The standard deployment descriptor is generated in the %SRC%/components/libs/model/META-INF directory.
Container-specific deployment descriptors.
The container-specific deployment descriptors are generated in the %SRC%/components/libs/model/<container_id>/META-INF directory.
Container-specific build support files.
The container-specific build support files are generated in the %SRC%/components/libs/model/<container_id> directory.
Progress and information pertaining to the code generation are logged to the Rose log window. Figure 8.18 shows an example of the generator output in the log window.
If 1 1.111 iinn 1 ll-Ti'IH ■ ill rtriE iTrffi - |l flf|| HZE
f-r [lb !|Wi SPjJnt ttni« rfri. -i£i /J'
e A □ ft R ? ft 7*
i+-
i e***
iOJJhCw^
£ Qtiink
y .-i: 11rv::M I
cmriUilii J| Mhi
* induribUkH
* II J
* «£l«M>5 dUIE
9 1 I
1 VJQt O tor^HT-
if
*
a N-sn
■A AuOTifcgnf r-ir_____.MX...
1 . __________________
I ____________
4S:?I| AnrGiriid Support:
46:21 j nDmponf nil ,Mi hii.'rri 3ll« l>Wl2 bl |'hU |||1 MTlI
WiftNnJS: unable-td gtiiMiDpcrtyCUl.Jnvb.ldE « 21| WKNING: unable- Ic gel property CWtS61.1i:: A'if-.il j Lnmponenbs/li bdjm odeljWldGI tr.c uri:tl Ic-t
Aj.li | mnpint ritul' bbJmcdelJWldEI ilbuild.prnpcrij i
■1:f.2 ?| curipontntr^lHbnJmDdelfcdnGI /build .bad
-1 !■:? Ii| Lornponentsjlpbi/m pdrlMi EI ^tsrtA.:yr l.Li ■ i
«:23| Weblopic J3u Ider PrujcLi:
&V.Z 3| LuraipcmrnCbJIiba/rTrodrltolnSl /mudt l.j yr
45;?d| mnip LI 11 <T 11 r|i J Li "1111 ud rIMa 51 /■■■ cdrl.E jh-JI p
#5;?4| fio«(№ncn«jlib4jm odtl WaSl
<b;?4| wmponenndiibUnibdtlMaSl/BEA WcHoflic
«;rs| MaipepenhJSbi/mpdei^iiaSji^lmflPKttiexti
4b:?H| HM1|»Wnhli*P*/'iinr1cl/Wlihl /lHbR_medel_Aj
4b:7bj nnrripenentppirbfl/rTTOdeUVrlPtil/Hiehber.ibtea.h 4b:7K| rnrTifi'jritnt-L1IHba|imDdclJwls:bl|irlriip Ibhlca.aqt 4h:7K|
Ah:7\i\ — gencmle dcpendnnl nichivt|sj 45£E|
fl!i:71i| — qenerblron 1n*k 15 ;;Ecarid(D|
4h:7U| Ci mi prat dr nf '"C^mb-ly Mtsar-plni'.EJcnrdeddl flG:?G| Gent-nrt nr linldbed. ^
J
FLiNtt pci: FI
Figure 8.18: Rose log window.
Building, Deploying, and Testing the EJB Components
This section shows how to use one of several build, deploy, and test constellations supported by the architectural IDE. It exhibits support for the implementation cycle work flows, test work flows, and several aspects of the deployment and monitoring work flow.
After the code has been generated, the following tasks are at hand: Customize the code.
Build the EJB JAR file.
Deploy the EJB JAR file in a test container.
Test the EJB components using the default test client.
-252-
Convergent Architecture
Chapter 8: Tutorial Example
The simple, ANT-based execution of these tasks is covered in the following subsections:
Code customization Build support
Code Customization
In this section, you will implement some custom business logic in the Account and Transfer beans. Moreover, you will implement custom test code in the default test client.
As explained in Chapter 7, the code generator uses the concept of protected areas to support round-trip development. Protected areas are code segments that are preserved across subsequent runs of the code generator. Custom business logic and other information that cannot be specified in the UML model are entered in these protected areas.
You can use any editor to customize the source code. However, Borland's Java IDE is explicitly supported by the architectural IDE for this purpose. A JBuilder project file, model.jpr, was generated in the
%SRC%/components/libs/model/<container_id> directory. It contains information regarding the Java sources, deployment descriptors, test packages, and other JBuilder information associated with the EJB archive component, model, that you created in the previous C-REF section.
Previous << 1 .. 124 125 126 127 128 129 < 130 > 131 132 133 134 135 136 .. 142 >> Next