OBEROn - Bug Trace

OBEROn 2.4 - Fast application development - 2011-09-12 10:55 - administrator [Announcement]

The main enhancements are:
- unit measure management: a metric system (or a set of unit measures) can be defined for single and multiple users so that every user can easily insert/edit/read object field values according to its - customizable - unit measure
- message localization: platform error/exception messages can be translated throught the internal dictionary
- ability to store the list of latest accessed objects for each user
- functionality for saving the search criteria (global query) and share them with all users
- new tool to automatically define UI forms, based on class fields

Besides, the form creation wizard allows to improve the application development significantly, by limiting the process to the following five steps:
1- analyze the application context
2- define the entities, their properties, the logical relationship among them
3- define the actors, their roles and the actions they can do in the information flow
4- execute the form generator to create the user interface
5- deploy the application for the proper rendering engine (HTML/JSP, SWT, JSF, Android ... )

OBEROn 2.2 - Workflow Management Improvements - 2011-04-28 12:08 - administrator [Announcement]

Workflow enhancements:
- start workflow-process automatically: you can associate a workflow to specific event and it will start as soon as the event occurs
- now it is possible to associate objects, add/remove user actors and parameters for a process steps
- user action step was kept distinct from system action step
- added workflow (user) decision element: you can define a poll between users and enable outgoing branches on the basic of user's choices (single/multiple)
- system steps can have multiple outputs; the system action program can decide about the next steps
- added a threshold to and-join steps: you can decide to complete this step if ALL or a minimal number of incoming steps are completed; you can also decide which incoming transitions are required in any case.
- added workflow/process start wizard
- added the functionality to suspend (and resume) user actions/decisions for the all running process-steps or for a single step

Other platform features:
- Added the OOQL upgrade command for updating the Oberon db schema from command line
- Tablespaces inside the db are now createt automatically when you define a new objectspace

Release 2.0: Workflow management - 2010-10-31 20:26 - administrator [Announcement]

Workflows are designed to achieve processing intents of some sort, such as physical transformation, service provision, or information processing.
Oberon implements now a workflow management system: it manages and defines a series of tasks within an organization to produce a final outcome or outcomes. It allows you to define different workflows for different types of jobs or processes. At each step in the workflow, one individual or group is responsible for a specific task. Once the task is complete, Oberon ensures that the individuals responsible for the next task are notified and receive the data they need to execute their stage of the process.

Release 1.6: SVN (Subversion) connector - 2010-10-31 20:25 - administrator [Announcement]

Usually, when you develop an application, you deal with the database schema and the source code. With Oberon the database schema is replaced with the application schema or in other words with the collection of administrative objects that represent the object classes, the object link-types, the lifecycles, the menus, commands, forms, views and so on. The schema is defined by using the Context Design tool (or directly with OOQL commands) and it is stored in the database. While the source code (web-pages or java classes) may be versioned and shared with a Subversion repository, the schema can be shared only if exported and imported (or compared) in the others Oberon DB instances.

The new release 1.6 allows to collaborate for the application schema creation and to share the administrative objetct definitions directly with the SVN repository, avoining the repeated and annoying export/import operations. You can simply check differences by connecting to the SVN repository and by updating your application schema or by commiting the modifications.

This accelerate the development of open source projects when the developers are distributed in different locations.

Release 1.5: SWT Desktop Applications - 2010-08-24 11:43 - administrator [Announcement]

Starting from release 1.5, you are enabled to access the same web-application with (SWT) desktop clients instead of a web-browsers. This is made possible because inside the Oberon core were added the functionalities to renderize the forms with SWT widgets and controls.

Release 1.4: document Indexing - 2010-05-11 17:17 - administrator

Indexing may be as simple as keeping track of unique document identifiers; but often it takes a more complex form, providing classification through the document metadata or even through word indexes extracted from the document contents. Indexing exists mainly to support retrieval.

The new release 1.4 togheter with to Apache Tika module provides objects retrieval through the attached files metadata and/or contents.

When you attach a file to a Oberon object, you may choose to index the file content and metadata simply using the "indexed" keyword in the OOQL command. For example:

object fileput <OBJECT_ID> indexed filetype "MS_Word" name "/home/myname/mydocument.docx";

The file content and the metadata will be extracted from the file and stored/indexed into the Oberon DB. With a command like the following:

query immediate object <ClassPattern> <NamePattern> <RevisionPattern> filter ( filecontent[MS_Word] ~= "<PatternToSearch>" );

you can retrieve all objects that match the <PatternToSearch> pattern in the attached files content/metadata (exclusively for MS_Word filetype).

Release 1.3: migrated from XFire to Apache CXF - 2010-03-13 19:25 - administrator

Apache CXF is a continuation of the XFire project and is considered XFire 2.0.
The Oberon WebService support employs now the new CXF framework and introduces a fast and easy way to create webservice clients with the following OOQL command:

webservice clientgen "http://localhost:8080/services/MyWebService?wsdl [^] ";

All generated classes are immediately ready to be applied into Oberon programs or triggers.
XFire libraries are removed from the platform distribution and CXF libraries are putted into a optional separated file.


	© 2008-2013 Mirko Solazzi \| Website Templates by IceTemplates.com Please Read: Privacy Policy and Terms of Use