Java Research & Development by Pavel

My 1st Out-Of-the-Box (OOB) series begins with making an example of how Seam 1.2.1 +MyFaces 1.1.6 + Facelets 1.1.14 can work on a default JBoss EAP 4.2.

Get the Maven2 project SeamExample, SeamExample.ear. Access the deployed application here

It will deploy a simple echo web app using Seam. Notice that the EAR is made to be minimal (all modules share the same JAR versions) and also includes a jboss-app.xml which sets a loader-repository

Enjoy!

(3 votes, average: 3.67 out of 5)

 Loading ...

Grinder 3 is awesome no doubt about it!

Grinder 3 also adheres to W3C recommendations to encode requests as if everything is in UTF-8, meaning that if you pass parameter values in other than UTF-8 encoding then Grinder will send garbage. This is hardcoded and can be seen in the Grinder 3 source (god bless open source … amen). The explanation is also a comment from the source.

The only way to make Grinder 3 to encode requests using the deprecated way is to follow this procedure:

Continue Reading »

(No Ratings Yet)

 Loading ...

Playing with Eclipse and JBoss WS ? Good !

Did not expect the word BEA to pop up while developing for JBoss? Do not be afraid it’s cool, we got it under control!!!

Don`t know which dependencies you need for the client ? No biggie …

Just add these from JBoss_HOME/client :

1. jaxws-api
2. jaxws-rt
3. jsr181-api
4. jaxb-api
5. jaxb-xjc
6. wstx.jar – this one solves this exception

and you are good to go.

Enjoy!

(3 votes, average: 5.00 out of 5)

 Loading ...

Everyone are working and having fun with JBoss 4.2. Many people are busy migrating applications from Websphere to JBoss but they got use to working with RAD 7. So they are stuck because they cannot setup JBoss 4.2 as a server in RAD which is based on Eclipse 3.2.1.

You cannot upgrade to latest JST server adapter for JBoss servers because the file format is not supported in Eclipse 3.2.x / RAD 7.

So here is the solution for you – our home made migrated server adapter for JBoss 4.2 to work with RAD 7 and Eclipse 3.2.1 (if you have to).

You may want to backup stuff during this procedure by archiving deleted directories or the whole eclipse / SDP07 directories.

Installation procedure:

1. Extract the contents of the server adapter archive from this post to the eclipse/plugins/org.eclipse.jst.server.generic.jboss…… directory (or IBM/SDP07/plugins/org.eclipse.jst.server.generic.jboss) and overwrite the contents

2. Make sure that RAD / Eclipse are shut down and delete the following directories in eclipse/configuration:

1. org.eclipse.core.runtime

2. org.eclipse.osgi

Deleting this will reset Eclipse / RAD plugin state cache and will reread the new server definitions adding JBoss 4.2 to your tool set

The magic is that newer file format is using wildcards to set the server’s classpath and the older format does not support that.

Enjoy!

(2 votes, average: 5.00 out of 5)

 Loading ...

You use RAD 7 and want to develop comfortably with JBoss AS 4 – 5 ?
Here you learn how to use my favorite Eclipse plugin with my favorite application server on RAD 7 (if you absolutely must).

Continue Reading »

(1 votes, average: 5.00 out of 5)

 Loading ...