A server action is generated from the client side when you call IlvView.prototype.performAction method. Server action listener will query the server for a new image, but additional parameters are sent in the image request so that an action such as adding, removing, or selecting objects can be performed before the image is generated. An action is defined by a name and a list of parameters. To implement the action on the client side, you will implement this class and check the action name and parameters.
If you have read my blog about how to customize interactor , you will find it is not easy to make customization for server action listener. Since JViews 8.8, we introduce more convenient ways to help you plug in your server action listener. You can override or remove the default server action listener and add yourself server action listener. JViews provides two ways for you to plug in server side action listener since version 8.8
The configuration rules as following:
If actionName is not exit action table, then the actionListener instance into server action listener list.
If actionName is exit in action table, then the actionListener instance will replace the old action listener.
If actionName is exit in action table, and actionListener is default value Object, then will remove the server action lister which used to deal with the actionName action.
you know, JViews web deployment provides many interactor components
to do interaction with view component. You can select, move and delete a
node in the diagrammer. You also can show tooltip or highlight a
node and so on. Even
there are many interactor components exist, maybe all those existing
interactors cannot satisfy your peculiar requirement . In this
case, you will want to do some customization. Before customizing
interactor, we need to know how interactor works in JViews. Let's go
through some diagrams to learn the interactor's working process now.
of client side and server side class diagrams show as below, they
can help us understand how interactor component works in JViews . We have
two ways to customize interactor on client side. One way is to
override the existing interactor, for example, IlvSelectInteractor. The
other way is to create a new interactor extends IlvInteractor.
side class diagram
the server side, for customizing interactor, we often need to
override an existing action listener class or create a new action
listener class to
then add it into manager servlet.
side class diagram
(I chose diagrammer... [More]
WebSphere Application Server Community Edition (WASCE) is a certified Java EE 6 application server. It is a IBM supported version of Apache Geronimo that uses Tomcat for servlet container and Axis 2 for web services. You can get more information on IBM WASCE website here and download it for free. In this blog post, I will show you different ways to deploy JViews Enterprise demo on WASCE 22.214.171.124. Deploy using a complete war file The first way is the easiest way. Like any other application servers, you can deploy JViews Enterprise demo with all jars bundled inside the war file. The steps are: Build the complete war file Open a command window and go to your JViews folder Run ant build.complete to generate a complete war file Stop Myfaces service in WASCE Log into WASCE administrative console Go to Applications -> System Modules Check the Expert User check box Find the module org.apache.geronimo.configs/myfaces/2.1.7/car and click stop Deploy the war file Go to Applications -> Deployer Click Browse button for Archive to locate your war file Click install button Deploy using shared library The second way is to use shared library provided by WASCE. In this way, you need to write a deployment plan for each JViews Enterprise demo to tell WASCE that this application needs to use shared library as a reference. The steps are: Build the war file Open a command window and go to your JViews folder Run ant build to generate a war file Write a deployment plan to use shared... [More]
As mentioned in previous blog posts (for instance Displaying attractive diagrams: quick hints for choosing a graph layout algorithm from Dojo Diagrammer ),
Dojo Diagrammer provides a comprehensive set of layout algorithms for
laying out nodes and links in graphs. In the present post I will provide
more in-depth information that may help for configuring the link layout
in a tricky case of graphs: nested graphs. Nested graphs are graphs
where nodes contain another graph, as opposed to flat graphs which do
not contain other graphs. An example of nested graph: In Dojo Diagrammer, there are several ways to get the links laid out. Link layouts can be performed by: Node
layout algorithms that also have extensive built-in link layout
capabilities: HierarchicalLayout, TreeLayout. These provide various link
styles and many configuration options. Node layout algorithms
that only support a straight link style: CircularLayout,
ForceDirectedLayout. These provide support for self-links (links
connecting a node to itself) and multi-links (several links that connect
the same pair of nodes). Specialized link layout algorithms: ShortLinkLayout and LongLinkLayout. These can be used in conjunction with a node layout. All
these algorithms can be applied to flat or nested graphs. The case of
nested graph is the trickiest, mostly because of two reasons: The
layout algorithms being applied locally to each subgraph in a
bottom-to-top traversal of the graph hierarchy,... [More]
In a previous blog post ( Displaying attractive diagrams: quick hints for choosing a graph layout algorithm from Dojo Diagrammer ), I've provided hints about how to choose a graph layout algorithm among those available in Dojo Diagrammer. Complementary
information about how to configure the parameters of these algorithms
can be found in the following developerWorks article: The
parameters that matter most for creating interactive diagrams on mobile
devices. (Algorithm tips and performance hints for using IBM ILOG Dojo
Diagrammer) . Hope this helps! (and, if you have questions, don't hesitate to ask)
Many types of complex business data can best be visualized as a set of
nodes and interconnecting links, more commonly called a graph or a
diagram. Examples of graphs include business organization charts,
workflow diagrams, telecom network displays, and genealogical trees. The
mathematical concept of graphs is so general that it is used as a
modeling tool in almost any domain. When we need to get a visual
understanding of the graph data, there is a need for the automatic
visualization of graphs. The purpose is to optimize the display by
obeying common rules in a given field and by maximizing the readability. Dojo Diagrammer , the new visualization component included in IBM ILOG JViews Enterprise 8.8, allows applications to display and edit graphs
(diagrams) and provides a comprehensive set of graph layout algorithms
for the automatic placement of the nodes and/or to ensure the links have
optimal shapes. For a flexible adaptation to various deployment requirements, the graph layout algorithms are available both client-side and server-side .
In the client-side case, the Dojo implementation of the algorithms runs
inside the browser. In the server-side case, a RESTfull/JAX-RS service
provided by Dojo Diagrammer executes the Java implementation of the
algorithms on the server, and the data passed between the browser and the
choose the client-side algorithms, or have a server... [More]
The IBM ILOG Dojo Diagrammer widget is a new visualization component included in IBM ILOG JViews Enterprise 8.8. As its name indicates, Dojo Diagrammer is a Dojo widget. If you are not familiar with Dojo, you can take a look here . Dojo Diagrammer is completely implemented in
interactions like selection, zooming, panning, and editing without any request to the server. Here are some examples of diagrams created using Dojo Diagrammer: An organization chart, where nodes represent people in the organization and links show the manager hierarchy.
A business process where nodes represent tasks or events and links represent transitions (solid lines) or messages (dotted lines). Dojo Diagrammer renders the diagram using vector graphics directly in the browser. For this, Dojo Diagrammer relies on the dojox.gfx module for its low-level rendering. GFX takes care of the final rendering using whatever 2D graphics technology the browser supports (SVG, VML, Canvas, ...). This means that you can use Dojo Diagrammer on any browser without caring of what the browser supports. Like many Dojo widgets Dojo Diagrammer can connect to a Dojo data store to load data from the server. This is roughly similar to how JViews Diagrammer loads data from a data model. The items of the data store will be represented by nodes, and there are different... [More]
Released earlier today is the new JViews Enterprise V8.8 trial available for you to try the full-featured product for 90-days. You can read further about the new features in version 8.8 . Download IBM ILOG JViews Enterprise, a set of tools, components and APIs for building the advanced graphical displays needed by business-critical applications. The product is designed for software developers working in Java and deploying to the desktop or Ajax-enhanced browser.
Today we look a little bit deeper inside the architecture of the SDM renderers, and what to do when things go unexpected or totally wrong in the rendering process. The IBM ILOG JViews Diagrammer has a MVC architecture that is controlled by style sheets. The data model representing the application data determines which objects exist and what are the object's properties. Whenever a new model object is created or deleted, or whenever a model property changes, the SDM data model communicates with the SDM engine by events. The task of the SDM engine is to refresh the graphic objects displayed in the SDM view. This is achieved by calling methods in the SDM rendering chain. For instance when a model object representing a node is added to the model, the model sends an SDMModelEvent to the engine, which then calls the method addNodeGraphic of IlvSDMRenderer on the first SDM renderer in the chain. The task of the SDM renderers is to create or to modify the graphic objects displayed in the view. The CSS style sheets specify which renderers are available and what each renderer should do in detail.
Why is it a renderer chain? The SDM engine knows only the first renderer, and each renderer has a link to the next renderer. Each renderer decides inside a rendering method what to do with the changed situation. If a renderer cannot handle the situation, it forwards the call to the next renderer in the chain, expecting that one of the next renderers will be able to handle the... [More]
There are three new IBM ILOG JViews Enterprise interactive demos for you available to help illustrate the range of graphical interfaces that can be built using JViews Enterprise: 1. Dojo Organization Chart - This example shows how the Dojo implementation of JViews Diagrammer can be used to display smart client-side organization charts. 2. Dojo Business Process Management (BPM) - JViews Enterprise’s Dojo capabilities can be used to display sophisticated business process flow diagrams. 3. Dojo Graph Layout Browser - Browse through the JViews Enterprise graph layout algorithms and parameters in this interactive, tutorial-style demo, in which all drawing and layout algorithms are client-side. We also have 19 additional interactive demos available if you are interested in playing with other features of JViews Enterprise. Enjoy!! Leave a comment and let us know what you think of these new demos.