HHH-19216 - NamedEntityGraph annotation supporting Hibernate parseable format

HHH-19237 - Expand graph language to optionally specify entity
HHH-19217 - Expose GraphParser#parse on SessionFactory

Author: sebersole

documentation/src/main/asciidoc/userguide/chapters/fetching/Fetching.adoc

@@ -285,7 +285,8 @@ the subtype Class.
 Hibernate allows the creation of Jakarta Persistence fetch/load graphs by parsing a textual representation
 of the graph.  Generally speaking, the textual representation of a graph is a comma-separated
 list of attribute names, optionally including any subgraph specifications.
-`org.hibernate.graph.GraphParser` is the starting point for such parsing operations.
+The starting point for such parsing operations is either `org.hibernate.graph.GraphParser`
+or `SessionFactory#parseEntityGraph`
 
 [NOTE]
 ====
@@ -370,6 +371,28 @@ include::{example-dir-fetching}/GraphParsingTest.java[tags=fetching-strategies-d
 ====
 
 
+[[fetching-strategies-dynamic-fetching-entity-graph-parsing-annotation]]
+==== @NamedEntityGraph with text representation
+
+Hibernate also offers a `@org.hibernate.annotations.NamedEntityGraph` annotation, as a corollary
+to the `@jakarta.persistence.NamedEntityGraph`, supporting the text representation
+<<fetching-strategies-dynamic-fetching-entity-graph-parsing,discussed previously>>.  The annotation
+may be placed on an entity or on a package.
+
+
+.@NamedEntityGraph example
+====
+[source, java, indent=0]
+----
+@Entity
+@NamedEntityGraph( graph="title,isbn,author(name,phoneNumber)" )
+class Book {
+	// ...
+}
+----
+====
+
+
 [[fetching-strategies-dynamic-fetching-profile]]
 === Dynamic fetching via Hibernate profiles
 

hibernate-core/src/main/java/org/hibernate/metamodel/model/domain/internal/JpaMetamodelImpl.java

@@ -491,7 +491,7 @@ private <T> ImportInfo<T> resolveImport(final String name) {
 		}
 	}
 
-	private void applyNamedEntityGraphs(Collection<NamedEntityGraphDefinition> namedEntityGraphs, RuntimeModelCreationContext runtimeModelCreationContext) {
+	private void applyNamedEntityGraphs(Collection<NamedEntityGraphDefinition> namedEntityGraphs) {
 		for ( NamedEntityGraphDefinition definition : namedEntityGraphs ) {
 			log.debugf(
 					"Applying named entity graph [name=%s, source=%s]",
@@ -680,7 +680,7 @@ public void processJpa(
 			}
 		} );
 
-		applyNamedEntityGraphs( namedEntityGraphDefinitions, runtimeModelCreationContext );
+		applyNamedEntityGraphs( namedEntityGraphDefinitions );
 
 		populateStaticMetamodel( bootMetamodel, context );
 	}

migration-guide.adoc

@@ -34,6 +34,28 @@ earlier versions, see any other pertinent migration guides as well.
 See this https://in.relation.to/2024/04/01/jakarta-persistence-3/[blog post] for a good discussion of the changes in Jakarta Persistence 3.2.
 
 
+[[NamedEntityGraph]]
+== @NamedEntityGraph
+
+A new annotation (`@org.hibernate.annotations.NamedEntityGraph`) has been added to allow
+specifying a named entity-graph using Hibernate's ability to parse a string representation of the graph.
+
+
+[source,java]
+----
+@Entity
+@NamedEntityGraph( graph="title, isbn, author( name, phoneNumber )" )
+class Book {
+	// ...
+}
+----
+
+
+See `org.hibernate.graph.GraphParser` for details on the syntax and the
+link:{user-guide-url}#fetching-strategies-dynamic-fetching-entity-graph-parsing-annotation[user guide] for additional details.
+
+
+
 [[hibernate-models]]
 == Hibernate Models