Au cas ou cet article tombe sous les yeux de quelqu’un que je peux intéresser…

Je suis actuellement à la recherche d’un boulot de développeur/Leader Technique/Architecte autour des technologies Java/J2EE. Mon CV en ligne est disponible sur LinkedIn à l’adresse suivante : http://www.linkedin.com/in/chamerling

Actuellement à Toulouse, je vise le secteur de Montpellier… Le SUD, le vrai!

ผมเองมักจะลืมว่า เจ้าเมธอดทั้งสามตัวนี้มันต่างกันตรงใหน เขียนผิดเขียนถูกอยู่นั่นแหละ รำคาญตัวเองก็เลยมาเขียนในบล๊อกเอาไว้กันลืม และเผื่อจะมีผู้สนใจร่วมคอมเม้นต์มาแลกเปลี่ยนความรู้ความคิดเห็นกัน

RequestDispatcher.forward() เป็นการทำงานที่อยู่บนเซิร์บเวอร์ แต่ response.sendRedirect() ทำงานอยู่บนบราวเซอร์. เมื่อมีการเรียกใช้งาน RequestDispatcher.forward(), servlet engine จะำทำการ Transfer control ของ HTTP request ที่ได้รับมาตั้งแต่แรกและยังทำงานอยู่ที่ Servlet หรือ ที่ JSP ยังทำการที่ Servlet อื่น. แต่เมื่อทำการเรียกใช้งาน response.sendRedirect() การส่งภาระให้กับบราวเซอร์คืนกลับไปจัดการเอง เหมือนทำให้ท้องแล้วไม่รับผิดชอบยังใงยังงั้น อ๊อบเจ็คต์ Request Response ก็ให้บราวเซอร์ทำการ Route ไปหา Servlet อื่นหรือหน้า JSP อื่นตัวเก่าก็ไม่เหลืออะไร

ส่วน RequestDispatcher.forward() และ PageContext.forward() จะมีหน้าที่เหมือนๆ กันแต่ PageContext.forward() จะเป็น Method Helper ให้กับทาง RequestDispacher.forward() อีกทีหนึ่งนั่นเอง

java.io.IOException: Unable to loadProperties:java.util.MissingResourceException: Can’t find bundle for base name mailprop, locale en_US
at com.dynamicRouter.Utility.FileMarshal.loadProperties(FileMarshal.java:48)
at com.dynamicRouter.servlet.AshSrv.CreateMail(AshSrv.java:189)
at com.dynamicRouter.servlet.AshSrv.doPost(AshSrv.java:82)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

Mar 27, 2008 1:58:30 AM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet action threw exception
java.lang.IllegalStateException: Cannot forward after response has been committed
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:302)

2008-03-20 17:57:28,546[ERROR] com.dynamicRouter.Utility.dmMail: 230- send:com.sun.mail.smtp.SMTPSendFailedException: 501 <DynamicMethod>: sender address must contain a domain

com.sun.mail.smtp.SMTPSendFailedException: 501 <DynamicMethod>: sender address must contain a domain

at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
at javax.mail.Transport.send0(Transport.java:169)
at javax.mail.Transport.send(Transport.java:98)
at com.dynamicRouter.Utility.dmMail.send(dmMail.java:224)…………………

I am using JDBC to connect to to embedded Derby database.I got Exception
“Naming exception in JNDIDatabase init javax.naming.NameNotFoundException: Name jdbc is not bound in this Context

Solution:

context.xml

Context antiJARLocking=”true”>

<Resource name=”jdbc/myDB” auth=”Container” type=”com.atomikos.jdbc.SimpleDataSourceBean”
factory=”org.apache.naming.factory.BeanFactory”
uniqueResourceName=”jdbc/myDB”
xaDataSourceClassName=”org.apache.derby.jdbc.EmbeddedXADataSource”
exclusiveConnectionMode=”true”
connectionPoolSize=”3″
connectionTimeout=”10″
xaDataSourceProperties=”databaseName=../work/users1;createDatabase=create”/>

<Transaction factory=”com.atomikos.icatch.jta.UserTransactionFactory” />

</Context>

Commons Validation

Pros:

Optimal use of use of resources: JavaScript validations are provided when JavaScript is enabled, and server-side validations are guaranteed.

A single point of maintenance: both client-side and server-side validations are generated from the same configuration and use the same error message.

Cons:

Lack of data conversions and transformations

The generated JavaScript is no modal, it does not engage until the form is submitted.

Spring Validation

Pros:

Server-side validation is easy to implement org.springframework.validation.Validator.

Use the same error message as commons validation. Easy internationalization.

Cons:

Spring client-side validation is in development progress, need standard version.

Configuration:

1. WEB-INF/validation-rules.xml

default validation rules such as email , creditcard, date validation rules.

2. WEB-INF/validation.xml

User-defined form validation rules.

<form-validation>

<formset>

<form>

<field property=”username” depends=”required”>

<arg0 key=”signonusername”/>

</field>

<field property=”password” depends=”required”>

<arg0 key=”signonpassword”/>

</field>

<field property=”lastName” depends=”required”>

<arg0 key=”accountfirstname”/>

</field>

<field property=”firstName” depends=”required”>

<arg0 key=”accountlastname”/>

</field>

<field property=”email” depends=”required, email”>

<arg0 key=”accountemail”/>

</field>

</form>

</formset>

</form-validation>

3. Web-INF/dms-servlet.xml add bean configuration

<bean class=”org.springmodules.commons.validator.DefaultValidatorFactory”>

<property name=”validationConfigLocations”>

<list>

<value>/WEB-INF/validator-rules.xml</value>

<value>/WEB-INF/validation.xml</value>

</list>

</property>

</bean>

<!–  Validating the Spring way –>

<bean id=”userValidator”/>

<!–Commons Validation define –>

<bean class=”org.springmodules.commons.validator.DefaultBeanValidator”>

<property ref=”validatorFactory”/>

</bean>

4.Web-INF/dms-servlet.xml Add validator property in Spring contoller

<bean id=”createUserController”>

<property name=”commandName” value=”account”/>

<property name=”formView” value=”createUser”/>

<property name=”successView” value=”redirect:logout.jsp”/>

<property name=”serviceLocator” ref=”serviceLocator”/>

<property name=”validators”>

<list>

<ref bean=”beanValidator”/>      <!–Commons Server-side validation –>

<ref bean=”userValidator”/>       <!–Spring validation –>

</list>

</property>

5. WEB-INF/classes/message_en_US.properties (English version) Add error message for the validation.

# — validator errors –

errors.required= {0} is required.

errors.minlength={0} can not be less than {1} characters.

errors.maxlength={0} can not be greater than {1} characters.

errors.invalid={0} is invalid.

6. Add class Dms.view.validator.UserValidator Spring server-side validator class.

7. Modify taglibs.jsp add jsp file tag definition

<%@ tglib uri=”http://www.springmodules.org/tags/commons-validator” prefix=”validator” %>

8. Modify /jsp/createUser.jsp add commons validation tag

Modify:

<form method=”post” action=”<c:url value=”/createUser.html”/>”>

Add in the last line:

<validator:javascript formName=”account”

staticJavascript=”false” xhtml=”true” cdata=”false”/>

<script

src=”<c:url value=”/scripts/validator.jsp”/>”></script>

9: Add /scripts/validator.jsp

<%@ page contentType=”javascript/x-javascript” %>

<%@ taglib uri=”http://www.springmodules.org/tags/commons-validator” prefix=”validator” %>

<validator:javascript dynamicJavascript=”false” staticJavascript=”true”/>

Only a single instance of the servlet is created, and each request simply results in a new thread calling the servlet’s service method (which calls doGet or doPost). So, shared data simply has to be placed in a regular instance variable (field) of the servlet. Thus, the servlet can access the appropriate ongoing calculation when the browser reloads the page and can keep a list of the N most recently requested results, returning them immediately if a new request specifies
the same parameters as a recent one. Of course, the normal rules that require authors to synchronize multithreaded access to shared data still apply to servlets.

Servlets can also store persistent data in the Servlet-Context object that is available through the getServletContext method. ServletContext has setAttribute and getAttribute methods that let you store arbitrary data associated with specified keys.

The difference between storing data in instance variables and storing it in the Servlet- Context is that the ServletContext is shared by all servlets in the servlet engine.

This position is an Application Administrator to support operations within our client’s department. This position has a critical role in delivering our services to clients and ensuring successful ongoing operation of our applications and services. It services a highly interactive software development build/release process as well as a rich operational environment with many interrelated applications/database services. The candidate should be self-motivated, detail oriented, adaptable to change and must work well in a flexible team environment with developers, QA, operations staff, system administrators and managers.

RESPONSIBILITIES:

Application and database support

• Provide on-going database administration in both back-end and front-end with application infrastructure support for our client’s administration systems, including the deployment of new applications.
• Review the physical design of existing databases for optimal database structures, database performance tuning, security, database backup/recovery strategy, implementing high-availability, and pro-active and reactive performance analysis, monitoring, troubleshooting and resolution of issues, capacity planning, monitoring data growth and system utilization, trend analysis and predicting future database resource requirements.
• Install web-base applications from ground up to full-ballooned implementation and support, including configuration at Unix/Linux/Windows system level, back-end integration with database, front-end integration with user-interface, final delivery to users to fulfill users’ requirement and on-going maintenance.
• Take the lead in ensuring that application and web services are configured and tuned according to application needs; provide troubleshooting as needed.
• Work with System Administrators to ensure test and production boxes conform to the software application configuration needs.
• Support the department-wide infrastructure application for database management, system monitoring and notification, job scheduling, deployment, provision and patching automation, application topology and service level management for campus-wide system performance.

Build/release activities

• Manage the build, tagging and release processes for a number of interdependent Java web applications and background processes in the QA and production environments. Ensure the build and release process is scalable and repeatable.
• Work with the development team to ensure efficient and understandable build procedures are adhered to and conform to a standard process for configuration and release management
• Develop and maintain tools that automate the building of software releases for an Agile-based development process. This is one of continuous integration, where the automated build process can be run many times a day if necessary.
• Work with and support the QA team to ensure automated test suites run as part of the continuous integration build process.

REQUIREMENT FOR SKILL AND COMPETENCIES:

• Expert hands-on with shell scripts, other scripting languages, preferably Perl, and tool automations
• Minimum 2 years database administration experience in Oracle and 3 years Application administration experience in Unix/Linux infrastructure environments is required.
• Hands-on experience of Oracle databases 10g for 24/7 database operations and tool automation in installation, configuration, backup/recovery, startup/shutdown, data refresh, and application integrations.
• Experience with OEM/Grid Control is highly desired.
• Knowledge and understanding of large scale ERP implementation and support like Oracle Financial and PeopleSoft systems.
• Expert knowledge of Apache and Tomcat, and other web/application servers such as JBoss
• Strong Unix and system administration skills with basic network and security knowledge
• Strong experience and ability in web applications deployment, configuration and integration from both OpenSource and Commercial based systems with or without sophisticated vendor support.
• Java/J2EE based programs
• Java/servlet/JSP based web applications
• Experience with Subversion, PVCS or similar source code repository
• Experience with Maven and familiarity with automated build processes
• Experience with the Agile development methodology and concepts of extreme programming and continuous integration
• Understanding of the layers/tiers of web applications and the communication protocol between the tiers with networking protocols (TCP/IP, HTTP, SSL, DNS, FTP, etc.)
• Ability to multi-task and work in a team environment is critical and should have excellent communication skills in both verbal and written forms.
• Ability to manage multiple competing priorities and work under pressure in high stress situations
• Excellent communication skills in both verbal and written
• Ability to work under pressure and to deliver results in a complex and dynamic operational environment

Qualifications

Minimum 5 years as an IT professional in build/release and application/database administration, plus one or more of the following areas: IT infrastructure operations 24/7, systems analysis and design, or application development.

Education
Bachelors Degree in Computer Science, Engineering or related field or equivalent experience

If you are interested, please send your resume to tsotelo@mindsource.com.

Hoy comienzo a utilizar IntelliJ IDEA de forma profesional, es decir, con proyectos reales. He utilizado este entorno antes, y creo que es uno de los más avanzados y rápidos. Soy usuario de Eclipse desde hace 2 años, y la verdad es que siempre a tenido problema de estabilidad. A veces, eclipse daba errores muy extraños que se solucionaban con volver a ejecutar la aplicación.

Según comenta la página de JetBrains (http://www.jetbrains.com/idea/):

IntelliJ IDEA lets you code without a hitch. It practices a non-intrusive, intuitive approach to help you write, debug, refactor, test and learn your code. Thanks to its deep understanding of languages and technologies, IntelliJ IDEA provides a second pair of hands for you when you need them. Playing the game by your rules without ever getting in your way — that’s our idea of a productive and pleasant development.

Y espero que de verdad esto sea “pleasant development”.

Si alguien quiere utilizarlo puede ir a la página: http://www.jetbrains.com/idea/, y descargarse una versión de pruebas de 30 días. O http://www.jetbrains.com/idea/download/index.html

If you are interested, please send your resume, expected pay rate and citizenship status (US citizen/green card/work permit) to sarada@quality-waves.com

Not long ago i came across this cool Java framework for building your own web applications. Actually I think someone posted it at Twitter ( @playframework ). At first i saw the invitational presentation which you can find here or at the framework’s page.

First Impression

This looked like fun and was very similar to what I’m used to in Symfony based web applications. So I said “what the hell” and started off with the tutorial, most of the things seemed obvious and I was pleased with the concept of writing in Java and having the ability to use any Java library I would like to.

IDE

But wait, it gets even cooler. The guys developing this framework prepared some tasks to make your project integrate with your preferable Java IDE. If it’s NetBeans, like it was in my case, or Eclipse this is a matter of typing one command in your console.

All the keys you need to use …

The coolest thing about it I think is that while developing a web application in Play you get to use all sorts of solutions like Hibernate, OpenId, JUnit, templates based on Groovy and integrate them easily with your project.

Fresh prince

Although this framework seems to be a reasonably “fresh” thing on the web (version 1.0 wright now), it has quite a good looking portfolio to speak for itself. I think this will aspire to be an awesome lite Java framework for all agile projects and web applications. Good luck and congrats to the Play team.

FindBugs^TM : static code analysis tool

FindBug is a static code analysis tool that examines your class or JAR files looking for potential problems by matching your byte-code against a list of bug patterns. With static code analysis tool, you can analyze software(s) without actually running the program.

Getting started with FindBugs:

To run FindBugs, you will need a Java Development Kit (JDK), version 1.4 or higher. One should download the latest release of FindBugs — currently 1.3.9. After downloading the zip or tar, unzip it into a directory of your choice. That’s it — the install is finished.

Running FindBugs:

Like most tools these days, you can run FindBugs in multiple ways — from a GUI, from a command line, using Ant, as an Eclipse plug-in and using Maven.

Using the FindBugs UI:

Using the FindBugs UI is straightforward, but a couple of points deserves some elaboration. One of the advantages of using the FindBugs UI is the description provided for each type of detected problem. Descriptions are provided for each bug pattern, which is extremely useful when you’re first becoming acquainted with the tool. Equally useful is the Source code tab in the lower pane of the window. If you tell FindBugs where to find your source, it will highlight the offending line of code when you switch to the appropriate tab.

It’s also important to mention that if you choose xml as your output option when running FindBugs as an Ant task or from the command line, you can load the results of a previous run into the UI. Doing so is a great way to leverage the advantages of the command-line-based tooling and the UI tooling at the same time.

For day to day activity developers find Eclipse plug-in is more suitable. But for this blog we will stick to ant as it gives us variety of reports depending upon the provided style sheets.

Integrate with Ant:

In build.xml we need to write the following code

<!– =================================

target: findbugs

================================= –>

<target name=”findbugs” depends=”compile” description=”description”>

<taskdef name=”FindBugs” classname=”edu.umd.cs.findbugs.anttask.FindBugsTask”>

<classpath>

<pathelement location=”${findbugs.home}/lib/findbugs-ant.jar” />

</classpath>

</taskdef>

<FindBugs home=”${findbugs.home}” output=”html” outputFile=” findbug-report.html”  jvmargs=”-Xms60m -Xmx250m” stylesheet=”default.xsl|fancy.xsl|fancy-hist.xsl|plain.xsl|summary.xsl”>

<class location=”${webinf.dir}/classes” />

<sourcePath path=”JavaSource” />

</FindBugs>

</target>

Let’s take a closer look at what’s going on in this code.

Target: Notice that the target depends on the compile. It’s important to remember that FindBugs works on class files, not source files, so making the target depend on the compile target ensure that FindBugs will be running across the up-to-date class files. FindBugs is flexible about what it will accept as input, including a set of class files, JAR files, or a list of directories.

Taskdef: Here we define task def name. This is general ANT Practice.

FindBug.home: One should mention directory that contain findbugs.

findbugs.home=D:/opt/findbugs-1.3.9

Output: The optional attribute output specifies the output format that FindBugs will use for its results. The possible values are xml, text, or emacs. If no output File is specified, then FindBugs prints to standard out. The XML format has the added advantage of being viewable within the UI.

jvmargs: In large projects it is tend to get OutOfMemoryException. To take care of such situation we should pass max and minimum memory by jvmargs. This is optional one.

Stylesheet: It specifies stylesheet to be used if output is html. This is optional attribute.

Class / ClassRegex: The class element is used to specify which set of JARs, class files, or directories you want FindBugs to analyze. To analyze multiple JARs or class files, specify a separate class element for each. The class element is required unless the project File element is included. See the FindBugs manual for more details.

AuxClasspath: You list your application’s dependencies by using the nested element auxClasspath. These are classes that your application needs, but you don’t want FindBugs to analyze. If you don’t list your application’s dependencies, FindBugs will still analyze your classes as well as it can, but it will complain when it is unable to find one of the missing classes. as with the class element, you can specify multiple auxClasspath elements in the FindBugs element. The auxClasspath element is optional.

SourcePath: If the sourcePath element is specified, the path attribute should indicate a directory that contains your application’s source code. Specifying the directory allows FindBugs to highlight the source code in error when viewing the XML results in the GUI. This element is optional.

Different Bugs identified by FindBugs:

• Use Long.valueOf(…) instead of new Long(…)
• Need to replace things like

int num = (int) (100000 * Math.random());
by
Random r = new Random();
r.nextInt(100000);

• concatenation with + , use String Buffer or String Builder
• change key set by entry set

Bug categorization:

FindBug categorize the bugs in following categories

•  Bad practice Warnings
• Correctness Warnings
• Malicious code vulnerability Warnings
• Multithreaded correctness Warnings
• Performance Warnings
• Dodgy Warnings

Refrences:

• http://findbugs.sourceforge.net/manual/anttask.html 

In attempting to understand how concurrency works with java it is important to lay the foundation by discussing process management in operating systems before moving on to specific concurrency issues in java.

Process Management in Operating Systems

A process is an instance of a computer program that performs some action. A process can have multiple threads and can be controlled by a user, other programs or by the operating system that its running on. The operating system will execute processes sequentially and can be running multiple processes at any one time, this is called concurrency.

To further explain, a single computer processor runs instructions one at a time, so that a user can run several programs at once, time-sharing is performed. Time-sharing allows for programs to be in either “executed” or “waiting to be executed” state, this gives the illusion to the user that multiple processes are running at the same time but in reality the operating system is switching between them rapidly. An operating system run on a computer with multiple processors can execute instructions simultaneously for different processes.

Mutexes and Threads

A mutex or mutual exclusion is used in parallel programming to “lock” a shared resources so that only one thread can access it at a time whilst at the same time giving waiting tasks a place to wait for their turn. A popular way to remember this is to think of an airplane bathroom. Only one person can access the bathroom at one time, in this case the lock is the mutex so when the door is locked the bathroom is unavailable to the people waiting in queue.

In java every object has one monitor and mutex associated with it. A monitor is a piece of code which is guarded by a mutex. Whenever a thread accesses a synchronized method, the mutex is locked, conversely when the method is finished, the mutex is unlocked. This ensures that only one synchronized method is called at a time on a given object.

Deadlocks and Prevention

A deadlock occurs when two or more threads are waiting for each other to finish and so therefore cannot.

Lock Ordering

One way to prevent a deadlock is to assign an order to the locks and require that they are accessed in that order. This can only work if you know about all locks ahed of time so is not always practical.

Lock Timeout

You can also prevent deadlocks by having a timeout function on lock attempts. This means a thread will only try for so long to acquire the necessary locks before quitting (backing up), thus freeing all locks taken. It will then try again after a random amount of time during which other threads can try to access the necessary threads.

One of the drawbacks if you have lots of threads trying to acquire the same lock they might end up waiting the same amount of time and therefore trying to obtain a lock at the same time over and over.

Deadlock Detected

What do you do if you have a deadlock? You can release all the locks and wait a random amount of time before retrying. But this is can have the same problems as described by a lock timeout above. A better way to do this would be to assigned a priority to the threads so that only the highest priority thread/s backup.

References

Processes:

• http://computer.howstuffworks.com/operating-system5.htm
• http://en.wikipedia.org/wiki/Process_(computing)

Mutexes:

• http://www.javaworld.com/javaworld/jw-10-1998/jw-10-toolbox.html

Deadlocks:

• http://tutorials.jenkov.com/java-concurrency/deadlock-prevention.html

Big Oh notation is used in computer science to decribe the complexity of an algorithm in terms of time and space (memory). Big Oh notation describes the worst case scenario of what happens when an algorithm is run with N values and is really only useful when talking about large sets of data.

Big Oh Complexity Over Time

Source: table source here also big thanks to Dean who made the graph for me

Explanation

O(1) = irrespective of changing the size of the input, time stays the same

O(N) = as you increase the size of input, the time taken to complete operations scales linearly with that size

O(log N) = growth curve that peaks at the beginning and slowly flattens out as the size of the data sets increase

O(N²) = growth will double with each additional element in the input

Java Example for O(1):

    public static boolean isArrayOver100(String[] args) {
        if (args.length > 100)
            return true;
        return false;
    }

Java Example for O(N):

    public static boolean contains(String[] args, String value) {
        for (int i = 0; i < args.length; i++) {
            if (args[i] == value)
                return true;
        }
        return false;
    }

Java Example for O(log N):

public static int binarySearch(int[] toSearch, int key) {
    int fromIndex = 0;
    int toIndex = toSearch.length - 1;

    while (fromIndex < toIndex) {
        int midIndex = (toIndex - fromIndex / 2) + fromIndex;
        int midValue = toSearch[midIndex];

        if (key > midValue) {
            fromIndex = midIndex++;
        } else if (key < midValue) {
            toIndex = midIndex - 1;
        } else {
            return midIndex;
        }
    }
    return -1;
}

See my other post on binary search here.

Java Exmaple O(N²)

public static boolean containsDuplicates(String[] args) {
        for (int i = 0; i < args.length; i++) {
            for (int j = 0; j < args.length; j++) {
                if (i == j)
                    break;
                if (args[i] == args[j])
                    return true;
            }
        }
        return false;
    }

I took this post as my inspiration as I found it to be a great introduction but have instead used java for the code examples.

Please send all resumes to rrabines@topsource.com

Must be: Citizen, Green Card or EAD

Location: Miramar, FL
Salary: High on Experience
Status: DIRECT HIRE

The Java Application Architect will work across teams to design, develop, and deploy business driven solutions consistent with the Enterprise Architecture strategy. The candidate will drive the evolution of a Service Oriented Architecture (SOA) by developing SOA based solutions spanning all layers of the SOA software stack, including but not limited to, service enablement of legacy systems, Enterprise Service Bus (ESB) based integration, Business Process Management (BPM), and SOA Management & Governance. The Jave Application Architect will be a middleware and integration expert chartered with developing mission-critical enterprise software solutions, for enterprise modernization and integration projects. This technical leadership position will require a deep understanding of modern SOA standards, integration patterns, and Web technologies. This person will also be required to map and model business processes, as well as manage integrated project schedules. The Java Application Architect will develop a deep understand of both the business architecture and technical architecture.

Requirements:

-     BS or higher in Computer Science, Computer Engineering, or Electrical Engineering
-     At least 10 years developing object oriented enterprise software solutions in Java
-     At least 12 years applying OOA/D techniques to architect and implement software solutions
-     At least 6 years using J2EE Application Servers and Java enterprise application frameworks
-     At least 4 years as a lead SOA architect working on enterprise integration projects
-     Experience with the full software development life-cycle and various software methodologies such as RUP and Agile approaches
-     Skilled at modeling with UML, as well as requirements capture and business process mapping
-     At least 4 years hands-on experience on enterprise modernization and integration projects employing ESB based SOA solutions
-     Extensive hands-on experience at all layers of the SOA solutions stack, including but not limited to: ESB, BPM, Business Rules, Workflow, SOA Governance & Management, Security & Identity Management, and Portal Development
-     Web Services and Standards Expert
-     Have used/implemented JMS, Message Oriented Middleware, Event Driven Architectures, & Complex Event Processing solutions
-     Project experience with service enabling legacy systems, assembling composite service enabled applications, and applying a wide-range of enterprise integration patterns
-     Experience creating a data services and management architecture for enterprise information integration, developing information models, XML and database schemas
-     Strong SQL skills and experience with one or more database systems
-     Knowledge/experience with various operating systems: Linux, Windows, and/or AS 400
-     First-hand experience developing SOA solutions for CRM, ERP, SCM, and/or e-commerce systems
-     The ability to effectively estimate work effort, create integrated project schedules, and function as a PM
-     Excellent verbal and written communication skills with the ability to create documentation and present to a varied audience

Responsibilities:

-     Provide leadership toward the evolution of an SOA based Enterprise Architecture
-     Design and develop SOA solutions and act as the lead architect on multiple enterprise projects, with hands-on development and management responsibilities
-     Provide expert knowledge on integration projects to the business and technical teams
-     Formulate standards, guidelines, methodologies and best practices for enterprise integration across the IT enterprise portfolio.
-     Work with various service delivery teams providing input for strategic initiatives that may require integration with internal systems and/or external solutions
-     Ensure IT governance and SOA best practices are being applied across the organization
-     Continue to monitor technology development and solution opportunities that support the overarching Enterprise Architecture Strategy
-     Lead and mentor more junior team members, as well as educate the broader IT organization
-     Evaluate products and vendor solutions against well defined evaluation criteria and make recommendations to the business

What is it?

Binary Search is a technique used to search sorted data sets. It works by comparing the middle element against the search value, if the search value is greater than the middle element a subset is created out of the upper half of the set. The same operation is then performed on the subset recursively until the value is either found and the index returned, or not found and -1 returned.

eg. If we start with with a set of ints: [1, 4, 6, 8, 9, 10, 11, 13, 15] and our search value = 11

• Choose the middle element: 9
• Is 9 > 11
• No, so take the upper half and create a subset [10, 11, 13, 15]
• Choose the middle element: 13 (4/2 =2 which is the third element in the array as arrays are zero based)
• Is 13 > 11
• No, so take the lower half and create a subset [10, 11]
• Choose the middle element: 11
• Is 11 >= 11 yes – we have found our element

Binary Search in Java

I have created my own java binary search method:

    public static int binarySearch(int[] toSearch, int key) {
        int fromIndex = 0;
        int toIndex = toSearch.length - 1;

        while (fromIndex < toIndex) {
            int midIndex = (toIndex - fromIndex / 2) + fromIndex;
            int midValue = toSearch[midIndex];

            if (key > midValue) {
                fromIndex = midIndex++;
            } else if (key < midValue) {
                toIndex = midIndex - 1;
            } else {
                return midIndex;
            }
        }
        return -1;
    }

Take a look at Arrays.binarySearch() method to see the java source code implementation of the search. If you don’t have the java source code attached to your favourite IDE I suggest you do so, it’s a great way to learn how everything works.

Complexity

The complexity of the binary search is O(log n).

Why use Binary Search?

Binary Search is quicker than searching through every element (O(n)) as it halves the amount of elements to search each iteration. This halving means that after a strong growth curve at the beginning, it slowly flattens out as the size of the input data set increases, therefore it is good for large data sets.

More Info

There is a good introductory explanation of binary search and O notation here.

I’m very pleased to announce that ICEfaces 2.0 – Alpha 1 is now available for download.

This inaugural development milestone release of ICEfaces 2.0 provides the fundamental capability of running the next-generation ICEfaces core on the Mojarra JSF 2.0.1 runtime. You can plug the icefaces.jar into your existing JSF2 application and immediately receive some of the benefits of ICEfaces Direct-to-Dom rendering, such as providing incremental page updates without the need to specify the JSF 2 “f:ajax” tag. A sample application is included demonstrating ICEfaces 2 with JSF 2 (“h:”) standard components, and Ajax Push.

Also included in this release is the initial implementation of the ICEfaces 1.x compatibility libraries, along with sample applications that demonstrate this capability. The ICEfaces 1.x compatibility libraries are used to readily port your existing JSF 1.2 / ICEfaces 1.8 applications to JSF 2.0 / ICEfaces 2.

See the Release Notes for all the details.

We are planning to have another significant ICEfaces 2 milestone release, featuring the beginnings of our all-new ICEfaces 2 component suite, before the end of this year, so stay tuned!

Source: www.icefaces.org

ICEfaces 1.8.2 is now available for download, SVN repository checkout, or via Maven public repository.

ICEfaces 1.8.2 is an official maintenance release that includes 165 fixes and improvements. Notable changes include:

Source: www.icefaces.org

Many of us have experienced projects that drag on much longer than expected and cost more than planned. Companies looking to improve their software development processes are now exploring how Agile can help their Enterprise more reliably deliver software quickly, iteratively and with a feature set that hits that mark.  While Agile has different “flavors”, Scrum is one process for implementing Agile.  This article discusses the Agile Scrum process that can be used to aid in improving your software releases.

http://szypulski.wordpress.com/introduction-to-agile-scrum/