EP1873656B1 - Faciliter l'accès aux données d'application sur un serveur d'application par un dispositif de communication sans fil - Google Patents

Faciliter l'accès aux données d'application sur un serveur d'application par un dispositif de communication sans fil Download PDF

Info

Publication number
EP1873656B1
EP1873656B1 EP06115926A EP06115926A EP1873656B1 EP 1873656 B1 EP1873656 B1 EP 1873656B1 EP 06115926 A EP06115926 A EP 06115926A EP 06115926 A EP06115926 A EP 06115926A EP 1873656 B1 EP1873656 B1 EP 1873656B1
Authority
EP
European Patent Office
Prior art keywords
markup language
application
action
routines
tag
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP06115926A
Other languages
German (de)
English (en)
Other versions
EP1873656A1 (fr
Inventor
Tim Neil
Scott Neil
Steve Grenier
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BlackBerry Ltd
Original Assignee
Research in Motion Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Research in Motion Ltd filed Critical Research in Motion Ltd
Priority to EP06115926A priority Critical patent/EP1873656B1/fr
Priority to CA2592399A priority patent/CA2592399C/fr
Publication of EP1873656A1 publication Critical patent/EP1873656A1/fr
Application granted granted Critical
Publication of EP1873656B1 publication Critical patent/EP1873656B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • G06F16/986—Document structures and storage, e.g. HTML extensions

Definitions

  • This invention relates to an approach to facilitate access to application data at an application server by a wireless communication device.
  • an application on an application server could be modified to parse received messages originating from the wireless communication device, trigger appropriate processing internally to the application, and generate any necessary message(s) in response.
  • This approach may require the existing application programming interface (API) to be modified to provide exposed routines (i.e. routines that are invokable from another computing device such as an intermediary transaction server) conforming to a predefined interface.
  • API application programming interface
  • the interface may require predetermined routine names and parameter names to be used, so that software executing at the intermediary transaction server can "hard code" invocations of these routines in order to pass along data from messages originating from the wireless communication device.
  • a wrapper application could be written and executed at the application server. The wrapper application could parse messages received from wireless communication devices and make appropriate API calls, passing information from the messages as parameters. In either approach, if the burden of making the needed modifications falls upon an integrator who is not the application provider, implementation may disadvantageously be slowed by the integrator's unfamiliarity with the API of the application.
  • US2004/254855 discloses an XML document with a markup language element and subordinate attributes specifying product information for use in a shopping basket system may be invoked via a graphical image, such as an icon, on a web browser or a desktop of the client computer.
  • FIG. 1 is a schematic view of a system suited for use of an embodiment of the subject invention
  • FIG. 2 is a schematic view of a rapid application development tool component of FIG. 1 configured in accordance with this invention
  • FIGS. 3A and 3B illustrate an exemplary XML document in accordance with an embodiment of this invention
  • FIGS. 4A-4C illustrate a portion of the graphical user interface of the rapid application development tool of FIG. 2 ;
  • FIGS. 5A and 5B illustrate an exemplary XML document in accordance with an embodiment of this invention
  • FIG. 6 is an example XML package from a wireless communication device
  • FIGS. 7A-7C contain pseudocode of object-oriented classes instantiated at the transaction server of FIG. 2 ;
  • FIG. 8 contains pseudocode of an object-oriented class forming part of a connector library at the transaction server of FIG. 2 .
  • Hulai et al. contemplate intercommunication between the application and multiple wireless computing devices of various types executing distinct operating systems such as the RIM operating system, Windows CB, or the Palm OS.
  • Each wireless communication device in communication with the transaction server is provided with virtual machine ("VM") software to interpret and "execute" the definition files.
  • the VM software varies depending upon the operating system of the wireless communication device.
  • a wireless communication device wishes to use an application for the first time, it downloads the application definition file for the application from the transaction server.
  • the application definition file controls the screen display at the wireless communication device, including the display of application data at the device, and the nature of possible user inputs, such as through displayed entry fields.
  • a package (message) containing this information in a format that accords with a format defined in the definition file may be created and sent to the transaction server.
  • the transaction server passes such packages to the application server.
  • a rapid application development (RAD) tool may be employed.
  • a RAD tool may be programmed computer providing an intuitive graphical user interface (GUI) that facilitates "drag and drop" application development, so that even those who lack depth of expertise in software development or markup languages may create definition files.
  • GUI graphical user interface
  • an integrator may create a hierarchy of graphical icons from a predetermined set of available icons. Icons generally correspond to XML elements representative of various wireless communication device application programming constructs, such as tables for storing data, messages to be sent to the transaction server, user interface screens, user interface screen components (e.g. widgets), actions to be performed upon the occurrence of specified events, and so forth.
  • Each type of icon may have properties, corresponding to attributes of the corresponding XML element, that may be viewed and set by a user through the GUI.
  • the structure of a created hierarchy of graphical icons, in terms of which icons are contained by (or are "children of") which other icons, may be limited by the permissible containment (i.e. parent - child) relationships between the various represented XML elements, as dictated by an applicable XML schema.
  • the tool 116 automatically generates the corresponding XML.
  • the RAD tool may prevent the integrator from having to manually develop definition files, which, although possible, would burden the integrator with learning the details of the applicable XML schema and with generating a valid and well-formed markup language document.
  • the RAD tool may be implemented within a generic integrated design environment (IDE) framework such as the Eclipse framework.
  • IDE integrated design environment
  • the subject embodiment utilises aspects of this approach to handling communications with wireless communication devices in a new approach, effected largely at the transaction server, for handling wireless computing device communications with the application on the application server.
  • FIG. 1 illustrates a system suited for use with an embodiment of the subject invention.
  • System 10 has an application server 12 with an application 14.
  • the application server 12 is connected to a transaction server 20 which, in turn, is connected to a wireless network gateway 22.
  • the connection between transaction server 20 and each of application server 12 and wireless gateway 22 may be by way of a data network (not illustrated), such as the Internet and may use HTTP running on top of a standard TCP/IP stack for example.
  • the wireless network gateway 22 connects to a wireless network 24 as does a wireless communications device 30.
  • Device 30 may be of the type described in U.S. Patent No. 6,396,482 issued May 28, 2002 to Griffin , the contents of which are incorporated by reference herein.
  • the device may have a processor operatively connected to a transceiver, a display, a memory, and a user interface.
  • a RAD tool 40 may also connect to the transaction server.
  • the integrator causes virtual machine software 60 at the transaction server 20 to parse incoming messages from the wireless communication device 30, pass message data to the application 14, and return any results from the application 14, via a connector 42 that is deployed at the transaction server 20.
  • the connector is a set of electronic files which effectively define a new API providing convenient access to the application 14 at the transaction server 20.
  • the integrator supplies a markup language document 44, referred to as a "master definition file", to the transaction server 20 which effectively configures the virtual machine software 60 to parse the incoming messages and pass parsed data to the application 14 via the new API provided by the connector. Creation of the master definition file 44 may be facilitated by a rapid application development (RAD) tool 40.
  • RAD rapid application development
  • FIG. 2 illustrates the transaction server 20 and RAD tool 40 of FIG. 1 in greater detail.
  • the server contains a conventional processor 24 interconnected with memory 26.
  • Memory 26 stores the connector 42, master definition file 44, and virtual machine software 60.
  • memory 26 stores object-oriented classes 62 and objects 70.
  • Virtual machine software 60 and classes 62 may be loaded from a machine-readable medium such as an optical disk 64.
  • the connector 42 has two components, namely, a library 48 and a connector descriptor document 50. Both of these components are authored by a "connector provider", who is either the application provider or another party with detailed knowledge of the application 14.
  • Library 48 is a set of one or more electronic files containing precompiled routines 49 for accessing the application 14.
  • the routines effectively define a new API, intended for use at the transaction server 20, that becomes the "face" of application 14 from the perspective of other, calling code at the transaction server-specifically, virtual machine software 60 (described below).
  • Routines 49 are written so as to provide useful or convenient mechanisms for "mobilizing the application", i.e. for causing the application to become accessible by wireless communication device 30.
  • the routines 49 take the form of methods defined within object-oriented classes.
  • the library 48 is a .NET assembly file (having the extension ".dll") comprising byte code that was generated by compiling source code written in an object-oriented programming language such as C# or Java for example.
  • the routines 49 include calls to the legacy API of the application 14 and may include logic which "massages" returned data from the application into a form that is useful for "mobilizing" the application.
  • the legacy API calls may employ such technologies as the Simple Object Access Protocol (SOAP) or Distributed Common Object Model (DCOM) for example, which are known in the art.
  • SOAP Simple Object Access Protocol
  • DCOM Distributed Common Object Model
  • routines 49 are written in contemplation of, and in support of, application mobilization. This may be contrasted against the application's legacy API, which may not contemplate presentation of the application at a wireless communication device at all.
  • a library routine may invoke a legacy API function which returns all email messages of a user's inbox, and may then provide a subset of those messages, say, fifteen email messages at a time upon each subsequent invocation. This may be useful for mobilizing an email application given that a typical wireless communication device display may only be able to list about fifteen messages at once, due to size constraints.
  • a wireless communication device application is to present two categories of data on its screens (e.g.
  • a library method could, when invoked, call a first legacy API function with certain parameters (e.g. an account number) and receive a return result falling within the first category (account holder surname), use the return result to invoke a second legacy API function and receive a return result in the second category (financial information), and further use both return results in formulating a customized return result (surname with financial information) that is convenient for presentation at the wireless communication device.
  • the library routines 49 effectively shield an integrator who is tasked with mobilizing an application from the legacy API, which may be confusing or ill-suited for use in accessing application data for presentation at a wireless communication device, and provides in its place a new API, to be invoked at run-time, which is better suited to application mobilization.
  • the integrator need only invoke the methods of the new, better-suited API in order to gain access to the application 14.
  • the integrator need not understand how the library routines 49 achieve their result.
  • the second component of connector 42 is a markup language document 50, referred to as a "connector descriptor" document, which describes the new API, i.e. describes the routines 49 in the library that are available for invocation at the transaction server 20.
  • the connector descriptor document 50 may also describe other aspects of the library 48 (e.g. system variables).
  • the connector descriptor document 50 is written in a markup language, such as Extensible Markup Language (XML), to facilitate its parsing and usage at run type by the virtual machine software 60.
  • XML Extensible Markup Language
  • the information in the connector descriptor document 50 facilitates the invocation of library methods 49 by the virtual machine software 60.
  • the relationship between a connector 42 and an application 14 is typically (but not necessarily) one-to-one. Thus if access to two applications was desired, two connectors may be used. The present embodiment seeks access to only one application 14, thus only one connector 42 is provided.
  • the connector 42 may also be referred to as a data source or a "plug-in". The latter term is based on the fact that the connector descriptor document 50 portion of the connector 42 can also be "plugged into" the RAD tool 40 to configure the tool 40 for generation of a master definition file 44, as will be described.
  • the master definition file 44 is a hierarchy of XML elements which effectively "encode” the manner in which the virtual machine software 60 at the transaction server 20 should: parse incoming XML packages from the wireless communication device 30; invoke library routines 49 to pass parsed message data to the application 14; and send response messages (also XML packages) back the wireless communication device 30.
  • the XML elements of the master definition file can be used to define "business logic" for execution at the transaction server 20, in support of mobilizing the application. For example, certain XML elements can be used to define if-then-else logic which results in the run-time invocation of two different library methods 49 (in the alternative) based on an ascertained value of a field in an XML package.
  • the virtual machine software 60 interprets these XML elements and generates a like hierarchy of object instances 70 at run time in the memory of the transaction server 20.
  • the relationship between an XML element and an object instance is generally one-to-one.
  • the object instances 70 are instantiated from a set of object classes 62 stored in memory 26. Each object 70 has data members that are populated with the values of the XML attributes associated with the corresponding XML element in order to "customize" the object for effecting the desired operation.
  • the master definition file 44 is generated by the integrator, with knowledge of: (1) the format of wireless communication device packages expected to be received at transaction server 20; and (2) the new application API (i.e. exposted library methods 49) as described by the connector descriptor document 50.
  • the XML may be in accordance with the XML 1.1 W3C Recommendation, 4th February 2004, Institut Yergeau et al. (edited in place 15 April 2004), provided at www.w3.org/TR/2004/REC-xml11-20040204/, the contents of which are hereby incorporated by reference hereinto.
  • the author of the virtual machine software 60 may publish interfaces (e.g. C# or Java interfaces) indicating types of objects (classes) and methods that need to be implemented within the library 48 in order for the virtual machine software 60 to be able to use the library 48 to access the application 14.
  • interfaces e.g. C# or Java interfaces
  • objects classes
  • methods that need to be implemented within the library 48 in order for the virtual machine software 60 to be able to use the library 48 to access the application 14.
  • the connector object may contain properties representing information necessary to connect to a back-end application (e.g. usemame, password, and path member fields) and may require implementation of a "connect" method for establishing a connection to the application.
  • the connector object may implement the following exemplary interface (shown in the C# programming language):
  • the looping object represents an array or set of objects returned by the application 14 and may require implementation of methods to facilitate processing these objects one by one, such as: a method to indicate the first object in the array or set ("beginning of the file”); a method to indicate the last object in the array or set ("end of the file”); a method to move to the next object; a method to move to the previous object; a method to move to the first object; and a method to move to the last object.
  • a looping object may also expose ad-hoc functions such as a function that returns a scratchpad Value or a function that returns looping object.
  • the looping object may implement the following exemplary interface:
  • a system variable object would allow the integrator to define a system variable (i.e. a variable defined within library 48) that could be accessed or set from the virtual machine software 60 at run time.
  • System variables could represent a username, password, and operating system path to the application at the application server, or other variables that may be useful in connection to application 14.
  • the system variable object may implement the following exemplary interface.
  • RAD tool 40 may be a computer having a processor 41 connected to memory 43 ( FIG.2 ).
  • the memory 43 stores the RAD software 52 which may be loaded for execution from a machine-readable medium such as an optical disk 54.
  • Execution of the RAD software 52 causes, RAD tool 40 to present a GUI which allows a user (the integrator) to enter user inputs 46 for defining a hierarchy of icons representing operation at the transaction server 20.
  • the hierarchy governs the run-time operation of virtual machine software 60 in parsing XML packages from device 30, invoking methods 49, and sending return results in other XML packages to device 30.
  • RAD software 52 is pre-programmed (e.g. as loaded from optical disk 54) to make available within the RAD tool GUI certain "default" icons that may be used (added to a hierarchy of icons) regardless of the nature of the connector(s) to be employed to access the application 14.
  • Such icons may for example represent such program constructs as table definitions defining local tables for storing application-related data or package definitions defining messages to be received from and sent to wireless communication device 30 or ACTION constructs as described in Appendix "A".
  • the RAD tool 40 is further configured with the connector descriptor document 50 "plug-in" to make the tool 40 aware of the objects (and invokable methods thereof) of connector 42.
  • the plug-in causes new selectable options to appear within the GUI of RAD tool 40 that are specific to the connector 42.
  • an ACTION icon may have a new type representing the invocation of a specific method 49 of a particular class defined in library 48.
  • a list e.g. in the form of a pull-down menu
  • another list e.g.
  • the RAD tool GUI may further enumerate the parameters for that method in a further properties window pane, with an edit box next to each parameter for entry by the integrator of the parameter values.
  • the RAD tool user may cause XML elements and attributes for effecting an invocation of that method to become encoded in the resultant master definition file 44 that will ultimately be generated by the RAD tool 40. If the RAD tool 40 were configured with one (or more) different connector descriptor documents, different options (e.g. different objects, methods and parameters) may become available in the RAD tool GUI.
  • the RAD tool 40 does not use the library portion 48 of connector 42. Accordingly, this portion 48 need not actually be resident in memory 43 of RAD tool 40. To reflect this fact, the library 48 is indicated in memory 43 with a dashed border in FIG. 2 .
  • the master definition file 44 and connector 42 are downloaded to the transaction server 20 prior to run time.
  • the virtual machine software 60 at the transaction server 20 instantiates objects 70 based on the master definition file 44 and triggers execution of certain methods of the objects 70.
  • the objects 70 essentially await the arrival of XML packages from the wireless communication device 30 and, upon their arrival (which is signaled by operating system callbacks into methods of certain objects 70), the objects 70 make appropriate calls to the methods 49.
  • the objects 70 may dynamically link to the library 48 to make these calls possible.
  • Instances of the classes defined in library 48 may be instantiated through use of an execution environment, such as a .NET framework (not shown), in conjunction with information from the connector description document 50, such as qualified name information for classes of the .NET assembly .dll file.
  • the qualified name information may be used to create instances of the classes (objects) of the .NET assembly.
  • the handles to these objects permit object methods 49 to be invoked.
  • an XML package arrives at the transaction server 20 from the wireless communication device 30, the instantiated objects 70 effectively parse the package into pieces, which are supplied to the application 14 via the instantiated library objects which effect the "new API" defined by connector 42.
  • any return result from the application 14 may trigger generation of a return XML package by objects 70, which package is sent to the device 30 to complete the transaction.
  • FIGS. 3A and 3B show a sample connector descriptor document 50, written in XML, which exposes functions of a custom API for connecting to and accessing an SQL database.
  • the described connector provides an ADO-like connector to an SQL database.
  • ActiveX Data Objects (ADO) is a Microsoft technology which provides a layer over a programming language (here SQL) to allow access to an SQL database with no knowledge of SQL. Further information concerning ADO is available at:
  • line 3 gives the connector descriptor document 50 the name "MyCompanyName.ADO". This name is referenced from the master definition file 44. The reference to document 50 within master definition file 44 permits the former document to be located at run time at the transaction server 20 by objects 70,which are formed based on the parsing of the file 44.
  • the type attribute on line 3 indicates that the library 48 is a .NET assembly.
  • Line 5 provides the name of the file representing library 48 so that it can be located at the time at the transaction server 20 by objects 70.
  • Lines 6 and 7 identifies the objects Username and Password as system variables. This indicates that the library 48 declares variables named Username and Password which can be set and read by objects 70 at run time.
  • Lines 8 to 20 declare an object named "ADOConnection” which implements the interface "Connector”, as indicated by the type attribute.
  • This declaration indicates that the library 48 defines a class named "ADOConnection” which implements the interface "Connector”.
  • the qualified name of the class namely "mycompany.ado.ADOConnection” is indicated by the qualifiedname attribute.
  • This attribute is used by a .NET framework at transaction server 20 (not illustrated) for purposes of identifying the correct class of the adoimpl.d11 file at run time, via reflection, for purposes of dynamically invoking the methods described below.
  • Lines 12 to 14 expose a method "Connect” of the ADOconnection object which has a string parameter "adostring".
  • the method returns a scratchpad value (i.e., a value that is cached at the transaction server 20) indicative of whether the connection was successfully established (TRUE for success or FALSE for failure).
  • Lines 17 to 19 expose a method "Execute" of the ADO connection object which takes an SQL string as an input (representing a statement used to query the database 14) and returns a set of matching records as a looping object "RecordSet”.
  • Lines 23 to 32 define the RecordSet object as an implementation of the looping object interface and indicates the qualifiedname of the relevant class within the DLL ("mycompany.ado.RecordSet").
  • Lines 27 to 29 expose the method "FieldByName" of the RecordSet object which returns a value of a field in the current record of the set of matching records.
  • the field name is specified by the fieldname parameter. This method extends the basic looping object interface described above.
  • Line 31 exposes the method “GetCurrentRow” of the RecordSet object which returns the current row (record) as a looping object “RecordSetRow”. This method also extends the basic looping object interface.
  • Lines 33-42 of FIGS. 3A-3B define the RecordSetRow object as another implementation of the looping object interface and indicates the qualified name of this object in the .DLL ("mycompany. ado. RecordSetRow").
  • Lines 37 to 39 expose the method "Column Value” of the RecordSetRow object which returns the value of the column (field) for the current row indicated by an input "index” parameter.
  • Line 41 exposes the method "ColumnCount" of the RecordSetRow object which returns the number of columns for the current row.
  • FIGS. 4A-4C illustrate a screen shot of a portion of the RAD tool GUI after configuration of the RAD tool 40 with the connector descriptor document 50 plug-in and entry of user inputs 46 by an integrator.
  • FIGS. 4A-4C are perhaps best viewed in conjunction with FIGS. 5A and 5B , which illustrate the master definition file 44 corresponding to the icon hierarchy shown in FIGS. 4A-4C as may ultimately be published (output) by the tool 40.
  • the window illustrated in FIGS. 4A-4C is a "project explorer" window which may represent only a portion of the GUI of RAD tool 40.
  • the term "project” is essentially synonymous with the master definition file 44 under development.
  • the project explorer contains a visual hierarchy of icons 100 that is created by the integrator to indicate the processing that should be performed at transaction server 20 by objects 70, in conjunction with connector 42, responsive to the receipt of XML packages from device 30.
  • the RAD tool GUI may include a main design area and a toolbar.
  • the main design area may display the properties of currently-selected application component (icon) of the hierarchy 100.
  • the properties are XML attributes associated with the XML element that is represented by the icon.
  • the user of the RAD tool 40 may be able to enter text in editable fields near each property name to set the XML attribute values.
  • the toolbar may facilitate various development activities which occur during the creation of the hierarchy 100.
  • the toolbar may for example include a menu list and icons for compiling or publishing the current project. Compiling refers to checking of various aspects of the defined program structure for errors or possible deviations from good programming practices (e.g. for an if then-else ACTION icon, a hint message may advise the user that no actions have been defined in the "else" logic branch).
  • Publishing refers to generating the master definition file 44 from the hierarchy 100. Publishing may entail serialization of a Document Object Model (DOM) tree representation of the master definition file 44 that is automatically generated within the memory 43 of RAD tool 40 as the user creates icons and assigns properties to them.
  • DOM Document Object Model
  • DOM Document Object Model
  • the hierarchy 100 includes three main branches represented by icons 102, 104 and 106.
  • the first two branches correspond to a portion of master definition file 44 which defines a wireless communication device application for downloading to, interpretation by and execution at the wireless communication device 30.
  • Device independent branch 102 pertains to aspects of the wireless communication device application which are consistent between wireless communication device operating systems, such as the definition of application events (occurrences which trigger processing at wireless communication device application regardless of the application's status), database tables (tables for storing application-related data at device 30) and data rules (rules which dictate how incoming or outgoing XML packages affect data stored in database tables at device 30).
  • the operating system branch 104 is for the definition of operation system-specific GUI screens that are displayed at the device 30.
  • server branch 106 corresponds to a portion of master definition file 44 which defines transaction server operation for parsing incoming messages from the wireless communication device 30, passing message data to the application 14, and returning any results from the application 14 to the device 30.
  • Server branch 106 is shown in expanded form (i.e. with subordinate branches/icons visible) in FIG. 4A .
  • Each server branch contains a data source branch and a rules branch.
  • the data sources branch 108 below server branch 106 identifies the connectors that the integrator has opted to use at transaction server 20 for connecting to application 14.
  • the integrator has opted to use only connector 42 to access the application 14. Accordingly, only one connector icon 110 appears in the data sources branch 108.
  • the data source branch 108 corresponds to lines 2-9 of FIG. 5A .
  • the user interaction with the RAD tool GUI for defining the connector icon 110 in the project explorer window may be as follows.
  • the data sources icon 108 may initially be selected with a mouse (or similar user input mechanism) of the RAD tool 40.
  • a right click (or similar user action) may cause a pop-up menu to be displayed.
  • the pop-up menu may present a list of permissible actions that may be taken in the context of the data sources branch 108, including which icons can be created in that branch.
  • An Add Connector option may permit the user to create an icon representing a connector to be used to access application 14 at run time. Selection of that menu item may cause the icon 110 to be created below icon 108, as shown in FIG. 4A , and a connection properties window to be displayed in a main design area of the RAD tool GUI.
  • a name field 122 allows the user (the integrator) to enter a name (“MyConnection") that will be displayed as part of the icon 110.
  • a "Connector” field 124 provides a drop-down list which lists, by name, each connector for which a plug-in has been provided to the RAD software 52 ( FIG. 2 ). In FIG. 4A , the list is illustrated in a dropped-down state, with only one entry, namely "ADO Connection", being visible.
  • the descriptor "ADO Connection” corresponds to the sole connector 42 of the present embodiment, and originates from the displayname attribute at line 2 of the connector descriptor document 50 ( FIG. 3A ).
  • a "read-only" portion A of the hierarchy 100 shows, at a first level, all of the classes defined in the library 48 (ADOConnection, RecordSet and RecordSetRow) and, at a second level, each method defined within each class.
  • a third level (not illustrated) may show each parameter for each method and the type of each parameter.
  • the information presented in read only portion A is obtained from the connector descriptor document 50 and is presented to communicate information about the features of connector 42 to the integrator.
  • the connector document 50 may be parsed and converted to a DOM tree representation to facilitate dynamic access to the XML elements and attributes of document 50 and their values to make presentation of portion A possible.
  • the rules branch 150 below server branch 106 contains one or more rules for handling messages from the wireless communication device 30.
  • a rule represents the processing to be performed by transaction server 20 upon the arrival of a particular type of XML package from device 30. Only one rule is defined in the present embodiment, for handling a package of type LOGIN. An exemplary instance of a LOGIN package is illustrated in FIG. 6 . This rule is represented by the rule icon 152.
  • the user interaction with the RAD tool GUI for defining the rule icon 152 in the project explorer window may be similar to the above-described procedure for creating a connector icon 110.
  • the Rules icon 150 may initially be right-clicked to cause a pop-up menu to be displayed with a list of permissible actions.
  • An Add Rule option may permit the user to create the icon 152 below icon 150 and a rule properties window to be displayed in a main design area of the RAD tool GUI.
  • rule properties in the rule properties window is illustrated in inset 160.
  • a name field 162 allows the user to enter a name (“DoLogin”) that will be displayed as part of the icon 152.
  • An "associated package” field 164 provides a drop-down list which lists, by name, each package that can be received at transaction server 20 as defined under the device independent branch 102 ( FIG. 4A ).
  • FIG. 4B the list is illustrated in a dropped-down state, with two entries, namely "LOGIN” and "LOGOUT", being visible.
  • the "LOGIN” entry corresponds to a LOGIN package, for which an exemplary instance (as might be received at run time) is shown in FIG. 6 .
  • the text "LOGIN” in the drop-down list originates from the pkgtype attribute of the PKG element.
  • the rule 152 is represented in master definition file 44 by the AXRULE element which is opened at line 11 of FIG. 5A .
  • the fact that the package has a body containing only one element also named "LOGIN" is indicated by the elementname and multielement attributes at line 11.
  • the actions icon 170 of FIG. 4B represents the actions to be performed when the package identified by the containing rule icon 152 (i.e. LOGIN package) arrives at the transaction server 20.
  • Icon 170 corresponds to the ACTIONS element (opened at line 12 of FIG. 5A , closed at line 63 of FIG. 5B ) and may be automatically generated below icon 152 upon the latter icon's creation.
  • Actions icon 170 a total of six action icons 172, 174, 176, 178, 180 and 182 are defined. Each of these action icons may be defined by initially right-clicking actions icon 170, selecting an Add Action pop-up menu option, and specifying a type for the action.
  • Permissible action types are defined in section 6 of Appendix "A" of U.S. Patent Application No. 10/537,621 . New action types DATASOURCEMETHOD, DATASOURCEVARIABLE, DATAOBJECTMETHOD and EXCEPTION, not described in the above noted publication, may also be defined. These action types are described below.
  • the actions 172, 174, 176, 178, 180 and 182 are performed in the order in which their icons appear in FIG. 4B . Only one of the icons 182 is shown with subordinate branches expanded in FIG. 4B ; the subordinate branches are collapsed for the other actions.
  • Action icon 172 represents a SAVEITEM action whereby the value of the attribute "username” in the LOGIN XML package shown in FIG. 6 is saved to a scratchpad memory variable "LoginUsername". This icon corresponds to the ACTION XML element at line 13 of FIG. 5A .
  • the value [XPATH:@username] uses Xpath notation.
  • XPath is a language that describes a way to locate and process items in XML documents by using an addressing syntax based on a path through the document's logical structure or hierarchy. Xpath is known in the art.
  • action icon 174 represents a SAVEITEM action whereby the value of the attribute "password" in the LOGIN XML package is saved to a scratchpad memory variable "LoginPassword".
  • Icon 176 corresponds to the ACTION XML element at line 14 of FIG. 5A .
  • Action icon 176 represent an action of type DATASOURCE-VARIABLE which causes a system variable defined within the library 48 to be set to a value specified by the integrator.
  • action properties may be defined in the main design area as shown at inset 190.
  • a name field 192 allows the user to enter a name (“SetSystemVarUsername”) that will be displayed as part of the icon 176.
  • a "systemvar" field 194 provides a drop-down list which lists, by name, each system variable defined within connector descriptor document 50. In FIG. 4B , the list is illustrated in a dropped-down state, with two entries, namely "Username” and "Password", corresponding to lines 6 and 7 of FIG.
  • Icon 176 corresponds to the ACTION XML element at lines 15-16 of FIG. 5A .
  • Action icon 180 is analogous to icon 176, and represents an action which causes system variable Password to be set to the value MasterPassword.
  • Icon 180 corresponds to the ACTION element at lines 17-18 of FIG. 5A .
  • Action icon 178 represent an action of type DATASOURCE-METHOD which causes one of the methods 49 of library 48 to be invoked at run time.
  • action properties may be defined in the main design area as shown at insets 200, 210 and 220 of FIG. 4C .
  • a name field 202 allows the integrator to enter a name (“CallConnect") that will be displayed as part of the icon 178.
  • An "object" field 204 provides a drop-down list which lists each class (each non-system variable object) defined within connector descriptor document 50, namely ADOConnection, RecordSet, and RecordSetRow.
  • a further methods field 212 may be presented which lists the public methods defined within the context of the selected ADOConnection object, i.e., Connect and Execute.
  • a further return result field 214 and parameters field 222 may be presented based on that selection.
  • the return result field is for user specification of a scratchpad variable name, "SuccessfulConnect", for storing the return result of the Connect method.
  • the parameters field 222 sets forth each parameter of the Connect method next to an edit box entry for user specification of the parameter value.
  • the contents of the field 222, "C:/MyMSFTDB.mdb" are hard-coded by the integrator via user inputs 46, based on knowledge of the directory of application server 12 in which the SQL database is stored.
  • Icon 180 corresponds to the ACTION XML element and subordinate PARAM element at lines 19-22 of FIG. 5A .
  • action icon 182 represents an action of type IF which causes one of the THEN branch 230 or the ELSE branch 232 of actions to be executed at run time based on an integrator-specified condition that is evaluated at run time.
  • the condition is the returned value of the Connect method as stored in the SuccessfulConnect scratchpad variable. If the connection was successful, as indicated by a "TRUE" value in "SuccessfulConnect", the THEN branch 230 is executed, otherwise the ELSE branch 232 is executed.
  • the integrator may specify the condition in an action properties window (not illustrated). This icon 182 corresponds to lines 23-24 of FIG. 5A .
  • THEN branch 230 and ELSE branch 232 correspond to lines 25-57 and 58-61 respectively of FIGS. 5A-5B .
  • Action icon 242 of FIG. 4B is another IF action whose condition is the return result of a run-time invocation of an end-of-file method of the RSLookup looping object.
  • the XML element corresponding to icon 242, i.e. line 33 of FIG. 5A may "activate" at run time a logic branch within an object 70 containing a hard-coded call to the end-of-file method to be executed at run-time. This hard-coded call is possible because the end-of-file method is an implementation of an interface which is known at design time to the author of the class 62 from which the object 70 is instantiated.
  • action icon 252 of type DATAOBJECTMETHOD results in the run time invocation of the FieldByName method of the RSlookup object in the scratchpad, with the value "USERID" being passed for parameter fieldname, and with the result being stored in another scratchpad variable UserID (see lines 35-38 of FIGS.
  • action icon 254 of type ARML results in the run time composition and transmission of an XML package of type LOGINRESPONSE, containing the result of the FieldByName method (as stored in scratchpad variable UserID), and an indication that login authorization has been provided, to wireless communication device 30 (lines 39-45 of FIG. 5B ). Otherwise, in subordinate ELSE branch 256, action icon 256 (lines 47-54 of FIG. 5B ) causes the same message to be sent but with different contents indicating that login authorization was not provided.
  • action icon 260 of type EXCEPTION results in the run-time throwing of an exception, which causes the failure to be logged to an exception file (see lines 59-60 of FIG. 5B ) at the transaction server 20.
  • transaction server 20 receives the LOGIN XML package of FIG. 6 from wireless communication device 30.
  • the transaction server 20 parses the XML package via an XML DOM Parser.
  • the transaction server 20 inspects the headers of the LOGIN XML package for attributes used to identify the master definition file 44 with which the package is associated in local storage.
  • the headers may for example be in the XML transport headers that form part of the same XML element as the ⁇ PKG> tags. These are used by the transaction server 20 and device 30 for routing.
  • An exemplary header may be as follows:
  • the values of the APPNAME and VERSION attributes are the name and version of the application registered on the transaction server 20. This information is used by the server 20 to uniquely identify master definition file 44 (the "application") corresponding to the message.
  • the virtual machine software 60 then instantiates objects 70 described in master definition file 44 within memory 26.
  • the virtual machine software 60 uses the PKG TYPE value of the LOGIN XML package to identify a rule object 70 corresponding to the received message.
  • only one rule, defining operation when a package of type LOGIN is received (which rule is represented by the AXRULE element at lines 11 to 64 of FIGS. 5A and 5B ), is defined.
  • the rule object 70 has data members and data member values corresponding to the attributes of the AXRULE element ( FIG. 5A . line 11).
  • the rule is "executed", i.e. a method of rule object 70 is invoked, which causes program logic defined within action objects 70 subordinate to the rule object 70 to be executed in sequence.
  • the action objects 70 correspond to the various ACTION elements at lines 12 to 63 of FIGS. 5A and 5B .
  • the action object 70 invokes one of the methods 49 (as provided by the connector provider - shown in FIG. 2 ) to achieve its objective.
  • This approach is used to invoke the Connect method 49 of the ADOConnector object for example (see lines 19-22 of FIG. 5A ).
  • the ADOConnector object may be located by way of a hashtable, which may be used to retrieve cached objects for greater efficiency as compared with loading the objects from XML from disk whenever they are needed.
  • the virtual machine software 60 ( FIG. 2 ) then locates the associated DLL, as specified in line 5 of FIG. 3A and loads the DLL into memory 26.
  • the virtual machine software 60 locates the Connect method 49 of the ADOConnection object through .NET reflection, using techniques and known to those skilled in the art (see, e.g., msdn2.microsoft.com/en-us/library/66btctbe(VS.80).aspx), which is incorporated by reference hereinto.
  • FIG. 8 An instance of the ADOConnection object is created.
  • the virtual machine 60 then executes the Connect method through .NET reflection method invocation, passing the supplied connection string parameter as defined at line 21 of FIG. 5A .
  • Pseudocode representating classes relied upon by action object 70 for purposes of invoking the Connect method is shown in FIGS. 7A-7C .
  • the significant data members that might be set are illustrated within the class.
  • Also illustrated are supporting classes DataSourceMethodParameter and DataSourceMethodAction.
  • Pseudocode representative of the class from which the ADOConnection object is instantiated is shown in FIG. 8 .
  • the Connect method ( FIG. 8 , lines 8-17) is executed in native .NET.
  • the result of the method is retrieved from application server 12 and further processed.
  • the ADOConnection object instance is held in memory 26 until the execution thread of the current rule is completed. It then falls out of scope and is released.
  • routines 49 may not invoke legacy API functions, Rather, the routines 49 may access a database at application server 12 in which the application 14 stores application data. The routines 49 may access and/or modify the application data in this database directly (i.e. without using the legacy API). In this case, the routines 49 may incorporate logic which emulates logic existing within the application 12 for causing any change to a database table or record to properly update any other database values which are tied or related to the changed value.
  • the logic may need to increment a customer count value in another database table. This logic may be necessary to avoid corrupting a database that is normally accessed by the application 14.
  • the author of the connector 42 who has a good understanding of application 14, emulates this logic within the routines 49 of library 48, the integrator who simply uses the connector 42 to invoke routines 49 by way of calls encoded within the master definition file 44 is freed from the burden of understanding and implementing that logic.
  • the interfaces provided by the author of the virtual machine software may define a "designer" object for facilitating the design of a particular connector in the RAD tool GUI.
  • a "designer" object for facilitating the design of a particular connector in the RAD tool GUI.
  • the author could design a custom interactive designer which conforms to a designer interface. The designer would "plug into” the RAD tool to provide a customized look and feel for creating SQL queries which goes beyond the conventional RAD tool GUI.
  • This document describes the structure and syntax of the ARML language.
  • the document is intended to be read by AIRIX developers and users of ARML.
  • ARML is an XML markup language used by the AIRIX platform. It performs three tasks;
  • ARML has been designed with the following goals in mind
  • the key to ARML usage is the application definition file held on the AIRIX server. This file defines the AIRIX tables for the application, the allowed message set and the user interface definitions for the application on a given device.
  • the scratchpad is used as a temporary storage area where a global value or a value associated to a screen can be saved for future use.
  • the syntax for a scratchpad value is as follows:
  • the syntax for retrieving a global scratchpad value can also be used to retrieve screen scratchpad values.
  • the Date Arithmetic tag is used to add or subtract days from the current date.
  • x represents the number of days added or subtracted. Developers can also choose to substitute a hard-coded date value in the Date Arithmetic tag, in the place of the [SYS.VAR.DATE] tag.
  • the single-field lookup will run a simple SELECT query with one where-clause to retrieve specific data.
  • the syntax is as follows:
  • the application definition section defines the AIRIX tables and ARML data packages that are used for transactions involved with a specific application.
  • the ARML application definition has the following structure
  • tags mark the start and end of the application definition.
  • THE AXSCHDEF tag has two attributes; Attribute Optional? Description APPNAME No The name of the application VERSION No Which version of the application the file describes DESC No A text description of the application for display purposes ARMLMAJOR No The major version of the ARML language this application definition was created with. ARMLMINOR No The minor version of the ARML language this application definition was created with.
  • the ⁇ EVENT> ... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • ⁇ EVENT>... ⁇ EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the ⁇ AXTDEFS>... ⁇ /AXTDEFS> pair marks the start and end of the table definitions section. It has no attributes.
  • the ⁇ DPACKETS>... ⁇ /DPACKETS> pair marks the start and end of the data package definitions section. It has no attributes.
  • the ⁇ DEVICES>... ⁇ /DEVICES> pair marks the start and end of the device interface definitions section. It has no attributes.
  • the table definitions section defines the tables on the mobile device for the application
  • the table definitions section has the following structure
  • Each table definition is enclosed within the ⁇ TDEF>... ⁇ ITDEF> pair.
  • the TDEF tag has the following attributes; Attribute Optional? Description NAME No The number of table definitions in the section PK No Which of the table fields is the primary key for the table DELINDEX No The index of this table with respect to all the tables for specifying the delete order. This value is 1 based.
  • the FIELDS tag has a no attributes.
  • the ⁇ FLD>... ⁇ /FLD> tag pair defines a single field in a table. Enclosed between the tags is the field name.
  • the ⁇ FLD> tag has the following structure; Attribute Optional? Description TYPE No The data type contained in the field. Permitted values are: INT - integer value STRING - a fixed-length string of n characters (see SIZE field) MEMO - a string of max 65535 characters AUTOINC - an integer value, automatically incremented by the database. This field will be read-only to the applications.
  • DATETIME - a datetime value SIZE No If the TYPE is set to STRING, this field specifies the number of characters in the field INDEXED No Specifies if the field needs to be indexed in the AIRIX database REFERENCEFTELD Yes If this attribute is present, it defines that this field is a foreign key.
  • the foreign table/field is given in the format "table(field)" ALLOWNULL No Specifies if the field is allowed to have a null value
  • An email application would use 2 tables for storing sent emails.
  • the package definitions section defines the structure of the application packages and the data that they carry.
  • the package definitions section has the following structure
  • the ⁇ AXDATAPACKET>... ⁇ /AXDATAPACKET> pair delimits a package definition.
  • the tag has the following attributes; Attribute Optional? Description BODY No This field gives the name by which the data package is known UPDATELOCALDATA No Specifies whether the package is to update the local database. SENDTOAPP No Specifies whether the package is sent to the application server
  • Each table update is enclosed within the ⁇ TUPDATE>... ⁇ TUPDATE> pair.
  • the TUPDATE tag has the following attributes; Attribute Optional? Description TABLE No The table in the database that is updated UPDATETYPE No The type of update that is being made to the database. Possible values are; ADD - adds a new record into the table DELETE - removes a record into the table UPDATE - modifies a record in the table WHEREFIELD Yes For a conditional update of a table, specifies the field and table to match on. This is in the format "table(field)". WHEREPARAM Yes Text string specifying the value. This tag has no meaning and will be skipped unless the WHEREFIELD attribute has been specified.
  • the PKGFIELDS tag has no attributes.
  • the ⁇ PKGFLD>... ⁇ /PKGFLD> tag pair defines a single parameter in a given data package. Enclosed between the ⁇ PKGFLD>... ⁇ /PKGFLD> tags is the field name.
  • the ⁇ PKGFLD> tag has the following attributes; Attribute Optional? Description NAME No This is the field in the AIRIX database that maps to the user interface field PARAMTYPE No This defines the type of parameter. It can take two values; PROP - this means that the parameter appears as part of the tag definition VALUE - this means that the parameter is contained between the two tags. Only one parameter in a given data package can be of this type
  • the display definitions section contains the user interface definitions for the various mobile devices that an application supports.
  • the device display definitions section has the following structure
  • the ⁇ DEV>... ⁇ /DEV> pair delimits an interface definition for a specific device.
  • the tag has the following attributes; Attribute Optional? Description TYPE No The type of device. Allowed values are: RIM - a Research in Motion Blackberry pager WAP - a WAP phone CE - Pocket PC
  • the ⁇ SCREENS>... ⁇ /SCREENS> pair delimits the screens definition for a specific device.
  • the tag has one attribute; Attribute Optional? Description STSCRN No The that is displayed when the application starts first screen that is displayed when the application starts
  • the following example shows the screen definitions section for an application that allows a user to view their inbox and the mails in it.
  • This section describes the general structure of an application-specific data package. As described in section , ;
  • An application defined package has the following structure
  • the ⁇ HEAD> tag is as described in section 7.1.3.1
  • the ⁇ PKG>... ⁇ /PKG> tags delimit the package data.
  • the PKG tag has the following attributes; Attribute Optional? Description TYPE No A text string identifying the type of package being sent
  • the first tag in the package is the BODY tag. This tag defines which type of package it is;
  • the package has two sections, which correspond to the two table update sections in the package definition;
  • the 'MAIL' section updates the 'SENTITEMS' table in the database. It does not update multiple rows.
  • the 'RECIPS' section updates the 'RECIPIENTS' table in the database; it does update multiple rows, and each row is contained within a pair of ⁇ RCP> tags.
  • Each of the MAIL and RCP tags have fields which are used to update the field in the database tables;
  • a screen definition file defines a single screen for a specific device.
  • a screen definition file has the following structure
  • the ⁇ SCREEN>... ⁇ /SCREEN> pair marks the start and end of the screen definitions section. It has attribute - Attribute Optional? Description NAME No An identifier for the screen. This is used to qualify variables and navigate between screens TITLE No The title that appears for the screen. BACKGROUND Yes If used, an image that appears behind the interface elements ORDERED Yes, only applicable on WAP If yes, WML is created with ORDERED property set to true, if NO, WML is created with ORDERED property set to false. Only applicable on WAP. See WML standard for definition of ORDERED.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the ⁇ EVENT> ... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the ⁇ QUERIES> ... ⁇ /QUERIES> pair marks the start and end of the queries definitions section. It has no attributes.
  • the ⁇ MENUS>... ⁇ /MENUS> pair marks the start and end of the menu definition section. It has no attributes.
  • the ⁇ BUTTONS>... ⁇ /BUTTONS> pair marks the start and end of the button definitions section. It has no attributes.
  • ⁇ TEXTITEMS>... ⁇ TEXTITEMS> pair marks the start and end of the text items section. It has no attributes.
  • the ⁇ CHOICEITEMS>... ⁇ /CHOICEITEMS> pair marks the start and end of the choiceitems section. It has no attributes.
  • the ⁇ IMAGES>... ⁇ /IMAGES> pair marks the start and end of the images section. It has no attributes.
  • the ⁇ CHECKBOXES>... ⁇ /CHECKBOXES> pair marks the start and end of the checkboxes section. It has no attributes.
  • the ⁇ GRIDS>... ⁇ /GRIDS> pair marks the start and end of the grids section. It has no attributes.
  • the queries definition section describes any queries that need to be run to populate a screen.
  • the queries definition section has the following structure
  • the ⁇ QUERIES> ... ⁇ /QUERIES> pair marks the start and end of query definition section. It has no attributes.
  • the ⁇ QUERY>... ⁇ /QUERY> pair marks the start and end of a given query. It has the following attributes; Attribute Optional? Description NAME No Name of the query. TABLE No The table in the database that is updated ORDERBY Yes Specifies the name of the field in the table that the results are to be ordered on. ORDERDIR Yes ASC or DESC, sort ascending or descending respectively. If ORDERBY is present and ORDERDIR is not, ASC is assumed.
  • the ⁇ W>... ⁇ /W> pair marks the start and end of a given where-clause.
  • the value of the parameter is contained within the ⁇ W>... ⁇ /W> tags. This value can be a specific value or a reference to a user interface field in the format "[SP.screen.savename] or [QU.query.field]". It has the following attributes; Attribute Optional? Description F No Specifies the field to match on. E No Specifies the expression type. Available expression types include: EQ NE LT GT BW (applicable only to fields of type STRING)
  • the menu definition section describes the menu for a given screen.
  • the menu definition section has the following structure
  • the ⁇ MENUS> ... ⁇ /MENUS> pair marks the start and end of menu definition section. It has no attributes.
  • the ⁇ MENU> ... ⁇ /MENU> pair marks the start and end of a menu definition. It has the following attributes. Attribute Optional? Description NAME No An internal identifier for the menu CAPTION No The text that appears for this item in the menu
  • the ⁇ MENUITEM>... ⁇ /MENUITEM> pair marks the start and end of a menuitem definition. It has the following tags; Attribute Optional? Description NAME No An internal identifier for the menu CAPTION No The text that appears for this item in the menu INDEX Yes The index of this menu item with respect to all of the menu items on this menu. READONLY Yes If True, the menu item is inactive. False is the default.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • buttons definition section describes the buttons that appear on a given screen.
  • buttons definition section has the following structure
  • the ⁇ BTN>... ⁇ /BTN> pair marks the start and end of a button definition. It has one attribute - Attribute Optional? Description NAME No An identifier for the button. INDEX No The order in which the button appears CAPTION No The caption that appears on a given button X Yes The X-coordinate of the button on the screen. This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser Y Yes The Y-coordinate of the button on the screen. This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser HT Yes This is the Height of the button.
  • This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser WT Yes This is the Width of the Button. This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser READONLY Yes If True, the button is not enabled. False is the default.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the text items section has the following structure
  • the ⁇ TI>... ⁇ /TI> pair marks the start and end of the screen definitions section. It has attribute - Attribute Optional? Description INDEX No The order in which the text item appears NAME No An Identifier for the Text Item CAPTION No Text to appear on the Text Item X Yes The X-coordinate of the text item on the screen. This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser Y Yes The Y-coordinate of the text item on the screen. This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser HT Yes This is the Height of the Text Item.
  • This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser WT Yes This is the Width of the Text Item. This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definitio-n. See section 6 for a detailed discussion of the Smart Client event model.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the edit boxes definition section describes what edit boxes exist for the screen.
  • the edit boxes section has the following structure
  • the ⁇ EB>... ⁇ /EB> pair marks an edit box definition. It has the following attributes - Attribute Optional? Description NAME No An identifier for the edit box. TEXT No The text to display in the edit box before any entry has been made. Only used if the DATASRC attribute is invalid or omitted. Can be a scratchpad or query value of the form [SP.screen.savename] or [QU.query.field]. INDEX No The order in which the edit box appears CAPTION No The caption for on a given edit box. MULTILINE No Boolean field that indicates whether the edit box is a multiline field. SAVE No Boolean value indicating whether or not to save the value in this field to temporary storage for use by other screens later on.
  • Saving the value to the scratchpad is triggered by either exiting the screen or by an explicit 'SAVE' action on a user interface control.
  • SAVENAME Yes If present, the name to save the field under in the scratchpad. This attribute has no meaning unless the SAVE attribute is set to 'Yes' X Yes The X-coordinate of the edit box on the screen. This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser Y Yes The Y-coordinate of the edit box on the screen. This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser HT Yes The Height of the Edit Box.
  • This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser WT Yes
  • the Width of the Edit Box The Width of the Edit Box.
  • This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser FT Yes Specifies the type of value expected (INT, STRING, MEMO,DATETIME) for the VM to validate prior to continuing a Save. If omitted, STRING is the default data type.
  • DATASRC Yes If present, the query and field in the query that populates this edit box. This is given in the format "query.field”. READONLY Yes If "TRUE" the edit box will be read only, otherwise it is editable. "FALSE is the default value.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • choice item definitions section describes the choice items that exist on a given screen.
  • a choice item is an interface item that requires the user to make a selection from a list of options. It can be represented in different ways on different devices; on a RIM pager, it is a choice box, while on a WinCE device, it is a drop-down list.
  • the choice items section has the following structure
  • the ⁇ CHOICE>... ⁇ CHOICE> pair marks the start and end of a choice item definition. It has these attributes - Attribute Optional? Description NAME No An identifier for the choice item. TEXT No The text to display in the choice item before any selection has been made. INDEX No The order in which the choice item appears CAPTION No The caption that appears for a given choice item SAVE No Boolean value indicating whether or not to save the value in this field to temporary storage for use by other screens later on. Saving the value to the scratchpad is triggered by either exiting the screen or by an explicit 'SAVE' action on a user interface control. SAVENAME Yes If present, the name to save the field under in the scratchpad.
  • This attribute has no meaning unless the SAVE attribute is set to 'Yes' X Yes The X-coordinate of the choice item on the screen.
  • This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser Y Yes The Y-coordinate of the choice item on the screen.
  • This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser DATASRC Yes If present, the query and field in the query that populates this choice item. This is given in the format "query.field”. IDDATASRC Yes If present, the query and field in the query that populates the Ids for this choice item. This is given in the format "query.field”.
  • the ID values created by the attributes should correspond directly to the choice item values. I.e. they should create a value, id pair. READONLY Yes If "True", the control cannot be modified. "False” is the default. SI Yes The value to indicate which item of the choice item is to be selected when loaded. This value will be compared with the ID property (hard-coded items) or the IDDATASRC property (database items).
  • the ⁇ ITEMS>... ⁇ /ITEMS> pair marks the start and end of a list of items to be included in the in the choice item. If a datasrc is specified, the ⁇ ITEMS> section is ignored.
  • the ⁇ I>... ⁇ /I> pair marks the start and end of an individual item in the choice items list. It has the following attributes: Attribute Optional? Description ID Yes An id used to identify this item in the list.
  • the value between the pair is the text value that is to be displayed in the choice item.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the checkboxes section describes a check box that appears on a given screen.
  • the checkboxes section has the following structure
  • the ⁇ CHK>... ⁇ /CHK> pair marks a check box definition Attribute Optional? Description NAME No An identifier for the check box. INDEX No The index of this control with respect to the list of all controls on the screen. CAPTION No The text to be displayed for this check box if the DATASRC is not available or is not specified. Save No Boolean value indicating whether or not to save the value in this field to temporary storage for use by other screens later on. Saving the value to the scratchpad is triggered by either exiting the screen or by an explicit 'SAVE' action on a user interface control. SAVENAME Yes If present, the name to save the field under in the scratchpad.
  • This attribute has no meaning unless the SAVE attribute is set to 'Yes' X Yes The X-coordinate of the check box on the screen.
  • This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser Y Yes The Y-coordinate of the check box on the screen.
  • This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser HT Yes The Height of the Checkbox.
  • This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser WT Yes The Width of the Checkbox.
  • DATASRC Yes the query and field in the query that populates this check box. This is given in the format "query.field”.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the listboxes section describes a list box that appears on a given screen.
  • the listboxes section has the following structure
  • the ⁇ LB>... ⁇ /LB> pair marks a list box definition Attribute Optional? Description NAME No An identifier for the list box. INDEX No The index of this control with respect to all of the controls on the screen. CAPTION No The text to be displayed as the title of this list box, where applicable. SAVE No Boolean value indicating whether or not to save the value in this field to temporary storage for use by other screens later on. Saving the value to the scratchpad is triggered by either exiting the screen or by an explicit 'SAVE' action on a user interface control. SAVENAME Yes If present, the name to save the field under in the scratchpad.
  • This attribute has no meaning unless the SAVE attribute is set to 'Yes' X Yes The X-coordinate of the list box on the screen.
  • This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser Y Yes The Y-coordinate of the list box on the screen.
  • This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser HT Yes The Height of the Listbox.
  • This attribute may not be meaningful in some display environments, in which case it would be skipped without processing by the parser WT Yes The Width of the Listbox.
  • the ⁇ ITEMS>... ⁇ /ITEMS> pair marks the start and end of a list of items to be included in the in the list box. If a datasrc is specified, the ⁇ ITEMS> section is ignored.
  • the ⁇ I>... ⁇ /I> pair marks the start and end of an individual item in the list box items list. It has the following attributes: Attribute Optional? Description ID Yes An id used to identify this item in the list.
  • the value between the pair is the text value that is to be displayed in the list box.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of a user-interface level event definition. See section 6 for a detailed discussion of the Smart Client event model.
  • Grids allow data to be displayed in row-column format. Grids can display data from a data source (query) or they can contain hard coded values. Each column in a grid can be visible or hidden. Hidden values are maintained, but not visible to the user.
  • the grids section has the following structure
  • the Smart Client has a set of actions that it ties to events. Events can occur at the application level, the screen level or the user interface item level; an application level event is listened for throughout the operation of the application, a screen level event is listened for while the screen is displayed, and so on. If an action for an event is defined at multiple levels, the lowest level has precedence; i.e., user interface actions override screen level actions, which override application level actions. An attempt to list an event multiple times at the same level (application, screen, item) is invalid and will generate an error message.
  • the following ARML fragment illustrates this schema (tags and attributes not relevant to the event model have been omitted);
  • the ⁇ EVENTS>... ⁇ /EVENTS> pair marks the start and end of the events section. It has no attributes.
  • the ⁇ EVENT>... ⁇ /EVENT> pair marks the start and end of an event definition. It has the following attributes; Attribute Optional? Description TYPE No The type of event that should be performed when the button is pushed. Allowed values are; BUTTONCLICK MENUITEMSELECTED DATA
  • the button click event occurs when the user selects a button. It has no attributes.
  • the menu items selected event occurs when the user selects a menu item. It has no attributes.
  • the data event occurs when ARML data is received from the wireless interface. It has the following attributes; Attribute Optional? Description NAME No The identifier of the specific package
  • the ⁇ ACTION>... ⁇ /ACTION> pair marks the start and end of an event definition. It has one fixed attribute, and a number of attributes that may or may not appear depending on the type of action required.
  • the fixed attribute is; Attribute Optional? Description TYPE No The type of action that should be performed when the button is pushed. Allowed values are; OPEN ARML SAVE PURGE NOTIFY CLOSE ALERT IF...Then...Else CLOSESCREEN REFRESH SAVEITEM
  • the open action tells the Smart Client to open a new screen. It adds one extra attribute to the ACTION tag; Attribute Optional? Description NAME No The name of the screen to open NEWINST Yes If true, a new instance of the screen is created. If false, the least recently used instance of the screen is opened and the data is not refreshed. True is the default.
  • the arml action tells the Smart Client to compose and send an arml package. It does not add any attributes to the ACTION tag, but has the following subtag;
  • ⁇ ARMLTEXT>... ⁇ /ARMLTEXT> pair is one of the application-defined data packages. Individual data items are marked with the user interface item that their value should be taken from, in the format " [SP .screen.savename]", or [QU .query.field]. If screen is not the current screen, then the Smart Client will look for the data in its scratchpad. See section 0 for an example of the ARML action.
  • the purge action tells the Smart Client to clear all fields that have been saved to the scratchpad. It has no attributes.
  • the notify action tells the Smart Client to activate the configured notification on a device. For devices where this has no meaning, it will cause a beep to be played. It has no attributes.
  • the close action tells the Smart Client to close the application. It has no attributes.
  • the alert action tells the Smart Client to display an alert item (e.g., a message box on Windows, an alert box on the RIM pager, an alert card on WAP). It has the following attributes; Attribute Optional? Description CAPTION Yes The caption to display in the title bar of the message box TEXT Yes The text to display in the message box
  • the integration action tells the Smart Client to pass data to an interface exposed on a device. For example a COM interface on Pocket PC. This action will allow the developer to pass a parameter into an exposed method and then also save the result of that method in a global scratchpad value.
  • the contents of the integration action's element are the input values to be passed to the interface. It has the following attributes; Attribute Optional? Description CLSID No This is the class identifier of the component that is to be called. SAVE No This tells the smart client if it should save the result into a global scratchpad value or not. SAVENAME Yes This is the name of the global scratchpad value
  • the close screen action tells the Smart Client to close all open instances of the screen specified by name in the NAME attribute. This action has the following attributes: Attribute Optional? Description NAME No Name of the screen to close.
  • the refresh action tells the Smart Client to re-run any queries and re-initialize all UI elements on the screen with the name specified by the NAME attribute. If there are multiple open instances of the screen, all open instances will be refreshed.
  • the refresh action has the following attributes: Attribute Optional? Description NAME No Name of the screen to refresh.
  • the saveitem action tells the Smart Client to create a new scratchpad item or to edit an existing scratchpad item.
  • the value of the scratchpad item is defined within the ⁇ ACTION>... ⁇ /ACTION> tags.
  • the saveitem action has the following attributes: Attribute Optional? Description SPN No Name of the scratchpad item to create or modify.
  • This action will contain two lists of actions. One a list of actions to perform if the condition evaluates to TRUE (IFLIST), and another list of actions to perform if the condition evaluates to FALSE (ELSEIFLIST).
  • Conditions are used in conjunction with the IF Action. Conditions are specified as follows: Attribute Optional? Description EVAL NO Specifies the parameter to be evaluated. Can be hard coded, scratchpad, or query values. It is the "input" to the function. TYPE NO Specifies the type of the condition. Possible values are: LESSTHAN MORETHAN EQUALS ISNUMERIC ISALPHA ISEMAIL ISFORMAT MAXCHARS MINCHARS VALUE Depends on TYPE The value that EVAL will be evaluated against. Not relevant for all conditions.
  • the following example serves to illustrate how a screen is used to compose a data package to be sent back to the AIRIX server.
  • the example used is a screen giving the bare functionality for composing a basic email message - to simplify the example, the user cannot cancel the action, and multiple recipients are not allowed.
  • the ARML package sent is an 'ME' package as described in the example in section 4.2.1. It is composed as follows;
  • the subject field is taken from the edit box named 'Subject';
  • the recipients field is taken from the edit box named 'Subject';
  • This section describes the primitives that are used for system-level interactions that the AIRIX Smart Client has with the AIRIX server.
  • the package header is delimited by the ⁇ HEAD>... ⁇ /HEAD> tags. Contained in text between the two tags is the id of the destination mobile.
  • the HEAD tag has the following attributes; Attribute Optional? Description DT No The date & time in RFC 1123 format (including time zone) ID No A unique ID for the message VERSION No The version number of the application (currently "2.0") APPNAME No The application name ("0" for System Messages) DEVICE No A numeric constant identifying the device PID Yes A unique value used to designate a device. AVMV No The version number of the Smart Client.
  • the ⁇ SYS>... ⁇ /SYS> pair contains the actual system package.
  • the tag does not have any attributes.
  • Device registration packages are sent from the AVM to the AIRIX server when a user registers their device.
  • a device registration package has the following structure
  • the ⁇ REG>... ⁇ /REG> pair delimit the registration request.
  • the tag has no attributes.
  • the ⁇ USERNAME>... ⁇ / USERNAME > pair contain the user name.
  • the tag does not have any attributes.
  • the ⁇ PASSWORD>... ⁇ /PASSWORD> pair contain the password.
  • the tag does not have any attributes.
  • This package would be sent by a user, to register their device under a given name
  • This packages is sent back from the AIRIX server to the AVM to confirm that the device has been registered.
  • a registration confirmation package has the following structure
  • the tag has no attributes.
  • the ⁇ VALUE>... ⁇ /VALUE> pair contains the status of the registration request.
  • the following text strings are allowable; CONFIRM - this means that the registration request was successful NOTREGPLATFORM - this means that the registration request failed because the device is not registered for the platform INVALIDUSERPASS - this means that the registration request failed because the user name or password was not valid NODEVICE - this means that the registration request failed because the device was not registered previously by an application
  • the ⁇ APPS>... ⁇ /APPS> pair contains a list of applications for the device.
  • the ⁇ APP>... ⁇ /APP> pair contains an application header. It has the following attributes; Attribute Optional? Description ID No The application ID NAME No The name of the application DESCRIPTION No A text description of the application REG No 'YES' if the user is registered for this application. 'NO' if they are not.
  • Find applications packages are sent from the AIRIX component to the AIRIX server when a user wishes to refresh their list of applications on a device
  • a device registration package has the following structure
  • the ⁇ FINDAPPS>... ⁇ /FINDAPPS> pair delimit the application registration request. It has no attributes.
  • This package is sent back from the AIRIX server to the AVM to and contains a list of applications available for the user
  • a registration confirmation package has the following structure
  • the tag has no attributes.
  • the ⁇ APPS>... ⁇ /APPS> pair contains a list of applications for the device.
  • the ⁇ APP>... ⁇ /APP> pair contains an application header. It has the following attributes; Attribute Optional? Description ID No The application ID NAME No The name of the application DESCRIPTION No A text description of the application REG No 'YES' if the user is registered for the application. 'NO' if they are not.
  • Application registration packages are sent from the AIRIX component to the AIRIX server when a user wishes to register or deregister for an application.
  • a device registration package has the following structure
  • the ⁇ APPREG>... ⁇ /APPREG> pair delimit the application registration request.
  • the tag has the following attributes; Attribute Optional? Description TYPE No This defines the type of parameter. It can take two values; ADD - this means that the application is to be added to the registration database DELETE - this means that the application is to be removed to the registration database ID No The ID of the application being registered/deregistered
  • This packages is sent back from the AIRIX server to the AVM to confirm that the applicaiton has been registered or deregistered.
  • a registration confirmation package has the following structure (note that for DELETE types, the ⁇ INTERFACE>... ⁇ /INTERFACE> section will not be included);
  • the tag has the following attributes; Attribute Optional? Description TYPE No This defines the type of parameter. It can take two values; ADD - this means that the application is to be added to the registration database DELETE - this means that the application is to be removed to the registration database ID Yes The ID of the application being returned (if any)
  • the ⁇ INTERFACE>... ⁇ /INTERFACE> pair delimit the interface definition.
  • the following example shows the application confirmation with screen definitions for an application that allows a user to view their inbox and the mails in it.
  • the AVM must send a 'set active device' package to the AIRIX server
  • a 'set active device' package has the following structure
  • the 'set active device' package is shown by the ⁇ SA>... ⁇ /SA> tags.
  • the tag has no attributes; the tag pair contains the user's usemame
  • This package would be sent by a user with the usemame of 'scotty';
  • This packages is sent back from the AIRIX server to the client in response to a request to set the current device as the active one.
  • a 'set active device response' package has the following structure
  • the ⁇ SACONFIRM>... ⁇ /SACONFIRM> pair delimit the confirmation.
  • the tag does not have any attributes.
  • the ⁇ VALUE>... ⁇ /VALUE> pair contains the status of the registration request.
  • the following text strings are allowable; CONFIRM - this means that the registration request was successful NOTREGISTERED - this means that the registration request failed because
  • This package would be sent by the AIRIX server to confirm a set active request
  • This package is sent back from the AIRIX server to the AVM in response to a request to interact with an application that is no longer registered with AIRIX.
  • An 'invalid application' package has the following structure
  • the tag has no attributes.
  • the ⁇ VALUE>... ⁇ /VALUE> pair delimit the return code. It can only be NOAPPLICATION - Application not found.
  • This package would be sent in response to a request if the application cannot be found;

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Claims (28)

  1. Procédé, mis en oeuvre sur ordinateur, comprenant les étapes consistant à :
    en fonction au moins en partie d'un premier document dans un langage de balisage extensible (50), ledit premier document dans un langage de balisage extensible (50) décrivant des routines (49) destinées à accéder à des données distantes dune application, produire un second document dans un langage de balisage extensible (44) qui décrit :
    un appel de l'une desdites routines ;
    des données à passer comme paramètres de ladite une desdites routines ; et
    des circonstances dans lesquelles ledit appel doit se produire ;
    dans lequel ledit second document dans un langage de balisage extensible (44) comprend au moins un élément de langage de balisage extensible qui doit constituer une base pour l'instanciation d'une instance (70) d'une classe orientée objets (62), ledit au moins un élément du langage de balisage extensible possédant des attributs qui doivent former une base pour la personnalisation de ladite instance (70) afin de réaliser ledit appel, ladite personnalisation comprenant l'attribution de valeurs desdits attributs à des éléments de données de ladite instance qui affectent l'exécution dudit appel ;
    dans lequel ladite étape de production dudit second document dans un langage de balisage extensible (44) comprend les étapes consistant à :
    présenter une interface utilisateur graphique offrant une option à sélectionner qui représente ladite une des routines ;
    en fonction en partie de l'interaction de l'utilisateur avec ladite option à sélectionner dans ladite interface utilisateur graphique, créer ledit second document dans un langage de balisage extensible (44).
  2. Procédé selon la revendication 1, dans lequel ladite étape de production est exécutée sur un premier dispositif informatique (40), lesdites étapes de personnalisation et d'appel sont exécutées sur un second dispositif informatique (20) et comprennent en outre le téléchargement dudit second document dans un langage de balisage extensible (44) entre ledit premier dispositif informatique (40) et ledit second dispositif informatique (20), avant ladite étape de personnalisation.
  3. Procédé selon la revendication 2, dans lequel ledit second dispositif informatique (20) est un serveur (20) en communication avec à la fois un serveur d'applications (12) stockant au moins une application (14) et un dispositif de communication sans fil (30).
  4. Procédé selon la revendication 3, dans lequel lesdites circonstances comprennent la réception d'un message dudit dispositif de communication sans fil (30).
  5. Procédé selon la revendication 4, dans lequel lesdites données à passer comme paramètres comprennent une partie dudit message et dans lequel ledit second document dans un langage de balisage extensible (44) identifie ladite partie dudit message.
  6. Procédé selon l'une quelconque des revendications 1 à 5, dans lequel ladite option à sélectionner est une option parmi une pluralité d'options à sélectionner dans ladite interface utilisateur graphique, lesdites options à sélectionner énumérant lesdites routines (49) destinées à accéder à des données distantes de l'application qui sont décrites dans ledit premier document dans un langage de balisage extensible (50).
  7. Procédé selon l'une quelconque des revendications 1 à 6, dans lequel ladite interaction de l'utilisateur avec ladite interface utilisateur graphique comprend en outre la création par l'utilisateur d'une hiérarchie d'icônes graphiques (100) à l'aide de ladite interface utilisateur graphique, chacune desdites icônes représentant une instante d'un élément du langage de balisage dans ledit second document dans un langage de balivage extensible (44).
  8. Procédé selon la revendication 7, dans lequel ladite Interface utilisateur graphique limite les relations d'inclusion autorisées entre les icônes de ladite hiérarchie (100) en fonction de relations d'inclusion autorisées entre les éléments du langage de balivage représentés par lesdites icônes, comme l'indique le schéma du langage de balivage.
  9. Procédé selon l'une quelconque des revendications 1 à 8, dans lequel lesdites routines (49) comprennent des méthodes au sein de classes orientées objets d'une bibliothèque liée dynamiquement (48), chacune lesdites classes orientées objets pouvant être identifiée par un nom qualifié, dans lequel ledit premier document dans un langage de balivage extensible (50) comprend des informations de noms qualifiés qui identifient lesdites classes orientées objets, et comprenant en outre l'étape consistant à utiliser lesdites informations de noms qualifiés pour faciliter ledit appel.
  10. Procédé selon la revendication 9, dans lequel ladite étape d'utilisation desdites informations de noms qualifiés pour faciliter ledit appel comprend l'étape consistant à utiliser ladite bibliothèque liée dynamiquement (48) pour obtenir une référence à l'une des classes orientées objets qui est identifiée par desdites informations de noms qualifiés.
  11. Support lisible par une machine (54), stockant du code destiné à être exécuté sur un dispositif informatique (40), comprenant :
    du code exécutable par une machine, destiné à produire, en fonction au moins en partie d'un premier document dans un langage de balisage extensible (50), ledit premier document dans un langage de balisage extensible (50) décrivant des routines (49) destinées à accéder à des données distantes d'une application, un second document dans un langage de balisage extensible (44) qui décrit :
    un appel de l'une desdites routines ;
    des données à passer comme paramètres de ladite une desdites routines ; et
    des circonstances dans lesquelles ledit appel doit se produire ;
    dans lequel ledit second document dans un langage de balisage extensible (44) comprend au moins un élément de langage de balisage extensible qui doit constituer une base pour l'instanciation d'une instance (70) d'une classe orientée objets (62), ledit au moins un élément du langage de balisage extensible possédant des attributs qui doivent former une base pour la personnalisation de ladite instance (70) afin de réaliser ledit appel, ladite personnalisation comprenant l'attribution de valeurs desdits attributs à des éléments de données de ladite instance qui affectent l'exécution dudit appel ; et
    dans lequel ledit code exécutable par une machine pour la production dudit second document dans un langage de balisage extensible (44) comprend :
    du code exécutable par une machine pour présenter une interface utilisateur graphique offrant une option à sélectionner qui représente ladite une des routines ; et
    du code exécutable par une machine pour créer ledit second document dans un langage de balisage extensible (44), en fonction en partie de l'interaction de l'utilisateur avec ladite option à sélectionner dans ladite interface utilisateur graphique.
  12. Support lisible par une machine (54) selon la revendication 11, dans lequel ladite interaction de l'utilisateur avec ladite interface utilisateur graphique comprend la création par l'utilisateur d'une hiérarchie d'icônes graphiques (100) à l'aide de ladite interface utilisateur graphique, chacune desdites icônes représentant une instance d'un élément du langage de balisage dans ledit second document dans un langage de balisage extensible (44), dans lequel ladite interface utilisateur graphique limite les relations d'inclusion autorisées entre les icônes de ladite hiérarchie (100) en fonction de relations d'inclusion autorisées entre les éléments du langage de balisage représentés par lesdites icônes, comme l'indique un schéma du langage de balisage.
  13. Support lisible par une machine (54) selon la revendication 11 ou la revendication 12, dans lequel des options à sélectionner dans ladite interface utilisateur graphique sont déterminées en partie par ledit premier document dans un langage de balisage extensible (50).
  14. Support lisible par une machine (54) selon la revendication 13, dans lequel lesdites options à sélectionner énumèrent lesdites routines (49) destinées à accéder aux données distantes de l'application.
  15. Support lisible par une machine (54) selon l'une quelconque des revendications 11 à 14, dans lequel lesdites routines (49) appellent des routines d'une interface de programmation d'applications, pour une application (14) se trouvant sur un serveur d'applications (12) distant.
  16. Support lisible par une machine (54) selon l'une quelconque des revendications 11 à 15, dans lequel lesdites routines (49) accèdent auxdites données de l'application directement sur une base de données utilisée par une application, sur un serveur d'applications distant, pour stocker lesdites données d'application.
  17. Support lisible par une machine (54) selon l'une quelconque des revendications 11 à 16, dans lequel lesdites routines (49) comprennent des routines précompilées dans une bibliothèque liée dynamiquement (48).
  18. Support lisible par une machine (54) selon la revendication 17, dans lequel ladite bibliothèque liée dynamiquement (48) comprend du code intermédiaire et dans lequel lesdites routines (49) comprennent des méthodes au sein de classes orientées objets qui sont décrites par ledit code intermédiaire, chacune desdites classes orientées objets pouvant être identifiée par un nom qualifié.
  19. Support lisible par une machine (54) selon la revendication 18, dans lequel ledit premier document dans un langage de balisage extensible (50) comprend des informations de noms qualifiés qui identifient lesdites classes orientées objets et comprenant en outre l'étape consistant à utiliser lesdites informations de noms qualifiés pour faciliter ledit appel.
  20. Support lisible par une machine (54) selon la revendication 19, dans lequel ladite étape d'utilisation desdites informations de noms qualifiés pour faciliter ledit appel comprend l'étape consistant à utiliser ladite bibliothèque liée dynamiquement (48) pour obtenir une référence à l'une des classes orientées objets qui est identifiée par lesdites informations de noms qualifiés.
  21. Procédé exécuté sur un dispositif informatique (20), comprenant l'étape consistant à :
    instancier une instance (70) d'une classe orientée objets (62) selon la revendication 1.
  22. Procédé selon la revendication 21, dans lequel ledit dispositif informatique (20) est un serveur (20) et dans lequel lesdites circonstances comprennent la réception d'un message en provenance d'un dispositif de communication sans fil (30) en communication avec ledit serveur (20).
  23. Procédé selon la revendication 22, dans lequel lesdites données à passer comme paramètres comprennent une partie dudit message et dans lequel ledit second document dans un langage de balisage extensible (44) identifie ladite partie dudit message.
  24. Support lisible par une machine (64), stockant du code destiné à être exécuté sur un dispositif informatique (20) afin de mettre en oeuvre le procédé selon la revendication 21.
  25. Support lisible par une machine (64) selon la revendication 24, dans lequel ledit dispositif informatique (20) est un serveur (20) et dans lequel lesdites circonstances comprennent la réception d'un message en provenance d'un dispositif de communication sans fil (30) en communication avec ledit serveur (20).
  26. Support lisible par une machine (64) selon la revendication 25, dans lequel lesdites données à passer comme paramètres comprennent une partie dudit message et dans lequel ledit second document dans un langage de balisage extensible (44) identifie ladite partie dudit message.
  27. Dispositif informatique (40), comprenant :
    une mémoire (43) destinée à stocker du code ; et
    un processeur (41) destiné à exécuter ledit code afin de commander audit dispositif informatique (40) d'exécuter les étapes du procédé selon l'une quelconque des revendications 1 à 10.
  28. Dispositif informatique (20), comprenant :
    une mémoire (26) destinée à stocker du code ; et
    un processeur (24) destiné à exécuter ledit code afin de commander audit dispositif informatique (40) d'exécuter les étapes du procédé selon l'une quelconque des revendications 21 à 23.
EP06115926A 2006-06-22 2006-06-22 Faciliter l'accès aux données d'application sur un serveur d'application par un dispositif de communication sans fil Active EP1873656B1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP06115926A EP1873656B1 (fr) 2006-06-22 2006-06-22 Faciliter l'accès aux données d'application sur un serveur d'application par un dispositif de communication sans fil
CA2592399A CA2592399C (fr) 2006-06-22 2007-06-19 Facilitation d'acces aux donnees applicatives d'un serveur d'applications par un dispositif de communication sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP06115926A EP1873656B1 (fr) 2006-06-22 2006-06-22 Faciliter l'accès aux données d'application sur un serveur d'application par un dispositif de communication sans fil

Publications (2)

Publication Number Publication Date
EP1873656A1 EP1873656A1 (fr) 2008-01-02
EP1873656B1 true EP1873656B1 (fr) 2012-06-20

Family

ID=36763269

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06115926A Active EP1873656B1 (fr) 2006-06-22 2006-06-22 Faciliter l'accès aux données d'application sur un serveur d'application par un dispositif de communication sans fil

Country Status (2)

Country Link
EP (1) EP1873656B1 (fr)
CA (1) CA2592399C (fr)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7188081B1 (en) 2000-10-30 2007-03-06 Microsoft Corporation Electronic shopping basket
WO2002041190A2 (fr) * 2000-11-15 2002-05-23 Holbrook David M Systeme et procede d'organisation et/ou de presentation de donnees
CN1156751C (zh) * 2001-02-02 2004-07-07 国际商业机器公司 用于自动生成语音xml文件的方法和系统

Also Published As

Publication number Publication date
EP1873656A1 (fr) 2008-01-02
CA2592399C (fr) 2014-02-11
CA2592399A1 (fr) 2007-12-22

Similar Documents

Publication Publication Date Title
US20070300237A1 (en) Facilitating access to application data at an application server by a wireless communication device
US7913234B2 (en) Execution of textually-defined instructions at a wireless communication device
US7321918B2 (en) Server-side control objects for processing client-side user interface elements
EP1156427B1 (fr) Traitement d'entrée retournée par des objets de commande coté serveur
US20070288853A1 (en) Software, methods and apparatus facilitating presentation of a wireless communication device user interface with multi-language support
US7865528B2 (en) Software, devices and methods facilitating execution of server-side applications at mobile devices
US7890853B2 (en) Apparatus and machine-readable medium for generating markup language representing a derived entity which extends or overrides attributes of a base entity
US8095565B2 (en) Metadata driven user interface
US7546298B2 (en) Software, devices and methods facilitating execution of server-side applications at mobile devices
US8046679B2 (en) Apparatus, method and machine-readable medium for facilitating generation of a markup language document containing identical sets of markup language elements
US20020101448A1 (en) Generating a declarative user interface
US20050076265A1 (en) Method and apparatus for supporting error handling in a web presentation architecture
CA2598317C (fr) Dispositif mobile possedant un logiciel extensible pour presenter des applications cote-serveur, logiciel et procedes correspondants
EP1873656B1 (fr) Faciliter l'accès aux données d'application sur un serveur d'application par un dispositif de communication sans fil
CA2578178C (fr) Appareil et support lisible par une machine pour produire un langage de balisage representant une entite derivee qui prolonge ou surclasse les attributs d'une entite de base
EP1865423B1 (fr) Logiciel et dispositif pour rafraichir des requêtes de bases de données basées sur un langage de balisage indépendement d'ecrans d'interface utilisateur
CA2578177C (fr) Execution d'instructions definies textuellement a un dispositif de communication sans fil
EP1865422A1 (fr) Logiciel, procédés et appareil facilitant la présentation d'une interface d'utilisation d'un dispositif de communication sans fil avec un support multinormes spécifiques
CA2655974A1 (fr) Methode et logiciel facilitant l'interaction avec une application de gestion des renseignements personnels a un dispositif de communication sans fil
Moroney Beginning Web Development, Silverlight, and ASP. NET AJAX: From Novice to Professional

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060622

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

AKX Designation fees paid

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AXX Extension fees paid

Extension state: BA

Payment date: 20060622

Extension state: HR

Payment date: 20060622

Extension state: AL

Payment date: 20060622

Extension state: MK

Payment date: 20060622

Extension state: RS

Payment date: 20060622

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: RESEARCH IN MOTION LIMITED

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 563398

Country of ref document: AT

Kind code of ref document: T

Effective date: 20120715

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602006030274

Country of ref document: DE

Effective date: 20120816

REG Reference to a national code

Ref country code: NL

Ref legal event code: T3

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 563398

Country of ref document: AT

Kind code of ref document: T

Effective date: 20120620

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

Effective date: 20120620

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120921

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120630

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121020

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121022

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120630

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120622

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121001

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120630

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

26N No opposition filed

Effective date: 20130321

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602006030274

Country of ref document: DE

Effective date: 20130321

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120920

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120620

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120622

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060622

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602006030274

Country of ref document: DE

Representative=s name: MERH-IP MATIAS ERNY REICHL HOFFMANN, DE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602006030274

Country of ref document: DE

Representative=s name: MERH-IP MATIAS ERNY REICHL HOFFMANN, DE

Effective date: 20140925

Ref country code: DE

Ref legal event code: R081

Ref document number: 602006030274

Country of ref document: DE

Owner name: BLACKBERRY LIMITED, WATERLOO, CA

Free format text: FORMER OWNER: RESEARCH IN MOTION LIMITED, WATERLOO, ONTARIO, CA

Effective date: 20140925

Ref country code: DE

Ref legal event code: R082

Ref document number: 602006030274

Country of ref document: DE

Representative=s name: MERH-IP MATIAS ERNY REICHL HOFFMANN PATENTANWA, DE

Effective date: 20140925

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 11

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602006030274

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0017300000

Ipc: G06F0016000000

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20230626

Year of fee payment: 18

Ref country code: FR

Payment date: 20230626

Year of fee payment: 18

Ref country code: DE

Payment date: 20230626

Year of fee payment: 18

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230627

Year of fee payment: 18

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602006030274

Country of ref document: DE

Ref country code: DE

Ref legal event code: R081

Ref document number: 602006030274

Country of ref document: DE

Owner name: MALIKIE INNOVATIONS LTD., IE

Free format text: FORMER OWNER: BLACKBERRY LIMITED, WATERLOO, ONTARIO, CA