Problem faced with jDom XPath ;)

Today I had faced an issue related with jDom Xpath. In my project I am using Xpath to get Nodes from a web service request. But during this  parsing a ‘Class not found exception‘ was throwing continuously and the funny thing is, the class which was not finding was already existing in that jar file. It was a crutial moment for me becouse a demo was going to be happen the day after next day and I have to deploy and give that web service to my friends working in the .net side to continue their work.

The exception was just like the following…
org.jdom.JDOMException: java.lang.NoClassDefFoundError: org/jdom/Text:
org/jdom/Text

The stack trace was like follows

Caused by: java.lang.NoClassDefFoundError: org/jdom/Text
at org.jaxen.jdom.JDOMXPath.<init>(JDOMXPath.java:100)
at org.jdom.xpath.JaxenXPath.setXPath(JaxenXPath.java:281)
at org.jdom.xpath.JaxenXPath.<init>(JaxenXPath.java:99)

I searched in net and got the following link. Here the author specified the non availability of the jaxen.jar file in the lib folder. This helped me a lot… thanks Connor.. But when I checked in my project lib [ I am also using jBoss for this project] , I found this ‘jaxen.jar’ is already there in my jBoss lib as well as in webapps lib.

I tried by downloading the following jaxen jar, “jaxen-1.1-beta-9.jar” and put in the lib folder. And Its Worked !!! Hope this post will helpful in future, for me or to any of my friends 🙂

How to change port number in JBoss App Server?

As we all know that JBoss is running on port number 8080 as default. If you want to change the port number of your JBoss (jBoss 4)  then thats also too easy. Just follow the following steps…

Click here to Read Full Article

What is Continous Integration and Continous Integration Servers?

The words of Mr.Martin Fowler…

Continuous Integration(CI) is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily – leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly. This article is a quick overview of Continuous Integration summarizing the technique and its current usage.

By Going through his this great article and example about CI will defenitly help you to get the clean idea about this.

Advantages of Continuous integration

  • When unit tests fail, or a bug is discovered, developers might revert the codebase back to a bug-free state, without wasting time debugging.
  • Integration problems are detected and fixed continuously – no last minute hiatus before release dates;
  • Early warning of broken/incompatible code;
  • Early warning of conflicting changes;
  • Immediate unit testing of all changes;
  • Constant availability of a “current” build for testing, demo, or release purposes;
  • The immediate impact of checking in incomplete or broken code acts as an incentive to developers to learn to work more incrementally with shorter feedback cycles.

Continous Integration (CI) Servers

A server process or daemon which monitors the version control system for changes, then automatically runs the build process (e.g. a make script or Ant-style build script or Maven type) and then runs test scripts (e.g. JUnit or NUnit) can call as Contious Integration Server. In many cases the build script not only compiles binaries but also generates documentation, website pages, statistics and distribution media (such as Windows MSI files or RPM files).

Two Examples…

  • Continuum is the open source CI server from the house of Apache.
  • Bamboo: The CI and Build server from Atlassian. (Commercial)

How to Choose a Continous Integration Server?

Going through this article in IBM Developer works by Mr.Paul Duvall (paul.duvall@stelligent.com), CTO, Stelligent Incorporated; will defently help you to make a decision in this matter.

Technorati Tags: ,

Glassfish features…

Here is some key features of Glassfish, the Open Source Application Server for Java EE 5. These info I got from ArunGupta’s blog. He summarizes the features in his latest post.

  1. Fastest open source application server (883.66, highly scalable).logo.gif
  2. Centralized management of clusters and instances distributed across multiple servers.
  3. Microsoft .NET 3.0 interoperability
  4. Java Business Integration and Open ESB
  5. Call flow analysis for diagnosing performance problems
  6. High performing message queue implementation (Open Message Queue), with a highly available message store.
  7. SIP Servlet support and Telco Support via SailFin
  8. Very small footprint and flexibility via modularity in GlassFish v3.

For more please visit here

Design a site like this with WordPress.com
Get started