JBoss Enterprise Application Platform Common Criteria Certification ...

More documents

Recommendations

Info

50 Chapter 6. The JNDI Naming Service Example 6.15. An example ejb-jar.xml resource-env-ref fragment MyBean This is a reference to a JMS queue used in the processing of Stock info jms/StockInfo javax.jms.Queue Example 6.16. ENC resource-env-ref access code fragment InitialContext iniCtx = new InitialContext(); javax.jms.Queue q = (javax.jms.Queue) envCtx.lookup("java:comp/env/jms/StockInfo"); 6.6.1.8. Resource Environment References and jboss.xml, 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 resourceenv-ref-name element to the JNDI name of the administered object deployed in JBoss. This is accomplished by providing a resource-env-ref element in the jboss.xml or jboss-web.xml descriptor. The JBoss resource-env-ref element consists of the following child elements: A resource-env-ref-name element that must match the resource-env-ref-name of a corresponding resource-env-ref element from the ejb-jar.xml or web.xml standard descriptors A jndi-name element that specifies the JNDI name of the resource as deployed in JBoss Example 6.17, “A sample jboss.xml resource-env-ref descriptor fragment” provides a sample jboss.xml descriptor fragment that shows a sample mapping for the StockInforesource-envref. Example 6.17. A sample jboss.xml resource-env-ref descriptor fragment MyBean jms/StockInfo queue/StockInfoQueue
JBoss Enterprise Application Platform Common Criteria Certification 5 Administration And Configuration Guide 51 Chapter 7. Web Services Web services are a key contributing factor in the way Web commerce is conducted today. Web services enable applications to communicate by sending small and large chunks of data to each other. A web service is essentially a software application that supports interaction of applications over a computer network or the world wide web. Web services usually interact through XML documents that map to an object, computer program, business process or database. To communicate, an application sends a message in XML document format to a web service which sends this message to the respective programs. Responses may be received based on requirements, the web service receives and then sends them in XML document format to the required program or applications. Web services can be used in many ways, examples include supply chain information management and business integration. JBossWS is a web service framework included as part of the JBoss Enterprise Application Platform. It implements the JAX-WS specification that defines a programming model and run-time architecture for implementing web services in Java, targeted at the Java Platform, Enterprise Edition 5 (Java EE 5). Even though JAX-RPC is still supported (the web service specification for J2EE 1.4), JBossWS does put a clear focus on JAX-WS. Warning JAX-RPC is not supported for JBoss Web Services CXF Stack. 7.1. The need for web services Enterprise systems communication may benefit from a wise adoption of web service technologies. Focusing attention on well designed contracts allows developers to establish an abstract view of their service capabilities. Considering the standardized way contracts are written, this definitely helps communication with third-party systems and eventually supports business-to-business integration; everything is clear and standardized in the contract the provider and consumer agree on. This also reduces the dependencies between implementations allowing other consumers to easily use the provided service without major changes. Other benefits exist for enterprise systems that incorporate web service technologies for internal heterogenous subsystems communication as web service interoperability boosts service reuse and composition. Web services eliminates the need to rewrite whole functionalities because they were developed by another enterprise department using a different software language. 7.2. What web services are not Web services are not the solution for every software system communication. Nowadays they are meant to be used for loosely-coupled coarse-grained communication, message (document) exchange. Recent times has seen many specifications (WS-*) discussed and finally approved to establish standardized ws-related advanced aspects, including reliable messaging, message-level security and cross-service transactions. Web service specifications also include the notion of registries to collect service contract references, to easily discover service implementations. This all means that the web services technology platform suits complex enterprise communication and is not simply the latest way of doing remote procedure calls. 7.3. Document/Literal With document style web services two business partners agree on the exchange of complex business documents that are well defined in XML schema. For example, one party sends a document describing a purchase order, the other responds (immediately or later) with a document that describes the status of the purchase order. The payload of the SOAP message is an XML document that can be validated against XML schema. The document is defined by the style attribute on the SOAP binding.
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 49: 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 101 and 102:
JBoss Enterprise Application Platfo
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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?