JBoss Enterprise Application Platform Common Criteria Certification ...

More documents

Recommendations

Info

4 8 Chapter 6. The JNDI Naming Service mapping information supplied by the Deployer. It must be one of Application or Container. An optional res-sharing-scope element. This currently is not supported by JBoss. The J2EE specification recommends that all resource manager connection factory references be organized in the subcontexts of the application component's environment, using a different subcontext for each resource manager type. The recommended resource manager type to subcontext name is as follows: JDBC DataSource references should be declared in the java:comp/env/jdbc subcontext. JMS connection factories should be declared in the java:comp/env/jms subcontext. JavaMail connection factories should be declared in the java:comp/env/mail subcontext. URL connection factories should be declared in the java:comp/env/url subcontext. Example 6.12, “A web.xml resource-ref descriptor fragment” shows an example web.xml descriptor fragment that illustrates the resource-ref element usage. Example 6.13, “ENC resource-ref access sample code fragment” provides a code fragment that an application component would use to access the DefaultMail resource declared by the resource-ref. Example 6.12. A web.xml resource-ref descriptor fragment AServlet The default DS jdbc/DefaultDS javax.sql.DataSource Container Default Mail mail/DefaultMail javax.mail.Session Container Default QueueFactory jms/QueueFactory javax.jms.QueueConnectionFactory Container Example 6.13. ENC resource-ref access sample code fragment Context initCtx = new InitialContext(); javax.mail.Session s = (javax.mail.Session) initCtx.lookup("java:comp/env/mail/DefaultMail"); 6.6.1.6. Resource Manager Connection Factory References with jboss.xml and jboss-web.xml The purpose of the JBoss jboss.xml EJB deployment descriptor and jboss-web.xml Web application deployment descriptor is to provide the link from the logical name defined by the res-refname element to the JNDI name of the resource factory as deployed in JBoss. This is accomplished by providing a resource-ref element in the jboss.xml or jboss-web.xml descriptor. The JBoss resource-ref element consists of the following child elements:
JBoss Enterprise Application Platform Common Criteria Certification 5 Administration And Configuration Guide 4 9 A res-ref-name element that must match the res-ref-name of a corresponding resource-ref element from the ejb-jar.xml or web.xml standard descriptors An optional res-type element that specifies the fully qualified class name of the resource manager connection factory A jndi-name element that specifies the JNDI name of the resource factory as deployed in JBoss A res-url element that specifies the URL string in the case of a resource-ref of type java.net.URL Example 6.14, “A sample jboss-web.xml resource-ref descriptor fragment” provides a sample jbossweb.xml descriptor fragment that shows sample mappings of the resource-ref elements given in Example 6.12, “A web.xml resource-ref descriptor fragment”. Example 6.14 . A sample jboss-web.xml resource-ref descriptor fragment jdbc/DefaultDS javax.sql.DataSource java:/DefaultDS mail/DefaultMail javax.mail.Session java:/Mail jms/QueueFactory javax.jms.QueueConnectionFactory QueueConnectionFactory 6.6.1.7. Resource Environment References Resource environment references are elements that refer to administered objects that are associated with a resource (for example, JMS destinations) using logical names. Resource environment references are defined by the resource-env-ref elements in the standard deployment descriptors. The Deployer binds the resource environment references to the actual administered objects location in the target operational environment using the jboss.xml and jboss-web.xml descriptors. Each resource-env-ref element describes the requirements that the referencing application component has for the referenced administered object. The resource-env-ref element consists of the following child elements: An optional description element that provides the purpose of the reference. A resource-env-ref-name element that specifies the name of the reference relative to the java:comp/env context. Convention places the name in a subcontext that corresponds to the associated resource factory type. For example, a JMS queue reference named MyQueue should have a resource-env-ref-name of jms/MyQueue. A resource-env-ref-type element that specifies the fully qualified class name of the referenced object. For example, in the case of a JMS queue, the value would be javax.jms.Queue. Example 6.15, “An example ejb-jar.xml resource-env-ref fragment” provides an example resourceref-env element declaration by a session bean. Example 6.16, “ENC resource-env-ref access code fragment” gives a code fragment that illustrates how to look up the StockInfo queue declared by the resource-env-ref.
Page 1 and 2: JBoss Enterprise Application Platfo
Page 3 and 4: Abstract JBoss Enterprise Applicati
Page 11 and 12: Chapter 1. Introduction JBoss Enter
Page 19 and 20: Chapter 4. Deployment Deploying app
Page 21 and 22: web JBoss Enterprise Application Pl
Page 23 and 24: Chapter 6. The JNDI Naming Service
Page 33 and 34: Example 6.2. A JNDI client that use
Page 47: JBoss Enterprise Application Platfo
Page 53 and 54: @XmlAccessorType(XmlAccessType.FIEL
Page 57 and 58: 7.15. WebServiceContext The WebServ
Page 59 and 60: ** * The getPort method returns a p
Page 61 and 62: Message Payload In this mode, clien
Page 71 and 72: @WebServiceClient(name = "EchoServi
Page 73 and 74: @WebService(name = "StatefulEndpoin
Page 89 and 90: ** * Creates a Jaxr Organization wi
Page 93 and 94: ** * Annotation for specifying the
Page 99 and 100:
JBoss Enterprise Application Platfo
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
that have not completed after a spe
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Oracle 10g: org.hibernate.dialect.O
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
That's it; that's all it takes to g
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Application Platform ships with a d
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
ean. By default true, since replica
Page 165 and 166:
a different physical host. If not a
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
deployment (war, ear, jar, whatever
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
The available attributes in the FD
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
import org.jboss.ha.cachemanager.Ca
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Example A.10. Sybase Datasource [ 1
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Example A.25. PostgreSQL XA Datasou
Page 255 and 256:
Example B.2. Filtering App1 Log Out
show all

JBoss Enterprise Application Platform Common Criteria Certification ...

Create successful ePaper yourself

Delete template?

Save as template?