Skip to main content

Home/ Java Development/ Group items tagged 6

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Arup Vidyerthy

Java for OS X 2013-002: How to re-enable the Apple-provided Java SE 6 web plug-in and W... - 0 views

support.apple.com/ht5559

apple java

shared by Arup Vidyerthy on 06 Jun 13 - No Cached
  • Arup Vidyerthy on 06 Jun 13
     
    Switching between Apple and Oracle Java plugin
Justin Pierce

Enjoy An Excellent Bookkeeping Service - 1 views

It is a small grocery with just 4 staff that I started 6 months ago. I thought I can smoothly run it on my own. But then I noticed that I always encounter troubles in doing the payroll and other mo...

started by Justin Pierce on 28 Dec 12 no follow-up yet
Hendy Irawan

6. Validation, Data Binding, and Type Conversion - Spring Framework - 0 views

static.springsource.org/...validation.html

validation data conversion type converter class spring framework

shared by Hendy Irawan on 26 Jan 12 - No Cached
  • Hendy Irawan on 26 Jan 12
     
    "There are pros and cons for considering validation as business logic, and Spring offers a design for validation (and data binding) that does not exclude either one of them. Specifically validation should not be tied to the web tier, should be easy to localize and it should be possible to plug in any validator available. Considering the above, Spring has come up with a Validator interface that is both basic ands eminently usable in every layer of an application. Data binding is useful for allowing user input to be dynamically bound to the domain model of an application (or whatever objects you use to process user input). Spring provides the so-called DataBinder to do exactly that. The Validator and the DataBinder make up the validation package, which is primarily used in but not limited to the MVC framework. The BeanWrapper is a fundamental concept in the Spring Framework and is used in a lot of places. However, you probably will not have the need to use the BeanWrapper directly. Because this is reference documentation however, we felt that some explanation might be in order. We will explain the BeanWrapper in this chapter since, if you were going to use it at all, you would most likely do so when trying to bind data to objects. Spring's DataBinder and the lower-level BeanWrapper both use PropertyEditors to parse and format property values. The PropertyEditor concept is part of the JavaBeans specification, and is also explained in this chapter. Spring 3 introduces a "core.convert" package that provides a general type conversion facility, as well as a higher-level "format" package for formatting UI field values. These new packages may be used as simpler alternatives to PropertyEditors, and will also be discussed in this chapter."
mahesh 1234

this keyword - 0 views

www.javatpoint.com/this-keyword

java

shared by mahesh 1234 on 23 Dec 13 - No Cached
  • mahesh 1234 on 23 Dec 13
     
    There can be a lot of usage of this keyword. In java, this is a reference variable that refers to the current object. Usage of this keyword Here is given the 6 usage of this keyword. this keyword can be used to refer current class instance variable.
sureshstalin

Job - Qa//java//6 Months - 1 Year//location: Baroda//immediate Joinees - India, GUJARAT... - 0 views

www.river2c.com/...viewjob.r2c

QA Manual Testing And Automated J2ee IT software Java developer spring library computer eclipse opensource framework web programming Development

shared by sureshstalin on 14 Jul 13 - No Cached
  • sureshstalin on 14 Jul 13
     
    Register for free, post your resume and apply for Java,dotnet,Sales, IT, marketing, software jobs in India through River2c.com. Submit your resume now and find the right job.
anonymous

1. Working with Spring Data Repositories - 0 views

docs.spring.io/...repositories.html

java Spring Data

shared by anonymous on 29 Oct 13 - No 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
  • 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.
Hendy Irawan

Apache Aries (incubating) -- Index - 0 views

incubator.apache.org/aries

apache incubating aries osgi ee 6 java enterprise web

shared by Hendy Irawan on 08 Oct 10 - Cached
  • Hendy Irawan on 08 Oct 10
     
    The Aries project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes. The OSGi R4 V4.2 Enterprise Specification can be found here: http://www.osgi.org/Download/Release4V42 To understand the complete scope of the Aries project, see the Aries proposal document on the incubator wiki.
Tomas V

Java VisualVM - 0 views

java.sun.com/...intro.html

java vm

shared by Tomas V on 10 Jul 08 - Cached
Subhash Chandran

Andrew Cowie - Sun's secret web server - 0 views

research.operationaldynamics.com/...sun-secret-webserver.html

cowie http java jdk6 server webserver

shared by Subhash Chandran on 14 Apr 08 - Cached
  • Subhash Chandran on 14 Apr 08
     
    JDK 6 has a hidden web server!
Hendy Irawan

Chapter 6. HTTP Caching - 0 views

hc.apache.org/...caching.html

caching http client apache components library

shared by Hendy Irawan on 14 Apr 11 - No Cached
  • Hendy Irawan on 14 Apr 11
     
    HttpClient Cache provides an HTTP/1.1-compliant caching layer to be used with HttpClient--the Java equivalent of a browser cache. The implementation follows the Decorator design pattern, where the CachingHttpClient class is a drop-in replacement for a DefaultHttpClient; requests that can be satisfied entirely from the cache will not result in actual origin requests. Stale cache entries are automatically validated with the origin where possible, using conditional GETs and the If-Modified-Since and/or If-None-Match request headers. HTTP/1.1 caching in general is designed to be semantically transparent; that is, a cache should not change the meaning of the request-response exchange between client and server. As such, it should be safe to drop a CachingHttpClient into an existing compliant client-server relationship. Although the caching module is part of the client from an HTTP protocol point of view, the implementation aims to be compatible with the requirements placed on a transparent caching proxy. Finally, CachingHttpClient includes support the Cache-Control extensions specified by RFC 5861 (stale-if-error and stale-while-revalidate).
‹ Previous 21 - 33 of 33
Showing 20▼ items per page