27 May

Web 3.0 : My Fantasy and What is it?

Today I was reading about the web 3.0 and I was glad with my visualization of what could web 3.0 mean to me. I visualize myself as :

  • I am tired of my rut life I want to go some place very nice that can surely make me feel better; I share my mood information with the web and the quick option are presented. It may be a small holiday destination or a spiritual class nearby; it may be something far; web shows me the available option and the best option to book it and reach there;
  • I have a craving for makki ki roti and saag; web searches the closest Indian restaurants serving it; with ratings and seat availability; I choose the best option; web informs the restaurant about me coming, my time to the restaurant; I reach there my order is ready and served to me;
  • I want to see a movie that had has Aamir Khan and is a comedy; web searches the closest/fastest options available;
  • I have 100$ and I want to go out with my family, watch a movie, eat an Italian food, eat a sundae and while coming back I stop at a wharf; web searches for the options, combines them and presents me the package options.
  • and many more weird dreams ……………..

This will be awesome! I know this is a dream and it will come true :o

What is Web 3.0? From the search links that I would like to share

FROM PCMAG

An Idiot’s Guide to Web 3.0

What will Web 3.0 look like? Who knows? But here are a few possibilities.

The Semantic Web

A Web where machines can read sites as easily as humans read them (almost). You ask your machine to check your schedule against the schedules of all the dentists and doctors within a 10-mile radius-and it obeys.

The 3D Web

A Web you can walk through. Without leaving your desk, you can go house hunting across town or take a tour of Europe. Or you can walk through a Second Life-style virtual world, surfing for data and interacting with others in 3D.

The Media-Centric Web

A Web where you can find media using other media-not just keywords. You supply, say, a photo of your favorite painting and your search engines turn up hundreds of similar paintings.

The Pervasive Web

A Web that’s everywhere. On your PC. On your cell phone. On your clothes and jewelry. Spread throughout your home and office. Even your bedroom windows are online, checking the weather, so they know when to open and close. &151

FROM WIKIPEDIA

I have a dream for the Web [in which computers] become capable of analyzing all the data on the Web

24 May

SCRUM Series

In last few days I have compiled some information on SCRUM in separate articles. Here is the consolidation of all the links:

  1. Scrum: An Introduction to this simple-powerful agile methodology
  2. Scrum: Characteristics and what is sprint?
  3. SCRUM: What are the different Roles?
  4. SCRUM: All the different Meetings
  5. SCRUM: Artifacts
  6. SCRUM: Scalability by SCRUM OF SCRUMS
  7. SCRUM:Some facts and resources

Reblog this post [with Zemanta]

21 May

Google TV: What does it means to a technologist and an enterpreneur?

HANNOVER, GERMANY - MARCH 02:  The camera of a...
Image by Getty Images via @daylife

Since yesterday I have searched lot of times and read many blogs to find out what does the Google TV means for a technical person like me. How can I use this technology or how can I think of using it. I want to understand the opportunities that lie in this breakthrough Google TV that can help me and you. Here is some information that may help you as it helped me:

Designing websites for Google TV

Table of Contents

  • Designing for TV: A Primer
  • Simplicity above all
  • Navigation is critical
  • A new kind of screen
  • Even TV needs text
  • Sound matters
  • Flash on Google TV

Source: Google TV

I would really appreciate your opinion on how to do you think that Google TV can be utilized from a perspective of a technologist or an entrepreneur.

Reblog this post [with Zemanta]
20 May

Google TV: TV meets web and web meets TV

A new revolution has arrived to a sector that is still not captured by the latest in IT and telecom. Lots of attempts have been made but none has made a huge impact. But it seems this time the story is different as couples of companies are getting together with Google to tear it apart. The sector is none other than what is watched 5 hours on average per day by every American and more than 4 billion people watch it across the world, THE TV.

So that got us thinking…what if we helped people experience the best of TV and the best of the web in one seamless experience? Imagine turning on the TV and getting all the channels and shows you normally watch and all of the websites you browse all day

20 May

SCRUM: Scalability by SCRUM OF SCRUMS

Scrum has been successfully used for projects with 500+ team members lots of time. As SCRUM can only last for 15 minutes and some other similar rules hence in order to scale the SCRUM for bigger team we can use SCRUM OF SCRUMS. Based on the type of work the scrum team is constituted for every 7 to 10 team members having a Scrum master and the Product Owner. After the first lever team SCRUMS we have SCRUM of SCRUMS and there could also be more level of SCRUM OF SCRUMS.

18 May

Software Development Methodologies

As these days I am writing about Scrum which is one of the agile methodologies, I though it could be nice if I can also list the other popular software development methodologies.

Three software development patterns mashed tog...
Image via Wikipedia

I have listed all these and also linked them to wiki as it has one of the very good definitions and details about every agile methodology.

Once I am done with the Scrum series I will touch the other ones. Hope this helps!

  1. Agile
  2. Cleanroom
  3. Iterative
  4. RAD
  5. RUP
  6. Spiral
  7. Waterfall
  8. Lean
  9. V-Model
  10. TDD
Reblog this post [with Zemanta]
17 May

SCRUM:Some facts and resources

Other facts about Scrum

  • The scrum methodology originated in 1993 at Easel Corp by Jeff Sutherland
  • Ken Schwaber presented Scrum at OOPSLA 96 with Sutherland
  • Ken Schwaber and Mike Cohn Co-founded Scrum Alliance in 2002
  • Used by all major companies like Microsoft, Yahoo, IBM, Siemens, John Deere, Time Warner, Turner Broadcasting, BBC and many more..
  • Used for software projects, life critical system, mobile phones, websites, Satellite controlled soft wares, support projects
16 May

Messages: WebSphere Application Server, Version 5.1.x

Here are some of the common messages that you may get while working with Websphere Application Server 5.1.x. I found this list at IBM publib:

WSVR0001I: Server {0} open for e-business
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0002I: Server {0} open for e-business, problems occurred during startup
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0003E: Server {0} failed to start {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0004E: The server name, {0}, is not a valid name.
Explanation: There is a mismatch between the name of the server speicified and the server name in the corresponding server.xml.
User Response: Make sure that the server name specified matches both the directory name for the server and the server name in the corresponding server.xml.

WSVR0007E: Could not find the {0} object in {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0008E: Error encountered reading {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0009E: Error occurred during startup {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0016W: Classpath entry, {0}, in Resource, {1}, located at {2} has an invalid variable
Explanation: A variable used in the classpath definition of the resource is not defined or does not contain a valid value.
User Response: Define the missing variable or provide a valid value for the missing variable.

WSVR0017E: Error encountered binding the J2EE resource, {0}, as {1} from {2} {3}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0018W: Unable to create CustomService, {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0019W: CustomService, {0}, failed to initialize. {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0020W: CustomService, {0}, failed to shutdown. {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0021W: Native path entry, {0}, in Resource, {1}, located at {2} has an invalid variable
Explanation: A variable used in the native path definition of the resource is not defined or does not contain a valid value.
User Response: Define the missing variable or provide a valid value for the missing variable.

WSVR0022W: The value, {0}, with Resource ID, {1}, located at {2} has an invalid variable
Explanation: A variable used in the resource is not defined or does not contain a valid value.
User Response: Define the missing variable or provide a valid value for the missing variable.

WSVR0024I: Server {0} stopped
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0025I: Creating temporary product license
Explanation: None
User Response: None

WSVR0026I: Error occurred while validating product license
Explanation: None
User Response: None

WSVR0027I: The product will expire in {0} days.
Explanation: None
User Response: None

WSVR0028I: The product has expired. Please re-install or purchase the product.
Explanation: None
User Response: None

WSVR0030E: ORB not initialized
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0031E: Unable to load container {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0032E: Object Adapter created already
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0033E: Unable to load security collaborator, {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0034W: Invalid passivation directory specified: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0035E: Failure to initialized the container: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0036E: Failure to obtain initial naming context: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0037I: Starting EJB jar: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0038I: No JNDI name found for {0}, binding home name as {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0039E: Unable to start EJB jar, {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0040E: addEjbModule failed for {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0041I: Stopping EJB jar: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0042E: Unable to stop {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0043E: Unbind failed for {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0044E: Unable to stop EJB jar, {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0045E: Unable to create sub-context {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0046E: Unable to bind, {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0047E: Batch naming operation failed : {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0048W: Binding {0} failed, no JNDI name found
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0049I: Binding {0} as {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0051W: Attempted to register a URL Provider, {0}, with a null protocol
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0052W: Attempted to unregister URLProvider with null protocol
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0055W: Unexpected objectToKey method callback for object {0}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0056W: Tie class of {0} can not be found.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0062E: Unable to start EJB, {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0064W: Minimum threads for pool {0} was less than 0; changing from {1} to 0
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0065W: Maximum threads for pool {0} was less than 1; changing from {1} to 1
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0066W: Maximum threads for pool {0} was less than the minimum; changing from {1} to {2}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0100W: An error occurred initializing, {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0101W: An error occurred starting, {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0102E: An error occurred stopping, {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0103E: An error occurred destroying, {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0104E: No type or class defined in {0} at line {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0105E: Both type, {0}, or class, {1}, are defined in {2} at line {3}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0106E: Invalid startup value {0} at line {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0107W: Duplicate component, {0}, in file {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0120E: An error occurred processing {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0150E: Missing entry for {0} in {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0200I: Starting application: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0201E: Application, {0}, failed to initialize {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0202E: Application, {0}, failed to start {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0205E: Module, {0}, of application, {1}, failed to initialize
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0206E: Module, {0}, of application, {1}, failed to start
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0207I: Preparing to start EJB jar: {0}
Explanation: Preparation includes reading deployment descriptors and loading classes.
User Response: No action is required for this status message.

WSVR0208E: Unable to prepare EJB jar: {0} {1}
Explanation: An EJB jar can fail preparation due to incorrect deployment descriptors.
User Response: Look for messages that appear between this message and the preceeding WSVR0207I message. If you find one, it may be related to the cause of this message. If none is found, use the exception that appears as part of this message as a possible cause of this message.

WSVR0209E: Unable to prepare EJB jar {0}, enterprise bean {1} {2}
Explanation: An EJB can fail preparation if the container required classes have not been generated for the EJB.
User Response: Verify the EJB jar that contains the failed EJB {1} has been deployed.

WSVR0210W: No modules defined for application, {0}, on server, {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0211W: Duplicate library, {0}, defined in {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0212W: Library, {0}, defined in {1} does not exist
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0213W: Classpath entry, {0}, in library, {1}, located at {2} has an invalid variable
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0214W: Application, {0}, already installed
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0215W: Starting application, {0}, failed. The application is not installed.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0216W: Stopping application, {0}, failed. The application is not started.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0217I: Stopping application: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0218W: No modules defined for application, {0}, on server, {1}, in cluster, {2}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0219I: Application, {0}, is disabled
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0220I: Application stopped: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0221I: Application started: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0230E: Invalid uri format encountered while processing cross document link: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0231E: Unrecognized resource type encountered during Application startup: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0232E: Unable to resolve cross document link identified by the uri: {0}, and referenced by document {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0300I: Problems found in {0}
Explanation: Parse errors or warnings were found.
User Response: Fix the errors and warnings.

WSVR0301W: Invalid value type, {0}, expecting {1} at line {2}
Explanation: The type specified in the XML file was not expected.
User Response: Fix the XML file such that the appropriate type is used.

WSVR0302W: Invalid value, {0}, at line {1}
Explanation: The value specified was not valid.
User Response: Change the value to valid value.

WSVR0303W: Invalid element tagname, {0}, at line {1}
Explanation: There is no implementation class for the tag.
User Response: Contact IBM Support

WSVR0304E: Unsupported encoding, {0}
Explanation: The file encoding is not supported
User Response: Using an encoding that is supported by Java.

WSVR0305W: Invalid attribute, {0}, at line {1}
Explanation: The attribute is not valid.
User Response: Remove the attribute.

WSVR0306E: Unsupported XMI version
Explanation: The XMI version is not supported
User Response: Update the file to XMI 2.0

WSVR0307W: Invalid namespace, {0}, at line {1}
Explanation: The namespace is not valid.
User Response: Contact IBM Support

WSVR0308W: Unknown package, {0}, at line {1}
Explanation: The package is not valid.
User Response: Contact IBM Support

WSVR0309E: No packages have been registered
Explanation: No packages are registered
User Response: Contact IBM Support

WSVR0310W: Unable to resolve reference for, {0}, at line {1}
Explanation: The reference could not be resolved.
User Response: Contact IBM Support

WSVR0311W: Unknown exception {0}
Explanation: An unexpected problem occurred.
User Response: Contact IBM Support

WSVR0312E: Unknown exception {0}
Explanation: An unexpected problem occurred.
User Response: Contact IBM Support

WSVR0313E: The Message Driven Bean listener service could not be started, message driven beans will not be able to receive messages.
Explanation: The message listener service may be disabled.
User Response: Verify the message listener service is enabled.

WSVR0313E: The Message Driven Bean listener service could not be started, message driven beans will not be able to receive messages.
Explanation: The message listener service may be disabled.
User Response: Verify the message listener service is enabled.

WSVR0314E: Failed to parse {0} at line {1}, column {2} {3}
Explanation: The XML file does not have a valid XML structure
User Response: Correct the XML file.

WSVR0400W: Unable to register the {0} MBean {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0401W: Unable to deregister the {0} MBean {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0402W: Invalid MBean name {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0500E: Unable to parse {0} at line {1}, column {3} {4}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0501E: Error creating component {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0600W: No thread context
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0601W: javaURLContext object missing for J2EEName {0}, caught exception {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0602W: Attempt to access javaNameSpace from a ComponentMetaData that does not support a javaNameSpace.
Explanation: Only Web-Components and EJB-Components support access to the javaNameSpace.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0603E: ComponentMetaDataAccessor beginContext method received a NULL ComponentMetaData.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0604I: Attempt to register EJBContainer MBean: caught exception {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0605W: Thread “{0}” ({1}) has been active for {2} milliseconds and may be hung. There are {3} threads in total in the server that may be hung.
Explanation: A thread has been active for an extended period. This may indicate that the thread is hung, including deadlock and infinite loop situations.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0606W: Thread “{0}” ({1}) was previously reported to be hung but has completed. It was active for approximately {2} milliseconds. There are {3} threads in total in the server that still may be hung.
Explanation: A thread that was previously reported as hung has now completed.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0607W: Too many thread hangs have been falsely reported. The hang threshold is now being set to {0} seconds.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0608I: WebSphere process class preloading is enabled using {0}.
Explanation: This is an informational message.
User Response: This is an informational message.

WSVR0609I: WebSphere process class preloading is disabled.
Explanation: This is an informational message.
User Response: This is an informational message.

WSVR0610I: WebSphere process class preloading is generating a preload file.
Explanation: WebSphere process class preloading is generating a preload file. The process startup time may take longer than normal. This will happen the first time a process is started or if a change is detected that requires the file to be regenerated.
User Response: This is an informational message.

WSVR0611E: WebSphere process class preloading could not find or create a preload file.
Explanation: The WebSphere class preloader could not find an existing preload file or was unable to create a new preload file. Class preloading is disabled for this process.
User Response: Verify that the WebSphere process has write authority to the was.install.root/logs/preload or the user.install.root/logs/preload directories and try again.

WSVR0612E: WebSphere process class preloading could not find or create {0}.
Explanation: The WebSphere class preloader could not find or create the specified preload file. Class preloading is disabled for this process.
User Response: Verify that the WebSphere process has write authority to create the specified file and try again.

WSVR0613E: WebSphere process class preloading could not write to the preload file.
Explanation: The WebSphere class preloader could not write to the preload file.
User Response: Verify that the WebSphere process has write authority to the preload file and try again.

WSVR0621E: CMP Bean “{0}” is configured to use a CMP Connection Factory JNDI name of “{1}” resource. This resource does not exist.
Explanation: This error indicates that a CMP which is configured to use a Connection Factory resource is not available. The CMP bean will not function because the resource is not defined by the administrator.
User Response: Create this Connection Factory by ensuring this data source is selected for CMP use in the administrative console.

Reblog this post [with Zemanta]
16 May

HTC EVO: A lethal blow to Nexus One and a tough competition to iPhone4

As per my opinion HTC EVO is better than Google‘s Nexus One. The following are the key features:

HTC EVO Main features:

  • 4.3-inch screen
  • Android 2.1
  • HTC Sense
  • 1 GHz Snapdragon processor
  • 1500 mAh battery
  • Wi-Fi capable
  • 3G/4G mobile hotspot capability
  • Dual cameras (first time a second front camera for social )
  • 8 megapixel and 1.3 megapixel front facing camera
  • networking and chatting
  • GPS Navigation
  • Stereo Bluetooth wireless technology
  • microSD Card Slot (upto 32 GB)
  • 3.5 mm headset jack
  • Micro USB
  • Proximity and motion sensors
  • Digital Compass
  • Unique kickstand for easy media viewing
  • Mobile HDTV experience
  • Output pictures, slides and video in HDMI
  • Social networking with Facebook, Twitter, Flickr