Spring Framework 1.1.1 Reference................................................................................. 146 13.7.1. Architecture ............................................................................................. Spring could potentially be a one-stop-shop for all your enterprise applications, however, Spring is modular, allowing you to use parts of it, without having to bring in the rest. You can use the bean container AspectJ, to enable all uses of AOP to be catered for within a consistent Spring-based application architecture. This integration will not affect the Spring AOP API or the AOP Alliance API; Spring AOP will0 码力 | 194 页 | 1.12 MB | 1 年前3
Spring Framework 1.1.3 Reference................................................................................. 152 13.7.1. Architecture ............................................................................................. Spring could potentially be a one-stop-shop for all your enterprise applications, however, Spring is modular, allowing you to use parts of it, without having to bring in the rest. You can use the bean container AspectJ, to enable all uses of AOP to be catered for within a consistent Spring-based application architecture. This integration will not affect the Spring AOP API or the AOP Alliance API; Spring AOP will0 码力 | 203 页 | 1.15 MB | 1 年前3
Spring Framework 1.1.2 Reference................................................................................. 151 13.7.1. Architecture ............................................................................................. Spring could potentially be a one-stop-shop for all your enterprise applications, however, Spring is modular, allowing you to use parts of it, without having to bring in the rest. You can use the bean container AspectJ, to enable all uses of AOP to be catered for within a consistent Spring-based application architecture. This integration will not affect the Spring AOP API or the AOP Alliance API; Spring AOP will0 码力 | 199 页 | 1.14 MB | 1 年前3
Spring Framework 1.1.5 Reference................................................................................. 163 14.4.1. Architecture ............................................................................................. Spring could potentially be a one-stop-shop for all your enterprise applications, however, Spring is modular, allowing you to use parts of it, without having to bring in the rest. You can use the bean container AspectJ, to enable all uses of AOP to be catered for within a consistent Spring-based application architecture. This integration will not affect the Spring AOP API or the AOP Alliance API; Spring AOP will0 码力 | 223 页 | 1.22 MB | 1 年前3
Spring Framework 1.2.1 Reference................................................................................. 168 14.4.1. Architecture ............................................................................................. Spring could potentially be a one-stop-shop for all your enterprise applications, however, Spring is modular, allowing you to use parts of it, without having to bring in the rest. You can use the bean container AspectJ, to enable all uses of AOP to be catered for within a consistent Spring-based application architecture. This integration will not affect the Spring AOP API or the AOP Alliance API; Spring AOP will0 码力 | 244 页 | 1.30 MB | 1 年前3
Spring Framework 1.2.0 Reference................................................................................. 167 14.4.1. Architecture ............................................................................................. Spring could potentially be a one-stop-shop for all your enterprise applications, however, Spring is modular, allowing you to use parts of it, without having to bring in the rest. You can use the bean container AspectJ, to enable all uses of AOP to be catered for within a consistent Spring-based application architecture. This integration will not affect the Spring AOP API or the AOP Alliance API; Spring AOP will0 码力 | 243 页 | 1.29 MB | 1 年前3
Spring Framework 1.2.2 Reference................................................................................. 179 14.4.1. Architecture ............................................................................................. Spring could potentially be a one-stop-shop for all your enterprise applications, however, Spring is modular, allowing you to use parts of it, without having to bring in the rest. You can use the bean container AspectJ, to enable all uses of AOP to be catered for within a consistent Spring-based application architecture. This integration will not affect the Spring AOP API or the AOP Alliance API; Spring AOP will0 码力 | 269 页 | 1.41 MB | 1 年前3
Apache ActiveMQ Artemis 2.8.0 User Manualof Contents Introduction Legal Notice Preface Project Info Versions Messaging Concepts Architecture Using the Server Upgrading Address Model Protocols and Interoperability AMQP MQTT STOMP please see Core Bridges and Diverting and Splitting Message Flows. Messaging Concepts 23 Core Architecture Apache ActiveMQ Artemis core is designed simply as set of Plain Old Java Objects (POJOs) - we a protocol agnostic messaging server designed to be used with multiple different protocols. Architecture 24 When a user uses the JMS API on the client side, all JMS interactions are translated into0 码力 | 495 页 | 5.09 MB | 1 年前3
Apache Wicket 8.x Reference Guidecontainers, just like AWT does with desktop windows. Both frameworks share the same component-based architecture: in AWT we have a Windows instance which represents the physical windows containing GUI components Application’s init method to initialize these kinds of entities, Wicket offers a more flexible and modular way to configure our classes. During application’s bootstrap Wicket searches for any properties components a desktop-like event-driven architecture. Then, we have introduced a new entity called initializer which can be used to configure resources and component in a modular and self-contained way. We have0 码力 | 350 页 | 9.95 MB | 1 年前3
Apache Wicket 7.x Reference Guidecontainers, just like AWT does with desktop windows. Both frameworks share the same component-based architecture: in AWT we have a Windows instance which represents the physical windows containing GUI components Application’s init method to initialize these kinds of entities, Wicket offers a more flexible and modular way to configure our classes. During application’s bootstrap Wicket searches for any properties components a desktop-like event-driven architecture. Then, we have introduced a new entity called initializer which can be used to configure resources and component in a modular and self-contained way. We have0 码力 | 346 页 | 10.00 MB | 1 年前3
共 305 条
- 1
- 2
- 3
- 4
- 5
- 6
- 31













