3rd party web frameworks is back in the web section
This commit is contained in:
parent
45c207aece
commit
b2017bb1ec
|
@ -9033,5 +9033,3 @@ policies and different topologies which other solutions do not (take for example
|
|||
`ConcurrentHashMap`) - exposing that in the cache abstraction would be useless simply
|
||||
because there would no backing support. Such functionality should be controlled directly
|
||||
through the backing cache, when configuring it or through its native API.
|
||||
|
||||
include::web/integration.adoc[leveloffset=+1]
|
||||
|
|
|
@ -19,4 +19,5 @@ include::web/webmvc-cors.adoc[leveloffset=+1]
|
|||
|
||||
include::web/websocket.adoc[leveloffset=+1]
|
||||
|
||||
include::web/integration.adoc[leveloffset=+1]
|
||||
|
||||
|
|
|
@ -1,13 +1,12 @@
|
|||
|
||||
[[web-integration]]
|
||||
= Integrating with other web frameworks
|
||||
= Other Web Frameworks
|
||||
|
||||
|
||||
[[intro]]
|
||||
== Introduction
|
||||
|
||||
This chapter details Spring's integration with third party web frameworks, such as
|
||||
http://www.oracle.com/technetwork/java/javaee/javaserverfaces-139869.html[JSF].
|
||||
This chapter details Spring's integration with third party web frameworks.
|
||||
|
||||
One of the core value propositions of the Spring Framework is that of enabling
|
||||
__choice__. In a general sense, Spring does not force one to use or buy into any
|
||||
|
@ -16,33 +15,7 @@ some over others). This freedom to pick and choose the architecture, technology,
|
|||
methodology that is most relevant to a developer and their development team is
|
||||
arguably most evident in the web area, where Spring provides its own web framework
|
||||
(<<mvc,Spring MVC>>), while at the same time providing integration with a number of
|
||||
popular third party web frameworks. This allows one to continue to leverage any and all
|
||||
of the skills one may have acquired in a particular web framework such as JSF, while
|
||||
at the same time being able to enjoy the benefits afforded by Spring in other areas such
|
||||
as data access, declarative transaction management, and flexible configuration and
|
||||
application assembly.
|
||||
|
||||
Having dispensed with the woolly sales patter (c.f. the previous paragraph), the
|
||||
remainder of this chapter will concentrate upon the meaty details of integrating your
|
||||
favorite web framework with Spring. One thing that is often commented upon by developers
|
||||
coming to Java from other languages is the seeming super-abundance of web frameworks
|
||||
available in Java. There are indeed a great number of web frameworks in the Java space;
|
||||
in fact there are far too many to cover with any semblance of detail in a single
|
||||
chapter. This chapter thus picks four of the more popular web frameworks in Java,
|
||||
starting with the Spring configuration that is common to all of the supported web
|
||||
frameworks, and then detailing the specific integration options for each supported web
|
||||
framework.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Please note that this chapter does not attempt to explain how to use any of the
|
||||
supported web frameworks. For example, if you want to use JSF for the presentation
|
||||
layer of your web application, the assumption is that you are already familiar with
|
||||
JSF itself. If you need further details about any of the supported web frameworks
|
||||
themselves, please do consult <<web-integration-resources>> at the end of this chapter.
|
||||
====
|
||||
|
||||
|
||||
popular third party web frameworks.
|
||||
|
||||
|
||||
[[web-integration-common]]
|
||||
|
|
Loading…
Reference in New Issue