RE: WebObjects and Javascript Response Rewriter
RE: WebObjects and Javascript Response Rewriter
- Subject: RE: WebObjects and Javascript Response Rewriter
- From: GILQUIN Pierre via Webobjects-dev <email@hidden>
- Date: Fri, 3 Jan 2020 08:57:39 +0000
- Ironport-sdr: XmFO6G1b3TT+yWYTJVOCs/ZcsOFOLeYJq6xIn5DUIfb/j+Hpnt7HW6HZyia66ZV/yAWbDg3UpA h8cBGOEeo85w==
- Ironport-sdr: 7x1LXjrUc0LbVYJ7GS5o3paV1NlzS7zImDsEAVIwu0noYjHCOxgDFB+lF8iJaS5AY6idOjQyi2 C3wmHVG8QNig==
- Thread-topic: WebObjects and Javascript Response Rewriter
Do you have a example application with this approach?
I did a "similar" way but 100% Java using GWT and the WOGWT framework instead
of REST JSON.
The eomodel was used to generate the eo equivalent client class.
The GWT client application used RPC calls to obtain a client objects tree and
save them back on the server.
The transformation between EO server objects into client objects is rather
cumbersome. I would like to try WORest to see if it's make thing easier ...
Pierre
De : Webobjects-dev
[mailto:webobjects-dev-bounces+pierre.gilquin=email@hidden] De la
part de Aaron Rosenzweig via Webobjects-dev
Envoyé : jeudi 2 janvier 2020 20:06
À : Jesse Tayler
Cc : WO
Objet : Re: WebObjects and Javascript Response Rewriter
Sounds like you have your feet straddling two different worlds.
You could consider building parts of your app in pure JS while other parts in
WO. You could do persistence with REST for your pure JS apps that are served by
WORest. You could use JSON web tokens to have authentication that is shared
between the two worlds so that users don’t lose their authentication as they
hop back and forth.
AARON ROSENZWEIG / Chat 'n Bike
e: email@hidden t: (301) 956-2319
On Jan 2, 2020, at 1:47 PM, Jesse Tayler via Webobjects-dev
<email@hidden> wrote:
I see.
Well, that’s a bit of a trick but of course, you can decide what you’d like to
do.
I once realized that my UI elements often needed settings, defaults and
configurations to exist in javascript — it seemed a waste and trouble to create
new components of course, in my case, I use a lot of D2W and did not need
programming outside the regular dev tools — but I did move the css and
javascript additions into D2W rules, which made the component reliable and the
programming of details often a matter of copying configurations you know work
and writing the rule to determine when that script should be placed into the
component.
In your case, it sounds like you might want a way they can write HTML /
javascript components that are pulled from your app and then vended from the
server.
Or better yet, a stub of your page with only the HTML required to jump off a
few queries to render the rest of the page using largely website type tools
with html segments deployed somewhere.
My sense is this would not be clean and likely won’t work out the way you’d
really like it to, but who knows! Your situation might lend itself to some
design choice like these and maybe that works for you.
On Jan 2, 2020, at 1:40 PM, Jérémy DE ROYER <email@hidden> wrote:
Hi Jesse,
for the moment we are using jquery to modify the html code, but after rendering
in the client browser and our front end designers don’t feel like « real »
developpers.
I would like to give the possibility to our front-end (javascript) designers to
add their custom js code without having to change the back end that is all
written in java with webobjects
is this better explained ?
Jérémy
Le 2 janv. 2020 à 19:33, Jesse Tayler <email@hidden> a écrit :
I might be confused —
Don’t you already have control at both ends?
On Jan 2, 2020, at 1:31 PM, Jérémy DE ROYER via Webobjects-dev
<email@hidden> wrote:
Hi all… and Happy New Year !
For this new year, I’de like to add a javascript postprocessor to the
webobjects response.
I mean I would like to give our front-end developpers the possiblity to rewrite
the reponse… before sending it to the customer.
Have any of you already done such a mechanism ?
Jérémy
_______________________________________________
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
_______________________________________________
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