I am coming back here after many years... :D
Will post my performance engineering and testing experience. 

Getting rid from error "setProperty must be overridden by all subclasses of SOAPMessage" in JBoss 4.2.3

I am using JBoss 4.2.3 with JDK 1.6.0_11 and had the following error while running client to call webservice as following:

ERROR [SOAPFaultHelperJAXWS] SOAP request exception
java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
at javax.xml.soap.SOAPMessage.setProperty(Unknown Source)
at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:83)
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:217)



Solution: https://jira.jboss.org/jira/browse/JBWS-1439

Simple eclipse problem screwed me up..

I imported an ear file and since this file did not have java source file so i copied all source file in src folder generated by eclipse.

what is next...I needed to modify in source code and deploye on JBoss server.
So, i tried to deploy it on JBoss server but message was showing..."Publish failed using Ant publisher".

I tried to fix this issue by changing so many configuration but i couldn't :(
even i tried to googling this problem but i did not find any luck.
so i tried to copy the message from details and when i copied and paste in text editor there was more messge as following.

Publish failed using Ant publisher
unable to assemble module
duplicate entry: org/jboss/seam/example/registration/test/RegisterTest.class

ohhh...this was silly problem... later I realised that there was and imported classes that should be deleted so I deleted all modified class from ImportedClasses and this got fixed :-)

link databse 2009

Index: http://20bits.com/articles/interview-questions-database-indexes/

Choosing among JCA, JMS, and Web services for EAI

http://www.ibm.com/developerworks/webservices/library/ws-jcajms.html

Java J2ee Q & A Link

Java/J2EE Career Centre

XML DTDs vs schemas

XML DTDs vs schemas
Takeaway: Developers familiar with XML know that DTDs and schemas serve a similar purpose, but the debate over which one to use shows no signs of settling down. Find out what XML newsletter columnist Brian Schaffner thinks.

Every technology has its share of controversial topics, and XML is not immune to debate—especially when it comes to document type definitions (DTDs) and schemas. Both of these XML technologies perform similar functions, but the argument over which you should use rages on. Let’s look at some of the pros and cons of each.

The role of DTDs and schemas
Essentially, DTDs and schemas fulfill the same purpose: helping XML developers describe the structure and data within their XML documents. Without DTDs and schemas, it would be difficult to determine whether an XML document is valid in terms of it meeting certain structural and data type criteria.

The DTD or schema provides the XML parser with a description of what a particular type of XML document should look like. For example, it will say whether a <City> element can be contained within an <Address> element. It will also say how many <City> elements the parser should expect to find in the <Address> element, and it can describe the type of data within the element.

The DTD argument
DTDs, which have been around longer than XML, describe the type of document you're dealing with. When XML arrived as a specification, certain concepts were considered to help protect against mistakes within the document. One concept, validation, is the process of comparing an XML document to its DTD.

Soundex

from http://en.wikipedia.org/wiki/Soundex

Soundex is a phonetic algorithm for indexing names by sound, as pronounced in English. The goal is for names with the same pronunciation to be encoded to the same representation so that they can be matched despite minor differences in spelling[1]. Soundex is the most widely known of all phonetic algorithms and is often used (incorrectly) as a synonym for "phonetic algorithm". Improvements to Soundex are the basis for many modern phonetic algorithms

Implementation

src/org/apache/commons/codec/language/Soundex.java&q=soundex%20lang:java
from http://www.google.com/codesearch/p?hl=en#CskViEIa27Y/src/org/apache/commons/codec/language/Soundex.java&q=soundex%20lang:java

JBoss memory setting to get rid of memory problem

-Xms128m -Xmx512m -XX:MaxPermSize=256m

JSF Include And Templating

Inside Facelets - Part 3: Templating and Re-Use


This is the third part in a series of articles about Facelets, an alternative view technology for building JSF applications. Facelets is a powerful templating system that enables you to define JSF views using HTML-style templates, reduces the amount of code necessary to integrate components into the view, and doesn't require a web container. This article explains how you can use Facelets for templating inside of your JavaServer Faces projects.


--------------------------------------------------------------------------------

For any view technology to succeed, it must have some aspect of templating and re-use that's both easy to use and understand. Facelets technology solves this issue in a way that is ideal for JavaServer Faces while keeping that sense of familiarity to traditional, tag-based user interfaces. This article covers the possible ways to increase re-use and simplify maintenance on your JavaServer Faces project.

When people first start creating web pages, they often find themselves repeating content across multiple files. As a developer, this can be frustrating when your object-oriented tendencies kick in. Wouldn't it be nice to simply maintain that content in one spot?

jboss seam learning

http://docs.jboss.org/seam/1.2.1.GA/reference/en/html/

layered masking of screen using css and iframe

this works for mozilla---
<div id="searchPanelCursorDiv" style="background-color: #D0D0D0; border: 0 none; height: 100%; left: 0; margin: 0; opacity: 0.5; padding: 0; position: fixed; top: 0; width: 100%; z-index: -200;"></div>

Steps to troubleshoot SQL connectivity issues

http://blogs.msdn.com/sql_protocols/archive/2008/04/30/steps-to-troubleshoot-connectivity-issues.aspx

How to negotiate, and win!

Life is one big negotiation--be it with your boss, spouse, customers or the used-car salesman.see
http://in.rediff.com/money/2008/nov/26how-to-negotiate-and-win.htm

JavaFX technology(Rich Internet Application)

The JavaFX technology enables you to develop rich internet applications (RIA) using the JavaFX programming language. The best way to start developing JavaFX applications is to use an integrated development environment (IDE). The NetBeans IDE 6.1 includes JavaFX support that enables you to develop, debug, and deploy JavaFX applications. It is a full featured development environment that comes bundled with the JavaFX Software Development Kit (SDK) and best practice samples to assist your software development project.

Pitched into the Rich Internet Application space as a competitor to Adobe’s Flex and Microsoft’s Silverlight, Sun’s JavaFX is one part of Sun’s strategy for addressing these issues for Java developers. JavaFX aims provide a new foundation platform for building Rich Internet Applications across desktop, internet and mobile devices. It also represents a significant shift in the way Sun engages with the Java product market, seeing them building up a complete solution rather than focusing solely on the underlying technology. The current technology preview comprises two major components: Project Nile, which focuses on designer/developer workflow, and JavaFX Script, a new declarative language for writing Java GUI applications.

Whilst both Flex and Silverlight use XML as their declarative language (MXML and XAML respectively) Sun have chosen to develop a new scripting language, JavaFX Script, for the task. Sun Staff Engineer Joshua Marinacci told us that Sun have no plans to add an XML dialect at this point:

"We have found a lot of people really hate using XML and wanted a more compact declarative syntax optimized for graphical interfaces. We think developers familiar with JavaScript will find JavaFX Script pretty easy to pick up."
JavaFX Script is a declarative, statically typed, compiled, Domain Specific Language (DSL) for creating user interfaces on top of the Java Standard and Micro Editions, with current Java packages accessible from the JavaFX environment. It targets two distinct user groups:

Java developers who are already familiar with Swing and are looking for a way of building feature rich interfaces in a faster, more productive way.
Web developers who are more familiar with other scripting languages such as JavaScript or ActionScript.
JavaFX Script has strong productivity features including some convenient predicate features for insert and delete operations (insert 10 before x[1]; for example). Other common problems are elegantly solved: binding UI components to a backend database is straightforward, for instance, and the language supports firing an event when the value of a variable changes, through a simplified listener-like mechanism referred to as an event trigger.


See more detail:
http://java.sun.com/javafx/index.jsp
http://java.sun.com/javafx/tutorials/jfx_nb_getting_started/

SOAP

Like http is text based protocol having header and body…in similar way soap is protocol that define data in xml….SOAP defines the XML-based protocol for exchange of information in a distributed environment, specifying the envelope structure, encoding rules, and a convention for representing remote procedure calls and responses. So, SOAP, originally defined as Simple Object Access Protocol, is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks. It relies on Extensible Markup Language (XML) as its message format and usually relies on other Application Layer protocols, most notably Remote Procedure Call (RPC) and HTTP for message negotiation and transmission

JAX-RPC provides a Java API for developers to invoke remote procedure calls, by abstracting and hiding the low-level SOAP semantics associated with RPC from applications.

How to Improve Product Quality

How to Improve Product Quality
Posted March 29, 2007 in Innovation, Management, 4 Comments »

weblink: http://learn.trizle.com/posts/807-how-to-improve-product-quality

Jini

Jini - a lightweight environment for dynamically discovering and using services on a network. The technology is used mostly in reference to allowing “network plug and play” for devices. It allows devices such as printers to dynamically connect to and download drivers from the network and register their services as being available. The goal in developing Jini was to create a dynamically networked environment for devices, services, and applications. In this environment, services and devices could be added to and removed from the network dynamically.

Functional vs. Non-Functional Requirements

Functional vs. Non-Functional Requirements
Functional requirements describe what the system should do
- things that can be captured in use cases
- things that can be analyzed by drawing sequence diagrams, statecharts, etc.
- Functional requirements will probably trace to individual chunks of a program
- Non-functional requirements are global constraints on a software system
- e.g. development costs, operational costs, performance, reliability,
maintainability, portability, robustness etc.
- Often known as the “ilities”
- Usually cannot be implemented in a single module of a program

Functional Requirements
The official definition for a functional requirement specifies what the system should do:

"A requirement specifies a function that a system or component must be able to perform."

Functional requirements specify specific behavior or functions, for example:

"Display the heart rate, blood pressure and temperature of a patient connected to the patient monitor."

Typical functional requirements are:
• Business Rules
• Transaction corrections, adjustments, cancellations
• Administrative functions
• Authentication
• Authorization –functions user is delegated to perform
• Audit Tracking
• External Interfaces
• Certification Requirements
• Reporting Requirements
• Historical Data
• Legal or Regulatory Requirements
Non-Functional Requirements
The official definition for a non-functional requirement specifies how the system should behave:

"A non-functional requirement is a statement of how a system must behave, it is a constraint upon the systems behavior."
Non-functional requirements specify all the remaining requirements not covered by the functional requirements. They specify criteria that judge the operation of a system, rather than specific behaviors, for example:
"Display of the patient's vital signs must respond to a change in the patient's status within 2 seconds."
Typical non-functional requirements are:
• Performance - Response Time, Throughput, Utilization, Static Volumetric
• Scalability
• Capacity
• Availability
• Reliability
• Recoverability
• Maintainability
• Serviceability
• Security
• Regulatory
• Manageability
• Environmental
• Data Integrity
• Usability
• Interoperability
Non-functional requirements specify the system’s ‘quality characteristics’ or ‘quality attributes’. Potentially many different stakeholders have an interest in getting the non-functional requirements right. This is because for many large systems the people buying the system are completely different from those who are going to use it (customers and users).



Functional requirements are typically phrased with subject/predicate
constructions, or noun/verb. "The system prints invoices."
Non-functional requirements may be found in adverbs or modifying
clauses, such as "The system prints invoices *quickly*" or "The system
prints invoices *with confidentiality*".

From a mathematical point of view, a "function" takes an input(s) and
yields an output(s). "Functional" refers to the set of functions the
system it to offer, while "non-functional" refers to the manner in which
such functions are performed.

How to find first and last entry of HashMap

http://forums.sun.com/thread.jspa?threadID=403658&tstart=81825
How come Hashtable / HashMap have search order constant . ?
/**
* The table, resized as necessary. Length MUST Always be a power of two.
*/
transient Entry[] table;
// and here's the method that intrests you
public Object get(Object key) {
Object k = maskNull(key);
int hash = hash(k);
int i = indexFor(hash, table.length);
Entry e = table[i];
while (true) {
if (e == null)
return e;
if (e.hash == hash && eq(k, e.key))
return e.value;
e = e.next;
}
}
so, as you see, if you have one Entry per bucket, then it's as easy as taking from an array, but if you have more that one entries in one bucket, then it has to loop that while for a while.