Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
爱吃血肠
spring-framework
提交
53dcb000
S
spring-framework
项目概览
爱吃血肠
/
spring-framework
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
S
spring-framework
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
前往新版Gitcode,体验更适合开发者的 AI 搜索 >>
提交
53dcb000
编写于
10月 10, 2019
作者:
T
Tomasz Letachowicz
提交者:
Rossen Stoyanchev
10月 24, 2019
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Typos in WebSocket section
Closes gh-23777
上级
562c0871
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
3 addition
and
3 deletion
+3
-3
src/docs/asciidoc/web/websocket.adoc
src/docs/asciidoc/web/websocket.adoc
+3
-3
未找到文件。
src/docs/asciidoc/web/websocket.adoc
浏览文件 @
53dcb000
...
...
@@ -1403,7 +1403,7 @@ for the return value, by default, a message is sent directly to the client (thro
When
is
this
useful
?
Assume
that
the
broker
is
mapped
to
`/
topic
`
and
`/
queue
`,
while
application
controllers
are
mapped
to
`/
app
`.
In
this
setup
,
the
broker
stores
all
subscriptions
to
`/
topic
`
and
`/
queue
`
that
are
intended
for
repeated
broadcasts
,
and
there
is
no
need
for
the
application
to
get
involved
.
A
client
could
also
also
subscribe
to
there
is
no
need
for
the
application
to
get
involved
.
A
client
could
also
subscribe
to
some
`/
app
`
destination
,
and
a
controller
could
return
a
value
in
response
to
that
subscription
without
involving
the
broker
without
storing
or
using
the
subscription
again
(
effectively
a
one
-
time
request
-
reply
exchange
).
One
use
case
for
this
is
populating
a
UI
...
...
@@ -2579,7 +2579,7 @@ When you use `@EnableWebSocketMessageBroker` or `<websocket:message-broker>`, ke
infrastructure components automatically gather statisticss and counters that provide
important insight into the internal state of the application. The configuration
also declares a bean of type `WebSocketMessageBrokerStats` that gathers all
available information in one place and by
, default logs,
it at the `INFO` level once
available information in one place and by
default logs
it at the `INFO` level once
every 30 minutes. This bean can be exported to JMX through Spring'
s
`
MBeanExporter
`
for
viewing
at
runtime
(
for
example
,
through
JDK
's `jconsole`).
The following list summarizes the available information:
...
...
@@ -2652,7 +2652,7 @@ Ideally, controllers under test should be invoked as they are at runtime, much l
the
approach
to
testing
controllers
that
handle
HTTP
requests
by
using
the
Spring
MVC
Test
framework
--
that
is
,
without
running
a
Servlet
container
but
relying
on
the
Spring
Framework
to
invoke
the
annotated
controllers
.
As
with
Spring
MVC
Test
,
you
have
two
two
possible
alternatives
here
,
either
use
a
"`context-based`"
or
use
a
"`standalone`"
setup
:
possible
alternatives
here
,
either
use
a
"`context-based`"
or
use
a
"`standalone`"
setup
:
*
Load
the
actual
Spring
configuration
with
the
help
of
the
Spring
TestContext
framework
,
inject
`
clientInboundChannel
`
as
a
test
field
,
and
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录