| 
| Servlet Context Integration [message #69023] | Sun, 06 January 2008 19:32  |  | 
| Eclipse User  |  |  |  |  | Originally posted by: rafaelubaldo.mac.com 
 Eclipse Community,
 
 I am a Mac "fan boy" and Steve idolizer, and IntelliJ loyalist. Now that we
 got that out of the way...elbow. I don't use Eclipse and I have not take a
 serious look at it since the days when it did not run correctly on a Mac.
 Does it now? Prompted by the rabid enthusiasm of a colleague, I downloaded
 the latest release to check out RAP.
 
 I've been sitting in this chair for the 4 hours gleaming with enthusiasm and
 noxious intrigue. I think this is the project I have been looking for coming
 over from the Lazlo cult. Please check my coat, I'm going to make myself at
 home.
 
 As I was recently introduced to RAP (and reintroduced the Eclipse platform
 in general) I have a lot courting to do the platform. I'm struggling to
 understand RAP's relationship to, and interoperability with, other resident
 JEE components, though I must say the niche or shall as grand "vista" that
 is fills with glorious Web 2.0 potential good ness is overwhelming evident.
 The ecosystem has a new 800 pound gorilla on the prowl.
 
 A few questions if thou unknown will indulge me:
 
 [1] Given RAP applications execute primarily on server side and in part on
 the client side, what portion of the application actually lives where once
 coded and rendered useful by RWT?
 
 [2] How susceptible are portions of the client side code to state tampering
 and possible allowance of request spoofing by design? What's the scoop on
 security?
 
 [3] Can RAP applications communicate with the host application server
 possibly received resource injection or making use of other JEE server
 features?
 
 [4] Can RAP applications live in JSP pages as embedded components, whether
 autonomous or collaboratively, or safely obtain a reference to the servlet
 context?
 
 [5] Scrap the work bench concept. It's too desk top centric (but I guess
 that's the point). What if there was RAP portal-like architecture? Something
 like the Eclipse Enterprise Portal Container. I saw something similar which
 was called the Rich Server Platform. The notion of plug-ins in web
 applications is very exciting to me. I've ate dinner sketching out the
 possibilities of RAP portal container. Are there any thoughts out there
 about RAP interoperability with JSR-168/WSRP containers and the
 possibilities?
 
 [6] Has anyone else considered the possibilities of implementing RWT as XUL,
 Adobe Flex, or Microsoft XAML? I am particularly interested in implementing
 the Flex layer. RAP has the function. Now it needs the form, ergo a more
 robust themes API that can bring applications alive and allow them to look
 less like an IDE or Windows 2000 artifact (I've had my good eye on SWT
 Cocoa). Haw does RAP compare and fair to other so called Web 2'oh frameworks
 and other AJAX lime-lights like Spry?
 
 Thanks in advance for your input and advice. I look forward to contributing.
 
 Regards,
 Rafael
 |  |  |  | 
| 
| Re: Servlet Context Integration [message #70069 is a reply to message #69023] | Tue, 15 January 2008 03:29  |  | 
| Eclipse User  |  |  |  |  | Originally posted by: fappel.innoopract.com 
 Hi Rafael,
 
 thanks for your interest in RAP. See the answers to your questions below.
 
 
 Ciao
 Frank
 
 
 "Rafael.Ubaldo" <rafaelubaldo@mac.com> schrieb im Newsbeitrag
 news:C3A6DD30.15F%rafaelubaldo@mac.com...
 > Eclipse Community,
 >
 > I am a Mac "fan boy" and Steve idolizer, and IntelliJ loyalist. Now that
 > we
 > got that out of the way...elbow. I don't use Eclipse and I have not take a
 > serious look at it since the days when it did not run correctly on a Mac.
 > Does it now? Prompted by the rabid enthusiasm of a colleague, I downloaded
 > the latest release to check out RAP.
 >
 > I've been sitting in this chair for the 4 hours gleaming with enthusiasm
 > and
 > noxious intrigue. I think this is the project I have been looking for
 > coming
 > over from the Lazlo cult. Please check my coat, I'm going to make myself
 > at
 > home.
 >
 > As I was recently introduced to RAP (and reintroduced the Eclipse platform
 > in general) I have a lot courting to do the platform. I'm struggling to
 > understand RAP's relationship to, and interoperability with, other
 > resident
 > JEE components, though I must say the niche or shall as grand "vista" that
 > is fills with glorious Web 2.0 potential good ness is overwhelming
 > evident.
 > The ecosystem has a new 800 pound gorilla on the prowl.
 >
 > A few questions if thou unknown will indulge me:
 >
 > [1] Given RAP applications execute primarily on server side and in part on
 > the client side, what portion of the application actually lives where once
 > coded and rendered useful by RWT?
 >
 RAP applications are in fact server-application with a thin client
 front-end. The thin client uses rich components and AJAX to provide a good
 user experience. This means that data models, program logic etc. resides on
 the server. As the requests between client and server transfer the UI-state
 changes only, the content-length of those requests are generally very small.
 The combination of the fast response time with the rich javascript widgets
 is the base concept the RAP web-workbench relies build on.
 
 > [2] How susceptible are portions of the client side code to state
 > tampering
 > and possible allowance of request spoofing by design? What's the scoop on
 > security?
 >
 We addressed this subject shortly before the 1.0 release. The outcome was
 that the RAP architecture itself avoids a lot of the known security problems
 of javascript based applications. So there were only a few additional lines
 of code necessary to close the rest. I don't want to pretend to be an expert
 on this, therefore I leave it with this superficial answer.
 
 > [3] Can RAP applications communicate with the host application server
 > possibly received resource injection or making use of other JEE server
 > features?
 >
 Sorry, I don't quite understand the question. Maybe there's a
 misunderstanding that RAP applications provide some kind of client side
 autonomy, which is not the case.
 
 > [4] Can RAP applications live in JSP pages as embedded components, whether
 > autonomous or collaboratively, or safely obtain a reference to the servlet
 > context?
 >
 In principle it is possible to embbed a RAP application in a JSP-page but I
 think the usefulness of this approach is limited. You could think of it as
 an applet running in a web-page. The other way around - embedding JSP pages
 into RAP applications - is the more common approach. Communication between
 RAP and JSP can be achieved using the common infrastructure of the web
 application (servlet-context, sessions etc.).
 
 > [5] Scrap the work bench concept. It's too desk top centric (but I guess
 > that's the point). What if there was RAP portal-like architecture?
 > Something
 > like the Eclipse Enterprise Portal Container. I saw something similar
 > which
 > was called the Rich Server Platform. The notion of plug-ins in web
 > applications is very exciting to me. I've ate dinner sketching out the
 > possibilities of RAP portal container. Are there any thoughts out there
 > about RAP interoperability with JSR-168/WSRP containers and the
 > possibilities?
 >
 The workbench concept is one possibility using the technology. You can use
 RAP and the bundle mechanism (plug-ins) provided by the Equinox
 infrastructure without workbench. It is even possible running RWT
 standalone. Regarding RAP and Portlets you may have a look at
 http://dev.eclipse.org/newslists/news.eclipse.technology.rap /msg00021.html.
 
 > [6] Has anyone else considered the possibilities of implementing RWT as
 > XUL,
 > Adobe Flex, or Microsoft XAML? I am particularly interested in
 > implementing
 > the Flex layer. RAP has the function. Now it needs the form, ergo a more
 > robust themes API that can bring applications alive and allow them to look
 > less like an IDE or Windows 2000 artifact (I've had my good eye on SWT
 > Cocoa). Haw does RAP compare and fair to other so called Web 2'oh
 > frameworks
 > and other AJAX lime-lights like Spry?
 >
 Here are some thoughts on this:
 http://dev.eclipse.org/newslists/news.eclipse.technology.rap /msg01429.html.
 
 > Thanks in advance for your input and advice. I look forward to
 > contributing.
 >
 > Regards,
 > Rafael
 >
 >
 >
 >
 >
 >
 >
 >
 >
 |  |  |  | 
Powered by 
FUDForum. Page generated in 0.02836 seconds