On Mon, 2004-10-04 at 15:40, Justin F. Knotzke wrote:
>
>Could someone please write out an example of what the select tag would look
> like so that the selected item is the item that is equal to the "foo"
> property?
I didn't quite understand your question, but you can access the request
obje
Hi,
I have been beating my head against the wall now for a few days trying to
figure this out. Here is what I have:
public class AClass
{
private String foo="";
public String getFoo() { return foo; }
public void setFoo(String _foo) { foo = _foo;
Quoting Malcolm Cowe <[EMAIL PROTECTED]>:
8< snip >8
> As an aside, I'm looking for a cheap and nasty server side XML-RPC
> implementation for an upcoming demo. Any pointers?
Have you looked at Apache XML-RPC? I'm not really familiar with it, but it's got
the right name ;-).
http://ws.apache.o
Placing the TLD in the taglib jar works in JSP 1.2 also. That is not a
new feature.
In order to take advantage of it, you need the following:
* Keep the TLD in the taglib jar
* Do not put the "taglib" directive in the web.xml
* Specify a "taglib" directive in the JSP that uses the URI specified
XTags is not deprecated, and I don't recall any discussions about moving in that
direction. However, it does seem like the arrival of JSTL has taken most of the
wind out of its development sails.
As for and POST, here's a relevant snippet from the JSTL spec:
When importing an external resource u
I personally find XTags to be extremely useful, particularly during
prototyping, since it if more functional than the JSTL XML
implementation. In particular, it is useful to me to be able to add and
remove XML elements before applying a stylesheet. Please don't deprecate it!
Would agree with yo
Hi,
I'm at the beginning stages of writing a client for xml-rpc using jsp tags.
First I thought I'd use the combination of the xtags and io libraries. Then, I
realized that jstl supports most xml functionality that I can think of
(transformation/xpath/parsing). Does this mean that xtags should b
