First of all I’ve always used JUnit and not TestNG. This post is not blaming on anything. It’s just pointing out the little stuff I had to do to make my eclipse works with TestNG.
- Install TestNG from eclipse marketplace and restart
- The @Test annotation has to be on it’s own line of the plugin won’t pick it up
- In assertEquals() (and I’m expecting all the others) expected vs actual values are actually exchanged
- You have to configure the Output Folder of eclipse to go under $project/target/target-classes or eclipse won’t pick it up.
That’s it for now.
REST application programming
Writing your first active energy manager application using REST
Sending delayed JMS Messages
The fastest ways to open editors in Eclipse using the keyboard
Swing 2.0 is Coming
The biggest announcement – and the biggest surprise for many – of JavaOne 2010 was certainly Oracle’s new plans for JavaFX 2.0… or, should we say, Swing 2.0?
via Flickr by Aeioux
Starting JBoss (5.1.x) from eclipse (3.5.x) it could happen that you get an exception like the following:
15:26:51,530 ERROR [Naming] Could not start on port 1099
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.bind(Unknown Source)
at java.net.ServerSocket.<init>(Unknown Source)
at javax.net.DefaultServerSocketFactory.createServerSocket(Unknown Source)
It’s because you have a port already in use. In this case it the port used for Naming service. While changing port from the eclipse editor didn’t work, you can (after stopping the server), open the file
search for the desired port (in this case 1099) and then change it to a new value (in my case 1199 was free).
<!-- Naming Service -->
<property name="description">The listening socket for the Naming service</property>
save and start the server.