Cached
Typically, your repository interface will extend
Repository,
CrudRepository or
PagingAndSortingRepository.
Alternatively, if you do not want to extend Spring Data interfaces,
you can also annotate your repository interface with
@RepositoryDefinition
Group items matching
in title, tags, annotations or url
1More
Online java tutorial - Exception Handling - 0 views
-
Java Topic / Java tutorial An exception is an abnormal condition that arises in a code sequence at run time. An exception is a run-time error. Most of these run-time errors could be prevented by doing proper input validation as shown in 151, but in cases where we can not prevent effectively we can use the exception handling mechanism provided by Java.
1More
unitsofmeasure - Units of Measurement API - Google Project Hosting - 0 views
-
"Units of Measurement API specifies one or more JavaTM packages for the programmatic handling of physical quantities and their expression as numbers of units."
1More
Where to Use Assertion in Java with Example - 0 views
-
Quick guide on where to use Assertion in Java with code example. Assertion in java is fairly underused feature but if used carefully can complement both Unit Testing and Exception handling. Since Assertion sits on code its gets more expose than unit testing and can test your function with more real data than one or two test data.
1More
Maven Archiver Plugin JAR WAR Manifest - Reference - 0 views
-
"The Maven Archiver is mainly used by plugins to handle packaging. The version numbers referenced in the Since column on this page are the version of the Maven Archiver component - not for any specific plugin. To see which version of Maven Archiver a plugin uses, go to the site for that plugin. "
1More
JSP Tutorial, JavaServer Pages Technology (JSP) - javatpoint - 0 views
-
JSP Tutorial - Javatpoint website provides you a complete JSP tutorial with practical programming examples and easy steps using this beginner's tutorial containing basic to advanced knowledge of Java JSP Technology including Form Data, HTTP Request Header, Response Header, Scripting elements, Directive elements, Custom tags, Cookies Handling and Session Tracking.
24More
1. Working with Spring Data Repositories - 0 views
-
-
It allows quick query definition by method names but also custom-tuning of these queries by introducing declared queries as needed.
-
CREATE_IF_NOT_FOUND (default)CREATE_IF_NOT_FOUND combines CREATE and USE_DECLARED_QUERY.
- ...21 more annotations...
-
the first By acts as delimiter to indicate the start of the actual criteria
-
The mechanism strips the prefixes find…By, read…By, and get…By from the method and starts parsing the rest of it
-
you can define conditions on entity properties and concatenate them with And and Or
-
The introducing clause can contain further expressions such as a Distinct to set a distinct flag
-
List<Person> findByEmailAddressAndLastname(EmailAddress emailAddress, String lastname); // Enables the distinct flag for the query List<Person> findDistinctPeopleByLastnameOrFirstname(String lastname, String firstname); List<Person> findPeopleDistinctByLastnameOrFirstname(String lastname, String firstname); // Enabling ignoring case for an individual property List<Person> findByLastnameIgnoreCase(String lastname); // Enabling ignoring case for all suitable properties List<Person> findByLastnameAndFirstnameAllIgnoreCase(String lastname, String firstname); // Enabling static ORDER BY for a query List<Person> findByLastnameOrderByFirstnameAsc(String lastname); List<Person> findByLastnameOrderByFirstnameDesc(String lastname);
-
You can combine property expressions with AND and OR. You also get support for operators such as Between, LessThan, GreaterThan, Like for the property expressions
-
AllIgnoreCase
-
IgnoreCase
-
The resolution algorithm starts with interpreting the entire part (AddressZipCode) as the property and checks the domain class for a property with that name (uncapitalized). If the algorithm succeeds it uses that property. If not, the algorithm splits up the source at the camel case parts from the right side into a head and a tail and tries to find the corresponding property, in our example, AddressZip and Code.
-
he infrastructure will recognize certain specific types like Pageable and Sort to apply pagination and sorting to your queries dynamically
-
Pageable
-
Sort sort
-
The first method allows you to pass an org.springframework.data.domain.Pageable instance to the query method to dynamically add paging to your statically defined query. Sorting options are handled through the Pageable instance too
-
<repositories base-package="com.acme.repositories" />
-
Spring is instructed to scan com.acme.repositories and all its subpackages for interfaces extending Repository or one of its subinterfaces. For each interface found, the infrastructure registers the persistence technology-specific FactoryBean to create the appropriate proxies that handle invocations of the query methods. Each bean is registered under a bean name that is derived from the interface name, so an interface of UserRepository would be registered under userRepository
-
This postfix defaults to Impl.Example 1.12. Configuration example<repositories base-package="com.acme.repository" /> <repositories base-package="com.acme.repository" repository-impl-postfix="FooBar" />The first configuration example will try to look up a class com.acme.repository.UserRepositoryImpl to act as custom repository implementation, where the second example will try to lookup com.acme.repository.UserRepositoryFoo
-
To exclude an interface that extends Repository from being instantiated as a repository instance, you can either annotate it with @NoRepositoryBean or move it outside of the configured base-package.
-
]In general, the integration support is enabled by using the @EnableSpringDataWebSupport annotation in your JavaConfig configuration class.
-
@Configuration @EnableWebMvc @EnableSpringDataWebSupport class WebConfiguration { }
-
In case you need multiple Pageables or Sorts to be resolved from the request (for multiple tables, for example) you can use Spring's @Qualifier annotation to distinguish one from another
-
Spring HATEOAS ships with a representation model class PagedResources that allows enrichting the content of a Page instance with the necessary Page metadata as well as links to let the clients easily navigate the pages.
1More
Commons Exec - Apache Commons Exec - 0 views
-
"Executing external processes from Java is a well-known problem area. It is inheriently platform dependent and requires the developer to know and test for platform specific behaviors, for example using cmd.exe on Windows or limited buffer sizes causing deadlocks. The JRE support for this is very limited, albeit better with the new Java SE 1.5 ProcessBuilder class. Reliably executing external processes can also require knowledge of the environment variables before or after the command is executed. In J2SE 1.1-1.4 there is not support for this, since the method, System.getenv(), for retriving environment variables is deprecated. There are currently several different libraries that for their own purposes have implemented frameworks around Runtime.exec() to handle the various issues outlined above. The proposed project should aim at coordinating and learning from these initatives to create and maintain a simple, reusable and well-tested package. Since some of the more problematic platforms are not readily available, it is my hope that the broad Apache community can be a great help."
1More
Apache MyFaces Trinidad - Mobile Application Development - 0 views
-
When developing a mobile application, you need not focus on the limitations or capabilities of different browsers, as Trinidad enables you to develop applications that function properly on different browser types. The Trinidad renderer ensures that the target browser can consume contents correctly. It handles the variations in both browser implementations of HTML, JavaScript, CSS, DOM, XMLHttpRequest and system performance. For example, if a browser does not support XMLHttpRequest and is incapable of posting a partial page request to a server, support for AJAX enables the application to revert automatically to a full page submit so that the same page functions whether the browser supports XMLHttpRequest or not. Furthermore, if the target browser does no support JavaScript Trinidad will automatically render contents that work on HTML by removing all dependencies on JavaScript.
1More
Java Secure FTPd Server - 1 views
-
FTP Server written in pure Java. Supports AUTH SSL (Explicit SSL), it is firewall friendly (handles the CCC command), has virtual home directories with individual read/write access, anoymous support and many more
2More
Shrinkwrap - JBoss Community - 0 views
-
Shrinkwrap provides a simple mechanism to assemble archives like JARs, WARs, and EARs with a friendly, fluent API.
-
Shrinkwrap provides a simple mechanism to assemble archives like JARs, WARs, and EARs with a friendly, fluent API. JavaArchive archive = ShrinkWrap.create(JavaArchive.class,"archive.jar") .addClasses(MyClass.class,MyOtherClass.class) .addResource("mystuff.properties"); From there you may deploy directly into any supported integration container like JBoss EmbeddedAS, GlassFish v3 Embedded, Jetty, or OpenEJB. Or perhaps you'd like to export the archive to a file or exploded directory structure. Maybe you'd prefer to serialize it over the network to a remote host. The possibilities are limitless. To boot, ShrinkWrap is the supported deployment mechanism of the Arquillian project, and together we render the testing of true enterprise components amiable as a puppy. Where Java EE brought a POJO programming model to application development, we've brought it to testing. You handle your business logic; we'll do the rest. To foster community participation, the majority of documentation and examples are available through our Wiki. Releases are available either via our Downloads section, or through the JBoss Maven Repository, which we recommend is configured in ${userHomeDir}/.m2/settings.xml:
1More
Online Java Training - Prevent exceptions - 0 views
-
Java Topic / Java tutorial The best way to handle exception is by preventing it. Since exception causes abnormal termination of programs and they consume lot of resources compared the to the normal code execution.
12More
GAME OVER - Java Server Faces | ComeSolveGo - 0 views
-
Almost everything is wrong with the framework
-
Little control over generated HTML
-
While you need basic functionalities, everything is fine. When you need to modify the component (which is configurable, right?) you are facing the problems
- ...8 more annotations...
-
EXTREMELY idiotic thing - because JSF has their famous lifecycle with lots of magic phases, some backing bean getters are called multiple times!
-
Back button problem.
-
Unreadable URLs. JSF always does the POST.
-
JSF is submitting a form on itself so it could call a backing bean method to handle an event. Of course, if you have a request, there is unnecessary repeated initialization, getter calls, postconstruct etc
-
Reusability? Good joke…
-
JSF - you are FIRED!
-
IDE support
-
Development of custom component? No way, extremely complicated. Extensible? In the movie, maybe…
125More
Organize Projects - Google Web Toolkit - Google Code - 0 views
-
com.google.gwt.gears.Gears
-
-
two ways to approach loading them
-
nclude each module with a separate <script> tag
- ...118 more annotations...
-
Create a top level module XML definition
-
Compile the top level module
-
the second approach will lead to much better end-user performance
-
each module has to be downloaded separately by the end-user's browser
-
each module will contain redundant copies of GWT library
-
conflict with each other during event handling
-
Linkers are divided into three categories, PRE, POST, and PRIMARY
-
one primary linker is run for a compilation
-
everal linkers are provided by Core.gwt.xml, which is automatically inherited by User.gwt.xml.
-
monolithic JavaScript file.
-
cross-site deployment model.
-
standard iframe-based
-
<add-linker name="xs" />
-
The GWT compiler
-
packaging its output with the Linker subsystem
-
responsible for the final packaging of the JavaScript code
-
providing a pluggable bootstrap mechanism
-
re-use an existing Java API for a GWT project,
-
<super-source>
-
"re-root" a source path
-
to emulate part of the JRE not implemented by GWT
-
tells the compiler to add all subfolders of com/example/myproject/jre/
-
to the source path
-
com/google/myproject/gwt/jre/java/util/UUID.java
-
most commonly used elements in the module XML file.
-
<inherits name="
-
herits all the settings from the specified module
-
<entry-point class=
-
Entry points are all compiled into a single codebase
-
when the onModuleLoad() of your first entry point finishes, the next entry point is called immediately.
-
Any number of entry-point classes can be added
-
<source path="
-
resources get copied into the output directory during a GWT compile.
-
client subpackage is implicitly added to the source path
-
<public path="path" />
-
treated as a publicly-accessible resource.
-
resources get copied into the output directory
-
the public subpackage is implicitly added to the public
-
<servlet
-
For RPC, this element loads a servlet class
-
mounted at the specified URL path
-
path=
-
-
class="
-
-
URL path should be absolute
-
@RemoteServiceRelativePath attribute
-
you must configure a WEB-INF/web.xml in your war directory to load any servlets needed.
-
n development mode,
-
<script src="
-
external JavaScrip
-
<stylesheet src="
-
Extends the set of values
-
for an existing client property
-
<replace-with-class>
-
<generate-with-class>
-
<when-property-is
-
three different types of predicates are
-
<when-type-assignable
-
<when-type-is
-
<all>
-
<any>
-
<none>
-
GWT libraries are organized into modules
-
you want to inherit at least the User module
-
contains all the core GWT functionality
-
including the EntryPoint class
-
widgets and panels
-
History feature
-
Internationalization
-
DOM programming, and more
-
Low-level HTTP
-
Use the following syntax to cause an external JavaScript file to be loaded
-
before your module entry point is called.
-
as if you had included it explicitly using the HTML <script
-
loaded before your onModuleLoad() is called.
-
all included scripts will be loaded when your application starts, in the order in which they are declared.
-
associate external CSS files with your module
-
GWT.getModuleBaseURL() + "foo.css" in client code
-
module's public path
-
useful when
-
inheritance makes resource inclusion particularly convenient.
-
If you wish to create a reusable library that relies upon particular stylesheets or JavaScript files, you can be sure that clients
-
see the documentation for FileSet for a general overview
-
<public>
-
<super-source>
-
<source>
-
includes
-
excludes
-
defaultexcludes
-
casesensitive
-
By default, the patterns listed here are excluded.
-
defaultexcludes is true
-
<script src='myApp/myApp.nocache.js'></script>
-
<script> tags always block evaluation of the page
-
<img> tags do not block page evaluation
-
two simultaneous connections
-
The body.onload() event will only fire once all external resources are fetched, including images and frames.
-
GWT selection script
-
like a normal script tag
-
but the compiled script will be fetched asynchronously.
-
Parsing is blocked until externalScriptZero.js is done fetching and evaluating.
-
myApp/myApp.nocache.js completes
-
the compiled scrip
-
(<hashname>.cache.html
-
begins fetching in a hidden IFRAME (this is non-blocking).
-
onModuleLoad() is not called yet, as we're still waiting on externalScriptOne.js
-
body.onload() fires
-
onload='alert("w00t!")
-
-
put the GWT selection script as early as possible
-
because it won't block any other script requests
-
<img> tags are not guaranteed to be done loading when onModuleLoad() is called
-
<script> tags are guaranteed to be done loading when onModuleLoad() is called
-
multiple EntryPoints
-
will all be called in sequence as soon as that module (and the outer document) is ready
-
multiple GWT modules within the same page
-
each module's EntryPoint will be called as soon as both that module and the outer document is ready
-
EntryPoints are not guaranteed to fire at the same time
-
or in the same order
-
in which their selection scripts were specified in the host page
