In many ways UML activity
diagrams are the object-oriented equivalent of
flow charts and
data flow diagrams (DFDs) from structured
development
Group items tagged
1More
Eclipse Scout - Project Home - 0 views
-
The objective of Eclipse Scout is to substantially reduce the development time needed for SOA and Java-conforming business software. Scout includes: an application model, a reference implementation, proven development functions and a comprehensive tool: the Scout SDK.
1More
shared by Hendy Irawan on 26 Apr 11
- No Cached
Jisql - a Java based interactive SQL application - 0 views
www.xigole.com/...E9656BBB8AECB30CEA90AD9E77EABD
sql workbench database tools development java j derby a jisql
shared by Hendy Irawan on 26 Apr 11
- No Cached
-
Jisql is a Java based utility to provide a command line interactive session with a SQL server. This application is conceptually modeled on the Sybase 'isql' program with, obviously, strong similarities to Microsoft SQL/Server isql and osql (as Microsoft got SQL Server from Sybase). The program can act in a similar way to Oracle's sqlplus and PostgreSQL's psql.
1More
Eclipse Gemini Blueprint - Home - 0 views
-
Eclipse Gemini Blueprint is the reference implementation for the OSGi Alliance Blueprint Service (chapter 121 of the OSGi 4.2 Compendium Specification). Gemini Blueprint project makes it easy to build Java applications that run in an OSGi framework. By using Gemini Blueprint, applications benefit from using a better separation of modules, the ability to dynamically add, remove, and update modules in a running system, the ability to deploy multiple versions of a module simultaneously (and have clients automatically bind to the appropriate one), and a dynamic service model. Gemini users may also be interested in Eclipse Virgo, an open source, completely modular, OSGi-based Java application server. Its documentation is considered a supplement to Gemini Blueprint as it explains in detail, how OSGi can be used in various development and production scenarios.
2More
Introduction to UML 2 Activity Diagrams - 0 views
24More
1. Working with Spring Data Repositories - 0 views
-
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
-
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
shared by Hendy Irawan on 03 Oct 10
- Cached
www.qi4j.org - www.qi4j.org - 0 views
www.qi4j.org
architecture complexity composite dev design development di domain opensource programming ddd modeling aop framework java spring osgi sca newton infiniflow for:wongacid for:febru for:ariekusumaatmaja for:tomfreakz qi4j
shared by Hendy Irawan on 03 Oct 10
- Cached
-
The short answer is that Qi4j is a framework for domain centric application development, including evolved concepts from AOP, DI and DDD. Qi4j is an implementation of Composite Oriented Programming, using the standard Java 5 platform, without the use of
Transaction strategies: Models and strategies overview - 0 views
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
1More
REST for Java developers, Part 4: The future is RESTful - JavaWorld - 0 views
-
Tyranny of the Common Form. The social costs of getting everyone to agree to the definition of these central models always outweigh the technical costs of implementing them.
‹ Previous
21 - 30 of 30