In fact we don't need REST/SOAP to access data inside Wicket. Wicket is another JEE bean inside same tomcat and same context.
If you take a look at current Admin/Users page it uses UserDAO only. Edit will be implemented the same way. Users entity will be used as Model object. It will be changed in the form and all changes will be reflected by Wicket, all we need is perform em.merge using UsersDAO. I'll try to make skeleton of all areas ASAP. I saw good Jquery plugin for calendar. On Thu, Sep 6, 2012 at 4:20 PM, [email protected] <[email protected] > wrote: > I think we can implement everything except the conference room itself > in the first iteration of the Ajax interface. > There are only some limited real-time communication areas outside of > the conference room. > My idea was to refactor everything except the conference room to > Ajax/JavaScript. > That way we get comfortable with the new framework and we can already > test/implement some basic functionalities with WebSockets. > Based on our experiences we can then in the second iteration start > refactoring the conference room itself to Ajax. > > For the first iteration I would suggest we use the existing SOAP/REST > API of openmeetings to generate regular HASHs like the "secureHash" to > enter a conference room. > We will have to add one more SOAP/REST call where it is possible to > not only set an external but also internal user id so that the user > does not get duplicated when he enters the conference room. > I can implement such functionality into the SOAP/REST API when we will > need it. > I think it should be possible that the client directly invokes the > REST API as it is situated on the server URL, there should be no > Cross-Site-Scripting issues. > > We just need to make sure that we keep in mind that in the second > iteration the conference room will be loaded into our Ajax interface. > > What do think about that? > > Sebasitan > > > 2012/9/6 Maxim Solodovnik <[email protected]>: > > @Sebastian > > Alexey asks for room user list implemented in wicket. > > What do you think is this possible? > > > > Also could you tell me is this possible to "enter the room by public SID" > > i.e. in Wicket I work with DB and I would like to open the room for the > > current user. > > I can create SID for the user and need mechanism to open the room. > > > > Right now I'll try to > > 1) display room list > > 2) add couple of editable fields to the user > > 3) implement chat (able to send receive messages) > > > > > > On Thu, Sep 6, 2012 at 3:54 PM, [email protected] < > [email protected] > >> wrote: > > > >> I will test as soon as possible > >> > >> Btw: Reading the release notes of Wicket 6.0.0: > >> > >> > https://cwiki.apache.org/WICKET/migration-to-wicket-60.html#MigrationtoWicket6.0-UseJQueryasabackinglibraryforWicketAjaxfunctionality > >> > >> Wicket now natively uses jQuery for Ajax. This should be quite handy > >> for us as we decided to use jQuery anyway! > >> > >> Sebastian > >> > >> 2012/9/4 Maxim Solodovnik <[email protected]>: > >> > Just commited improved Wicket app > >> > > >> > What was improved: > >> > 1) Application is now single paged > >> > 2) Application is available at > >> > http://localhost:5080/openmeetings/html(both old and new apps are > >> > accessible) > >> > 3) Only 1 menu item works as expected (Admin Users) > >> > > >> > What is not done > >> > 1) bookmarkable params need to be added (gmail style) > >> > 2) some more pages (available to USER not ADMIN) > >> > 3) functionality to edit User/handle errors > >> > > >> > any feedback is appreciated > >> > > >> > On Wed, Sep 5, 2012 at 12:35 AM, Raju Bitter < > >> > [email protected]> wrote: > >> > > >> >> Just a comment on using OpenLaszlo: Seeing that Gliffy > >> >> http://www.gliffy.com essentially rebuilt their HTML5 version of the > >> >> software not using OpenLaszlo, I don't know any major software > product > >> >> using the DHTML runtime besides what Laszlo does with Webtop (and I > >> >> still have to see a public version of Webtop running in DHTML in > >> >> production). I agree with Sebastian that it would be more future > proof > >> >> for OpenMeetings to not use OpenLaszlo for the HTML5 version of > >> >> OpenMeetings, unless there is any willingness to become involved with > >> >> DHTML runtime support - which is not very advisable for this project. > >> >> > >> >> - Raju > >> >> > >> > > >> > > >> > > >> > -- > >> > WBR > >> > Maxim aka solomax > >> > >> > >> > >> -- > >> Sebastian Wagner > >> https://twitter.com/#!/dead_lock > >> http://www.webbase-design.de > >> http://www.wagner-sebastian.com > >> [email protected] > >> > > > > > > > > -- > > WBR > > Maxim aka solomax > > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > [email protected] > -- WBR Maxim aka solomax
