Skip to main content

Using a non-managed bean with an XPage

By
For a long time, every time I wanted to create a controller or model bean, I wrote it and then added it to my managed beans in faces-config. But this can create a very bloated faces config, particularly when these beans are only used by a single XPage. Then I learned about dataContext.

A dataContext can be created for any container all the way up to the xp:view element, which allows for great flexibility. It works like this:

<xp:this.dataContexts>
  <xp:dataContext var="beanVar">
    <xp:this.value><![CDATA[${javascript:
      var unid = param.get("unid");
      var notice:package.Notice = new package.Notice(unid);
      return notice;}]]></xp:this.value>
  </xp:dataContext>
</xp:this.dataContexts>

This bean can then be bound to controls like so:
<xp:text id="name" value="#{beanVar.name}"></xp:text>

If the bean returns a collection, this can be used as a data source for a repeat control like so:
<xp:repeat id="repeatItems" value="#{beanVar.itemList}" var="item" rows="50">
  <div class="row>
    <xp:text id="itemName" value="#{item.name}">
    <xp:text id="itemQty" value="#{item.quantity}">
  </div>
</xp:repeat>

So it works just like a managed bean except it is declared in the XPage instead of faces-config. This has the added benefit of making it clearer where the bean variable name is coming from when you are looking at the XPage in the future.
Labels:

Comments

Post a Comment

Popular posts from this blog

Pass data between XPages and existing LS scripts

By
I'm working on modernizing a fairly hefty application with a lot of existing script libraries which we want to leverage within the XPages environment. Here is a technique that works very well. First, create an in-memory document in SSJS. We can set any input values needed for the back end. Then we pass that document to a LS Agent which can work it's magic using the values set in SSJS and use the same document to return values back to the XPage. Here is how it works in detail:
6 comments
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

XPages Application Framework (Part 2 of ?)

By
In my last post, I offered a very rough overview of the framework I've been building and adapting. Full credit where it's due, I've been borrowing and adapting from Jesse Gallagher's XPages Scaffolding - an awesome project that I've learned a great deal dissecting. This is one of those projects that, if you make the effort to truly understand it, will give you entirely new tools and approaches for problems. As usual, I've learned the most changin g things and breaking them. My project differ s f rom Jesse's mostly in that it supports 8.5.3 and doesn't require any relaxed security permissions - bec ause I'm on 8.5.3 and because the admins h ere will not grant any relaxed permissions.
Post a Comment
Read more