> 1) Why can't I use the useBean tag when the class is really a
> implementation of an interface. E.g.:
>
> <jsp:useBean id="aBean" class="java.util.List" scope="request" />
>
> Must I write an instancable class in the class="" definition?
> Why? I want to use this with the stuts logic taglibrary for
> iterating a list, but do I then have to fetch the list with <%
> List l = request.getAttribute("..."); %> ?

Try using the "type" attribute instead of "class":

<jsp:useBean id="aBean" type="java.util.List" scope="request" />


>
>
> 2) Why can't I write:
> <tl:tag attib="<jsp:getProperty name="aBean" property="a"/>"/>
> when
> <tl:tag attib="<%= aBean.getA() %>"/>
> works perfectly (the tag's attribs are all set to rtexprvalue =
> true).

The first is not valid XML.

Also, the behavior of the jsp:getProperty action is defined to do
something specific. From the JSP 1.2 spec:

"An <jsp:getProperty> action places the value of a Bean instance
property, converted to a String, into the implicit out object,"

The spec says something similar about expressions, but then clarifies
their use as tag attribute values in section 2.13.



Gennis

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to