Skip to main content

Revisiting passing Parameters through EL - this time with functional techniques

By
The strangest thing about being a developer, to me, is that every time I think I have perfected my technique for something, I revisit it after some time away and find a better way of doing things. So this is my 4th iteration of how to pass and accept parameters through Expression Language. Allow me to introduce... the Mapper. (Quick side note: my old GetMap was based on the Map interface. Mapper is based on DataObject just because it is smaller. Mapper could just as easily implement Map if you prefer.

Just as a quick reminder, the goal is to accept a parameter through Expression Language, like so:
styleClass="#{MyViewBean.buttonStyle['MyButton']}"

public class Mapper implements DataObject, Serializable {
public static interface Function {
Object map(Object in);
}
private final Function func; //This will be an anonymous implementation

public Mapper(Function func) {
this.func = func;
}
public Object getValue(Object key){
return func.map(key); // Call the anonymous Function method
}
public void setValue(Object key, Object value){
throw new UnsupportedOperationException();
}
public Class<?> getType(Object key) {
throw new UnsupportedOperationException();
}
public boolean isReadOnly(Object key) {
return true;
}
}

This came from studying functional programming concepts and I believe this is a vast improvement on my earlier versions. It is certainly much easier to read and implement, and the most flexible. It works like this:

public class MyViewBean {
private String activeButton = "MyButton";

private final Mapper btnStyleMapper = new Mapper(
new Mapper.Function(){ // define the translation function
public Object map(Object in) {
return getActiveButton().equalsIgnoreCase(in.toString()) ? " active" : "";
}
}
);

public String getActiveButton() {
return this.activeButton;
}

public void setActiveButton(String activeButton) {
this.activeButton = activeButton;
}

public Object getButtonStyle() {
return btnStyleMapper;
}
}
One thing this version does sacrifice is strongly-typed objects due to the DataObject interface. You could use Map for better typing, but the endpoints are still going to be Objects, so it might be best to just validate the input and be on your way.

Comments

Post a Comment

Popular posts from this blog

XPages Application Framework (Part 1?)

By
Note: I changed projects and priorities after my last POI article, resulting in a long hiatus. I anticipate using that framework on my current project and will likely refine and complete my related article series. For the past several months, I've been fortunate enough to lead a project overhaul from traditional Domino Webapp to XPages. I had a few goals in mind, but the top three were integrating Bootstrap, embracing MVC principles, and eliminating all SSJS . I imagine the motivation for Bootstrap integration is self-explanatory. There is an OpenNTF project out there called Bootstrap4XPages. I didn't use that for a number of reasons - the main being a policy in the current environment. But you may ask yourself (if you didn't follow that link), why so much hatred for SSJS? I have a litany of reasons. It impacts readability of the XPage source; it hurts maintainability when logic is scattered across dozens of XPages, custom controls, and script libraries; it mixes log...
Post a Comment
Read more

Killing SSJS - Passing a parameter using Expression Language - Part 2

By
In part 1, I showed how you can expand the DataObject implementation to allow you to pass a parameter to a method and return the result. It's not a perfectly elegant solution, and it has some limitations, but it's a very solid technique and not at all difficult to implement or maintain. But I kept running into roadblocks. What if I have to compute part of the expression? What if I have to get a value based on another parameterized getter? You can't compute part of an EL expression in your EL. So after some research and experimentation, I created the GetMap. This isn't a new concept - it was developed for JSF 1.1 (which is what XPages is built on) but the rest of the world has moved on to JSF 2.0 and so some of these older techniques can be a little tricky to unearth since this hasn't been an issue in the JSF world for years.
Post a Comment
Read more

Fixing FontAwesome for Windows 10

By
I ran into an issue with FontAwesome a few months back, where a NoCache header was being injected at the server and FA was broken for any partial refresh. I convinced the admin to reverse that setting and all was well until last week... We had some users who were not getting any icons to appear. Ever. We tracked it down to a new Windows 10 setting for IE11 which disallows untrusted fonts. Since we do not set security protocols for our users, and there is no chance of ever convincing those admins to change this policy that they explicitly turned on, I had to find a new solution. I did some searching and it turned out to not be too difficult. First, here is the original implementation. The theme: <control> <name>Icon.Search</name> <property mode="override"> <name>tagName</name> <value>i</value> </property> <property mode="concat"> <name>styleClass</name> <value>fa fa-search...
Post a Comment
Read more