Well, <%= %> doesn't really clutter your code....
Actually, what I personally prefer, after all the custom tags are said
and done, is to do this:
<% String myValue = request.getAttribuite"aksjhdkjahsd"); %>
<html stuff>
<a href="<%= myValue %>/link.html">Cool Link</a>
However, all this is beside the point for dynamic content.
What I like is that TC4 finally supports dynamic includes.
<jsp:include page="/WEB-INF/include/main_template.jsp" flush="false" />
I don't know what you designers use, but mine use Dreamweaver, and so
far it has not been able to support resolving these things. And Short
of integrating with Tomcat, I don't think It could. The best we've
gotten that it knows about shtml and apache includes. So You have the
designer use dynamic includes when they give you a new template.
I think the problem is that the wysiwyg tools are not integrated with
the concept of JSP development. Dream weaver seems to be moving there,
but with their purchase of JRun, I wonder if BEA etc are going to be
leary of contributing to a competitor.
Adam
Jeffrey Bonevich wrote:
>
>
> Joseph Barefoot wrote:
>
>>> Hm. Seems to me that if you have done your configration correctly and
>>> published the content that is available to the designer, they should
>>> have no problem using URL-bases from your configuration content. Maybe
>>> I have jsut made it too easy on myself and the designers I have worked
>>> with in the past.
>>>
>>
>> I believe we are talking about two different things here; I mean the
>> kind of
>> URL re-writing that attaches the sessionID in the event that the client
>> browser has cookies disabled. Nice of you to keep your designers in
>> mind
>> while architecting a site though--I think way too many programmers
>> look at
>> designers with disdain ("You can't write/read code? Oh, the horror! ).
>
>
>
> Yes, I was missing that point. However, I can still accomplish this
> very easily:
> <a href="{{config.requestURL}}/mypagehandler{{session.urlId}}">link</a>
>
> Here config and session are objects (in this case a HashMap and an
> HttpSession), upon which a key or method call is made to provide the
> data. In the case of session, our engine resolves "urlId" to one of
> three possibilities: (1) a map key (session.get("urlId")), (2) a
> getter method (so session.getUrlId()), or (3) an actual method call
> (so session.urlId()). We also account for object adapters to direct
> the dynamic resoltion of the data; so the developer can provide an
> HttpSessionAdapter with an urlId method calling the actual
> session.getValue("urlId"), etc. So, yes, maybe in this case the
> designer does need to remember to stick the {{session.urlId}} on the
> end of hrefs.
>
> I suppose in JSP it could be comparable (but much less readable, with
> lots of context lookups and <%= ...%>).
>
>
>>
>>
>>> Tag libraries are a good start, but JSP
>>> is just HTML-in-your-servlets writ backward. There was little attempt
>>> to actually come up with something useful and interesting.
>>>
>>
>> Aha! Something we can definitely agree upon! :):)
>>
>>
>> cheerful regards,
>> Joe Barefoot
>>
>>
>>
>>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
