openfire自动订阅接受
我已经安装了 openfire 的订阅插件，并且已进行设置以接受所有本地订阅请求。
然而，当我尝试将用户添加到我的名册中时，它的订阅类型仍然看起来是“无”，但我在这里想要的是，一旦我将用户添加到我的名册中，它的订阅类型应该是“来自”或“两者”。我认为订阅插件是造成这种情况的原因，但我认为它不起作用或者我错过了一些东西 有人知道吗？
我还检查了系统日志并看到以下错误：
2012.02.17 16:13:48 org.jivesoftware.openfire.container.PluginServlet - org.jivesoftware.openfire.plugin.SubscriptionPlugin 无法转换为 org.jivesoftware.openfire.plugin.SubscriptionPlugin
java.lang.ClassCastException：org.jivesoftware.openfire.plugin.SubscriptionPlugin 无法转换为 org.jivesoftware.openfire.plugin.SubscriptionPlugin
在 org.jivesoftware.openfire.plugin.subscription.subscription_002dplugin_002dproperties_jsp._jspService(subscription_002dplugin_002dproperties_jsp.java:58)
I' ve installed subscription plugin for openfire and I've made the settings to accept all local subscription request.
However when I try to add a user to my roster it's subscription type still seems 'none' but what I wanted here is as soon as I add a user to my roster it's subscription type should be either 'from' or 'both'. I Think subscription plugin is responsible for that but I dont think its working or I'm missing something
Does anyone know anything about it?
I've also checked the system logs and see the below error:
2012.02.17 16:13:48 org.jivesoftware.openfire.container.PluginServlet - org.jivesoftware.openfire.plugin.SubscriptionPlugin cannot be cast to org.jivesoftware.openfire.plugin.SubscriptionPlugin
java.lang.ClassCastException: org.jivesoftware.openfire.plugin.SubscriptionPlugin cannot be cast to org.jivesoftware.openfire.plugin.SubscriptionPlugin
at org.jivesoftware.openfire.plugin.subscription.subscription_002dplugin_002dproperties_jsp._jspService(subscription_002dplugin_002dproperties_jsp.java:58)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我遇到了同样的问题。在我的具体情况下，订阅插件允许发送和接收请求的域（由 EC2 分配的域）不是我用来连接到服务器的域（这是服务器的 IP 地址）。当我将服务器的域从 EC2 域更改为 IP 地址时，插件按预期响应。
这可能是因为订阅请求以 IP 地址作为域，而插件正在查找来自不同域的请求。这是我的理解，可能是错的。
仅当我将接受标准设置为“仅接受来自同一域”时，我才看到此问题。所有这一切都与 Ryan 的订阅插件有关。
I ran into the same issue. In my specific case, the domain that subscription plugin was allowing requests to and from (a domain assigned by EC2), was not what I was using to connect to the server (which was the IP address of the server). When I changed the domain of the server from the EC2 domain to the IP address, the plugin responded as expected.
This might be because the subscription request comes in with the IP address as the domain, whereas the plugin is looking for requests that come from a different domain. This is my understanding, I could be wrong.
I saw this issue only when I was setting the acceptance criteria to 'Accept from the same domain only'. And all this is with respect to the Subscription plugin by Ryan.