Hello, boxed wrote:
This could work the other way too. Don't forget that many new users may start off wanting to use JSTL but after they find it lacking may want to switch to WW tags. It would be much easier to switch if the WW out tag was basically the same. If the WW tag bears no or little resemblance to the JSTL one, it will be much more confusing when and if someone attempts to switch between the two.How about just 'out' for print? To go along with out.println etc.Yes, as this aligns better with JSTL. The syntax of <ww:out ...> should probably be the same or a superset of <c:out ...>.
I know that out is the name in JSTL but I personally feel that this is an
argument against using that name since we don't want confused users if they
have to mix the two.
Just for reference, here are the JSTL <c:out> tag attributes:
Attribute Description Required Default
value Information to output Yes None
default Fallback information No Body
to output
escapeXml True if the tag should No true
escape special XML
characters
Since a <ww:set> tag has been proposed, note that JSTL has a <c:set>. Here are the attributes:
Attribute Description Required Default
value Information to save No Body
target Name of the variable No None
whose property should
be modified
property Property to modify No None
var Name of the variable to No None
store information
scope Scope of variable to No page
store information
The <ww:set> wouldn't have a scope attribute.
The JSTL reference is available at http://www.manning.com/bayern/appendixA.pdf.
> Furthermore I would strongly advice against having
When I mentioned a common syntax, I should have specifed common attributes where it makes sense. No, the JSTL EL wouldn't be emulated so I can't see how there would be any performance implications. It's a given that users would have to convert between the different EL's when switching.<ww:out> (or whatever) as a superset of <c:out> because that would force us to implement a lot of stuff that would slow down the tag considerably and it may have other side effects like having to change the EL.
In summary, remember that the WW tags are proprietery to WebWork so at least some new users will be reluctant to use them. If barrier of entry to switch from a JSTL to WW tag is low, people would have less of a problem switching to the WW version if it's fairly compatible.
// Anders Hovmöller
-Bill
------------------------------------------------------- This sf.net email is sponsored by: Are you worried about your web server security? Click here for a FREE Thawte Apache SSL Guide and answer your Apache SSL security needs: http://www.gothawte.com/rd523.html _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
