Zafif, You can move the jar file that is associated with the JRUN tag library into another JSP server, but JRUN does not guarantee that it will work inside of another JSP server. I believe that there is also a TLD file associated with the JRUN jar file, but you would need to search on the JRUN site to find the name of the file. You would need both the jar file and the *.tld file to "port" their tag library over to another server. Most of the tags I suspect would port, but a few, such as the Transaction tag, probably would not (it contains an EJB behind it, and JRUN's EJB container is not yet Sun certified, if my memory serves me correctly).
As you stated in your email, the advantage of using the JRUN Input, Form and Select tags are the validation that these tags can do for you over writing your own validation in JS for HTML tags. Some of the other tags in the tag library do NOT have HTML equivalents, such as the SQL, SQLParam, SQLStoredProcedure and Servlet tags. These tags are "shorthand" for writing your own Java logic in a JSP. The same goes for the logic tags (if, foreach, case, and switch). Celeste -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 21, 2002 2:23 PM To: JRun-Talk Subject: input tags : html or jrun tags? So far, I've created my forms using html, now that I've discovered jrun tags, I was wondering if any of you can tell me from experience which is better to use and why. The benefit I see for using jrun tags would be easy validation check. The disadvantage would be making the code less portable to another web server (which is not an issue for us at the moment). What would you guys recommend? Thanks, Zeina ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
