Re: WOGWT adaptor
Re: WOGWT adaptor
- Subject: Re: WOGWT adaptor
- From: Dan Beatty <email@hidden>
- Date: Fri, 20 May 2011 11:23:34 -0700
- Thread-topic: WOGWT adaptor
Title: Re: WOGWT adaptor
Greetings Chuck,
Yeah, I might be in that category myself (despite the fact that I work for the U.S. Government.)
Also, I tend to treat WO-GWT from a RESTful stand point similar to Pascal’s talk last year with Dojo + ERRest. I have been working on a hybrid, but have never had the funding. I can add that facet to my talk coming up at WOWODC with a few examples from my academic research, if that helps.
I hear there are channels to get DoD persononell to work with non-government entities for common feature projects, but I am not privy to the details. That may be one business item to bring to the table at WOWODC. I can not speak for the government, but I can listen.
Later,
Dan
On 5/20/11 9:56 AM, "Chuck Hill" <email@hidden> wrote:
er, us used contractors. :-P
must have more coffee...
On May 20, 2011, at 9:53 AM, Paul D Yu wrote:
Chuck, US? or used???
Your client should send you and some newbs to WOWODC, Mike.
Paul
On May 20, 2011, at 12:46 PM, Chuck Hill wrote:
On May 19, 2011, at 9:07 PM, Michael DeMan wrote:
Hi John,
Thanks for the follow up.
The bottom line is that for the current contract that I am on, WO is plagued in two (of the same old) areas:
1) Lack of developers. As we all know, its a pretty tiny marketplace. The people generally are top notch, but nonetheless for a large company they need from a risk management perspective to know that they can find people, whether current employees or run over a bus, find more interesting things to do in life - or whatever.
There are still some of use contractors out here. :-)
Chuck
2) Lack of client side stuff. I personally have steered clear of _javascript_ since when Netscape first prefixed the name 'java' onto their client-side browser scripting technologies. Nonetheless, for large companies and for internal-only back office operations, it is nice to be able to deliver quasi-native-desktop application working environments to folks within the browser with minimal risk to core functionality. It seems that GWT is relatively mature now and is possibly a solution for the work scenario I am in.
I will also follow up with you off-list within the couple of days. Again, thank you for the follow up.
- mike
On May 19, 2011, at 8:24 PM, John Huss wrote:
I don't think it's actively maintained. I started a project called WOGWT (also on google code); it's out of date, but newer than this one.
It really depends on what you need because you can communicate with a WO server in many possible ways:
1) JSON/XML via direct actions
2) JSON/XML via REST
3) JSON/XML via component actions
4) RPC via direct actions
5) RequestFactory somehow
For JSON or XML you don't really need anything specific to GWT on the server.
For RPC, WOGWT has a request handler you could use.
RequestFactory is the newest RPC method in GWT and could be very useful, but I haven't heard of anyone integrating it with WO yet.
What are you looking to do?
John
On Thu, May 19, 2011 at 7:18 PM, Michael DeMan <email@hidden> wrote:
Hi All,
Does anybody know status on the WOGST adaptor (is it reliable/well designed?) - or is there another standard technique to use to be able to utilize GWT on the client side with WebObjects on the back end?
http://sites.google.com/site/wogwtadapter/
Thanks,
- Mike DeMan
_______________________________________________
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