more presentation cleanups
This commit is contained in:
parent
59b6f702e5
commit
96b503454e
|
@ -149,11 +149,10 @@ The `<persistence-unit>` element defines a named _persistence unit_, that is:
|
|||
|
||||
Each `<class>` element specifies the fully-qualified name of an entity class.
|
||||
|
||||
[TIP]
|
||||
// .Scanning for entity classes
|
||||
====
|
||||
.Scanning for entity classes
|
||||
****
|
||||
In some container environments, for example, in any EE container, the `<class>` elements are unnecessary, since the container will scan the archive for annotated classes, and automatically recognize any class annotated `@Entity`.
|
||||
====
|
||||
****
|
||||
|
||||
Each `<property>` element specifies a _configuration property_ and its value.
|
||||
Note that:
|
||||
|
|
|
@ -182,6 +182,7 @@ So there's that.
|
|||
|
||||
One thing that some repository frameworks offer is the ability to declare an abstract method that queries the database, and have the framework fill in an implementation of the method.
|
||||
But the way this works is that you must encode your query into the name of the method itself.
|
||||
|
||||
Which, at least in principle, for a not-very-complicated query, leads to a method name like this:
|
||||
|
||||
[.text-center]
|
||||
|
|
|
@ -429,7 +429,7 @@ List<Book> matchingBooks =
|
|||
|
||||
When a query has multiple parameters, named parameters tend to be easier to read, even if slightly more verbose.
|
||||
|
||||
[IMPORTANT]
|
||||
[WARNING]
|
||||
// .Using parameters to avoid injection attacks
|
||||
====
|
||||
_Never_ concatenate user input with HQL and pass the concatenated string to `createSelectionQuery()`.
|
||||
|
|
|
@ -11,7 +11,13 @@ body:before {
|
|||
#header {
|
||||
width: 1000px !important;
|
||||
}
|
||||
#toctitle,.sidebarblock>.content>.title,h4,h5,h6{
|
||||
.sidebarblock>.content>.title,h4,h5,h6{
|
||||
font-size: 1.3em !important;
|
||||
margin-top:0em !important;
|
||||
margin-bottom:1em !important;
|
||||
line-height:1.0125em !important
|
||||
}
|
||||
#toctitle>.content>.title,h4,h5,h6{
|
||||
font-family:"Open Sans","DejaVu Sans",sans-serif !important;
|
||||
font-weight:300 !important;
|
||||
font-style:normal !important;
|
||||
|
|
Loading…
Reference in New Issue