HİBERNATE TEKNOLOJİLERİNE Giris,

Posted on May 21, 2015June 4, 2015 by coder

Guzel bulmus oldugum iyi bir calismayi, Sizinle paylasmak istedim.

Bu dosya Hacettepe universitesinin internet sayfasindan indirilmistir.

Hazırlayan : Adem Öztürk << Tesekkur ederim kendisine. İÇİNDEKİLER: 1. GİRİŞ: .................................................................................................................................... 3 2. HİBERNATE ÇALIŞMA İLKELERİ VE MİMARİSİ......................................................... 4 3. SESSIONFACTORY YAPILANDIRMASI............................................................................ 6 3.1 Programlama yoluyla yapılandırma ................................................................................. 6 3.2 SessionFactory elde etme ................................................................................................. 7 3.3 JDBC baglantıları............................................................................................................. 7 3.4 XML Yapılandırma Kütüğü............................................................................................. 7 4. KALICI SINIFLAR (PERSISTENT CLASSES) .................................................................. 8 4.1 Kalıcı sınıfların temel özellikleri.................................................................................... 10 4.2 Kalıcı sınıflarda ayırıcı (identifier) alanı ve Veri tabanı birincil anahtar niteliği ilişkisi .............................................................................................................................................. 10 4.3 Final tanımlanmış sınıflar ve türemiş sınıflar ................................................................ 10 4.4 equals() , hashCode() metotları hakkında ...................................................................... 10 4.5 Güncelleme, silme önlemleri ve yaşam döngüsü ara yüzü ............................................ 11 5. BASİT NESNE/İLİŞKİSEL MODEL EŞLEME (OBJECT/RELATİONAL MAPPİNG). 11 5.1 Nesne/ilişkisel model eşleme(Object/Relational Mapping) kütüğü içeriği.................... 14 5.1.1 Doctype ................................................................................................................... 14 5.1.2 hibernate-mapping................................................................................................... 14 5.1.3 class......................................................................................................................... 14 5.1.4 id.............................................................................................................................. 15 5.1.5 property ................................................................................................................... 16 5.1.6 many-to-one ............................................................................................................ 16 5.1.7 one-to-one................................................................................................................ 17 5.1.8 subclass.................................................................................................................... 17 6. KALICI VERİNİN İŞLENMESİ (MANİPULATİNG PERSİSTENT DATA ) ................. 17 6.1. Kalıcı nesnenin oluşturulması ....................................................................................... 17 6.2 Kalıcı nesnenin geri yüklenmesi(loading of a persistent object) ................................... 18 6.3 Sorgulama (Querying).................................................................................................... 19 6.4 Güncelleme ve Silme ..................................................................................................... 20 7. ÖRNEK UYGULAMALAR................................................................................................ 21 7.1 Örnek uygulama 1 .......................................................................................................... 21 7.1.1 eşleme (mapping) kütükleri..................................................................................... 21 7.1.2 Hibernate.properties kütüğü.................................................................................... 22 7.1.3 Şema oluşturma ....................................................................................................... 23 7.1.4 Kalıcı sınıfları oluşturma......................................................................................... 23 7.1.5 Hibernate ile Kalıcı Sınıfları Kullanma .................................................................. 23

Download link: Hibernate_giris_Adem…._fileserver_mirror_kutayzorlu.com

Maven, What is Maven? , What is Maven doing?

Posted on May 21, 2015June 4, 2015 by coder

Convention over configuration (also known as coding by convention) is a software design paradigm which seeks to decrease the number of decisions that developers need to make, gaining simplicity, but not necessarily losing flexibility.

The phrase essentially means a developer only needs to specify unconventional aspects of the application. For example, if there is a class Sale in the model, the corresponding table in the database is called “sales” by default. It is only if one deviates from this convention, such as calling the table “product sales”, that one needs to write code regarding these names.

When the convention implemented by the tool matches the desired behavior, it behaves as expected without having to write configuration files. Only when the desired behavior deviates from the implemented convention is explicit configuration required.

Aspect oriented programming (AOP)

Posted on May 21, 2015June 4, 2015 by coder

In computing, aspect-oriented programming (AOP) is a patented[1] programming paradigm that aims to increase modularity by allowing the separation of cross-cutting concerns. It does so by adding additional behavior to existing code (an advice) without modifying the code itself, instead separately specifying which code is modified via a “pointcut” specification, such as “log all function calls when the function’s name begins with ‘set'”. This allows behaviors that are not central to the business logic (such as logging) to be added to a program without cluttering the code core to the functionality. AOP forms a basis for aspect-oriented software development.

AOP includes programming methods and tools that support the modularization of concerns at the level of the source code, while “aspect-oriented software development” refers to a whole engineering discipline.

Aspect-oriented programming entails breaking down program logic into distinct parts (so-called concerns, cohesive areas of functionality). Nearly all programming paradigms support some level of grouping and encapsulation of concerns into separate, independent entities by providing abstractions (e.g., functions, procedures, modules, classes, methods) that can be used for implementing, abstracting and composing these concerns. Some concerns “cut across” multiple abstractions in a program, and defy these forms of implementation. These concerns are called cross-cutting concerns.

Logging exemplifies a crosscutting concern because a logging strategy necessarily affects every logged part of the system. Logging thereby crosscuts all logged classes and methods.

All AOP implementations have some crosscutting expressions that encapsulate each concern in one place. The difference between implementations lies in the power, safety, and usability of the constructs provided. For example, interceptors that specify the methods to intercept express a limited form of crosscutting, without much support for type-safety or debugging. AspectJ has a number of such expressions and encapsulates them in a special class, an aspect. For example, an aspect can alter the behavior of the base code (the non-aspect part of a program) by applying advice (additional behavior) at various join points (points in a program) specified in a quantification or query called a pointcut (that detects whether a given join point matches). An aspect can also make binary-compatible structural changes to other classes, like adding members or parents.

void transfer(Account fromAcc, Account toAcc, int amount, User user,
    Logger logger) throws Exception {
  logger.info("Transferring money…");
 
  if (!isUserAuthorised(user, fromAcc)) {
    logger.info("User has no permission.");
    throw new UnauthorisedUserException();
  }
 
  if (fromAcc.getBalance() < amount) {
    logger.info("Insufficient funds.");
    throw new InsufficientFundsException();
  }
 
  fromAcc.withdraw(amount);
  toAcc.deposit(amount);
 
  database.commitChanges();  // Atomic operation.
 
  logger.info("Transaction successful.");
}

Spring Modules

Posted on May 21, 2015June 25, 2015 by coder

Java spring modules list

Spring Core Container: This is the base module of Spring and provides spring containers (BeanFactory and ApplicationContext).^[6]
Aspect-oriented programming: enables implementing cross-cutting concerns.
Authentication and authorization: configurable security processes that support a range of standards, protocols, tools and practices via the Spring Security sub-project (formerly Acegi Security System for Spring).
Convention over configuration: a rapid application development solution for Spring-based enterprise applications is offered in the Spring Roo module
Data access: working with relational database management systems on the Java platform using JDBC and object-relational mapping tools and with NoSQL databases
Inversion of control container: configuration of application components and lifecycle management of Java objects, done mainly via dependency injection
Messaging: configurative registration of message listener objects for transparent message-consumption from message queues via JMS, improvement of message sending over standard JMS APIs
Model–view–controller: an HTTP- and servlet-based framework providing hooks for extension and customization for web applications and RESTful Web services.
Remote access framework: configurative RPC-style marshalling of Java objects over networks supporting RMI, CORBA and HTTP-based protocols including Web services (SOAP)
Transaction management: unifies several transaction management APIs and coordinates transactions for Java objects
Remote management: configurative exposure and management of Java objects for local or remote configuration via JMX
Testing: support classes for writing unit tests and integration tests

Example Opensource Projects for Spring,.

Posted on May 21, 2015June 4, 2015 by coder

Here is the list of projects,

Shopizer

Powerstone

Tudu Lists

Alfresco Content Management

SpringSide

Plazma

agileexpress

Zksample2

Spring Rich Client

Broadleaf Commerce

OpenERP

HISPACTA

Luigi Open Search Engine

JOSSO

HSE

Java Small Business Platform

jrecruiter

Windows command line, BAT file Compile java

Posted on April 27, 2015June 4, 2015 by coder

1- Very important.

set PATH="C:\Program Files\Java\jdk1.5.0_14\bin";%PATH%

set JAVA_HOME="C:\Program Files\Java\jdk1.5.0_14"
set PATH=%JAVA_HOME%\bin;%PATH%

set PATH="C:\Program Files\Java\jdk1.5.0_14\bin";%PATH%

set JAVA_HOME="C:\Program Files\Java\jdk1.5.0_14"

set PATH=%JAVA_HOME%\bin;%PATH%

rem Display environment variables for verification
echo Verify current build environment settings:
echo CLASSPATH: %CLASSPATH%
echo JAVA_HOME: %JAVA_HOME%
echo ICS211_HOME: %ICS211_HOME%
echo TEXTPAD_HOME: %TEXTPAD_HOME%
echo .
echo PATH: %PATH%
echo .

rem GoTo ICS211_HOME directory
d:
cd %ICS211_HOME%

rem Display environment variables for verification

echo Verify current build environment settings:

echo CLASSPATH: %CLASSPATH%

echo JAVA_HOME: %JAVA_HOME%

echo ICS211_HOME: %ICS211_HOME%

echo TEXTPAD_HOME: %TEXTPAD_HOME%

echo .

echo PATH: %PATH%

echo .

rem GoTo ICS211_HOME directory

cd %ICS211_HOME%

To create a similar batch file, you should verify the full paths to any directories that you want to

add to your system PATH variable. Then you can make any necessary changes to this
example code, and save it as a batch file on your system.
You can download a copy of my batch file using this URL:

kutay.bat

// JAVA Compiler :
Console> javac JavaFileName.java

1 2	// JAVA Compiler : Console> javac JavaFileName.java

How to Run,

Console> java JavaFileName

1	Console> java JavaFileName

what is Model in MVC ?

Posted on March 23, 2015May 29, 2015 by coder

* A model could be a single object  or Arrays of objects or some structure of objects. Connection Data...

* There should be a one-to-one correspondence between the model and its parts on the one hand, and the represented world as perceived by the owner of the model on the other hand.

* For simple models using a table gateway/active record implementation may work. 

* Some Models isolates the database from the rest of your application.

* You controller should process the request and pass whatever relevant data is needed to the model.

* The model (or the data mapper) then uses the connection. 

* Model uses bootstraps or posted datas

* A model could be a single object or Arrays of objects or some structure of objects. Connection Data...

* There should be a one-to-one correspondence between the model and its parts on the one hand, and the represented world as perceived by the owner of the model on the other hand.

* For simple models using a table gateway/active record implementation may work.

* Some Models isolates the database from the rest of your application.

* You controller should process the request and pass whatever relevant data is needed to the model.

* The model (or the data mapper) then uses the connection.

* Model uses bootstraps or posted datas

MVC is

Data (Model)
An interface to view and modify the data (View)
Operations that can be performed on the data (Controller)

M + V = C>> Controller is preparing Model then creating View.

In the Center there is a Controller

For Simple > Model = ‘ DATAS’

* The model is the data, and does nothing else.

Models (All of models in project ) does NOT depend on the controller or the view.

Controller Calling Model then pushing it to View. Controller is handling. But for the preparing the datas, controller does not effect how the model creating data sets, structs, objects.

Controller says model to that: Prepare user_table[array] ,

After pushing this object to View, View is using this table,

what is Controller ?

Such as button clicks. The controller depends on the view and the model.

Events.

The controller and the view are the same object. WHY > You can return a string as a page return “”

  public string index2() {
            return "Index2 Return"; 
}

public string index2() {

return "Index2 Return";

}

What is the Advantage of model ?

Unnecessary complexity is the devil of software development.

Time loss for companies. . Complexity leads to software that is buggy, and expensive to maintain.

The easiest way to make code overly complex is to put dependencies everywhere.

* You can use model, Directly Copy paste inside of another Project. You can Call the Model from different Views, or Controllers.
>> Conversely, removing unnecessary dependencies makes delightful code that is less buggy and easier to maintain because it is reusable without modification.

* The primary advantage of the MVC is that makes model classes reusable without modification.

Page 14 of 815

« 1 … 12 13 14 15 16 … 815 »