On Mon, 4 Sep 2000, Billy Donahue wrote:
> I've been working with JSPs lately, and I'd use something like:
>
> <jsp:useBean name="someIterator" type="java.util.Iterator">
> <dadadada:iterator iterator="<%= someIterator %>">
> <table>
> <tr>
> <th>Name</th>
> <th>Address</th>
> </tr>
> <dadadada:iteratorLoop id="x" type="dadadada.someapp.SomeBeanClass" >
> <tr>
> <td><jsp:getproperty name="x" property="name" /></td>
> <td><jsp:getproperty name="x" property="address" /></td>
> </tr>
> </dadadada:iteratorLoop>
> </table>
> </dadadada:iterator>
>
> Which is close enough to HTML that the HTML people should understand it.
> You never really have to "break character" while writing presentation
> pages. I prefer the custom tags approach to the embedded code approach..
> See, in Java you're better off having a servlet set up the 'beans' for
> the JSP, and then invoking the 'dumb' JSP to present them. The logic is
> in the servlet, and the JSP imports the results with useBean statements.
> The designers never have to tiptoe around the logical work, they only
> edit the JSP files.
>
> That said, I am a mod_perl novice, and I don't know if there's anything
> equivalent or better than this in the mod_perl world.
Well to stick the AxKit oar in, yes, of course there's something better...
In AxKit your developers design custom "taglibs" that allow you to design
your own tags however you want them to appear. There's a built in taglib
for SQL, which allows you to produce XML from a DBI database, but writing
taglibs is relatively easy. Once you've written the taglib, its just a
drop-in component that your designers can use. And they don't need to know
anything about these vegetables you speak of... :-)
--
<Matt/>
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org | AxKit: http://axkit.org
