Comments for Blog IT - Mateusz Mrozewski

Comment on From JUnit3 to Easyb by Scott Davis

Scott Davis — Fri, 12 Mar 2010 21:23:00 +0000

Great post! I always have to explain to folks that easyb doesn’t offer dramatically different testing capabilities over JUnit version.x — if you are already unit testing, easyb doesn’t change that. Yes, there are some slight syntax changes, but they aren’t the interesting part. What easyb brings to the party is a bit of a semantic shift — your source code for the tests become a bit more self-documenting, and the easyb HTML reports really shine when you put them in front of the end users. Nice work!

Comment on From JUnit3 to Easyb by mati

mati — Fri, 12 Mar 2010 19:25:00 +0000

There is a comment in source code that is has been removed for clarity. I will update the post with a note that is it necessary.

Comment on From JUnit3 to Easyb by Paweł Stawicki

Paweł Stawicki — Fri, 12 Mar 2010 19:23:00 +0000

You missed “equals” method in Money class. Without it, test “Assert.assertTrue(expected.equals(result));” will always fail, as it is comparing different instances.

Comment on Grails – plug-ins by mati

mati — Fri, 12 Mar 2010 09:49:00 +0000

O to samo spytałem Marcina w mailu Czekamy na odpowiedź

Comment on Grails – plug-ins by Jacek Laskowski

Jacek Laskowski — Fri, 12 Mar 2010 09:41:00 +0000

@Marcin Piechota, a mógłbyś napisać, co jest niedojrzałego. Nie twierdzę, że Grails jest dojrzały i mam wewnętrzną potrzebę poznania, co Tobie/Twojemu zespołowi nie pasowało.

Comment on Grails – plug-ins by Marcin Piechota

Marcin Piechota — Fri, 12 Mar 2010 21:46:00 +0000

Robimy teraz pierwszy projekt w Grails i mimo, że jesteśmy nowicjuszami idzie to bardzo sprawnie. Ale jednak muszę powiedzieć, że dojrzałość grailsów jest bardzo mała, ale czego wymagać po nowym frameworku.

Comment on EJB3 Tutorial part 01 – environment setup and first EJB with JBoss Tools and JBoss AS by Blaze

Blaze — Fri, 12 Mar 2010 21:33:00 +0000

@mati Thanks, Mati. I'm check my client code and found that write Context ctx = new InitialContext(); instead of Context ctx=new InitialContext(props);

Comment on EJB3 Tutorial part 01 – environment setup and first EJB with JBoss Tools and JBoss AS by mati

mati — Fri, 12 Mar 2010 19:30:00 +0000

@Blaze: check if you have modified the build path for the client project as described and if you don’t have any typos in your client code (especially around setting the properties).

Comment on EJB3 Tutorial part 01 – environment setup and first EJB with JBoss Tools and JBoss AS by Blaze

Blaze — Fri, 12 Mar 2010 18:03:00 +0000

Hi.

I get exception when try to run client appliation:

Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at Main.main(Main.java:19)

I’m see to Jboss console and find Consolbe EJB bean in it, but i can’t access to it from client

Comment on rootnode.net by ahes

ahes — Fri, 12 Mar 2010 23:51:00 +0000

@Tomek Bujok Not anymore.