Big thanks for link. I fully agree about self-designed code, but - I see too many information about using httprequest objects in infernet, but found only modifications of 3-4 samles, not full frameworks with wide range of tested clients. Even commercial products, such as ICEFaces project, don't support full range of clients - for example, ICEFaces don't work with firefox 1.06, my favorite browser, and MS IE in My configuration, google products don't work with My pocketPc , JS Library used in sundbox ajax components don't work wit My configuration of MS IE ( support of ActiveX enabled for local intranet only ) etc.
> -----Original Message----- > From: Martin Cooper [mailto:[EMAIL PROTECTED] > Sent: Monday, August 08, 2005 11:06 PM > To: MyFaces Development > Subject: Re: Demo for AJAX faces componets > > > > > On Fri, 5 Aug 2005, ir. ing. Jan Dockx wrote: > > > Sorry, Alexander, on Safari, Mac OS X, it doesn't do didly. > > After a minute, I get a dialog that says "Reqest error, status > : 504Message: > > Gateway timeout". > > This is exactly why I keep trying to encourage people to stop writing > their own custom AJAX comm layer and build on top of something that's > already well tested and robust. ;-) For example, Dojo: > > http://www.dojotoolkit.org/ > > If you pick just the IO profile, you'll have a lightweight and > robust comm > layer to build your apps on. (I'm not saying Dojo is the only > robust layer > around, but there are far more flaky ones than robust ones. ;) > > -- > Martin Cooper > > > > On 5 Aug 2005, at 15:53, Enrique Medina wrote: > > > >> Great example using an AJAX-enabled dataTable. This can be > really helpfull! > >> I think that Martin's students are also working on something similar... > >> > >> Alexander, could you please post some reviews about your > examples, I mean, > >> some kind of explanation of how is it done? Or better a wiki > in MyFaces? > >> > >> 2005/8/5, Alexandr J. Smirnov <[EMAIL PROTECTED]>: > >>> After any little problems, my demo/test application visible from > >>> internet. > >>> You can see it by : > >>> http://smirnov.org.ru/myfaces-ajax/ . > >>> At present, it was tested with Firefox 1.06, Microsoft IE > 6.0 and 5.0 ( > >>> from default install of Windows 2000 ) and Opera 8.02 > >>> I will be very glad for report of success/failure test on > other browsers. > >>> > >>> My skills in JavaScript less then 1 month, but long time I > worked with > >>> java, > >>> c, c++ - as result, I was surprised many times by unexpected > work of any > >>> code... > >>> I don't have any problems for server side part, but need any help for > >>> build > >>> client-side scripts... Most in creating portable code for different > >>> clients. > >>> > >>> ??? > >>> Do you have a demo of this technology up and running? > >>> > >>> Can you start a discussion with code snippets on the mailing > list how you > >>> implemented that? > >>> > >>> How many changes would it take to get My Faces to use your approach? > >>> > >>> regards, > >>> > >>> Martin > >>> > >>> > >>> On 8/2/05, Alexandr J. Smirnov <[EMAIL PROTECTED]> wrote: > >>> I have worked ( as alpha-alpha-alpha .. ) set of custom components for > >>> create AJAX-like user interfaces for Java Server Faces > Applications. Main > >>> idea - in faces lifecycle, ve have view tree on server side > and DOM tree > >>> in > >>> client browser ( at present, saving tree on client side don't > used ). For > >>> ajax request, client send all user input of current form ( as normal > >>> submit > >>> request ). Request phases work as usual, but on render responce phase > >>> server > >>> send ONLY CHANGED parts of view ( i don't create full > compare, but send > >>> only > >>> fo pre-defined parts, or submitted form ). For this I created special > >>> AjaxContainer component, wich render it's children ( or part > of children ) > >>> components. List of clientId's for rendered components included in > >>> response > >>> for client-side part of framework. > >>> For other cases ( for example, such will work in-page Jabber client ) > >>> component can render updated xml in custom Listener, and set > >>> responseComplete to FacesContext. > >>> > >>> On client side, JavaScript get list of rendered parts and > update page DOM > >>> Tree. > >>> In result, we have two-way communications between client > browser and JSF > >>> view, and have sync tree's on client and server side. It's work like > >>> common > >>> desctop applications. > >>> Such arch don't need create special RenderKit or change most of > >>> components - for example, at present, I have only custom > tag's-renderers > >>> for > >>> UICommand ( link & Button ) components, and have worked all > standart and > >>> most of custom ( tree2 and any other Myfaces components ) as > AJAX ... On > >>> other hand, custom renderers based on usual Html renderers, > and work also > >>> in non-JavaScript environment as simple html... > >>> > >>> For client side script use XMLHttpRequest object, and, if it > don't exist, > >>> special "JavaScript"HttpRequest. It's worked same as XMLHttpRequest ( > >>> designed with same properies and methods ), but use other idea. For > >>> perform > >>> request, It appended to page <script> tag. Browser load > script ( url maked > >>> from form action url with query string as normal GET request > ), but script > >>> produced by special Filter on server from Html code of JSF > Response - as > >>> pseudo-Dom tree of objects. Loaded script call handler > function for update > >>> page - same as XMLHttpRequest. Not need any iframe or other > incompatible > >>> technologies for non XMLHttpRequest browsers. > >>> It can work in wide range of browsers, even in 4+ IE & Netscape ??? > >>> ( in theory. At present tested with Mozilla Firefox and IE > 5.5+ browsers. > >>> I > >>> need help for make JavaScript compatible with others. ) > >>> At present, XMLHttpRequest work only in Mozilla. Code for MS > ActiveX was > >>> disabled since I don't can get any functionality of XML part > for microsoft > >>> object ! Xml parsed withowt errors. ( For xml request, i use > in servlet > >>> Filter nekkohtml parser, and make valid xml, with all declarations and > >>> mime-type headers ). It make responseXML Tree, but any methods for > >>> navigate/manipulate don't worked ! Also, elements from > responseXML can't > >>> be > >>> inserted to page, don't produce event handlers etc. > >>> Current view of code repository - > >>> http://svn.demi.spb.ru/repository/myfaces-ajax/ Project created in > >>> Eclipse. > >>> Sorry for possible mistakes - my native language is Russian. > >>> ======================================== > >>> Alexander J. Smirnov > >>> > >> > >> > > Met vriendelijke groeten, > > > > Jan Dockx > > > > PeopleWare NV - Head Office > > Cdt.Weynsstraat 85 > > B-2660 Hoboken > > Tel: +32 3 448.33.38 > > Fax: +32 3 448.32.66 > > > > PeopleWare NV - Branch Office Geel > > Kleinhoefstraat 5 > > B-2440 Geel > > Tel: +32 14 57.00.90 > > Fax: +32 14 58.13.25 > > > > http://www.peopleware.be/ > > http://www.mobileware.be/ > >
