Why a people with the name william called Bill?

Some of Best Answers which i got it from net :

1)
Because the ancient Greek philosophers' symbol for the letter "W' was some sort of alteration of the letter "B". So, instead of Will for short, people started to write Bill. And now in today's modern age that is the most common name for somebody named William


2)
William is sometimes shortened to Will too. It is because it was shortened to Will originally, that it became 'Bill':

Will(iam) > Bill was, in fact, part of a great 13th-14th century trend of swapping some other letter for the original first letter of a name as rhyming slang. There were hundreds at the time but most have now died out. Other names resulting from this process include: Polly from Molly, Bob from Rob (from Robert), Hick and Dick (from Richard), Hodge from Roger, Molly from Mary, Sally or Sadie from Sarah, Dolly from Dorothy, Harry from Harold, Betty or Bess from Beth (from Elizabeth).

Many of the original names from which these nicknames were formed were Norman French names. William is the anglisied version of Guillumme, an old French name. It appears that the changes were part of the English adapting them to their own language. Apparently one impetus (there were others) in the trend for letter swapping at that particular time was a dislike amongst the native English for the harsh Norman French "r".
_________________

appMIGRATE - a next generation data migration tool for Oracle E-Business Suite R12/11i

appMIGRATE is a powerful tool to extract, transform, validate, cleanse, correct and migrate data from an older version of Oracle E-Business Suite or any legacy system into newer version of Oracle EBS. Upon finalization of requirements the migration of data from legacy/older Oracle EBS systems to newer Oracle 11i/R12 can be accomplished in 2-4 weeks.

Some of the key features includes:
1. Data Extraction from legacy or Oracle EBS Older systems (prior to R12)
2. Pre-built extraction adapters for Oracle 11i data
3. Project / Task Groups - Tasks - capable of handling parallel and serial processing of
data migration
4. Data Consolidation - for Big bang or roll-out approaches
5. Data Cleansing
6. Data Corrections
7. Data Transformation - before validation or after validations
8. Data loads in the background application server
9. Duplicate data filtering
10. Easy mapping tool
11. Seamless integration with appLOAD and appEXTRACT tools.


Projects and Tasks
appMIGRATE provides a flexible framework to create multiple projects and each project can have multiple tasks. Each task can handle appropriate extractions and transformations, validation, cleansing, automated data correction and loading.



Extraction
appMIGRATE provides simple and powerful wizard driven extraction tool. Extraction can be done from tables, views and appEXTRACT adapters. Links between data tables can be also performed.



Mapping
appMIGRATE provides drag and drop mapping tool to map the extracted data into appLOAD.



Scheduler
appMIGRATE can schedule to execute the project and tasks in accordance with a specific timeline. Processes run in parallel and/or in sequence. All processes are executed in the background without any intervention. The completion of processes triggers email notifications to the process owner. The email notifications show detailed checksum information, extraction, loading, error, validation, and log information. This information is stored in the application server for any future auditing purpose.



Transformation
The extracted data can be transformed by a simple condition based action logic. It supports grouping of conditions. Transformation can be applied based on specific field data or another field data of the same record.



Validation
appMIGRATE has pre-seeded validations on all loading templates. The business user/developer can add additional validations as needed. The records which fail validation remain unprocessed. We provide an automated data correction feature (Cleansing Engine). This acts on unprocessed data by applying threshold factors.



Loading
appMIGRATE loads data using appLOAD. Therefore all its features are inherited.



Software as a Service
appMIGRATE is also available to our customers in SaaS managed services and SaaS subscription models. In the SaaS managed services Chain-Sys will perform the migration activity as a service. In the Saas subscription model the customers pay yearly subscription and use the product hosted on our datacenter in Lansing,MI.

N900, BBC iPlayer setup

Instructions
1. Point your N900′s browser to http://www.bbc.co.uk/iplayer/bigscreen/ or http://www.bbc.co.uk/iplayer/

See it’s much nicer than bbc iPlayer direct. It’s very finger poke friendly. It’s like it was made for the N900.

Is Eclipse 3.3.1.1 Better and Jdeveloper 10g

In my work environment there has always been a debate of whether we should be using Eclipse or Jdeveloper. I have always been a believer that JDeveloper is the best solution for our organization since we are a Oracle shop, so we should use the tools that Oracle has provided for us. This argument is always agreed with by developers using Eclipse, but argue that Eclipse is still much better. Some advantages I have always seen, as related to using the IDE in our organization are:


It is easy for Developer to setup and start working with
Works nicely with the other Oracle products (Well most of the time)
It is what I am familiar with

JDeveloper has been a great too for me, but when you start developing projects using different Application Servers like Tomcat, Jboss, ect. JDeveloper becomes very limited. JDeveloper’s main disadvantages are:


Very resource intensive.
Runs slow on most machines.
Can only run apps, through the ide, on OC4J.
EJB tools seem to only work well to run on Oracle App Servers.
Does not lend itself well when importing projects created outside of JDeveloper

I have recently been working on some new projects, where Eclipse is suggested for setting up the development environment. I figured that this would be a great time to install and start using Eclipse 3.3.1.1. I will say that this new version of Eclipse and plugins provided are very impressive.

The disadvantages, of JDeveloper, become very apparent when you start using Eclipse. Eclipse is a great development IDE. Not only is it well written, the IDE allows for developers to generate custom plugins to support many different development environments. Some of Eclipses advantages are:


Runs very fast
Is developed using the SWT toolkit.
Is designed to be easily expandable with plugins.
Had a verity of tools availiable.
Ability to handle many different application servers internally.
Provides everything JDeveloper does and address all of its limitations.

The disadvantages are:


Eclipse can be difficult for some developers to start using.
Setup can be frustrating sometimes for plugins
You have to install a lot of additions/plugins to get started working efficiently.

There seems to be more disadvantages to using JDeveloper than Eclipse for a variety of development projects. Eclipse also has some great plugins like the JBoss Tools which provide you with a some great visual tools and awsome management of the JBoss app server thorough the IDE.

I now feel that JDeveloper is only good when you are working with all Oracle products, but Eclipse is definately the better IDE of the two. Oracle should take a note from JBoss and get rid of there IDE and start developing nice plugins for the Eclipse IDE. I think that this would benefit the community in a much better way. I can’t believe what I am saying, but I think I have changed sides now, and I am a Eclipse fan. I can’t wait to migrate some of my projects into the IDE and start working inside of it.

Source :