On Wed, May 24, 2006 1:09 pm, Ian Roughley wrote: >> I wonder about the response though... one thing I've found is that >> people >> for some reason, generally anyway, don't realize that they can use a JSP >> to render an Ajax response. Maybe all the examples they see shows the >> response being constructed manually in a servlet or Action and they >> figure >> that's what you have to do. I mean, constructing JSON or XML in a JSP >> is >> childs' play, and you get the benefit of being able to use all the same >> tags you use to create an HTML response. I wonder if it might be >> sufficient to simply demonstrate this to people and make it more >> well-known, rather than writing anything to do it specifically, and then >> getting into new result types and all that? What do you think? >> > True, but it would be nice if a pre-determined XML structure or JSON > could be automatically generated by using the model from the ModelAware > interface. It would lower the entry point for people using the feature.
I hear you. In that case, I would suggest focusing on JSON... with XML, you really do have to pre-determine the schema, but with JSON that shouldn't be an issue since it's just a representation of the internal object graph of a given object. Might make it easier to get the feature implemented initially, and then expand it later to XML or whatever else. Just a thought. > I sat in on the google presentation on this at J1. The feeling I get is > that GWT is for constructing entire application rather than for > individual components, and it ties in heavily to the custom logic. I > need to look into it further though. It's funny... when I first saw the GWT announcement, I remember looking at it and thinking "eh, big whoop". Then I see everyone everyone saying how it's the greatest thing since sliced bread... well, either it's just Google fanboyism, or I missed something :) So I'm in the same boat as you, I need to take a further look. I was just raising it because someone raised it to me. I do think however that a widget object model would be a very nice thing to have, and I think would jive with what you were talking about early in terms of using DWR for widgets... I've always felt that Struts was way too thin in what it offered on the client, something Webwork is already a big improvement in, so taking it further seems naturaly. It seems to me that that would be easier to do if there was a known component model to write widgets to. Maybe Don's work with getting JSF component in is the answer, maybe a whole new object model, maybe some other existing answer, I don't know. >>> /Ian Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
