jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marco.Mistr...@nokia.com
Subject RE: Offer to submit <form>-related taglib
Date Fri, 18 Aug 2000 06:24:09 GMT
HI shawn,
	sorry if i was not clear also in hte second message

what i mean is, given a form like this:

<form action="...">
<input type="text" name="name" />
<input type="text" name="surname" />
<input type="text" name="address" />

generate a request in XML format(redirected to a servlet or whatever
application) such as

<?xml version="1.0"?>
	<parameter name="name">Marco</parameter>
	<parameter name="surname">Mistroni</parameter>
	<parameter name="address">Sunset Boulevard, 140 - Los

this request is a STRING, and can be passed to a generic application that
can process the request and call some back end application
the point is to use XML as a data-exchange format between different

so far, i have done something like that, but for generating the request in
XML format i extract all the parameters from the request and build a XML
string that looks as the XLM above
now, considering the taglibs available for processing form elements, such as
yours and joe's, can considering especially the case of joe in which he (as
far as i understood) use the taglib to populate a JavaBean with some
don't u think that is feasible to write a taglib that takes all the form
input parameters and build, as i told, a request in XML format??
i haven't thought in detail how to do that, but what is your opinion??

thanx in advance & regards

> -----Original Message-----
> From: EXT Shawn Bayern [mailto:shawn.bayern@yale.edu]
> Sent: 18. August 2000 0:05
> To: taglibs-dev@jakarta.apache.org
> Subject: RE: Offer to submit <form>-related taglib
> On Thu, 17 Aug 2000 Marco.Mistroni@nokia.com wrote:
> > i was interested in your taglib what about extending it so that all
> > the form parameters can be transformed in an XML request ???
> I corresponded with Marco offline a bit in response to this, 
> but I'm still
> not entirely clear what's meant by "XML request."  The two 
> possibilities
> seem to be (a) XML-written forms or (b) XML-based form encodings (sent
> from a browser to a server).
> An incipient W3C standard, "XForms," describes a data model 
> representing a
> more generalized, XML-based successor to HTML forms.  I think 
> it'd be a
> phenomenally good idea to support XForms with the "input" taglib when
> XForms solidifies.
> But if you mean the POSTing of XML to an HTTP server (e.g., a 
> POST with a
> content type of text/xml instead of, say, 
> application/x-www-form-urlencoded)
> -- and, from our earlier correspondence, that's what I think 
> you mean --
> I'm not sure how the "input" tag library (or any tag library, really)
> could help.  As far as I know, current browsers support only 
> application/
> x-www-form-urlencoded and multipart/form-data as data-encoding types.
> If future browsers support different encoding methods, <form> authors
> could specify that a particular <form> is meant to generate a 
> particular
> type of "request."  But even then, it wouldn't necessarily be 
> the province
> of the "input" taglib to support it:  the "input" taglib produces
> individual form elements, not entire forms.
> Hope that helps,
> Shawn

View raw message