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 'componetized' 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
encapsolated the relevent 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.
Mike
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=46468&messageID=94626#94626
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
