This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[#200601251500; modules of collab from NB UC 50 Beta] 1.Create public conversation 2.Open created conversation 3.Write message and push Send button No feedback appears. The text just disappears from the edit window, but the window with conversation stack is blank.
The problem seems to be that the conversation is created as read-only. If you leave the conversation, manage it to make it read-write, then rejoin it, everything works as expected. Hardly P1. Workaround exists and creating (named) conversation is not a key feature.
> The problem seems to be that the conversation is created as read-only. Yes, it looks like. I have to say, each user expect, that once you are owner (or you created something), you have permision to do what it's supposed to be for. > If you leave the conversation, manage it to make it read-write, then rejoin > it, everything works as expected. So your proposed workflow is: 1. create Conversation 2. manage default to read-write 3. unsubscribe conversation 4. open the same conversation once more ... really very intuitive ;( > Hardly P1. I don't think so, from any point of view, it's P1. You are not able to work with conversation if you are the owner ! > Workaround exists Nothing to say, probably I don't think we can call steps above by word "workarround". > and creating (named) conversation is not a key feature. Well, so just to be sure, what are the key feature(s) of Collaboration module?
I forgot to mention, P1 or not ... this issue is stopper for 5.0 .
Investigating...
So the message is actually both sent and received. It just gets lost somewhere during routing inside collab code. > So your proposed workflow is: > 1. create Conversation > 2. manage default to read-write > 3. unsubscribe conversation > 4. open the same conversation once more In fact, it is enough to just create, leave and join again, no need (for this particular case) to adjust privileges. But in reality, you'll change the rights to r/w anyway most of the time, as "moderated" (i.e. generally read only) forum is usefull only in few very specific cases, so we should change the default access rights as well.
There was a hidden NPE deep inside the collab code (just another "catch (Exception e) {}"), which blocked a handful of other post-creation setup. The proper behaviour is: Create the conversation. Open the conversation management so you can adjust requested access rights. Join the conversation once you finish managing it. I probably have a fix.
Fixed in trunk: collab/ui/src/org/netbeans/modules/collab/ui/DefaultUserInterface.java,v1.10 dev AU: Collab/UI v1.4
Backported to release50: collab/ui/src/org/netbeans/modules/collab/ui/DefaultUserInterface.java,v1.8.2.2 5.0 beta AU: Collab/UI v1.1.2
It works fine in fcs build of 5.0 + .nbms from update center downloaded today (2006/03/22).