I have recently begun to wotk with web services in Java. Testing these web services in Java was not as easy as just typing a random request into soapUI.
The soapUI test needs to follow the order defined by the interface definition or XSD.
I have recently begun to wotk with web services in Java. Testing these web services in Java was not as easy as just typing a random request into soapUI.
The soapUI test needs to follow the order defined by the interface definition or XSD.
Admit that Spring is very hard to configure. If you are like me and you do not setup a new Spring project each month you would most likely search it up on google for answers. Admit it once more that you do not always find what you are looking for. And its true, its a mess out there with different tutorials showing you Spring 2.5 and Spring 3.0, and you do not know whats what immediately. In this article I will show you how to configure Spring 3 MVC for use with JavaScriptMVC 3.0.
I really agree on the fact that connection pools need connection validation on return or on borrow. A connection pool without connection validation isnt worth much. But its certainly the last step to do while creating an application. The last fine tuning before the app goes live. Not the first thing to setup. Because the underluying functionality might change one needs to carefully test that the applied parameters is working and not trust a connection pool template as suggested by the comments on this blog entry!
Database Connection Pooling In Grails – solving the idle timeout issue | Javalobby.
I found this interesting article covering the reasons for why a project should use Grails.
Groovy on Grails (Grails) is certainly the meaning of life for a professional programmer. Grails brings me closer to programming heaven than I will ever get. But I will most propably not be using it in the near future. Working with a tool like Grails makes alot things easier but it all needs to be learned. There are some key concepts within Grails that must be understood. Without this knowledge the applications will become badly designed, even with the help of such a strong framework. So what am I talking about? I am going to talk about in this post how I see Grails as an application framework and when it should not be used.
Sometimes as a programmer you get to a point where you have to choose HOW to do your stuff. You have plenty of options. In Java almost everything is done before. So there is no need to it your self. But consider this, would it be worth while to use a library when you could have hacked down the same functionality in about half the time? I am going to consider what to use when you need to retrieve the contents of a XML element.
A lot of critical voices are shouting out about the bad things the module pattern in JavaScript brings with it. Well, I am going to shout back because they are just silly stupids that doesnt know how to code. Maybe they are still living with their mom eating pizzas. Who knows. But who am I to judge about that :)
I am going to give you a brief intro to why I like this pattern and how I use it in my current project.
It is truly unquestionably the best cms framework for Java. And it makes managing content with pluggable dynamic sections easy. It excels in many ways and features. but it is mainly aimed towards bigger sites. i had actually began the work of making my own cms/blog when i accidentally discovered Brix. i fooled around with it and quickly came to the following conclusion:
its to big for use in simple cases like a blog. making a blog in wicket is just hammering nails. making something similar in brix means adding alot more stuff and not needed wrapping. It is per example no need in my blog for changing or creating the templates when the application is running. templates can be predefined and switched in an administration panel.
My final conclusion is that i have not yet seen the best of Brix and that I still need some time playing with it and learning its internals.
I will absolutely recommend Brix for more advanced sites that need an active dialog with designers and webdevelopers. they wont even know that the page is written in Java because all they see is Xhtml!
I have in my past two years as a professional Java web developer stumbled upon the fact that if my code is not reusable and readable, as well as not structured and modularized, it cannot be maintained in the long run. I have had the need for good web frameworks and I have learnt a few of the available support frameworks along the way. By saying support frameworks I mean for example Freemarker templating engine. It is not a web framework in it self but rather a helping hand for separating code from design.
(Continued)
The magic about a one time clickable button in C# is to override Button and place the default onclick event to aspnet_onclick and add another function to onclick that disables the button if Page_IsValid. I will not post the whole solution, but I will share the javascript that enable the disable effect.
function SubmitButton_InitOnClick( id, className )
{
var sb = document.getElementsByName(id)[0];
sb.aspnet_onclick = sb.onclick;
sb.button_className = className;
sb.onclick = SubmitButton_Click;
}
Even if it is a good solution it does not work well with updatepanels because the buttons are rebinded. Thats a topic i have not yet solved. Please tell me if you have a solution to this problem.