Record Management
System is an important subsystem of J2ME, which aims to achieve persistent storage of local data in applications. Currently, mobile information devices that support file systems are limited, so Record
Management System is the preferred way for J2ME developers to implement local data storage. The purpose of this article is to comprehensively introduce Record Management
System knowledge.
As the name suggests, Record Management System is a system for managing data, and Record is the most important entity in the system. What is stored in the mobile device storage space is not a field, but a byte array. The Mobile Information Device PROfile (MIDP) specification does not stipulate what kind of data can be stored as a record. In fact, a record is any data that can be represented by a byte array, such as pictures, text, etc. Record
Management
The responsibility of the System is to store and uniquely identify records, while the task of representing data is completed by the application. Therefore, J2ME developers often have to spend more energy processing the data in the storage space. The purpose of this is to simplify the implementation of MIDP and make the J2ME subsystem as small and flexible as possible. After all, mobile information devices have limited storage space and processor capabilities.
Record Store is an ordered collection of a series of records. Records cannot exist alone and must belong to the Record Store. Record Store ensures that the read and write operations of records are atomic and the data will not be destroyed. In the API, Record Store is implemented by javax.microedition.rms.RecordStore. The specific operations of RecordStore will be introduced in detail in the following article.
The MIDP specification states that mobile information devices must provide at least 8K of non-volatile storage space for applications to achieve persistent storage of data. But the space provided by different devices is not the same. If MIDlet
The suite uses Record Management
System, then it must specify the minimum data storage space it requires by setting MIDlet-Data-Size in the MANIFEST file and JAD file, in bytes, for example, MIDlet-Data-Size: 8192. If your value exceeds the maximum specified by the mobile device then your application will not install correctly. This value is not the maximum Record that the mobile device actually provides to the application.
Management
System storage space is often larger, so developers should avoid setting the minimum storage space required by applications too large and refer to the instruction manual of the relevant device when necessary. Reading and writing data in non-volatile storage space is often slow, so it is best to provide a caching mechanism to improve performance for frequently accessed data. Record
The read and write operations of the Management System are thread-safe, but because the Record Store is controlled by the entire MIDlet
Suite is shared, so if threads running on different MIDlets operate the Record Store, we should perform necessary thread synchronization to avoid data damage.
About Record in MIDP1.0 and MIDP2.0
The implementation of Management System is somewhat different. MIDlets in the same MIDlet suite can access each other's Records.
Store. However, in the implementation of MIDP1.0, there is no provision for sharing Records between different MIDlet suites.
Store mechanism. A new API is provided in MIDP2.0 to solve the problem of sharing Records between different MIDlet suites.
Regarding Store issues, when creating a Record Store, the sharing mechanism is managed through the authorization mode and read-write control parameters. I will introduce it in detail in the next article.
Strengthen the Record
Management
The best way to understand System is to carry out actual development. During the development, I found that not all MIDP implementations of mobile devices are accurate. When I use the getSizeAvaliable() method to query the available records of Nokia6108
The value I got when using the Store space was more than 1M bytes, but when I wrote 40K of data, a RecordStoreFullException exception occurred, so I wrote an automatic test phone Record
Store the software with the largest storage space. The principle is to send data to Record every certain time, such as 100-500 milliseconds.
Write 1K bytes of data into the Store. When an exception that the storage space is full is thrown, the maximum value can be obtained. The precise unit is K bytes. The following is the source code of the program and the contents of the JAD file. The development platform is Eclipse3.0RC2+EclipseME0.4.1+Wtk2.1+J2SDK1.4.2._03. The test passed on the real Nokia 6108 and showed that the maximum value is 31K. (Please do not test on the simulator, as the results will be meaningless)
Summary: This article only leads readers to the Record
Management System has a general understanding, although an application is provided at the end of the article. But there is no in-depth analysis of how to use Record
Management
System. In the next article, we will analyze the classes in the javax.microedition.rms package in depth, focusing on how to use the RecordStore class.
import javax.microedition.lcdui.Alert;
import javax.microedition.lcdui.AlertType;
import javax.microedition.lcdui.Display;
import javax.microedition.midlet.MIDlet;
import javax.microedition .midlet.MIDletStateChangeException;
import javax.microedition.rms.RecordStoreException;
public class RMSAnalyzer extends MIDlet
{
private Display display;
private CounterCanvas counterCanvas;
private Alert alert;
protected void startApp() throws MIDletStateChangeException
{
display = Display.getDisplay(RMSAnalyzer.this);
alert = new Alert("錯(cuò)誤提示");
try
{
String interval = this.getAppProperty("INTER");
int t = Integer.parseInt(interval);
counterCanvas = new CounterCanvas(t, 1, this);
}
catch (RecordStoreException e)
{
this.showAlertError(e.getMessage());
}
display.setCurrent(counterCanvas);
}
public Display getDisplay()
{
return display;
}
protected void pauseApp()
{
}
protected void destroyApp(boolean arg0) throws MIDletStateChangeException
{
}
public void showAlertError(String message)
{
alert.setString(message);
alert.setType(AlertType.ERROR);
alert.setTimeout(3000);
display.setCurrent(alert);
}
}
import java.util.Timer;
import java.util.TimerTask;
import javax.microedition.lcdui.Canvas;
import javax.microedition.lcdui.Command;
import javax.microedition.lcdui.CommandListener;
import javax.microedition.lcdui.Displayable;
import javax.microedition.lcdui.Graphics;
import javax.microedition.midlet.MIDletStateChangeException;
import javax.microedition.rms.*;
public class CounterCanvas extends Canvas implements CommandListener
{
private RMSModel model;
private RMSAnalyzer RMSanalyzer;
private int interTime;
private int counter;
private boolean go = true;
public static Command backCommand = new Command("退出", Command.EXIT, 3);
public static final int INC = 1;
public final Timer timer = new Timer();
public CounterCanvas(int interTime, int base, RMSAnalyzer rmsa)
throws RecordStoreException
{
this.interTime = interTime;
this.counter = base;
this.RMSanalyzer = rmsa;
model = new RMSModel(base, RMSanalyzer);
this.addCommand(backCommand);
this.setCommandListener(this);
TimerTask timerTask = new TimerTask()
{
public void run()
{
try
{
model.writeRecord(INC);
counter++;
} catch (RecordStoreFullException e)
{
go = false;
model.deleteRMS();
timer.cancel();
} catch (RecordStoreException e)
{
model.deleteRMS();
RMSanalyzer.showAlertError(e.getMessage());
timer.cancel();
}
repaint();
}
};
timer.schedule(timerTask, 1000, interTime);
}
public void setCounter(int counter)
{
this.counter = counter;
}
public void setInterTime(int interTime)
{
this.interTime = interTime;
}
protected void paint(Graphics arg0)
{
int SCREEN_WIDTH = this.getWidth();
int SCREEN_HEIGHT = this.getHeight();
arg0.drawRect(SCREEN_WIDTH / 10, SCREEN_HEIGHT / 2,
SCREEN_WIDTH * 4 / 5, 10);
if(RMSanalyzer.getDisplay().isColor())
{
arg0.setColor(128, 128, 255);
}
arg0.fillRect(SCREEN_WIDTH / 10, SCREEN_HEIGHT / 2, counter, 10);
if (!go)
The above is the content of J2ME learning - RMS from entry to master. For more related content, please pay attention to the PHP Chinese website (m.miracleart.cn)!
Hot AI Tools
Undress AI Tool
Undress images for free
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Clothoff.io
AI clothes remover
Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!
Hot Article
Hot Tools
Notepad++7.3.1
Easy-to-use and free code editor
SublimeText3 Chinese version
Chinese version, very easy to use
Zend Studio 13.0.1
Powerful PHP integrated development environment
Dreamweaver CS6
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
Asynchronous Programming Techniques in Modern Java
Jul 07, 2025 am 02:24 AM
Java supports asynchronous programming including the use of CompletableFuture, responsive streams (such as ProjectReactor), and virtual threads in Java19. 1.CompletableFuture improves code readability and maintenance through chain calls, and supports task orchestration and exception handling; 2. ProjectReactor provides Mono and Flux types to implement responsive programming, with backpressure mechanism and rich operators; 3. Virtual threads reduce concurrency costs, are suitable for I/O-intensive tasks, and are lighter and easier to expand than traditional platform threads. Each method has applicable scenarios, and appropriate tools should be selected according to your needs and mixed models should be avoided to maintain simplicity
Best Practices for Using Enums in Java
Jul 07, 2025 am 02:35 AM
In Java, enums are suitable for representing fixed constant sets. Best practices include: 1. Use enum to represent fixed state or options to improve type safety and readability; 2. Add properties and methods to enums to enhance flexibility, such as defining fields, constructors, helper methods, etc.; 3. Use EnumMap and EnumSet to improve performance and type safety because they are more efficient based on arrays; 4. Avoid abuse of enums, such as dynamic values, frequent changes or complex logic scenarios, which should be replaced by other methods. Correct use of enum can improve code quality and reduce errors, but you need to pay attention to its applicable boundaries.
Understanding Java NIO and Its Advantages
Jul 08, 2025 am 02:55 AM
JavaNIO is a new IOAPI introduced by Java 1.4. 1) is aimed at buffers and channels, 2) contains Buffer, Channel and Selector core components, 3) supports non-blocking mode, and 4) handles concurrent connections more efficiently than traditional IO. Its advantages are reflected in: 1) Non-blocking IO reduces thread overhead, 2) Buffer improves data transmission efficiency, 3) Selector realizes multiplexing, and 4) Memory mapping speeds up file reading and writing. Note when using: 1) The flip/clear operation of the Buffer is easy to be confused, 2) Incomplete data needs to be processed manually without blocking, 3) Selector registration must be canceled in time, 4) NIO is not suitable for all scenarios.
How does a HashMap work internally in Java?
Jul 15, 2025 am 03:10 AM
HashMap implements key-value pair storage through hash tables in Java, and its core lies in quickly positioning data locations. 1. First use the hashCode() method of the key to generate a hash value and convert it into an array index through bit operations; 2. Different objects may generate the same hash value, resulting in conflicts. At this time, the node is mounted in the form of a linked list. After JDK8, the linked list is too long (default length 8) and it will be converted to a red and black tree to improve efficiency; 3. When using a custom class as a key, the equals() and hashCode() methods must be rewritten; 4. HashMap dynamically expands capacity. When the number of elements exceeds the capacity and multiplies by the load factor (default 0.75), expand and rehash; 5. HashMap is not thread-safe, and Concu should be used in multithreaded
Effective Use of Java Enums and Best Practices
Jul 07, 2025 am 02:43 AM
Java enumerations not only represent constants, but can also encapsulate behavior, carry data, and implement interfaces. 1. Enumeration is a class used to define fixed instances, such as week and state, which is safer than strings or integers; 2. It can carry data and methods, such as passing values ??through constructors and providing access methods; 3. It can use switch to handle different logics, with clear structure; 4. It can implement interfaces or abstract methods to make differentiated behaviors of different enumeration values; 5. Pay attention to avoid abuse, hard-code comparison, dependence on ordinal values, and reasonably naming and serialization.
What is a Singleton design pattern in Java?
Jul 09, 2025 am 01:32 AM
Singleton design pattern in Java ensures that a class has only one instance and provides a global access point through private constructors and static methods, which is suitable for controlling access to shared resources. Implementation methods include: 1. Lazy loading, that is, the instance is created only when the first request is requested, which is suitable for situations where resource consumption is high and not necessarily required; 2. Thread-safe processing, ensuring that only one instance is created in a multi-threaded environment through synchronization methods or double check locking, and reducing performance impact; 3. Hungry loading, which directly initializes the instance during class loading, is suitable for lightweight objects or scenarios that can be initialized in advance; 4. Enumeration implementation, using Java enumeration to naturally support serialization, thread safety and prevent reflective attacks, is a recommended concise and reliable method. Different implementation methods can be selected according to specific needs
Java Optional example
Jul 12, 2025 am 02:55 AM
Optional can clearly express intentions and reduce code noise for null judgments. 1. Optional.ofNullable is a common way to deal with null objects. For example, when taking values ??from maps, orElse can be used to provide default values, so that the logic is clearer and concise; 2. Use chain calls maps to achieve nested values ??to safely avoid NPE, and automatically terminate if any link is null and return the default value; 3. Filter can be used for conditional filtering, and subsequent operations will continue to be performed only if the conditions are met, otherwise it will jump directly to orElse, which is suitable for lightweight business judgment; 4. It is not recommended to overuse Optional, such as basic types or simple logic, which will increase complexity, and some scenarios will directly return to nu.
How to fix java.io.NotSerializableException?
Jul 12, 2025 am 03:07 AM
The core workaround for encountering java.io.NotSerializableException is to ensure that all classes that need to be serialized implement the Serializable interface and check the serialization support of nested objects. 1. Add implementsSerializable to the main class; 2. Ensure that the corresponding classes of custom fields in the class also implement Serializable; 3. Use transient to mark fields that do not need to be serialized; 4. Check the non-serialized types in collections or nested objects; 5. Check which class does not implement the interface; 6. Consider replacement design for classes that cannot be modified, such as saving key data or using serializable intermediate structures; 7. Consider modifying
