7.1.5  Request event 

Request events occur when the 

processRequest 

method is called from an application JSP page. One event 

is raised for every HTML element that is passed from the JSP page in the HTTP request. The events are 

useful for overriding values that are then passed to actual e FixIT data components. For example: 

  void this_request(RequestEvent e) { 

   if (e.getParameterName().equals("abbreviation")) 

    e.setParameterValue(e.getParameterValue().toUpperCase()); 

  } 

This event changes all values of FM field 

abbreviation

  to upper case, just before the value is passed to 

the actual data component. 

7.2  FixIT based events 

As the server application has no graphical user interface, it cannot receive input directly from user. This 

means that easiest way to add logic to the application is via events that are provided by database 

components, 

afterSave

/

beforeSave

 in XfijSource, for example. The events work the same way as in 

Delphi/Web FixIT. For an example, please see chapter 11.3. 

7.3  Properties of a server application object 

The picture in chapter 6.4 shows the properties of a server application object. 

applicationName

. This name is used for logging purposes and in configuring broker connections 

(see below: 

maxWRPCBrokers

). For more information, please see chapters 7.8 and 8.1. 

context

. This property describes the context (which is found in OPTION file) in which the 

application is run FileMan wise. For more information about options, please see 

FixIT 

Developer's Guide

, chapter 3. 

editAlways

. If this property is set true, the application assumes it is always in edit state. If the 

property is false(default), the end user must click Edit or Insert button to edit a record.

maxWRPCBrokers (a hidden property)

. Leaving this property to   1 (default) means each 

server application will create a new broker for database connection each time a new user logs in. If 

you have want to impose a strict limit in your M server for user processes e FixIT applications use, 

you may consider setting the property.

However, this property should 

ONLY

 be set if there's 

really

 a need to limit the number of 

available connection for e FixIT applications. Only the number of connections you specify will be 

used for one www server. For example, if your server application's 

maxWRPCBrokers 

is set to 

2, 

all

 the created application objects (of a specific application) will share the two connections 

provided. This property can be set also at run time. It should be set before 

getBrokerFromPool()

is called in the application Java code. 

If you set this property, you will have to set also 

sharedAccessCode

 and 

sharedVerifyCode

properties of the application. These codes will be always used by a connection, after a new user 

first logs in. 

This property should be used with extreme caution in a multi user application 

environment, because several users may be using the same broker connection between 

www server and the database server; this will likely lead to unwanted behaviour from the 

26