Re: How to get ServletContext, HttpServletRequest, HttpServletResponse from WOContext, WORequest and WOResponse ?
Re: How to get ServletContext, HttpServletRequest, HttpServletResponse from WOContext, WORequest and WOResponse ?
- Subject: Re: How to get ServletContext, HttpServletRequest, HttpServletResponse from WOContext, WORequest and WOResponse ?
- From: Timo Hoepfner <email@hidden>
- Date: Tue, 8 Sep 2009 17:15:52 +0200
For integration of WO with Flash/Flex, you might want to take a look
here: http://www.intellicore.info/wox
What is Wox
Wox stands for WebObjects/FleX. This project tries to bring the ease
of use, the power and effectiveness of WebObjects to Flex/AIR
lightweight client. It is a developer framework which allows to
easily manipulate enterprise objects between a server and a client,
offers remote method invoking, classical EOF-like features and more.
It consists of two parts: - Wox4f for Flex client-side - Wox4j for
Java WebObjects server-side
Each part implements the necessary code to allow the developer quick
and efficient work without plunging him into low-level serialization
mechanics and expensive configuration. Even if this framework is
heavily oriented towards WebObjects developers, any Java/Flex
developer might be interested in Wox as an introduction to the
proven robustness and ease of use of WebObjects (WebObjects is the
Java engine behind the Apple's own website, iTunes Music Store,
iPhone AppStore, BBC News, Disney WorldWide Reservations, U.S.
Postal, among many others).
Wox's Goals
Wox's aim is to gain advantages both from a visually appealing
client (Flex) and an improved backend server (WebObjects). The Wox
team has the feeling there will be huge need of such technologies,
which will allow seamless integration of the nice and the powerful.
We've tried to push the integration beyond the Flex's standards and
implemented what one could call 'very light client-side EOF'. That
way all WebObjects developers will feel friendly with enterprise
object's manipulation when in Flex code. Wox is another solution for
client-side projects, together with Ajax (Wonder), JBND, JPBindings...
Main features
* EOF-like Flex object manipulation: fetchspecification,
DataContext, DataObject, saveChanges, ...
* GraniteDS serialization: much faster than traditional XML/SOAP
communications
* Standard WebObjects sessions management
* Remote method invocation: fetchObjectsWithNamedFetchSpecification,
invokeServerSideMethod, ...
* Client-side automatic fault handling (toOne, toMany)
* Flex classes and subclasses templates (eogen)
Current status
Wox is in a usable and stable version, though it is a work in
progress. Users are expected to experience both bugs and awaited
features; it is actually used by several real sized projects under
construction.
The source code is available for download under LGPL. You can
connect as anonymous to the subversion repository to checkout the
freshest version here:
http://www.intellicore.info/wox/repos/releases/0.9
Best regards, The Wox Team
Timo
Am 08.09.2009 um 15:41 schrieb Matthieu Segret:
Hi,
I need to access to the three objects ServletContext,
HttpServletRequest and HttpServletResponse in order to use a library
correctly (GraniteDS). However, I can only access to WOContext,
WORequest and WOResponse with WebObjects.
I used a WOServletContext object from a WORequest, to have the
ServletContext, HttpServletRequest and HttpServletResponse objects I
want. Actually, it's not sufficient to use a WOServletContext
because the userInfo dictionary from the WORequest is null by default.
I'm working with WebObjects 5.3 (without Wonder). Am I in the right
way? if not, what have I to do?
Matthieu Segret
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden