| Q: |
Can I update the generated Java file? |
| A: |
To update a generated Java file, run the
mt_sdl utility specifying the -java option:
> mt_sdl -d mydatabase stubgen -java [-n package] myapp.odl |
| Q: |
Whenever Java files already exist, they are renamed by adding an .OLD extension. |
| A: |
Only the automatically generated code between specific markers is updated, in order to preserve the application source code. |
| Q: |
What is the procedure for updating a Java class definition? |
| A: |
To change a Java class definition (for
example to add or remove a property), update the ODL file and then
run the mt_sdl utility with the -java option.
> mt_sdl -d mydatabase stubgen -java [-n package] myapp-v2.odl
|
| Q: |
How do I deploy an applet to access information from the database? |
| A: |
The three-tier architecture is the most effective and reliable architecture for deploying applets to access information from a database. Create an application server to manage the persistent data objects. This will allow Matisse to create an isolation layer between the applet (presentation layer) and the database server (the dynamic content). |
| Q: |
Is the Java interface ODMG compliant? |
| A: |
The Matisse Java interface respects the ODMG Java language syntax in a single unified type system shared by the Java language and the Matisse object database. Individual instances of these common types can be persistent or transient.
Persistent Java class declarations are automatically generated
from the ODL definition using the mt_sdl utility. The mt_sdl utility
also enables Matisse to generate the application schema in the database. |
