Vaadin“一个id为xy的连接器已经注册" [英] Vaadin "A connector with id xy is already registered"

查看:20
本文介绍了Vaadin“一个id为xy的连接器已经注册"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我的 Vaadin 应用程序中的某个地方,我使用第二个浏览器连接后立即收到此异常

Somewhere in my Vaadin application, I'm getting this exception as soon as I connect using a second browser

Caused by: java.lang.RuntimeException: 一个 id 为 22 的连接器已经注册!在 com.vaadin.ui.ConnectorTracker.registerConnector(ConnectorTracker.java:133)

它总是发生在同一个地方,但我不知道为什么会出现这种情况,原因肯定是在其他地方.

It happens always in the same place but I don't know why exactly as the reason for this must be somewhere else.

我想我可能会从另一个会话中窃取 UI 组件 - 这不是我的本意.目前,我没有看到我可能在多个会话中使用的 UI 组件的任何 static 实例.

I think I might be stealing UI components from the other session - which is not my intention. Currently, I don't see any static instances of UI components I might be using in multiple sessions.

我该如何调试?它已经成为一个相当大的项目.有什么要寻找的提示吗?

How can I debug this? It's become quite a large project. Any hints to look for?

推荐答案

我想我可能会从另一个会话中窃取 UI 组件 - 这不是我的本意.目前,我没有看到可能在多个会话中使用的 UI 组件的任何静态实例.
I think I might be stealing UI components from the other session - which is not my intention. Currently, I don't see any static instances of UI components I might be using in multiple sessions.

就是这样.我实际上是在事先不知情的情况下窃取 UI 组件.

That was it. I was actually stealing UI components without prior knowledge.

它很好地隐藏在所有实例似乎都相同的部分中.这是真的:算法是一样的.

It was very well hidden in a part which seems to be same for all instances. Which is true: the algorithm is the same.

并不意味着我也应该重用相同的 UI 组件...

Doesn't mean I should've reused the same UI components as well...

感谢那些仔细观察的人.

Thanks to those who took a closer look.

这篇关于Vaadin“一个id为xy的连接器已经注册"的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆