(fory-site) branch main updated: 🔄 synced local 'docs/guide/' with remote 'docs/guide/'

[chaokunyang]

This is an automated email from the ASF dual-hosted git repository.

chaokunyang pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/fory-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 1c50229de 🔄 synced local 'docs/guide/' with remote 'docs/guide/'
1c50229de is described below

commit 1c50229de6c76fc7e9d0d4fdd2af2d2e1f44ff4d
Author: chaokunyang <shawn.ck.y...@gmail.com>
AuthorDate: Fri Sep 26 11:26:31 2025 +0000

    🔄 synced local 'docs/guide/' with remote 'docs/guide/'
---
 docs/guide/graalvm_guide.md | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/docs/guide/graalvm_guide.md b/docs/guide/graalvm_guide.md
index 6c5174fd9..88b005552 100644
--- a/docs/guide/graalvm_guide.md
+++ b/docs/guide/graalvm_guide.md
@@ -42,7 +42,7 @@ Args = 
--initialize-at-build-time=org.apache.fory.graalvm.Example
 
 Fory achieves this by using **codegen instead of reflection** - all 
serialization code is generated at build time when you call:
 
-- `fory.register(YourClass.class, true)` to register your classes
+- `fory.register(YourClass.class)` to register your classes
 - `fory.ensureSerializersCompiled()` to compile serializers at build time
 
 Note that Fory `asyncCompilationEnabled` option will be disabled automatically 
for graalvm native image since graalvm
@@ -61,8 +61,10 @@ This means you need to register your class with Fory. **Do 
NOT add it to reflect
 ```java
 static {
   fory = Fory.builder().build();
-  fory.register(MyClass.class, true);  // Enable codegen for this class
-  fory.ensureSerializersCompiled();    // Compile at build time
+  // register class
+  fory.register(MyClass.class);
+  // ensure all serializers for registered classes being compiled by fory at 
graalvm native image build time.
+  fory.ensureSerializersCompiled();
 }
 ```
 
@@ -97,9 +99,9 @@ public class Example {
 
   static {
     fory = Fory.builder().build();
-    // register and generate serializer code.
-    fory.register(Record.class, true);
-    // ensure lazy initialized serializers being compiled by fory.
+    // register class
+    fory.register(Record.class);
+    // ensure all serializers for registered classes being compiled by fory at 
graalvm native image build time.
     fory.ensureSerializersCompiled();
   }
 
@@ -144,9 +146,9 @@ public class ThreadSafeExample {
   static {
     fory = new ThreadLocalFory(classLoader -> {
       Fory f = Fory.builder().build();
-      // register and generate serializer code.
-      f.register(Foo.class, true);
-      // ensure lazy initialized serializers being compiled by fory.
+      // register class
+      f.register(Foo.class);
+      // ensure all serializers for registered classes being compiled by fory 
at graalvm native image build time.
       fory.ensureSerializersCompiled();
       return f;
     });
@@ -175,8 +177,7 @@ Args = 
--initialize-at-build-time=org.apache.fory.graalvm.ThreadSafeExample
 
 For framework developers, if you want to integrate fory for serialization, you 
can provided a configuration file to let
 the users to list all the classes they want to serialize, then you can load 
those classes and invoke
-`org.apache.fory.Fory.register(Class<?>, boolean)` to register those classes 
in your Fory integration class, and configure that
-class be initialized at graalvm native image build time.
+`org.apache.fory.Fory.register(Class<?>)` to register those classes in your 
Fory integration class. After all classes are registered, you need to invoke 
`org.apache.fory.Fory.ensureSerializersCompiled()` to compile serializers at 
build time, and configure that class be initialized at graalvm native image 
build time.
 
 ## Benchmark
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@fory.apache.org
For additional commands, e-mail: commits-h...@fory.apache.org