I briefly looked into M7 last year -- it looked very interesting, but the
pricing gave me pause. The pricing clearly targeted enterprises, not
individual developers -- last September, the price of the M7 Application
Assembly Suite was $12,500 per server plus $3,000 per developer. Even if it
was
To add a support for a custom tag library into Dreamweaver MX, there are a
few simple steps:
1) Click Edit Tag Libraries ...
2) In the Tag Library Editor dialog, under Tags click on the plus (+) icon.
3) In the drop-down list, choose JSP Import from file (*.tld,*.jar,*.zip).
4) In the Import
The Maverick 2.1 announcement seems relevant to both the current MVC
discussion as well as to JSTL users in general:
[Maverick offers] Clean, easy-to-understand MVC separation
Maverick is an excellent tool for use with the JSTL standard tag library;
the primary JSP example uses JSTL to render
It seems confusing to me (and no doubt others) that Standard Taglib is
synonymous with JSTL or JavaServer Pages Standard Tag Library. When I first
went looking for JSTL, it wasn't immediately apparent that this was the
place to find it. I would much prefer to see the listing as JSP Standard
Tag
Hmmm...this is one of the most frequently asked for options on the
JSP-Interest mailing list. You'd think there would be an option like this
in the Jakarta taglibs. Is there a way to do this in JSTL 1.0? If not,
could this be in JSTL 1.1?
Steve
-Original Message-
From: Modha Kumar
Today Macromedia announced Dreamweaver MX, which replaces both Dreamweaver
and Dreamweaver Ultradev. With this new version, you can quickly import tag
library information from TLD files and make this information available in
Code Hints drop-down menus, a Tag Chooser, and the Tag Inspector. For
in the JSP
1.2 specs:
a simple default short name that could be used by a JSP page
authoring tool to create names with a mnemonic value; for
example, the it may be used as the preferred prefix value in taglib
directives.
Steve
Steve Bang
Sr. Staff Information Developer
AlphaBlox (http
I'm encountering developers who question the value of the EL, since it often
isn't really much different than using Java as a scripting language. Using
Java as a scripting language in JSP pages is more akin to JavaScript, it
seems, than it is to the EL. See the snippet below for an example of
If I redefined the prefixes, then when my customers or I buy Shawn's book
(or any others), they'd have to reinterprete every description and example
to map the new prefix names to the default ones. And, likewise, it would
complicate any newgroup or mailing list discussions. So, a solution to
While Java also supports meaningful naming, in this case the goal is to
create tag libraries for non-programmers. So, names like x and fmt are
not terribly clear. The HTML tags are not cryptic, and whenever possible,
neither should JSP tags. I undestand that the HTML tags don't need a
prefix,
opinions.
On Thu, 21 Mar 2002, Steve Bang wrote:
While Java also supports meaningful naming, in this case the goal is
to create tag libraries for non-programmers. So, names like x and
fmt are not terribly clear. The HTML tags are not cryptic, and
whenever possible, neither should JSP tags
We have a custom tag library that treats all of our tags with a session
scope (by design). Is it possible to use JSTL's c:set tag to change the
scope on one of the attributes on our tags? Users are requesting the
ability to dynamically change an attribute value on our tags when a page is
is correct, no changes will be made.
Glenn
Glenn Nielsen wrote:
Steve,
Thanks for reporting this. The correct element name is
taglib-uri.
Looks like there is a bug in the taglibs build. I'll look into it.
Thanks,
Glenn
Steve Bang wrote:
In the Jakarta tag libraries
In the Jakarta tag libraries, including the DateTime and DBTags tag
libraries, the TLD files include a uri tag to define the tag library's URI
and the jspversion is defined as 1.1. But, the JSP 1.1 specs do not
mention the uri tag. Isn't this new to JSP 1.2? If so, why were the URI
tags added
JSTL states that it supports JSP 1.2. Does mean that it is required for all
of the tags, or only the ones dependent on JSP 1.2 functionality? I'm
curious since I want to experiment with the use of JSTL with our company's
product, which currently supports Tomcat 3.2.3, WebLogic 6.1, and WebSphere
What's the best way to reference different TLD versions? In some of the
Jakarta taglibs, it seems that the uri is used to define the version, while
others do not seem to show version information. Is the tlibversion tag in
the TLD reserved? If a tag lib is updated, is there an appropriate place
16 matches
Mail list logo
