A Deep Dive On Building Notes/Domino Applications With XPages

A Deep Dive on building Notes/Domino
Applications with XPages

Martin Donnelly | Software Architect | IBM Ireland
Tony McGuckin | Software Engineer | IBM Ireland
Agenda
● Introductions
● Quick XPages App Dev Summary
● XPages Architecture Overview ● Advanced Data Sources

● Data collections
● DOJO
● Deep Dive Demos ● AJAX in action
● Server side language
● Client side processing
● Recaps ● Custom controls
● Managed Beans
● XPages on the Rich Client
● A View To The Future ● Themes
● Q&A
Speaker Introductions
Martin Donnelly Software Architect: IBM Ireland
▬ IBM Lotus® Domino® Designer 8.5.x / IBM Lotus® Domino® XPages
▬ IBM Lotus® Component Designer 6.0
▬ JavaServer™ Faces (JSF) Tooling IBM® Rational® Application Developer
▬ Java Visual Editor extensions for IBM® Rational® Application Developer
Software Developer: Iris Associates / Lotus Development

▬ IBM Lotus® Domino® Designer V4.6 to V6.01
▬ IBM Lotus® 1-2-3® for Unix®, LotusScript, etc.
Tony McGuckin Software Engineer: IBM Ireland
▬ IBM Lotus® Domino® Designer 8.5.x / IBM Lotus® Domino® XPages
▬ IBM Lotus® Component Designer 6.0
▬ Customer Enablement / Proof of Concept Development
▬ Lotus OneUI Adoption and iWidget Consistency Work
XPages
App Dev Summary
Notes/Domino Application Development
Onwards & Upwards
•- Source Control Integration
•- Improved JavaScript Editors
•- CSS Preview
•- Many more under investigation
• - Designer Framework Enhancements
Domino Designer • - Improved Version Awareness
• - Customer Driven Tactical Improvements
- Performance/Stability Improvements
- New editors
Later... Notes/Domino next
- New Extensibility APIs • - XPages next generation
- NO CHARGE Designer Download !!! • - Consumes/generates REST services
• - Generates Dojo based UI
- Rebased to Eclipse platform
- New XPage & Custom Control 2010 Notes/Domino 8.5.x • - Advanced set of Web controls
• - Full client integration
design elements • - Mobile devices support
- Fully integrated XPages • - Integration with other Lotus products
development environment
• - Quickr, Connections, Sametime
• - Stability/performance
2009 Notes/Domino 8.5.1 improvements
• - More data sources (RDBMS...)
• - iWidget consumption
• - Runs within the Notes client • - Better client integration
Notes/Domino 8.5 • - Generates iWidget • - Fixing pending issues/requests
• - First release of XPages • - Active Content Filtering • - Extensibility
• - Runs on the Domino server • - Performance/scalability
improvements XPages Runtime
 The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes on
and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing o
any features or functionality described for our products remains at our sole discretion
XPages Birthday
2010 celebrates the first XPages birthday

But the technology behind it is over 5 years old …
JavaServer Faces
XFaces & Lotus Component Designer
Get the full story here: http://thexcast.net/?p=11

XPages Proof Point:
RAD Web 2.0 framework
Build application assets with less effort
Maximize reuse of assets
Architect your user experience
for consumability
52 custom controls maximize reuse
Dojo: Customized RTE, Tooltips
Implemented Blueprint for the CSS framework
Develop once for Web and client
XPages provide client access choice (Notes, browser, mobile)
Mobile
IPhone / AndroidTM
XPages Proof Point: ITANA
“XPages have allowed me to deliver classic Notes
database applications to the iPhone without
having to change the template. I can simply
create one database with an XPage,
and it will connect to the database that is
appropriate for the particular user – even if the
other database is on different server.”
Mark Hughes – HughesConnect.com
XPages Proof Point: IBM
developerWorks/Lotus wikis
www.ibm.com/developerworks/lotus/commu
nity/wikis.html
Select the Lotus Notes and Domino Application Designer wiki
IBM Lotus and WebSphere Portal Business

Solutions Catalog
https://greenhouse.lotus.com/catalog/
XPages
Architecture
Overview
XPages in a Nutshell
● A Notes/Domino design element
● A runtime designed to generate modern Web applications
● Pure XML markup, defining:

▬ Controls, data sources, business logic, custom controls
● Solves age-old limitations expressed by the Notes/Domino community

▬ UI/Data separation, HTML generation control, server state, localization, extensibility …
● Capable of targeting multiple clients
● Highly extensible runtime and design time
● Standards-based technology: JavaServer™ Faces
● Full integrated into Domino Designer 8.5.x
● Visual Design Page, Source Page, Control Palette, Outline View etc
XPages Architecture
XPages Development Model
Use the XPages

native API
Use managed beans
and advanced
extensions
Integration of Java
libraries/classes
JavaScript libraries Java developers

and custom
controls
Drag & drop
application building
using XPages
Advanced users with
development skills
XPages Extensibility API
8.5.x
Power users
XPages Technology
● Java and JSF behind the scene
▬ Runs in the Domino JVM, within the http process
▬ JSF had been extended in many places to make it richer and easier
▬ XML File format, composite controls, script languages, data sources,
localization, simple actions, ajax requests...

▬ As of 8.5.x, uses and extended JSF 1.1 library
▬ Lot of performance and scalability enhancements
▬ Some JSF 1.2/2.0 API had been back-ported

● XPages runs within a servlet engine
▬ A custom servlet engine is used to run NSF based Web applications
▬ The NSF is seen as a deployed J2EE® Web Module
▬ The Servlet API is available to the running XPages
● The Dojo Toolkit is used as the runtime JavaScript™ library
▬ Used as a core JavaScript library as well as a UI widget framework
▬ Tightly integrated within the XPages Runtime
J2EE Artifacts
XPages in the Notes Client
How it works – pretty much the same as on the server
Notes Client XPages requests sent to

an embedded Java Web
Embedded XULRunner
Web Container container
The XPages runtime

XPages UI Container
XPages Runtime
inserts as a generic web
module and provides a
virtual container for NSFs
In Short Each NSF can be

 NSF apps have a new XPages client launch option
projected as an auto-
When app is opened, this URL is passed to XPages client container deployed Web Module.
The container further transforms the URL ...
•Creates a instance of the XULRunner browser NSF design elements
•Sends a secure request to client web container
The web container routes all XSP requests to the XPages runtime
(XSP, Java™ class files…)
XPages runtime renders pages back to the XULRunner browser are made available as
module resources to the
servlet API.
Global Architecture
Supports both the Domino server and the
rich client
Supports the data and the design elements
replication
Domino Server Notes Client
The runtime directly reads

from the NSF
Domino Designer in Eclipse
NSF files
NSF replication
Eclipse
Workspace
Eclipse directly reads/writes to the NSF
thanks to a custom EFS
XPages Architecture - 8.5/8.5.1 NSF Applications
NSF Applications
XPages Extensions
OSGi bundles
XPages Extensions
provided as jar files
Profile XPages
+Web Container Runtime
XPages
Runtime
OSGi Runtime
Domino HTTP Task Notes Client Process

● You can extend XPages within an NSF Application, or as separate XPages Extensions.
● The Domino runtime is deployed as a set of jar files into well defined directories
Extensions are provided as jar files copied to <domino>/xsp/nsf/lib
(warn: this directory is cleaned-up by the installer when upgrading the server)
● The Client runtime is deployed as a set of OSGi bundles (plugins)
Extensions are also deployed as OSGi bundles
17
XPages Architecture – 8.5.x
NSF Applications NSF Applications
XPages Extensions XPages Extensions

OSGi bundles OSGi bundles
XPD Profile XPages XPD Profile XPages

Runtime +Web Container Runtime
OSGi Runtime OSGi Runtime
Domino HTTP Task Notes Client Process

● Both the Domino server and the Notes client are deployed as OSGi bundles
The same extension mechanism is used in both platforms; extensions are provided as OSGi bundles.
18
XPages XML File format
● Each tag in the XML file represents a control or a complex property (an
object attached to a control)
▬ All the standard XPages controls are in a single, reserved, namespace
▬ Each tag in the XML file represents a control or a complex property
▬ There is one root tag, called <xp:view>
● Control properties are passed as element attributes

▬ Special <this.prop> syntax to make the XML file more “readable”, when it contains illegal XML
characters, like CR/LF
▬ Collections as defined through <this.prop> tag, where each sub-tag is an entry in the collection
(this supports polymorphism, for example data sources)
● Pass-through tags
▬ Tags without a namespace are passed “as is” to the browser, without any further processing
XPages Files
● XPages and Custom controls are defined as:
▬ An pure XML file defining the page content
▬ A xsp-config file is defining the content of a custom control
▬ Ex: list of controls properties, icon, palette category...
● The XPages Compiler

▬ From .xsp to .java to .class
▬ Designer generates a high performance Java file out of the XPages XML source
▬ The Eclipse Java compiler compiles this Java file into a class file
▬ Both processors feeds the Eclipse problems view
● How an XPage is version-ed

▬ Each control in the page has a minimum runtime requirement
▬ Each property of each control has the same requirement
▬ -> the runtime requirement for the page is the requirement maximum above
▬ This is also extended in 8.5.x to get an application version
JSF Processing Model
http://www.ibm.com/developerworks/java/library/j-jsf2/
Page Rendering
JSF Markup – XML + HTML JSF Hierarchy of Components
Rendering Phase
JSF Render-kit
 One single markup for all the platforms HTML Basic

 Actual rendering is done using JSF RenderKit
 Render-kit is selected using an extension point HTML Dojo Handheld Client
 Can leverage platform specificities
- Control properties can be set per platform
- Pages can be per render-kit
- Use of the platform style sheets
HTML Markup
Can use Dojo
library/widgets Mobile devices
Notes Client
Browser
XPages
Deep Dive Demos
XPages Introductory Demo
Ideally view this demo first
https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?
lang=en_US&source=dw-c-wcsdp&S_PKG=051410A
Data Sources
What Are Data Sources?
● Data sources are XPages artifact for connecting the UI controls to the data
▬ Data is well separated from the UI
▬ An XPage is not linked to a single document or a view – Can connect to multiple data sources at the
same time!
● Data Sources can be defined globally in the page or in panels

● Data Sources are making available objects (ex: a Domino document) that
are used by the UI controls for accessing the data
▬ These objects are seen by any control located in the children hierarchy
● Extensible architecture for new data sources in the future

Domino Data Sources
● XPages is equiped, in standard, with 2 Notes/Domino data sources:
▬ View data sources
▬ Access to Domino views or folders
▬ Document data sources
▬ Access to Domino documents
● Based on the Java back-end API

▬ Publishes View and Document back-end objects
View Data Sources
● Building a View Data Source ...
▬ Visual helpers to generate markup
▬ Data palette to work with members
▬ Property sheet for detailed settings
▬ All properties computable via JS
● Simple Tag
▬ <xp:dominoView var="dominoView” viewName="xpAllDocuments">
Views Are Also About Folders
● UI support in Lotus Domino Designer 8.5.x is for Notes view data sources
only
▬ But... The XPages runtime system supports both Views and Folders
▬ And... It's on the list of things to be added for 8.5.x
▬ View name is editable, type in folder name into “View” editbox.
▬ Type name of column into “View Column” field (or, compute it!) editable
Summary On View Data Sources
● How do I work with data in Domino Folders?
▬ You can use a folder name anywhere you use viewName
<xp:dominoView var="dominoFolder" viewName="My Folder">
● What if my view or folder is in another db on another server

▬ Just specify the database name at the data source level
▬ All these information can obviously be computed
<xp:dominoView var="dominoFolder" databaseName=”serverName!!myDb.nsf”
viewName="($All)">
● And if I want to use a replica id instead of a database name?

▬ You guessed it:
<xp:dominoView var="dominoFolder" databaseName=”802574A9:004134AF”
viewName="($All)">
▬ And you can finally cut/copy/paste replica ids in Designer 8.5
How To Manage Multiple Data Sources In
The Same Page?
● No restrictions on the number of data sources used on an XPage!
▬ Multiple data sources require special management in certain cases
▬ e.g. Open Document simple action generates a URL using the UNID
▬ http://localhost/d080905a.nsf/p02.xsp?documentId=662F287DE0738485802574BE0
02E8A8A &action=openDocument
● If multiple document data sources are defined on the page ...

▬ Which one does this map “documentId” and “action” to?
▬ We can handle this scenario easily using a special data source property!
Data Sources Parameters and URL
● Each data source has a set of parameters
● These parameters can be controlled by a URL
▬ View data sources
▬ Document data sources
● Tweaking the URL behavior

▬ Multiple data sources in the same page
▬ Ignoring the URL parameters
▬ Ex: multiple data sources in the same page (a view and a document)
▬ Ex: security reasons, do not let people access document others that the one you want them to
access
▬ But the parameters, as any other properties, can be computed and access the URL query string
Examples
● Ex: 2 Domino Document Data Sources using Customer and Order forms
▬ <xp:dominoDocument var="document1" formName="customer"
requestParamPrefix="cust"> </xp:dominoDocument>
▬ <xp:dominoDocument var="document2" formName="orders"></xp:dominoDocument>
● Construct a URL using the prefix to uniquely identify the data source
▬ http://localhost/d080905a.nsf/p02.xsp?custdocumentId=662F287DE0738485802574B
E002E8A8A &custaction=openDocument
● More detailed example online

▬ Updating data from multiple forms from a single XPage
▬ http://www.jmackey.net/groupwareinc/johnblog/johnblog.nsf/d6plinks/GROC-
7FFLYJ
Advanced Data Sources
● Repeating data sources
▬ Data sources can be located within a repeat tag
▬ In that case, multiple objects will be opened, one per repeat occurence
● Example: repeating documents

▬ A main View data source is used to browse the view entries
▬ Opening a document for each entry in a view
▬ The document id is computed based on the current view entry
▬ The save action will save all the documents being opened
▬ -> be careful: each document opened consume memory resources, plus takes time to open
Working With
Data Collections
What is a Data Collection
● A data collection is a set of objects that can be iterated
▬ Ex: a view is a collection of view entries
● Data collections can be iterated using dedicated controls

▬ Data table
▬ View control
▬ Repeat control
Data Table
● A data table is made of columns
▬ Each column has 3 parts
▬ A header
▬ A body
▬ A footer
● The data table repeats through the collection and create one body row per
occurrence
● The body row contains controls that will be repeated
▬ Those controls can be editable, when the data source supports it
▬ Limitations: domino views are not editable
Data Table vs View Panel
● The view panel has extended, simplified data binding
▬ It displays data in read only mode
▬ The column data binding doesn't require controls to be added to the body
▬ A column name is generally used for easy data binding
▬ A 'value' property can also be used to compute the column value
▬ Controls added to the body are supported if needed
● The view panel has extended user behaviors

▬ Allows hierarchical data display with twisties
▬ Categorized columns
▬ Documents hierarchy (responses)
▬ Supports column resorting
Repeat Control
● A repeat control is used to repeat content made of an arbitrary set of
controls
▬ Gives the highest flexibility when displaying repeated data
▬ Can be stacked, contain data sources or any kind of controls (views...)
● 2 modes are available:

▬ Dynamic repeat behavior
▬ The JSF hierarchy contains the repeat control and one copy of its contents. At runtime, the content is
repeated per occurrence, by giving a different context to the repeated control
▬ Create controls
▬ The repetition happens when the JSF tree is constructed and the runtime create one set of child
controls per occurrence. The repeat control is only used once and removed from the hierarchy
The Pager
● A pager is a customizable control
● A custom pager can be created by simply accessing the collection iterator
properties
▬ first: defines the index of the first element to display
▬ rows: defines the number of items to display
● The repeat control, as well as the data table, have convenience methods
to set the current position (8.5.2)
▬ gotoFirstPage(), gotoNextPage()...
● A pager can now be configured to navigate to the last entry (8.5.2)

▬ alwaysCalculateLast="true“
▬ Has performance implications to consider
"The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes
only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release,
and timing of any features or functionality described for our products remains at our sole discretion"
Creating a Custom Pager
● How the pager works?
▬ It connects to FacesDataIterator components, like a dynamic repeat control, a data table or a view
panel
▬ The items being displayed by the FacesDataIterator are defined by 2 property
▬ first: the index of the first item being displayed (0 to count-1)
▬ rows: the number of rows being displayed
▬ When displaying itself, the pager grabs the value of those properties and displays the pages and the
action links
▬ When clicking on the pager links, the pager adjusts the first property of the FacesDataIterator
● A custom control can use the same behavior

Server Side
Languages
XPages Expressions
● Every control property can have a static value or can be computed
▬ In Designer, a diamond appears next to the property to make it computed
▬ In the source code, the value of the attribute is using a specific syntax
● Load time versus runtime execution

▬ A load time expression is only evaluated once, when the page is constructed
▬ Syntax: ${[language:]xxxxx}
▬ A runtime expression is evaluated each time it is needed
▬ Syntax: #{[language:]xxxxx}
▬ Can lead to many evaluations when the page is processed
▬ Some properties, like the control id, do not support this mode
JavaScript on The Server
● XPages choose JavaScript as the default processing language on the
server
▬ Parity with the browser: reuse your skills
▬ Tighly integrated with Java
● Uses the javascript: prefix in an expression

Global Objects
● JavaScript makes some objects available as global objects
▬ Exposed by the Designer script editor
▬ session, database...
▬ No need to declare the object like in Lotuscript (Dim s as new NotesSession)
● The available scopes

▬ application, session, view, request
▬ Store data at different levels
● The XPages context object

▬ Gives access to set of useful APIs
Global Functions
● Besides global object, JavaScript also has global functions
▬ getComponent()
▬ Returns the JSF component
based on its id.
▬ See control snippets
for available methods
▬ Save()
▬ Saves all the data sources in the page
JavaScript Libraries
● JavaScript code can be located in different places
▬ In the XPages themselves
▬ No need for agents!
▬ In libraries of reusable code (.jss)
● Libraries processing model

▬ Loaded the first time they are used
▬ Discarded when the system is claiming for memory
▬ Uses Java weak references mechanism
▬ Unpredictable: do not store global values in the library, use scopes instead!
Integrating Java Code
● Calling Java from JavaScript
▬ The JavaScript bridge
▬ Package names, importPackages, Package keyword
▬ How types are mapped
● Adding Java files into an NSF

▬ New source directory – do not use “Local”!
● Adding libraries into an NSF

▬ WEB-INF/lib
● Adding a shared library

▬ Better scalability
▬ Server directories:
▬ 8.5.1: <domino>/xsp/nsf/lib – Warn, as it is clear out when the server is reinstalled
▬ 8.5.x next: OSGi plug-ins
Accessing the JSF Controls
● Each control in the page is in fact an instance of a Java object that inherits
from the JSF UIComponent object
● The Java objects can be accessed through the getComponent() global
function
▬ The controls are accessed using their JSF id ('name')
▬ Each component property/method can be accessed through JavaScript
▬ Ex: getComponent('MyComputedField').getValue()
▬ Domino Designer is providing code completion on the available method
What is EL?
● EL means Expression Language
▬ Main JSF processing language
▬ Not a complete language, but a bridge between pages and Java
▬ Default when no language is specified in a expression #{myobject.myprop}
▬ Used to bind controls to Domino documents
▬ Internally uses JSF variable and property resolvers. Can be extended in Java.
● EL syntax
▬ Used to access object properties
▬ myobject, myobject.property, myobject[“property”]
▬ http://developers.sun.com/docs/jscreator/help/jsp-jsfel/jsf_expression_language_intro.html#syntax
Advanced Uses of Expressions
● Sometimes, when computing a string property, it can be useful to compute
different parts of the value separately
▬ The XPages expression engine supports an expression that is a mix of expressions and static strings
▬ Ex: computing the style property
style=”background: #{o.bg}; font-family: #{o.font}”
● When a load time expression generates a runtime expression

▬ Ex: a custom control that needs a dynamic data binding capability
Client Side
Processing
Client Side JavaScript
● Inserting client script into a page
▬ The Script resource at the page level
▬ The outputScript tag
● The Event handler

▬ What is different between the eventHandler and the all properties?
● Dynamic client script

▬ The script contained in an outputScript tag can be computed: server side script can compute client
side script.
Using Dojo Controls
● dojoType & dojoAttributes
▬ Each control can have a Dojo type and a set of Dojo attributes assigned
▬ Dojo attributes are only generated if there is a Dojo type defined
▬ In the future, some optimizations can be used to generate JavaScript instead of HTML tags, thus not
triggering the Dojo parser
● Dojo Modules
▬ Dojo modules can be defined in a page or in a custom control. Gerenates a dojo.require()
statement in the HTML
● Dojo & clientID

▬ When a Dojo type is assigned to a control, then a client id is automatically generated
▬ Use #{id:xxx} to find the runtime control ids
Controls Ids in the Browser
● Multiple XPages controls can have the same JSF id in the same page, or
in the same “NamingContainer”
▬ For example, when the same custom control is added twice to the same page
● But the browsers require the ids to be unique in the page

▬ The XPages runtime then generate unique client ids per controls
▬ These ids are composed by the ids of the parent (naming containers) concatenated using ':'. When
within a repeat/data table, the current iteration index in also appended
● Warnings
▬ The ':' character used to compose the final client id, is not CSS friendly – This is a JSF design flaw
▬ Client ids are not easily predictable To make them predictable, be sure that their ids are designed in
Designer, else the runtime will generate random _idxxx ids. As a good practice, do not rely on client
ids in your code. Use dedicated functions instead.
Calculating a Control Client Id
● Computing a client id for a control can be done by:
▬ Calling the getClientId() global function in server side JavaScript
▬ Using the #{id:xxxx} expression on the server side

Custom Controls
What is a Custom Control?
● Composite controls
● Parameterizable sub-forms
● Controls made by assembling existing controls
● Behave exactly as native controls
● Appear in the Control palette Control is like a page
● Define their own set of properties
▬ Hierarchical with custom editors
● Pure Java controls

● Use the full JSF APIs
● Base classes provided to ease development
Defining the Control Properties
● Each control can have custom properties
▬ Defined in the Designer property panel
▬ The properties can be hierarchical
● At runtime, the custom control can access the value using

compositeData.
Using Editable Areas
● Editable areas are place holders in a custom control where users can drop
their own controls
● Can be used to define common page layouts
● Uses the JSF concept of facet

Extending the Design Time Experience
● Providing a design time rendering
▬ This is a piece of markup rendered by designer instead of the custom control definition
▬ Provides a better user experience
● Using property editors

▬ Property editors can be assigned
to help users setting values
● Leveraging the “pretty” panels (8.5.2)

▬ Some panels are automatically displayed if the control contains some properties
▬ Data panel
▬ Style panel
▬ Dojo panel
XPages
and Managed Beans
Managed Beans
● Define the scope: request, page, session, application
● Standard Java Bean class (needs a parameterless constructor)
● Mapping to a global name in faces-config.xml
● Can be used in JavaScript like the global build in objects
● Good for external stuff
XPages in the Notes Client
Launching XPages in the Notes Client
Launch Properties can be set in both Lotus Notes and Lotus Domino
Designer
Notes Client:
Lotus Domino Designer:

Customization of XPages in Notes
Rich Client Platform Specific Properties
Native Platform Dialogs
Client Themes
Ability to customize application user experience for the Notes Client
XPages Toolbar
Navigation, Clear Cache / Refresh Page, View Source, Print / Page Setup
enableModifiedFlag
Prompt to save any modified content
Bookmarking XPages
Failover Support
SWT Dialogs instead of JavaScript™ Alert / Confirm Dialogs
Web Notes Client
● Client Side JavaScript Access to Java Platform Services

▬ XSP.Alert() XSP.Xxx();
▬ XSP._NotPublished();
Rich Client Platform Specific Properties
Provide a different user experience in Web and in Notes
In Notes, analogous to traditional 'hide/when' functionality
e.g. Discussion Template 8.5.1 Toolbar
<xp:label value="Welcome " id="labelWelcome">

<xp:label.rcp rendered="false"></xp:label.rcp>
</xp:label>
<xp:text escape="true" id="cfUserName" value="..">
<xp:text.rcp rendered="false"></xp:text.rcp>
</xp:text>
enableModifiedFlag
Integrated with Notes Client document save model
Main Save menu sensitive to modified document content
Hooks explicit File Save / {Ctl}{S} operations
Alerts user to unsaved content on certain events

<Esc> / Close Window
Navigation to other page (client + web)
Applying enableModifiedFlag
Can be applied to any input control
Default setting overrides the need to specify behavior in many places
disableModifiedFlag flag allows an input control to explicitly “opt out” of the process
Handles client side and server side validation scenarios

Client side JavaScript reports an error before save can be performed
Server side validator finds an error after the page is submitted

XPages Client Theme
Support for Client Themes
Different look and feel when applications are used in the Notes Client
8.5.1 Application Properties panel extended

Allow property setting for Application, Web and Client Themes
No “Out of the Box” Client Theme for 8.5.1 / 8.5.2

XPages & Composite Applications
Full integration with Composite Applications in 8.5.1
Comp App supports XPages applications and XPages Components
Component
A new 8.5.1 Component design element
Define Publish & Receive Events for interaction with other components
Define Parameters to conditionalize component behavior
Wire XPages components together or with other components

PIM (mail),
Managed Browser
Symphony Containers
Widgets...
New XPages Simple Actions to easily handle Publish Events

Receive Events handled with JavaScript
XPages in Composite Applications Editor
Adding an XPages Application/Component to a Composite Application
Easy peasy – select Notes URL via the design element picker or just specify manually
XPages in Composite Applications
XPages Discussion
Component
Google
Widget
Notes Mail
View
XPages & Composite Applications
Two Part Online Video Shows Full Details
www-10.lotus.com/ldd/ddwiki.nsf/dx/XPage_Components_in_Notes_851_Videos.htm
www-
10.lotus.com/ldd/ddwiki.nsf/dx/XPages_Components_in_the_Notes_8.5.1_Client_De
monstration_Video
A Glimpse of the Future
Designer & XPages are central to the Notes/Domino App Dev Vision
We continue to invest on these technologies
This is not a commitment on the new features being developed

This shows the direction we are taking
This is provided as information to keep you updated and get your feedback
 The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes on
and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing o
any features or functionality described for our products remains at our sole discretion
XPages Extensibility APIs
Let people create deployable XPages libraries
Deployed as Eclipse plug-ins in the Notes client and the Domino server
Shared by all the applications!
Controls, render kits, data sources, simple actions, servlets, request

customizers, ...
Common custom controls shared in jar files
Make public the XPages Java APIs
Javadoc – articles and samples
Open source library of controls shared on openNTF
The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product
is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any
material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion
XPages Runtime in Notes/Domino (cont.)
CKEditor for rich text editing
Replaces DOJO rich text editor as default RTE
Domino Server + Notes Client (Windows, MacOS and Linux)
DOJO editor still available – set dojoType=ibm.xsp.widget.layout.RichText
Added Features
Embedded Images, Tables, Links, Emoticons, Find/Replace, Maximize
Customizable Toolbar
Slim, Medium, Large
XPages Runtime in Notes/Domino (cont.)
New back-end classes capability
Running agents on top of in-memory documents
Support for multiple levels of categorization
cat1\cat2 ... finally !
View Data Source startKeys property
Not a filter, an actual starting point for the view contents
Data collection Pager can force “last” option to be presented
Has performance implications to consider
Document Data Source
Supports “soft delete” through a new property
Data Validation
Documents can be saved without validation
New property disableValidators="true"
Use case = Save As Draft
XPiNC – What YOU said YOU want!
● We have started to address some of these points in 8.5.x
XPiNC – Client Consistent Behaviors
Enabling appropriate Menu items
File \ Replicate, Open in Designer etc
8.5.1 8.5.x
Link Handling & Document Interoperability
XPages & CD|MIME Interoperability
XPages arrival in the Note Client 8.5.1 resurfaced old CD|MIME issues
XPages apps use MIME rich text format everywhere (web & client)
Lossy editing experience when moving client apps to XPages
Round tripping Doc, View & DB links between MIME and native CD
Image resources also adversely affected
XPages 8.5.1 runtime did some work to minimize CD/MIME conflicts
In memory massaging of HAPI Domino server dependent links
e.g. Transient conversion to “notes://” when running on client
Not all use cases addressed
Link Handling & Document Interoperability
8.5.2 Enhancements for CD/MIME
Worked with HAPI team to define new API options
Generate links that are easier to identify, parse and convert
Include replica ids instead of literal NSF names
Take advantage of NSF layer functionality to resolve link
Added new property allowing app developer to define how links are saved
Notes format is the default
Images no longer embedded in link, e.g.
Similar to iNotes behaviour
Simplifies portability
No broken links on client
Window Management Client Behaviors
Window Management
Lift single-window restriction on XPages client applications
e.g. Allow documents to be opened in new window like traditional Notes client apps
Dictate behavior by preference settings
Leverage existing client preferences
Enable this option for
Links
Page navigations
View column selections
XPages Next Generation
XPages stateless mode
Generates HTML without the server side life cycle
Rich HTML interfaces – Dojo dijits
Still leverages XPages strengths
Component/renderkit model, Page composition, Localization, i18n, Security,
Dynamic page generation, Simple actions, Script languages for business
logic…
XPages embraces REST services

Generated UI bind to data coming from REST services
Existing or custom services
Should be able to easily produce REST services
On both the Domino server and the Notes client, using the available Web
container
Extend existing services with custom business logic
Advanced Dojo Based Controls
And also...
Improving the reuse of existing assets
LotusScript libraries, existing design elements (forms, views...)
XPiNC
Remove integration pain points (better context menus etc)
Eclipse Selection Manager Integration
XPages Widget Support
Data sources
Relational data access
More XPages Templates

Currently prototyping XPages version of team room template
Mobile devices support
Detecting the devices, dedicated themes, accessing the device capability...
Better Documentation
Including a new XPages app dev book from IBM Press !!!
Resources
● Lotus Domino Designer wiki

▬ http://www.lotus.com/ldd/ddwiki.nsf
powered by XPages!
● OpenNTF – Open source developer community

● Planet Lotus – Aggregation of Lotus related blogs. Lots of Domino app
dev related posts
▬ planetlotus.org
● XPages blog: http://xpagesblog.com/

● IBM DeveloperWorks
● XPages Pod Cast: http://www.thexCast.net
● Bleedyellow.com (Sametime: im.bleedyellow.com )
IBM Software Group | Rational software
Want to Buy What You’ve Seen Today?

The IBM Software online Catalog makes it easy IBM SW online Catalog
to shop for IBM software.
 Quickly find the products you need by name,
part # or by category
 Obtain up-to-date translated product and
SRP* pricing information
 Have questions? Ready to move to the next
step? You can place your order by phone or
online
Learn, Shop and Buy the way that works best
for you!
ibm.com/software/ecatalog Or you can call 1-877-426-3774
Phone number for other countries on
website
*Suggested Retail Price (SRP) shown. For volume pricing,
simply create cart and input existing Web Identity user
name and password
Question & Answer Session
 No need to submit your questions more than once

– Your question will not be posted to this page
until it is answered
 For more Rational Web events (webcasts,
teleconferences, podcasts and videos) visit:
ibm.com/software/rational/talks/
 Thank you for participating!
Contact information:
martin_donnelly@ie.ibm.com
tony.mcguckin@ie.ibm.com
Take Action
Visit IBM Rational
http://www.ibm.com/rational
© Copyright IBM Corporation 2010. All rights reserved.

The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible
for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or
representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials
to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may
change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way.
IBM, the IBM logo, the on-demand business logo, Rational, the Rational logo, and other IBM Rational products and services are trademarks or registered trademarks of the International Business
Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.
Legal Disclaimer
© IBM Corporation 2009. All Rights Reserved.
The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS
IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for
any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or
representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.
References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this
presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing
contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.
If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete:
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many
factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given
that an individual user will achieve results similar to those stated here.
If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete:
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics
may vary by customer.
Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus® Sametime® Unyte™).
Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to http://www.ibm.com/legal/copytrade.shtml for guidance
on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks
that you use in your presentation as follows; delete any not included in your presentation.
IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other
countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both.
If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete:
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
If you reference Java™ in the text, please mark the first use and include the following; otherwise delete:
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete:
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete:
Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete:
UNIX is a registered trademark of The Open Group in the United States and other countries.
If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete:
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

A Deep Dive On Building Notes/Domino Applications With XPages

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

A Deep Dive On Building Notes/Domino Applications With XPages

Uploaded by

Copyright:

Available Formats

A Deep Dive on building Notes/Domino

Applications with XPages

● Quick XPages App Dev Summary

● XPages Architecture Overview ● Advanced Data Sources

● Deep Dive Demos ● AJAX in action

● Server side language

● Client side processing

● Recaps ● Custom controls

● XPages on the Rich Client

● A View To The Future ● Themes

Software Developer: Iris Associates / Lotus Development

2010 celebrates the first XPages birthday

Get the full story here: http://thexcast.net/?p=11

IBM Lotus and WebSphere Portal Business

● A runtime designed to generate modern Web applications

● Pure XML markup, defining:

● Solves age-old limitations expressed by the Notes/Domino community

● Capable of targeting multiple clients

● Highly extensible runtime and design time

● Standards-based technology: JavaServer™ Faces

● Full integrated into Domino Designer 8.5.x

XPages Development Model

Use the XPages

JavaScript libraries Java developers

localization, simple actions, ajax requests...

▬ Some JSF 1.2/2.0 API had been back-ported

Notes Client XPages requests sent to

The XPages runtime

In Short Each NSF can be

Domino Server Notes Client

The runtime directly reads

Domino HTTP Task Notes Client Process

Domino Server Notes Client

XPages Extensions XPages Extensions

XPD Profile XPages XPD Profile XPages

OSGi Runtime OSGi Runtime

Domino HTTP Task Notes Client Process

Domino Server Notes Client

● Control properties are passed as element attributes

● The XPages Compiler

● How an XPage is version-ed

 One single markup for all the platforms HTML Basic

● Data Sources can be defined globally in the page or in panels

● Extensible architecture for new data sources in the future

● Based on the Java back-end API

● What if my view or folder is in another db on another server

● And if I want to use a replica id instead of a database name?

● If multiple document data sources are defined on the page ...

● Tweaking the URL behavior

● More detailed example online

● Example: repeating documents

● Data collections can be iterated using dedicated controls

● The view panel has extended user behaviors

● 2 modes are available:

● A pager can now be configured to navigate to the last entry (8.5.2)

● A custom control can use the same behavior

● Load time versus runtime execution

● Uses the javascript: prefix in an expression

● The available scopes

● The XPages context object

● Libraries processing model

● Adding Java files into an NSF

● Adding libraries into an NSF