Leif Hanack wrote:
>>>i think the loss of using interfaces is a big disadvantage. on the
>>>serverside it will not be clear, why i have a class User with getter
>>>and setter and a User2 with just setter.
>>
>>I disagree. I believe it's a huge advantage. It means that I don't have to
>>code server
> > i think the loss of using interfaces is a big disadvantage. on the
> > serverside it will not be clear, why i have a class User with getter
> > and setter and a User2 with just setter.
>
> I disagree. I believe it's a huge advantage. It means that I don't have to
> code server-side objects spe
> > i think the loss of using interfaces is a big disadvantage. on the
> > serverside it will not be clear, why i have a class User with getter
> > and setter and a User2 with just setter.
>
> One of the prices we pay for more convenience for page authors is the loss
> of some distinctions like t
> "Julia" == Julia A Case <[EMAIL PROTECTED]> writes:
Julia> I'm trying to use foreach in the following way
Julia>
Julia>
Julia> <%= genre %>
Julia>
Julia> getGenres() returns an array of Strings
Julia> The same logic works both above and below with other
I'm trying to use foreach in the following way
<%= genre %>
getGenres() returns an array of Strings
The same logic works both above and below with other functions. But
this one keeps telling me bean genre not found in scope. Looking at the
java code that is created from the jsp it look
On 17 Jul 2002, David M. Karr wrote:
> I'm working on an experimental tag library that is an extension of
> Struts, where all the tags use the JSTL EL evaluator instead of using
> RT expressions.
>
> In general, the subclasses will be quite simple boilerplate code, just
> requiring calls to "Exr
I'm working on an experimental tag library that is an extension of Struts,
where all the tags use the JSTL EL evaluator instead of using RT expressions.
In general, the subclasses will be quite simple boilerplate code, just
requiring calls to "ExressionUtil.evalNotNull()" for each attribute that
Hi everyone,
I apologize for the shameless plug, but I wanted to correct something I
said earlier, and I thought the update might be useful to some people.
I had previously said the entire e-book for "JSTL in Action" might be made
available for free on Manning's site. This may still happen, but
The best place to start is the Struts web site:
http://jakarta.apache.org/struts/
In the Resources section, you'll find links to many articles on Struts, and
also on MVC in general.
Regarding tag libraries, the Struts taglibs do have some overlap with JSTL.
In particular, the Struts 'bean' and
> -Original Message-
> From: Leif Hanack [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 17, 2002 1:47 AM
> To: Tag Libraries Users List
> Subject: RE: jstl: expression language does not use interface?!!
>
>
>
> > If you don't want to let the user set information on an object with
There are some over-lap in Struts and JSTL, but it is possible to use
both. Struts borrows ideas from Swing's MVC framework such as actions.
JSTL has the advantage of expression language to resolve variables.
peter lin
Tim Ringwood wrote:
>
> I am newbie to JSP, XSL, custom tags and JSTL. B
I am newbie to JSP, XSL, custom tags and JSTL. Been
playing around with it all those for about one month.
I can do what I need to, but next on my list to give a
look over was struts.
First do JSTL and struts work together or are they
incompatible?
What do folks things of struts? On the surface
On Wed, 17 Jul 2002, Leif Hanack wrote:
> > If you don't want to let the user set information on an object with
> > , it must not have setter methods. You can always wrap the
> > underlying object in a wrapper that provides only one-way access, but an
> > interface does not provide this protecti
> If you don't want to let the user set information on an object with
> , it must not have setter methods. You can always wrap the
> underlying object in a wrapper that provides only one-way access, but an
> interface does not provide this protection.
mmh?! thanks so fare. i'm a bit disappointe
14 matches
Mail list logo
