Adobe 38000382 Getting Started Guide - Page 42

About enterprise resource adapters and JRun, About enterprise applications and JRun, resource adapter

Page 42 highlights

XDoclet (for EJBs and web applications) JRun provides integration with XDoclet, a popular open-source tool that generates EJB interfaces and deployment descriptors based on special Javadoc comments in an enterprise bean implementation source file. You can also use XDoclet to generate web application deployment descriptors and JSP tag library descriptors based on comments in servlet or tag library source files. JRun extends XDoclet to support the JRun-specific deployment descriptors, and provides automatic compilation and deployment. For more information, see JRun Programmer's Guide. About enterprise resource adapters and JRun A resource adapter is a J2EE component that implements the J2EE connector technology for a specific EIS. The resource adapter provides a standard API through which a J2EE application communicates with an EIS resource that is outside of the J2EE server. The JCA architecture defines a set of contracts that a resource adapter must support to plug into a J2EE product; for example, transactions, security, and resource management, that are managed by the JRun server. The resource adapter provider creates the standard deployment descriptor file, ra.xml. You use jrun-ra.xml when you require more than one managed connection, to specify the resource adapter's JNDI name, configuration properties, security information, and connection pool settings. About enterprise applications and JRun An enterprise application consists of one or more J2EE modules and an enterprise application deployment descriptor, application.xml, packaged in an EAR file or an expanded directory. JRun completely supports the J2EE application model and provides a runtime environment for executing enterprise applications. J2EE enterprise applications are based on standardized, modular components, to which JRun provides a complete set of services and handles many details of application behavior automatically, such as transaction management, lifecycle management, and resource pooling. JRun facilitates enterprise application development and deployment by providing the following features: • You can deploy an enterprise application EAR file or expanded directory. • JRun automatically deploys J2EE modules that are located in the server's deploy directory. • JRun dynamically detects changes to J2EE modules in the deploy directory and redeploys them. For more information on developing and deploying enterprise applications, see JRun Programmer's Guide and JRun Assembly and Deployment Guide. 28 Chapter 2 JRun Programming Model

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132

28
Chapter 2
JRun Programming Model
XDoclet (for EJBs and web applications)
JRun provides integration with XDoclet, a popular open-source tool that generates EJB
interfaces and deployment descriptors based on special Javadoc comments in an
enterprise bean implementation source file. You can also use XDoclet to generate web
application deployment descriptors and JSP tag library descriptors based on comments in
servlet or tag library source files.
JRun extends XDoclet to support the JRun-specific deployment descriptors, and
provides automatic compilation and deployment. For more information, see
JRun
Programmer’s Guide
.
About enterprise resource adapters and JRun
A
resource adapter
is a J2EE component that implements the J2EE connector
technology for a specific EIS. The resource adapter provides a standard API through
which a J2EE application communicates with an EIS resource that is outside of the J2EE
server.
The JCA architecture defines a set of contracts that a resource adapter must support to
plug into a J2EE product; for example, transactions, security, and resource management,
that are managed by the JRun server.
The resource adapter provider creates the standard deployment descriptor file, ra.xml.
You use jrun-ra.xml when you require more than one managed connection, to specify the
resource adapter’s JNDI name, configuration properties, security information, and
connection pool settings.
About enterprise applications and JRun
An
enterprise application
consists of one or more J2EE modules and an enterprise
application deployment descriptor, application.xml, packaged in an EAR file or an
expanded directory.
JRun completely supports the J2EE application model and provides a runtime
environment for executing enterprise applications. J2EE enterprise applications are based
on standardized, modular components, to which JRun provides a complete set of services
and handles many details of application behavior automatically, such as transaction
management, lifecycle management, and resource pooling.
JRun facilitates enterprise application development and deployment by providing the
following features:
You can deploy an enterprise application EAR file or expanded directory.
JRun automatically deploys J2EE modules that are located in the server’s deploy
directory.
JRun dynamically detects changes to J2EE modules in the deploy directory and
redeploys them.
For more information on developing and deploying enterprise applications, see
JRun
Programmer’s Guide
and
JRun Assembly and Deployment Guide
.