Thanks, got it.
In summary then, my question should have been "can JSTL
be used with variables created within scriptlets?" to which
the answer would have been "nope, only with variables with
scope which means using the tag".
Stephen.
"Karr, David" <[EMAIL PROTECTED]> wrote:Oh, yeah, and as anot
Sorry, you're right, David. I should have (and thought that I had) stated
that no output was seen, and was quite embarrassed to reread my
message and see the dumb "does not work".
You're right about my problem being that sending no output
and thanks for diagnosing the lack of scope problem. As f
Hi Eric,
Thanks for explaining that to me about JSTL automatically
translating ${book.title} to book.getTitle().
I expected JSTL to work somewhat like Velocity (which is
much more intuitive by comparison).
And you're right - I haven't got the reference to the 'book' object
in the correct conte
Before I look more deeply into bug 16751 submitted by Pere
that seems to be related to what Alberto and Pablo
have been experimenting in the past,
could someone translate the important points of the email sent
by Pablo on that topic.
I'd think that "funcionaba correctamente" means that it works
p
Pierre,
If I were managing the group, my decision would be based
on the abilities of "Philippe" (page designer) and "Mike"
(the server-side engineer). If the page designer was part
of the team and had an interest in the technology,
I would try to get him to embrace JSTL and go for it. Have
hi
On Tue, 2003-02-04 at 16:51, Pierre Delisle wrote:
> How much of a stretch is it to get Philippe (assuming typical knowledge of
> JavaScript a designer would have) to use JSTL so he can have full control
> over the pages of the website?
>
> Or is it simply easier to just forget about training Phi
"Renick, Garrel" wrote:
>
> This is an interesting topic, and people obviously have
> strong opinions about successes and failures at using
> this technology within their work environments.
>
> My viewpoint is that JSTL provides a nice set of
> features that most page designers with some progra
[EMAIL PROTECTED] wrote:
>
> Hello-
>
> Forgive my comments as they are not technical. Just observations I have made on a
>few projects over the past couple months.
>
> Since there are very few java programmers who are designers, and vice versa - there
>must be a comfortable zone where desi
This is an interesting topic, and people obviously have
strong opinions about successes and failures at using
this technology within their work environments.
My viewpoint is that JSTL provides a nice set of
features that most page designers with some programming
experience will be able to use
This is an interesting discussion. As the spec lead for JSTL,
I'm always interested in hearing about the practical experiences
people have with the technology.
Lyndon mentioned the following:
> Nonetheless I dont see the average "web designer"
> using jstl. Maybe jstl 2.0 will offer easier integ
But your designers can handle EL when they need to?
And I never say any problems with WYSIWYG tools like Dreamweaver...
and design teams I worked with used it... maybe we do simpler things,
but it worked...
On Tue, 2003-02-04 at 17:59, [EMAIL PROTECTED] wrote:
> Hello-
>
> Forgive my comments
Hello-
Forgive my comments as they are not technical. Just observations I have made on a few
projects over the past couple months.
Since there are very few java programmers who are designers, and vice versa - there
must be a comfortable zone where designers/developers can integrate their works
> As a developer I can tell you I dislike having to open up designers
> html especialy those who use WYSWIG tools.
Maybe you should use a WYSIWYG tool too :-)
>On the other insert jsp,jstl
> etc into html and send it back to designers leads to problems with
> keyboard happy designers who
Jerome Jacobsen wrote:
What does Javadoc document? Java. I think it is too much to ask most page
designers to understand JavaBeans which means understanding Java types
(primitive, wrappers, Collections, Maps). And then they'd need to
understand this Expression Language and its type conversion/
Your approach of designers design html and send files to developers
seems to imply that it work well where designers and developers share
intimate knowledge. What happens when there is less intimacy in terms of
knowledge and designers and programmers are working remotely? For
example the Athens
On Tue, 4 Feb 2003, Jerome Jacobsen wrote:
> What does Javadoc document? Java. I think it is too much to ask most page
> designers to understand JavaBeans which means understanding Java types
> (primitive, wrappers, Collections, Maps). And then they'd need to
> understand this Expression Lang
XMLC seems nice, but what about performance? XML transformation
probably is costly, compared to taglib use, isn't it?
Anyway, I see no problems about designers do their design with no
dynamic content, and then send the HTML files to developers add tag
calls.
On Tue, 2003-02-04 at 16:24, Jerome
What does Javadoc document? Java. I think it is too much to ask most page
designers to understand JavaBeans which means understanding Java types
(primitive, wrappers, Collections, Maps). And then they'd need to
understand this Expression Language and its type conversion/coercion rules.
Not to me
Thanks for your comments. However experience has shown that knowledge of
a scripting language is not necessarly a prerequisite for understanding
a programming language or mvc or other application developer concepts. I
have worked on AOLTV 1.0 where there web designers who fairly understood
java
On Tue, 4 Feb 2003 [EMAIL PROTECTED] wrote:
> I disagree... By using a scriptfree TLD (as described in "JSTL In Action"),
> you can very well restrict your web designers to use only JSTL (or whatever
> tags you want them to use). Our web designers aren't allow to publish any
> JSP pages unless t
I don't know... but to me it seems you get really good web designers
:-)
Here I ask the designers to do page layout first, then programmers
insert the taglib calls... so the first group can use their dreamweaver
freely, we can hire cheap designers and programmers can make their tests
as soon as
I disagree... By using a scriptfree TLD (as described in "JSTL In Action"),
you can very well restrict your web designers to use only JSTL (or whatever
tags you want them to use). Our web designers aren't allow to publish any
JSP pages unless the first line reads
<%@ taglib prefix="scriptfree" uri=
Ideally, applications will be designed using the Web MVC paradigm, so
view pages will contain only "view logic". However, in a complex
application, using even the most popular frameworks (Struts, for
instance), it's still difficult to completely avoid using scriptlets or
scriptlet expressions. If
JSTL or not, I'd say that non-Java programmers can write JSPs only if the
project has some very strict guidelines and very good documentation on those
guidelines and your custom tags. You would have to design the guidelines to
be very restrictive of what tags you allow in the JSP. These restricti
Actually, JSTL was introduced into our company for exactly that purpose.
Now, I'm not the one saying that every web designer will understand it, BUT
from my point of view a web designer must know JavaScript. Now, if he
understands JavaScript, how far is he from understanding JSTL? It's just a
new s
Greetings,
As a software developer I would like to delegate some of
the more mundane and simpler development tasks to non developers,
programmers etc. The JSTL specification document claims that the jstl
was created to facilitate or ease development for web designers and non
jav
Oh, yeah, and as another poster pointed out, it is "${book.title}",
assuming your bean class is written correctly.
-Original Message-
From: Stephen Riek [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 9:52 PM
To: [EMAIL PROTECTED]
Subject: Escaping quotes in form fields - c:out
First of all, it would help if you made it clear exactly what your first
problem is. Whenever the most detailed statement of what went wrong is
"it does not work", then you haven't given enough information.
I'm going to guess that you see nothing from your "c:out". This is
because you've created
Sure, book.getTitle() is the public method, but that's translated into
${book.title} for JSTL.
JSTL is smart enough to know that ${book.title} corresponds to
book.getTitle(). The only thing that might not have happened is that you set
the reference to your object as "book" in your request context.
Yo lo resolví , cambiando la configuración del tomcat, para q no cacheara
las tag-libs,
aunque aun así no funcionaba correctamente.
Un problema que detecté es que había cierta "interacción" con otras
tag-libs, pq
haciendo dos jsp's q sólo tuvieran los tags de , y funcionaba
correctamente.
Así que
book.getTitle() is the public method for my Book class.
book.title is a private String property so it's not accessible.
Even if book.title were visible, I'm pretty sure that
must be able to use javabean methods as well as properties,
both of which just return a String after all (at least in my
>From my understanding, all you need is to use
">
Note: Not ${book.getTitle()}, but ${book.title}
Best regards,
Eric
> -Original Message-
> From: Stephen Riek [mailto:[EMAIL PROTECTED]]
> Sent: Dienstag, 4. Februar 2003 06:52
> To: [EMAIL PROTECTED]
> Subject: Escaping quotes in form fie
32 matches
Mail list logo
