Hmm.. this sound like a lot of work for the "Framework/HTML/User interface" guy considering the user- and presentation-intensive kind of pages nowadays ;-)
And that's precisely what happens in practice; in fact that was also my point in the previous message. Working with JSPs (and Servlet / Action as controllers for the views) requires "Framework/HTML/User interface persons" (aka java web developers which are supposed to be experts in HTML, JSP and Servlets) to solve common web applications problems.
It's also true that Struts makes easier much of these aspects, but still...
At 21:13 11.03.2005, you wrote:
We don't even try to have the development people do the web page. In theory the process is:
1. Framework/HTML/User interface person creates an HTML version of the page that includes as manny of the options and alternatives as possible.
2. Application developer builds the business logic and controller to build the functionality. Along the way, the static HTML page is transformed into a JSP page.
3. First person then does final tweaks and maintenance on the JSP page.
In practice, there are mutliple iterations of this, and I couldn't conceive of it working unless the framework person and the developer person work well together and are close both in the organization chart and geographically.
Mark Benussi wrote:I agree, a good J2EE developer can take a UI from a designer (A Photoshop file or the like) and return a pixel perfect html representation as well as meeting the MVC business requirements. -----Original Message----- From: Radu Badita [mailto:[EMAIL PROTECTED] Sent: 11 March 2005 17:20 To: Struts Users Mailing List Subject: Re: Typical Struts development team and distribution of tasks?
Good question!
I barely can wait for answers from the other guys out there; cuz in what I saw so far, the Java Developers are supposed to be able to turn static visual models (often not even html) into Struts web applications, finding "clever" solutions (usually good ol' javascript) to UI designs that don't account for the nature of web applications (request/response interactions).
So a Java [web] Developer must know a lot of html, css, javascript (and of course Struts tags / JSTL) or at least enough to know where to find solutions to particular problems...
On the other hand, I'm just starting with Tapestry right now and beginning to see that it could really make possible starting with a static html design of a UI and "enhancing" it to become a dynamic web app. Also it provides an almost event-driven kind of framework... Also note that Shale is supposed that will support pretty much of the same design (components and events, but without the almost pure html templates), and even better, support for dialog-like interactions across multiple requests.
At 18:38 11.03.2005, you wrote:
Do most companies developing Struts applications tend to employ Web Designers, or is it more common for Struts development to be undertaken by a team consisting solely of Java Developers (who therefore need strong knowledge of HTML, Struts Tags, JSTL, CSS, JavaScript, etc as well asJ2EE)?
Along the same lines... If you are working in a mixed team of Web Designers and Java Developers, what is the best way to divide up Struts (+ Tiles) development between these groups?
The reason I ask these questions is that the vast majority of my previous experience has been in back-end development (EJB, JMS, ORM, RDBMS, etc), and now that I am learning Struts I am more than a little bit confused as to what I'd be expected to know for the average Struts job...
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Neil Erdwien, [EMAIL PROTECTED], Web Technologies Manager Computing and Network Services, Kansas State University
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
