The truth is, I want both Struts and JSF in my toolbox. I don't want one to supplant the other.
I have a couple of JSF questions.
1) I do a lot of Swing work with some HTTP-based services (some with a human interface, some with a programmatic interface) mixed in with other services that use other protocols. To do the HTTP stuff, I am interested in a killer, but focused, controller. I just don't need "web services" proper and a bunch of XML bloat, and I don't need tag libraries, for what I'm talking about. Struts 1.3 CoR controller looks promising in this aspect. Can JSF help me in this aspect? If not, you see how JSF is not a replacement for Struts, in my world (or in one of my worlds).
2) At first, and second, glance, JSF looked to me like the ultimate tag library (obviously I'm not looking deep enough). That's great for when I'm doing tag-centric development, but that's just one aspect of my development. I see that JSF claims to be independent of HTTP/HTML. Can JSF express view-control logic that I can use as the backbone for putting an HTML interface as well as, say, a Swing interface, on the same application? If not, could you give me an example of what the independence from HTTP/HTML buys me? This is the thing I'm more curious about than anything.
The thing I am trying to avoid is investing in code that is tied to Internet Explorer or Mozilla -- in particular, to JavaScript. A timeless Web app or view-control framework for me will offer *adapters* for those browsers, and those adapters might be implemented with JavaScript, but the framework won't be focused on them, and the author(s) will look at the JavaScript adapters as something that makes the framework a reality for now but can be replaced easily when better browsers and browser APIs come along.
Thanks, Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
