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

Quick tip: Convert a number to String in EL

By
I just had a need to do this and a Google search didn't immediately turn up a solution. So I thought for a couple of minutes and came up with this: value="0#{numberVar}" This takes advantage of the way Java auto-converts objects to strings when doing a concatenation. So if your number is 13, Java EL turns this into new String("0"+13), which becomes "013". You can then strip off the leading zero or just parse the string back into a number.
Post a Comment
Read more

Project in Review - Part 3: What didn't work

By
Of course, not everything was an unmitigated success. I tried many things that didn't work out. Much of which I've removed and forgotten about, but a few things remain - either scarred into my psyche or woven too deeply to fix. What didn't work Storing my entire configuration in application.properties Using properties files is great. It let me get configuration out of a profile document and into something much easier to edit - particularly configuration that users will never see or maintain (and thus there is no need for an interface for). But I took it too far. The paths to the other databases are there, and that's good. But view aliases are also there, and that was a mistake. I already have a ViewDefinition enum that describes each view and all the information I need to know about it. I could have set view names there, but instead I'm reading them from the application config. I can change where a view is pointing without having to go into my code. Except of co
Post a Comment
Read more