Nowadays Searching right data withing an organization is becoming very important and Google – The most popular search engine provider, is also providing this within an organization. GSA – Google Search Appliance is a product from Google , which provides fast and relevant search within intranet.
GSA like Google site, would croll all the listed intranet sites, and some known data sources like content management systems, user portals and indexes all the documents for search. It also exposes an Google search interface to end users. One can also customize the front end according to their company needs. GSA can also be configured to pull some real time data using special applications called ‘OneBoxes’ which fetch real time data during the search.
According to google :
Google OneBox for Enterprise brings the power and simplicity of search as a “fast front door” to information into the enterprise network. OneBox Modules provide secure real time access to information on the Google Search Appliance or external data sources. On Google.com, OneBox modules display specially formatted information like movies, weather and airport information. Imagine accessing critical information like your business calendar, your business contacts or even sales reports from an easy to use search interface.
Altogether Google is showing how a simple search could add value within an enterprise also.
In this post we will talk about how to integrate hibernate Search into your existing Spring, JPA and Hibernate application and some of the challenges we faced.
We have a web application using Hibernate (with JPA ) and Spring. This application relies on Spring for transaction, bean initialization / injection etc. EntityManager, transaction are configured in application.xml file. When integrating Hibernate search in such an application one might face problems. In this post I am sharing some problems I faced during integration and the solutions for same.
Entitymanager configuration in my application.xml
Spring configuration:
<bean id=”propertyConfigurer”>
<property name=”location” value=”classpath:myproperties.properties”/>
</bean>
Read more…
Once your dynamic site has gone bigger, data in relational database has grown, there is always a need for searching the contents. SQL queries with like ‘%…%’ are useful. But to do multiple columns / table searching, we’ll need to have big SQL queries with different conditions, ANDed and ORed. Such searching is not realistic and can not be maintained and extended easily.
For Hibernate users, Hibernate search helps searching rows from database. Without writing any complex SQL queries, you can search multiple columns and get related objects from db.
In our site Skill-Guru , you will notice a search box on the right hand side. We have enabled the search on few tables and columns initially. Currently it will search for the tests , description and keywords for the input keyword.
Read more…
In our last post , Getting started with JSF , we had covered JSF1.2. JSF has come a long way from that. JSF 2 has come with very new features, some of them taken from different frameworks / components. Now JSF developers don’t have to look out. JSF2 helps JSF developers to keep their application simple.
There are many articles explaining new features of jsf 2. But here in this blog, I brief you some of the features:
1. The introduction of View scopes, flash scope and custom scope - View scopes,Flash scopes and custom scopes are ‘bigger than request scope but smaller than session scope’. Many times developers are forced to keep objects in session scope just because they want the objects available till end of their front view operation or make them work in the redirection or till end of their front end operation. For example you might have experienced implementing edit/delete/ add operations to datatable, many times its necessary to make the bean session scope to make it working right way. This can be avoided by view scope variables. The custom scope helps objects to be available till end of user operation (user has to decide the scope of bean). This is like flow scope.Flow scopes were offered by frameworks like spring webflow etc .. But for an application already done in JSF, it is easier to shift to JSF2 than webflow.
Read more…
One-to-One mapping can be done in 2 ways:
- Primary key association:
- Foreign key association.
My previous post described about the Primary key one-to-one mapping in Hibernate. This post gives an example of Foreign key one-to-one association in Hibernate. Read more…
In Real world applications it is natural to have tables with composite keys. The row will be identified with combination of key column values of a row.
Consider Following scenario:
A test selling website defines tests and customers.
Read more…
In Hibernate One-to-One mapping can be done in 2 ways:
- Primary key association:
- Foreign key association.
This article describes how a Primary key One-to-one association can be done.
Consider a Customer and address entities. Each customer will have one address. And an address is associated with one customer. To make this relationship work in database customer and address will have same Id(primary key). Mapping this kind of relationship in Hibernate is called primary key One-to-One association. Doing so will help you saving, updating, deleting related entities easy.
Read more…
In the past articles, I’ve discussed OOP(Object Oriented Programming) and Game Programming.Be sure to at have a grasp of the basics before diving to this next article.
The basic prerequisites to develop your first iPhone GameApp are:
1)Objective C
2)the iPhone SDK
3)MAC:XCode
So to develop a game in the iPhone , these prerequisites will force you to work in a MAC, and learn Objective C on top of learning the iPhone SDK. Do not be alarmed. Take one step at a time.If you know OOP already, then you just have to familiarize.
Read more…
