Skip to content

Latest commit

 

History

History
41 lines (27 loc) · 1.93 KB

README.md

File metadata and controls

41 lines (27 loc) · 1.93 KB

Parsley

Parsley is a template parser for WO. It's based on WOOgnl and thus supports it's inline binding syntax. It's a pure WO project, meaning it does not require Project Wonder (although, of course, it works fine with Project Wonder as well).

Currently at development stage so mostly useful for testing, brainstorming, or whatever other fun things you usually do with experimental parsers.

Why?

To get nice inline error messages when template parser errors occur (rather than a huge stack-tracey exception page). Currently, this only applies when you attempt to use an element/component that doesn't exist, and for handling WODynamicElementCreationException which for well designed elements will cover things like wrong binding configuration.

parsley_inline_error_screenshot

Actually, this isn't the real "why" of the project. But it's currently the nicest byproduct visible to the user, making for a good cover story.

Usage

To use the parser, clone this repo and import the project to your workspace or mvn install it.

Then add this dependency to your pom.xml:

<dependency>
	<groupId>is.rebbi</groupId>
	<artifactId>Parsley</artifactId>
	<version>0.1.0-SNAPSHOT</version>
</dependency>

…and add this somewhere in your application's initialization, for example in the Application class constructor:

public Application() {
	parsley.Parsley.register();
}

Differences from WOOgnl

  • We don't support OGNL expressions in binding paths. Support could be added as a plugin, but I'm not a fan of it myself so...
  • We don't support WOOGnl's parseStandardTags behaviour. Might be looked into if anyone actually uses it, which I doubt.
  • We don't support tag processors (WOOgnl's <wo:not> being an example use). Never used them but the idea isn't that bad. However functionality of that kind needs work in the parser so that's for later.