Spring

Hi,


It has been a great meeting today in Park Hayarkon today, I hope you guys had as much fun as I did!

 

If you have other user-experiences or best practices, please share them on the comment section...


Attached to this post you'll find:

1. Presentation slides (in digital form, thank God!)

zvika 31/10/2010 - 15:51

We have a Swing Applet client that needs to communicate with a Spring/hibernate application running on tomcat, the requirements are pretty standard , passing data objects through and forth, considering firewalls and performance.
the current implementation is soap with axis 1 (that has some limitations on transmitting hibernate objects and proxies,have to set null on proxies before sending them with axis).

what would you consider as a replacement to soap/axis? Rest? RMI? Spring remoting?

shalom 14/06/2009 - 20:31

  As the subject states, new version of this integration framework is released. The new features motly include adaptors for new external resources, like RabbitMQ, MongoDB, Redis, etc. The full list of features is available here: blog.springsource.org/2012/01/09/spring-integration-2-1-is-now-ga/

 

 

andrew 10/01/2012 - 14:53

Feature-toggle is an agile development paradigm where features are committed to the main development branch, but are turned off until ready. This avoids merging branches and helps discover conflicts between features early. Another benefit is that QA can test the feature and approve it before it officially appears in the product.

 

Many times, a feature-toggle is just an 'if' statement that wraps the entry code to the feature. E.g. 'if (formValidationFeature) validateForm()'

 

However, in some cases, the feature modifies the top level services in the product. If using Spring, it means modifying the bean declarations. In this post I'd like to quickly show how to do this using Spring 3.1's new profiles feature.

 

The profiles feature allows toggling bean definitions. You can read more about it here

 

ittayd 20/12/2011 - 12:37

This is really impressing! They created a full application with several entites on MongoDb, and deployed it to Cloud Foundry. In less than 50 lines of Roo commands from an empty dir to the application deployed on CloudFoundry.com. Actually, in less than 40 lines, if you don't count comments and empty lines :) I don't think even Jango would allow the same with less than 40 lines of script and code combined.

 

blog.springsource.com/2011/09/14/new-application-layering-and-persistence-choices-in-spring-roo/

andrew 25/09/2011 - 13:16

Recently, I was in need to deploy Spring's sample Travel web application on JBoss 5.1. The process of making the deployment pass mainly consisted of solving mismatches between JBoss JPA and the web-application-contained Hibernate. I hope the following description of the steps will help others (diminishing bunch?)  deploy Spring apps on JBoss 5.1.


1. Remove logj jar from your WEB-INF/lib


2. Remove xml-apis jar from your WEB-INF/lib


zvika 10/03/2011 - 16:00

 While reading "AspectJ In Action, 2nd Ed", I ran across the following method of accessing an advised aop proxy from within the proxied class while still activating the aspect functionality:

 

AopContext.currentProxy()

 

 

That's it. Barely worth a post, I know, but may come as great help if you ever used Spring's AOP Wrapping (transactions, caching, ...) and needed to make a self-bound call that should go through the AOP interceptors.

zvika 01/12/2010 - 13:32

This is a summary of the communication methods I’ve employed in an application at one of our clients recently, methods gathered from various other sites, blogs, etc.

 

I’ll start with some basic terminology -

zvika 29/11/2010 - 15:00

Recently I had to find a solution for mocking arbitrary-depth-level beans in Spring tests; when saying "arbitrary-depth-level beans" I mean a situation where, for example, I have the following Autowiring Chain:

 

Test Class -> ServiceA -> ConnectorFactoryBean(Singleton) -> ConnectorBean (Prototype) -> ConnnectionFactory(Singleton) -> Connection (Prototype).

 

During test execution, I'd like to mock the connection factory used by the ConnectorBean, thus opening a fixed-result connection instead of opening a real external data source connection which is not needed by my test, as I'm testing higher level functionality.

Had the object dependency graph been simpler, I could have just injected the mock into the service in the test itself, but that is quite possible, especially as prototype beans are tricky to follow.

 

zvika 17/11/2010 - 12:27
Syndicate content