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

paulk pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/groovy-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new e8188b5  add Jakarta EE related changes to release notes (additional 
note)
e8188b5 is described below

commit e8188b547a9f71c3956ee512673ce160e04afdab
Author: Paul King <[email protected]>
AuthorDate: Thu Jan 9 18:13:46 2025 +1000

    add Jakarta EE related changes to release notes (additional note)
---
 site/src/site/releasenotes/groovy-5.0.adoc | 19 ++++++++++++++++---
 1 file changed, 16 insertions(+), 3 deletions(-)

diff --git a/site/src/site/releasenotes/groovy-5.0.adoc 
b/site/src/site/releasenotes/groovy-5.0.adoc
index 3fcf069..23dc908 100644
--- a/site/src/site/releasenotes/groovy-5.0.adoc
+++ b/site/src/site/releasenotes/groovy-5.0.adoc
@@ -145,15 +145,28 @@ public pets = ['cat', 'dog']
 
 The `groovy-servlet` module supports:
 
+* Writing servlets as Groovy scripts (_Groovlets_), e.g.:
++
+[source,groovy]
+----
+html.html {
+    head {
+         title 'My first Groovlet'
+    }
+    body { h1 'Welcome to Groovlets!' }
+}
+----
 * Writing servlets as Groovy classes (typically extending 
`AbstractHttpServlet`)
-* Writing servlets as Groovy scripts (_Groovlets_)
 * Writing Template-style, JSP-like _Groovy Server Pages_ which combine 
(typically) HTML with Groovy control-logic within special tags
 
 Groovy 5 defaults to Jakarta EE versions of the Servlet-related standards.
 This mostly involves using versions of the underlying classes with different
 package names.
-When writing Groovlets or GSPs, the change in package name might not be 
apparent
-but the underlying classes being used would change.
+
+When writing Groovlets or GSPs, the change in package name might not be 
apparent,
+since for simple examples, like the one shown above, the package names don't 
appear, but the underlying classes being used would change.
+If you are using Groovylets, your transition to Jakarta EE should be a little
+easier.
 
 You can still obtain the older Javax EE versions of the relevant classes using
 the "javax" classifier when specifying your dependency on `groovy-servlet`.

Reply via email to