Mike, It certainly is a possibility. For most part it is close to trivial, with the exception of taglib support, which I think would require more changes to the infrastructure of JXP. Others suchs as "page extends" etc doesn't really apply to JXP. For now, I probably would add the simple ones (since i have implemented jsp import), and will add taglib support later in a separate (long)release. thlee
> > Would you consider elevating JXP to a top-level > project and in doing so, bring JXP closer to the JSP > spec (except for the areas that create a dependency > on a JSP/Servlet container)? > > I personally see broad appeal for the project and > that is why I started using it. In my opinion, having > access to a template/scripting language that emulates > JSP syntax/functionality and is available via the > classpath is highly valuable. > > There is a tremendous amount of code lying around out > there in JSP's that could be easily componentized via > JXP. > > When we started using JXP, we took a number of JSP > fragments from older projects and turned them into > JXP templates. Then created java classes that > encapsulated the relevant fields methods and > attributes and implemented a common render routine. > What we got was an easy to use, easy to work with > internal toolkit. > > We use the default JSP editor in WebTools (You have > to configure the editor to recognize .jxp files) and > it works great. With JSP style imports, you even get > code assist in the templates :). > > I hope you keep trucking with JXP, because we > certainly intend to continue using it. > > Mike --------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=46468&messageID=94639#94639 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
