Spring Framwork Integration v5.3.36 SNAPSHOTSpringBeanAutowiringSupport: /** * JAX-WS compliant AccountService implementation that simply delegates * to the AccountService implementation in the root web application context. * * This wrapper proxy objects (normally configured inside a Spring container), which act as codeless business delegates. You need not write another Service Locator, another JNDI lookup, or duplicate methods in a hand-coded dynamic destinations or support for a hierarchical namespace of destinations. The JmsTemplate delegates the resolution of a destination name to a JMS destination object that implements the DestinationResolver0 码力 | 141 页 | 2.13 MB | 1 年前3
Spring Framwork Testing v5.3.36 SNAPSHOTtest. The TestContextManager also updates the state of the TestContext as the test progresses and delegates to TestExecutionListener implementations, which instrument the actual test execution by providing management and caching support for the test instance for which it is responsible. The TestContext also delegates to a SmartContextLoader to load an ApplicationContext if requested. TestContextManager TestContextManager the following implementations: • DelegatingSmartContextLoader: One of two default loaders, it delegates internally to an AnnotationConfigContextLoader, a GenericXmlContextLoader, or a GenericGroovyXmlContextLoader0 码力 | 193 页 | 2.53 MB | 1 年前3
Spring Framwork Web on Servlet Stack v5.3.36 SNAPSHOTcontextConfigLocation Servlet parameter empty. 1.1.2. Special Bean Types WebFlux The DispatcherServlet delegates to special beans to process requests and render the appropriate responses. By “special beans” we request mapping or is thrown from a request handler (such as a @Controller), the DispatcherServlet delegates to a chain of HandlerExceptionResolver beans to resolve the exception and provide alternative handling Content Negotiation WebFlux ContentNegotiatingViewResolver does not resolve views itself but rather delegates to other view resolvers and selects the view that resembles the representation requested by the0 码力 | 259 页 | 3.58 MB | 1 年前3
Kotlin 1.2 Language Documentationcorresponding to the property will be delegated to its getValue() and setValue() methods. Property delegates don’t have to implement any interface, but they have to provide a getValue() function (and setValue() println("$value has been assigned to '${property.name}' in $thisRef.") } } When we read from p that delegates to an instance of Delegate , the getValue() function from Delegate is called, so that its first the example. The Kotlin standard library provides factory methods for several useful kinds of delegates. lazy() is a function that takes a lambda and returns an instance of Lazywhich can serve as 0 码力 | 333 页 | 2.22 MB | 1 年前3
Spring Framework 1.2.6 ReferenceFor example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the JDO-based ProductDao. Each specified method would then automatically get executed within For example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the TopLink-based ProductDao. Each specified method would then automatically get executed within For example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the OJB-based ProductDao. Each specified method would then automatically get executed within0 码力 | 290 页 | 1.49 MB | 1 年前3
Spring Framework 1.2.x ReferenceFor example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the JDO-based ProductDao. Each specified method would then automatically get executed within For example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the TopLink-based ProductDao. Each specified method would then automatically get executed within For example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the OJB-based ProductDao. Each specified method would then automatically get executed within0 码力 | 289 页 | 1.50 MB | 1 年前3
Spring Framework 1.2.8 ReferenceFor example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the JDO-based ProductDao. Each specified method would then automatically get executed within For example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the TopLink-based ProductDao. Each specified method would then automatically get executed within For example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the OJB-based ProductDao. Each specified method would then automatically get executed within0 码力 | 290 页 | 1.49 MB | 1 年前3
Spring Framework 1.2.4 ReferenceFor example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the JDO-based ProductDao. Each specified method would then automatically get executed within For example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the TopLink-based ProductDao. Each specified method would then automatically get executed within For example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the OJB-based ProductDao. Each specified method would then automatically get executed within0 码力 | 289 页 | 1.49 MB | 1 年前3
Spring Framework 1.2.7 ReferenceFor example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the JDO-based ProductDao. Each specified method would then automatically get executed within For example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the TopLink-based ProductDao. Each specified method would then automatically get executed within For example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the OJB-based ProductDao. Each specified method would then automatically get executed within0 码力 | 290 页 | 1.49 MB | 1 年前3
Spring Framework 1.2.5 ReferenceFor example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the JDO-based ProductDao. Each specified method would then automatically get executed within For example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the TopLink-based ProductDao. Each specified method would then automatically get executed within For example, you could define a TransactionProxyFactoryBean for a ProductService, which in turn delegates to the OJB-based ProductDao. Each specified method would then automatically get executed within0 码力 | 290 页 | 1.49 MB | 1 年前3
共 662 条
- 1
- 2
- 3
- 4
- 5
- 6
- 67













