My First J2EE application

Ahem ! I did not write my own J2EE application, but followed a tutorial and typed the code exactly as it was given in the tutorial. It took me more than a week before i managed to complete the coding, build the package an deploy it on application server.

I used Eclipse-jBoss ide and JBoss Application Server. I have selected this because i dont want to depend on any big brand name like WSAD or RAD [The latest version is called RAD only, i included WSAD just to show off].

After a little over 7 years of mainframe experience, i am finding it very difficult to come out of the structured programming paradigm. Now, i can understand how the well experienced MVS/OS390 community will feel about migrating to the Linux world.

For the last few days, one problem was breaking my head. The solution was simple and probably an oversight. But, the amount of time spent to uncover the issue was huge.

Problem:

14:54:24,733 INFO [EARDeployer] Init J2EE application:
file:/home/bright/jboss-4.0.3SP1/server/default/
deploy/FiboApp.ear
14:54:25,444 WARN [verifier] EJB spec violation:
Bean : Fibo
Section: 22.2
Warning: The Bean Provider must specify the fully-qualified name of the Java class that implements the enterprise bean's business methods in the element.
Info : Class not found on 'tutorial.ejb.FiboBean': Unexpected error during load of: tutorial.ejb.FiboBean, msg=tutorial/ejb/FiboBean (Unsupported major.minor version 49.0)

14:54:25,446 ERROR [MainDeployer] Could not create
deployment: file:/home/bright/jboss-4.0.3SP1/server/
default/tmp/deploy/tmp18511FiboApp.ear-contents/FiboEJB.jar
org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages.
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:575)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)

...

Solution:
set JAVA_HOME to the path locating the jdk 1.5 version

Pretty much impressive, isnt it? Huh...:-(

...bright