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
Spring Framework 2.0.8 ReferenceSpring could potentially be a one-stop-shop for all your enterprise applications; however, Spring is modular, allowing you to use just those parts of it that you need, without having to bring in the rest. You AspectJ, to enable all uses of AOP to be catered for within a consistent Spring-based application architecture. This integration does not affect the Spring AOP API or the AOP Alliance API: Spring AOP remains instantiation models, and richer pointcut composition. It has the advantage of keeping the aspect as a modular unit. It also has the advantage the @AspectJ aspects can be understood both by Spring AOP and by0 码力 | 502 页 | 3.61 MB | 1 年前3
Spring Framework 2.0.3 ReferenceSpring could potentially be a one-stop-shop for all your enterprise applications; however, Spring is modular, allowing you to use just those parts of it that you need, without having to bring in the rest. You AspectJ, to enable all uses of AOP to be catered for within a consistent Spring-based application architecture. This integration does not affect the Spring AOP API or the AOP Alliance API: Spring AOP remains instantiation models, and richer pointcut composition. It has the advantage of keeping the aspect as a modular unit. It also has the advantage the @AspectJ aspects can be understood both by Spring AOP and by0 码力 | 495 页 | 3.57 MB | 1 年前3
Spring Framework 2.0.2 ReferenceSpring could potentially be a one-stop-shop for all your enterprise applications; however, Spring is modular, allowing you to use just those parts of it that you need, without having to bring in the rest. You AspectJ, to enable all uses of AOP to be catered for within a consistent Spring-based application architecture. This integration does not affect the Spring AOP API or the AOP Alliance API: Spring AOP remains instantiation models, and richer pointcut composition. It has the advantage of keeping the aspect as a modular unit. It also has the advantage the @AspectJ aspects can be understood both by Spring AOP and by0 码力 | 498 页 | 3.55 MB | 1 年前3
共 246 条
- 1
- 2
- 3
- 4
- 5
- 6
- 25













