-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support other view frameworks other than JSP #36
Comments
Is it causing a problem ? Or the intent is to save a few Kbs in the stripes jar ? |
No problem. It's just an idea to make it possible for the open source community to build integrations with other front-end libraries. |
Ok. So you mean factor out the "core" tagblib functionality into reusable java code ? |
Yeah, I have used Velocity with Stripes. My biggest issue is that it's hard to use some of the Stripes functionality because the logic is hardcoded into the JSP tags. So you are correct, bringing the taglib stuff into reusable Java is really what I am looking for. |
I could not agree more. I've had the same problem with TTT (a Statically Typed Templating lib) when I integrated with Stripes. I ended up writing a subset of a JSP engine in order to handle this. In the end, it's a bit scary, but it works. It imposes some design though... Have a look at this if you're interested : The idea is to use the This allowed me to reuse Stripes tags directly. Otherwise, it's quite a lot of work to rewrite the whole thing to make it reusable. Was clearly not intended to. It also has the benefit of allowing to reuse virtually any taglib, not only Stripes'... |
It would be nice if by bringing in Stripes, we didn't have to bring in all the JSP tags with it. Could we possibly have Stripes-framework and then separate Stripes JSP.
The text was updated successfully, but these errors were encountered: