struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillermo Meyer" <>
Subject RE: Struts development methodology
Date Wed, 15 Sep 2004 12:08:17 GMT
We are also working with Struts in a banking application. 
In our case the requeriment was to have skinning capabilities, so we develop
a framework to manage skins and then open sourced it to Xkins (

Our approach is to determine the pieces of the UI. We create a mock page
with all posible combinations and people from graphic designs create that
mock page with all UI elemens. Then, we extract this pieces of pages to
Xkin templates and use taglibs to decorate struts tags in the JSP pages.
These taglibs uses xkins templates. When we need to change a style or a
piece of HTML, we just change the Xkin template. And additionally, if we
need other skin, we create a new one and the application looks completely

Of course, the secret is to determine the "pieces" so that you always can
compose your pages.

Xkins has also XkinsForms that has an implementation of this idea that you
could use and extend to add your own templates.

Xkins templates uses Velocity and you could use other template languages
like groovy or JByte.


>-- Mensaje original --
>Reply-To: "Struts Users Mailing List" <>
>Subject: Struts development methodology
>From:	Victor Grazi <>
>Date:	Tue, 14 Sep 2004 19:28 -0400
>We are developing an important struts application for a major bank, and
>need some advice on methodology...
>Our graphic designers are developing the UI in HTML using Dreamweaver and
>Notepad. (They are gifted artists, but they don't much know about Struts
>We also have Java developers who are concurrently creating the Struts 
>Question is - how do you synch up the work of these 2 teams?
>One approach would be to give the Java team the html pages and have them
>translate the tags to struts. However this becomes difficult to maintain,
>because if the graphics team makes a few small changes, the entire page

>needs to be retranslated to struts.
>Another approach would be to download a Dreamweaver plugin such as FWA

>Visual Struts. We tested that approach and we were actually able to get
>tags to render in Dreamweaver. However the artists always need to view
>pages in MS Internet Explorer before signing off, and since the Java 
>classes don't exist yet, they can't do that.
>We considered another approach where we would create an XSLT transform
>transform the html pages to a struts equivalent, and embed struts specific
>info into the document using some tags that would not be recognizable to
>the browser. However this is difficult since there is not really a 1 to
>correspondence between tags and attributes.
>Ok, so those were our ideas, none of them great.
>So can you give us any advice?
>To unsubscribe, e-mail:
>For additional commands, e-mail:

FiberTel, el nombre de la banda ancha

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message