Skip to main content

A Simple MVC Application with Eclipse/JBoss

Coming up here , which I'll post in a couple of hours will be simple MVC baby application where I'll use /We'll need

o Eclipse (eclipse-SDK-3.1M4-win32.zip) make sure you get the 3.1 M4 for JBoss IDE/J2EE integration
o Get JBoss, get the 4.0.2. That'll do. For installation see Instructions
o We'll Install the JBoss IDE Plugin via the Eclipse Install Manager.
o XDoclet as well.(Not for now but for other test endeavors, but we can still install it)
o Well there are score's of cool plugins like Lucene(search engine), Hibernate(PersistanceManager) for Databases, but like I said we'll come to that later in the series. Remember our poor brain can only handle small things, so we go easy
o Last but not the least a working JDK, get JDK 5.0 from http://java.sun.com while you're at it. I would assume that you can configure it easily on your OS(be it windows/linux)

Eclipse Installation
-----------------------

You can have as many environments as you like. All you need to do is unzip the file into your directory. And you're(we'll almost done!) . I have for instance several homes, currently Eclipse 3.1 Final release and for now the M(Milestone)4 for the JBoss IDE integration.

Assuming that you're done installing and configuring your eclipse environment, which is nothing!(phrrrrew, the brain wheezes :))

We can get on with the installation of the JBoss IDE plugin and as well as XDoclet plugin installation, again no sweat here as you'll notice soon.

JBoss IDE /XDoclet Installation
---------------------------------
If you've got no patience and your brain is already gunning to go ,then see this for JBoss IDE installation via the eclipse plugin, but if your brain is aching like mine read on...;-)

Follow the prints to install the JBoss IDE

Well uploading pictures sucked bigtime(tried flickr,picasa,Hello, all had limitations and remember my poor brains has it's lobes full with Java) so I posted them on my own "Singapore" gallery.

Starting the JBoss 4.0.2 AS
------------------------------
*(This is fully J2EE compliant server, and not like the Tomcat Server which acts as a container(although it also has capabilities to function as a reasonably good app server)

o Again simple, unzip it into say /usr/java/jboss-4.0.2 or D:\java\jboss-4.0.2
o Have your bash profile/env variables set up properly
o And then you can either start the app. server via cmd line or via the eclipse. All you need is to invoke the /bin/run.sh or \bin\run.bat

Ok then we're all set and have our IDE kinda of ready to dish out a simple MVC J2EE application.

Comments

  1. well I'll post my own comment here:

    If installing Jboss on a windows box make sure that you don't put it under "program files" ..path with spaces in between will make it throw exceptions such as
    "main class not found and what not!"

    Answer is simple just put it in a folder(s) which don't have spaces in their names.:-)

    ReplyDelete

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op