Showing posts with label Java. Show all posts
Showing posts with label Java. Show all posts
Tuesday, November 06, 2007
JBoss Seam 2 is out
JBoss released Seam 2.0 to the world.
What I like most is GWT integeration and the door Seam developers left open for integerating Seam with framework other than JSF , my vote is for WebWork2 (I don't like Struts2 name, WebWork is much more sexy).
JBoss Seam
Thanks for all JBoss Seam developer for creating such a great framework.
What I like most is GWT integeration and the door Seam developers left open for integerating Seam with framework other than JSF , my vote is for WebWork2 (I don't like Struts2 name, WebWork is much more sexy).
JBoss Seam
Thanks for all JBoss Seam developer for creating such a great framework.
Sunday, November 04, 2007
Tuesday, October 23, 2007
GWT & SiteMesh… Friends or foes?
SiteMesh is a powerful lay outing framework for Java web applications based on the “Decoration Pattern”.
It is the lay outing framework that fuels AppFuse project and the new bad boy in Java web development jammed market “Grails”.
If you are anything like me, then you are thinking of Google Web Toolkit (GWT) every day.
GWT & SiteMesh are very powerful technologies but do they mix smoothly without collateral damage?
That’s what I have been trying to achieve in a small Java web application.
My web application has the following structure:
Shopping folder contains my GWT module host page (Cart.html) and cart folder contains com.web.gwt.cart.ManageCart.html
Here is Cart.html head tag:
Now, with every thing is neat and dandy, lets try to request our spoiled GWT Cart.html page.
Do you see any thing?
No!
SiteMesh template is shown but the Cart.html is not.
Here FireFox’s plug-in “FireBug” comes to rescue.
FireBug shows that the HTTP response contains my SiteMesh template twice!
Damn, I forgot that SiteMesh allows us to exclude resources based on URL patterns.
Here is my first shot:
(decorator.xml file):
Let’s try to see our spoiled GWT Cart.html page again.
…
Nothing again!
I started to lose my nerves but let me see FireBug again.
FireBug shows that the actual request for Cart.html page contains some extra parameters in the form of:
Cart.html?32451237845234
Here is my second shot for decorators.xml:
This time, Cart.html is destined to work, right?
Right!
So, what is the moral? GWT & SiteMesh are friends and good amigos indeed.
It is the lay outing framework that fuels AppFuse project and the new bad boy in Java web development jammed market “Grails”.
If you are anything like me, then you are thinking of Google Web Toolkit (GWT) every day.
GWT & SiteMesh are very powerful technologies but do they mix smoothly without collateral damage?
That’s what I have been trying to achieve in a small Java web application.
My web application has the following structure:
/context-root/
|
-------- shopping
|
------ Cart
Shopping folder contains my GWT module host page (Cart.html) and cart folder contains com.web.gwt.cart.ManageCart.html
Here is Cart.html head tag:
<head>
<meta tag name="gwt:module" content="/armada/shopping/Cart=com.web.gwt.cart.ManageCart">
</head>
Now, with every thing is neat and dandy, lets try to request our spoiled GWT Cart.html page.
Do you see any thing?
No!
SiteMesh template is shown but the Cart.html is not.
Here FireFox’s plug-in “FireBug” comes to rescue.
FireBug shows that the HTTP response contains my SiteMesh template twice!
Damn, I forgot that SiteMesh allows us to exclude resources based on URL patterns.
Here is my first shot:
(decorator.xml file):
<excludes>
<pattern>/shopping/Cart/*.html</pattern>
</excludes>
Let’s try to see our spoiled GWT Cart.html page again.
…
Nothing again!
I started to lose my nerves but let me see FireBug again.
FireBug shows that the actual request for Cart.html page contains some extra parameters in the form of:
Cart.html?32451237845234
Here is my second shot for decorators.xml:
<excludes>
<pattern>/shopping/Cart/*.html?*</pattern>
</excludes>
This time, Cart.html is destined to work, right?
Right!
So, what is the moral? GWT & SiteMesh are friends and good amigos indeed.
The Magnificent Seven
JetBrains released The Magnificent Seven.
Spring & Hibernate integration looks so promising, Dependency Structure Matrix is a new tool for class dependency analysis.
IntelliJ IDEA 7 also comes armed with Web Services support , Ruby/JRuby and Groovy support.
But what I’m really have been waiting for is Grails support.
IntelliJ IDEA productivity + Grails == killer compination
How can you beat that?
IntelliJ IDEA is simply the best Java IDE in the market, I can’t wait to put my hands on this “Tyrant” tool.
Tuesday, June 12, 2007
Getting started with Grails
Finally, after spending a considerable amount of time trying get ride
of this ugly error while I'm trying to create my first Grails application:
Mr. Graeme Rocher came to rescue.
So, if you have GROOVY_HOME environment variable defined in your system and and you got that ugly error while you are trying to run Grails scripts, then remove the GROOVY_HOME environment variable.
Maybe you don't want to remove it completely, you can just "remove" it from your current console.
In MS Windows, you can use :
Enjoy your search of the Grails!
of this ugly error while I'm trying to create my first Grails application:
Welcome to Grails 0.5 - http://grails.org/
Licensed under Apache Standard License 2.0
Grails home is set to: D:\Grails
Base Directory: D:\GrApp
Environment set to production
Note: No plugin scripts found
Running script D:\Grails\scripts\CreateApp.groovy
Error executing script CreateApp: Cannot invoke method addURL() on null object
java.lang.NullPointerException: Cannot invoke method addURL() on null object
at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:1
05)
at org.codehaus.groovy.runtime.Invoker.invokePogoMethod(Invoker.java:148
)
at org.codehaus.groovy.runtime.Invoker.invokeMethod(Invoker.java:110)
at org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.
..........
Mr. Graeme Rocher came to rescue.
So, if you have GROOVY_HOME environment variable defined in your system and and you got that ugly error while you are trying to run Grails scripts, then remove the GROOVY_HOME environment variable.
Maybe you don't want to remove it completely, you can just "remove" it from your current console.
In MS Windows, you can use :
set %GRAILS_HOME%=
Enjoy your search of the Grails!
Subscribe to:
Posts (Atom)
