German, I see you've added a build file. Great. Just one point - I used "main" subdirectory to be compliant with maven directory structure. If you put build file inside main, there is no point of having main.
Vieri, jitsi invitations won't work with 1.9 release. We changed openmeetings on our side to provide invitation hashes for jitsi. Which version are you using? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Jul 11, 2012 at 11:13 AM, German Grekhov <[email protected]> wrote: > Hello, Vieri. > > My name is German. I am familiar with Alexei and I also take part in > development of the Openmetings plugin for Jitsi. > > The current version of the plugin has own settings tab in the advanced Jitsi > settings. These settings allow a user to set up Openmeetings server, > username and password. So, there are no any hard-coded test servers in the > plugin. > > The current code of the plugin is available here: > http://svn.apache.org/repos/asf/incubator/openmeetings/trunk/plugins/jitsi/main/ > > It will be great if you and your teammates look through this code, try to > execute it and tell us your comments. It will help a lot for making this > plugin better and integrating it faster to the Jitsi trunk. > > Best regards, > German Grekhov > Openmeetings developers team > > > 11.07.2012 13:58, Vieri пишет: > >> Hi, >> >> Personally I never got the plugin working. >> I configured it to use the openmeetings test server at >> http://188.127.229.12:5080/openmeetings (user/pwd: test/test). >> >> When I select the "invite to conference" from the drop-down menu I get the >> following error: >> >> URL = http://188.127.229.12:5080/openmeetings/services/UserService?wsdl >> null >> null >> 08:29:55.471 GRAVE: util.UtilActivator.uncaughtException().88 An uncaught >> exception occurred in thread=Thread[AWT-EventQueue-0,6,main] and message >> was: null >> java.lang.NullPointerException >> at >> net.java.sip.communicator.plugin.openmeetings.OpenmeetingsPluginMenuItem.actionPerformed(OpenmeetingsPluginMenuItem.java:63) >> >> So this is failing in OpenmeetingsPluginMenuItem.java, actionPerformed: >> invitationUrl = OpenmeetingsConfigManager.getInstance().getInvitationUrl( >> OpenmeetingsConfigManager.getInstance().getLogin() ); >> >> Alexei, you say it works for you. Are you running the code from this site >> or have you taken it from somewhere else or patched it? >> http://svn.apache.org/viewvc/incubator/openmeetings/trunk/plugins/jitsi/ >> Can you send a test invitation to http://188.127.229.12:5080/openmeetings >> (test/test)? >> >> Thanks, >> >> Vieri >> >> --- On Tue, 7/10/12, Emil Ivov <[email protected]> wrote: >> >>> Thanks Alexei, >>> >>> On 08.07.12 14:11, Alexei Fedotov wrote: >>>> >>>> JFYI folks, >>>> >>>> The plug-in reference appeared here first: >>>> http://comments.gmane.org/gmane.comp.voip.sip-communicator.devel/12854 >>> >>> Thanks for the ref, and sorry again for scoling you >>> wrongfully. >>> >>>> Though I believe that the proper place for jitsi plugin >>> >>> is jitsi code >>>> >>>> base, I put it here just for the reference: >>>> http://svn.apache.org/viewvc/incubator/openmeetings/trunk/plugins/jitsi/ >>> >>> Yup, we should probably think about integrating this at some >>> point. I >>> suppose a good first step would be to make sure it is >>> compatible with >>> Jitsi's code conventions (i.e. all methods with javadocs, >>> start imports, >>> accolades on their own line, asterisk imports, using spaces >>> rather than >>> tabs, not exceeding column 80 and such, Jitsi license >>> headers and such). >>> >>> Also, is the plugin stable already? I saw a few things >>> looking weird >>> here and there, like for example: >>> >>>> public static IvParameterSpec iv = >>> >>> new IvParameterSpec(new >>>> >>>> >>> >>> byte[]{1,2,3,4,5,6,7,8}); >>>> >>>> private static String xform = >>> >>> "DES/CBC/PKCS5Padding"; >>>> >>>> //private static SecretKey key; >>>> public static SecretKey key = new >>> >>> SecretKeySpec(new >>>> >>>> >>> >>> byte[]{1,1,1,1,1,1,1,1},"DES"); >>> >>> >>> >>> Cheers, >>> Emil >>> >>> >>> >>>> Maybe the plug-in is already published somewhere. >>>> >>>> -- >>>> With best regards / с наилучшими >>> >>> пожеланиями, >>>> >>>> Alexei Fedotov / Алексей Федотов, >>>> http://dataved.ru/ >>>> +7 916 562 8095 >>>> >>>> >>>> On Sun, Jul 8, 2012 at 2:57 PM, Alexei Fedotov >>>> <[email protected]> >>> >>> wrote: >>>>> >>>>> [added openmeetings-dev] >>>>> >>>>> Hello folks, Elena, >>>>> >>>>> I have just tried Apache Openmeetings plug-in. >>> >>> First nice thing I've >>>>> >>>>> noticed - it works! Thanks, Elena, for the great >>> >>> job! BTW, is the code >>>>> >>>>> in the project SVN somewhere? >>>>> >>>>> I faced the following problem with existing >>> >>> solution for a particular >>>>> >>>>> corporate network setup. The company where I've >>> >>> installed jitsi uses >>>>> >>>>> web proxy for 80 port, and has direct access for >>> >>> other ports. This is >>>>> >>>>> likely used for filtering web pages contents, so >>> >>> there is some >>>>> >>>>> justification for such approach. >>>>> >>>>> By default the plugin does not work for this case, >>> >>> because it has both >>>>> >>>>> SOAP calls to openmeetings server and jabber >>> >>> exchange to set up a >>>>> >>>>> conference. The former should be proxied, and the >>> >>> latter shouldn't. >>>>> >>>>> I've just hardcoded the following in >>> >>> OpenmeetingsPluginSoapClient >>>>> >>>>> constructor, and get things working. >>>>> >>>>> >>> >>> System.getProperties().put("proxyHost", >>> ...); >>>>> >>>>> >>> >>> System.getProperties().put("proxyPort", >>> ...); >>>>> >>>>> That's not very beautiful code. I'm trying now to >>> >>> figure our how the >>>>> >>>>> correct product solution would be for this case. >>> >>> Would you please >>>>> >>>>> answer some questions? >>>>> >>>>> 1. >>>>> The first thing to improve is to avoid changing >>> >>> global properties. >>>>> >>>>> SOAP library documentation on .call method is not >>> >>> very explicit on how >>>>> >>>>> to make proxied calls. Is there any working example >>> >>> around? >>>>> >>>>> 2. >>>>> If I set up global proxy, than jabber stops working >>> >>> because it starts >>>>> >>>>> using proxy. Should we use a "hacked" version for >>> >>> our case with >>>>> >>>>> hardcoded settings, or implement a special >>> >>> configuration for this >>>>> >>>>> case? >>>>> >>>>> Thanks in advance! >>>>> >>>>> -- >>>>> With best regards / с наилучшими >>> >>> пожеланиями, >>>>> >>>>> Alexei Fedotov / Алексей Федотов, >>>>> http://dataved.ru/ >>>>> +7 916 562 8095 > > > > -- > Best regards, / С наилучшими пожеланиями, > German Grekhov / Герман Грехов >
