I’ve tried today to expose some of our services in our application service layer.
All those classes are simple POJOs, autowired with Spring.
I’ve chosen Hessian for few reasons:
- I never liked xml, soap, etc…
- we need web services over http (so no RMI)
- it’s very fast
- we might need different type of clients connecting to the application (Hessian apparently supports not only plain old Java but also JavaFX, Flex, almost every decent popular programming language)
Well the modification to the code (I’ve changed a couple of xml files) took less than an hour.
You can find the instructions here, there’s nothing else I can add to that document, it just works.
Many people says that Java is death or will die soon but what Spring gives “to the masses” is still incredibly valuable and I found always very quick to implement a change in the code or make a big redesign of the codebase.
Lately I’ve been impressed by the autowiring features and the java config new stuff.
Have a look, java is perhaps struggling but still not death.
2 Comments
It looks good and cool, but I met a problem and raised it in spring forun, http://forum.springsource.org/showthread.php?t=70553, it blocked my development, and caused me plan to turn to balzeDS.
Would you please take a look, and do me a favor? Thanks in advance.
Edward He
That class seems to be in these versions of hessian: http://www.findjar.com/class/com/caucho/hessian/io/SerializerFactory.html
hessian-2.1.12.jar
hessian-3.0.1.jar
hessian-3.0.8.jar
resin-3.0.9.jar
You should probably double check the maven settings!
for me this configuration worked:
org.springframework
spring
2.5.6
com.caucho
hessian
3.1.5
declaring the hessian exported servuce in this way: