BDD is a great concept.
It’s like TDD’s brother. Both share a lot of common ideas. TDD is started with focus on developers, while BDD trying to cover business side as well.
BDD tries to fill in the gap between business and technical, which kind of solution I’m looking for.
Please check my grangular project in GitHub.
My current implementation requires some modification & update to existing Grails plugins (Spring Security and angular resource).
- Spring Security plugin. Need the plugin to return 401 instead of redirecting to login form.
- Angular resource plugin. I want to upgrade the plugin to use the latest angular JS (currently 1.2.0-RC3).
I’ll wait first until I get response for the pull requests before I start sharing more detail in this post.
Is Java slow? Yeah. But so what? We have JRebel!
As I’ve mentioned in other articles. We have old web application using Struts 1, Spring, and iBatis.
The existing web user interface is plain JSP with no Ajax whatsoever.
User still need to key in some value like port code, country code, and other domain-related code using normal input without any sort of hints from the system. And they’ve been using this old software for about 5 years! Amazing! The users can use this software without complaint probably because they’ve been working in their vessel terminal for a very long time. They remember all those codes by heart.
We want to gradually provide better UI experience in the newer version of this software. In this article, we’ll focus on providing autocompletion for port code. Continue reading
My company has existing Java enterprise project. One of the project is web application developed using old version of Spring, Struts, & iBatis.
My task is to upgrade some of libraries & dependencies, make it works with Microsoft SQL (previously it runs only on top of Oracle DB), and deploy it to Tomcat instead of Oracle Weblogic. Basically, there will be changes but the UI will remain the same. UI will be the last part to upgrade.
Ideally, I can just reuse existing functional testing codes to make sure my modification doesn’t break existing code.
Unfortunately, the previous developer didn’t write a single test code. So, I’m planning to start covering all the codes with tests, be it unit test, integration, and/or functional tests.
For this article, we’ll focus on writing functional testing code
The grails application exposes JSON webservice API. The persistence is MyBatis.
I want to have separate log file that only contains:
- which API is being called
- what SQL script being called
- what’s the parameter passed
This will be very helpful for debugging the application.
I’m rewriting one of existing application. It’s a messy Swing application. There’s no clear separation of concern. It makes direct JDBC calls from View , Controller, anywhere. It’s all over the places. WHAT THE FFHHH!!
My plan is as follow:
- to move those SQLs to a separate application that serve the data via webservice APIs.
- to replace JDBC call with ORM. I choose iBatis, well.. MyBatis.
- to use Grails framework
Manage jenkins -> configure system.
Enter your email address and other detail as follow
note that the password is not the one you usually used to login gmail.
You need to generate application specific password and use the generated code as the password here.
If you follow Grails development update, the community has put serious effort in bringing REST experience in Grails to next level. Check this JIRA progress.
Now that Grails 2.3.0M2 has been released, I’ve created simple (but not that simple) grails app that expose RESTful API using that new version.
The intention is to develop real application exposing REST APIs that will be consumed by Android application. I’ll share more once I created the android application and done some testings.
to be continued..
I desperately want to be a better pragmatic programmer.
Skills.. attitudes.. knowledge.. Everything!