-
a few more things:
- trying to edit basic-conf component throws exceptions:
javax.script.ScriptException: java.lang.Exception: Could not find component class for component: basic-conf javax.script.ScriptException: javax.script.ScriptException: java.lang.Exception: Could not find component class for component: basic-conf …
- while removing component removes it from service discovery it is still present in the list of components to edit/remove (within the script)
--
I've created TTS tests for add/edit/remove but due to limitations of TTS they mostly check whether ad-hoc is at least functioning;
-
OK, CompManager is fixed.
Similar plugin to manage plugins doesn't work as well.
<iq type="set" to="basic-conf@atlantiscity" id="ad47a"> <command xmlns="http://jabber.org/protocol/commands" node="plugin-manager"/> </iq> <iq from="basic-conf@atlantiscity" type="result" to="admin@atlantiscity/Psi+" id="ad47a"> <command xmlns="http://jabber.org/protocol/commands" status="executing" node="plugin-manager"> <x xmlns="jabber:x:data" type="form"> <field type="hidden" var="submit"> <value>submit</value> </field> </x> <actions execute="complete"> <complete/> </actions> </command> </iq>
-
It was working fine until reload of plugins/processors was blocked by additional checking if component is initialized, which allowed reload in plugins only if component was not initialized yet. I changed implementation of plugins reload mechanism to make it work and I fixed root cause for which this condition was added.
-
following scenario:
-
disable plugin (e.g. jabber:iq:version)
-
try to re-enable it
doesn't work and throws Exception:
java.lang.StringIndexOutOfBoundsException: String index out of range: 0 at java.lang.String.charAt(String.java:658) at tigase.server.xmppsession.SessionManagerConfig.getDefaults(SessionManagerConfig.java:227) …
-
Type |
Bug
|
Priority |
Normal
|
Assignee | |
RedmineID |
1563
|
Version |
tigase-server-5.2.0
|
Spent time |
0
|
Issue Votes (0)
Watchers (0)