How to avoid / solve Spring validation errors ?

I integrated spring IDE plug-ins in my eclipse environment. I wanted use some additional namespaces like camel, CXF and some custom schema to spring.xml, spring beans file. When I tried to validate the spring.xml file the spring IDE it was showing following errors and warnings in "Problems" / "Error Log" view of eclipse

•  Unable to locate Spring Namespace handler...
•  Incorrect usage of element for certain elements ... (The element was refereed form my custom schema)
•  Many errors of Class Not Found.
•  No setter found for property ... (When I am trying to set some property in spring.xml) 

Here, I am going to discuss the approaches I used to solve these issues, read complete article at http://technical-tejash.blogspot.com/2010/03/how-to-avoid-spring-validation-errors.html

Eclipse Tools: Howt to avoid cyclic dependency between 2 plugins without refactoring code

I have encountered a cyclic dependency issue while developing application using eclipse based plug-in development environment. Here I am going to explain the issue, which you might be also encountered during the plug-in development and which would have lead you to re-factorize your code to solve this issue. But here I am going to use extension-point using which I can invoke execute code from another plug-in and get results without adding interdependency between them.

Example:
I have eclipse plug-ins PluginA and PluginB, here PluginB is already dependent on PluginA. Now I have some class method in PluginB, and I would like to execute that method from one of the class in PluginA .
- If we add the dependency of PluginA on PluginB then it would result in cyclic dependency.
- Alternatively, what we can do is to re-factor the code in such a way that this method and relevant calsses moved to PluginA so that it would be available in both PluginA and PluginB, but this solution will be expensive in the well deployed system since it involves lot of testing efforts and it may break, if we missed out something during re-factoring, And there may more such logic should come out and again we need to re-factorize with same process.
- Here, I am going to discuss alternate and permanent solution which can be used for calling method of the class which belong to PluginB form some class of PluginA without adding dependency and avoiding the re-factorization of the code.

Visit http://technical-tejash.blogspot.com/2010/03/eclipse-avoid-cyclic-dependency-between.html for step by step guide about Using extension-point to avoid cyclic dependency between 2 plugins without refactoring code

What's new in FUSE Integration Designer 1.2

A new version of FUSE Integration designer is released last week and there are some new exciting features. Here is a very broad overview of all (well, almost all :-)) new features available.

The latest FUSE Integration designer can be downloaded from http://www.fusesource.com/downloads

Also, now there is no need to install it using Eclipse update site (which is really painful if there are some dependency issues) – but you can still install through the update site esp if want to try FID on unsupported platforms like Mac OS X and 64 bit Ubuntu Linux – the usual disclaimer follows – these are not supported!

Integrated tooling: The new FUSE Integration designer now includes tooling for ActiveMQ and ServiceMix. And all the tools are integrated like deploying EIP projects on ServiceMix, using FUSE Messaging in running an EIP diagram. FID 1.2 is has now a professional (or enterprise :-)) look with new Splash screen, Welcome screen, FUSE perspectives, New File wizards and also some cheat sheets.

New Splash screen for FID 1.2:

Welcome Screen: First time you launch FID

New file menu:

EIP Tooling

• EIP Editor: A completely new (and powerful) graphical editor for EIP patterns. Has a new auto connected layout so that you need not worry about the connections. EIP editor has now a completely different and much clearer theme – new colors, new selection highlight, new breakpoint visualization.
  
  

• EIP editor now supports almost all patterns and processors Camel 1.5 has. The list is too long (check the screen shots). There are some new endpoints added to the tooling – CXF, JBI, SEDA and Mock.

• Run/ Debug improvements: A new preference for Camel Runtime home folder – Run uses this Camel to run the EIP, start the route using FUSE message, and many bug fixes.

• Java DSL: In the preview release of FID (1.1 and 1.0), there is virtually no support for Java DSL. In this release, there is new Java DSL project (even though there is no visual editor or support for enhanced debugging – this might come in future releases), DSL project is quite useful to get start with Java DSL and also you can deploy the Java DSL on FUSE ESB (ServiceMix). Tooling will take care of packaging, deploy and starting the Java DSL.
• New Expression Editor: There is now a new Expression editor that supports all the languages (including Bean expressions) by Camel.
  
  

FUSE ESB tooling

• WTP Server integration: ServiceMix server is now integrated with WTP Server's framework. Now, we can start, stop, restart, publish projects on ServiceMix server from a single view.

• FUSE ESB tooling support both 3.x and 4.x versions. ServiceMix console is integrated with Eclipse Console view.

• Supports deploying EIP project, Java DSL project and also CXF projects on both FUSE ESB 3.x and FUSE ESB 4.x versions.

Messaging tooling

Like FUSE ESB tooling, this is also a completely new tooling added in FID 1.2.

• New Messaging project: Useful to store all the messages and sender and listeners in a single project.

• Send and/or Listen to a Queue and/or Topic: Can send a message to a topic or queue in a local or remote ActiveMQ server. Also, we store the messages received.

• Send different types of messages like XML message, Text message, Message with Headers.

• Add or Remove JMS header properties using Message editor

Web Services Tooling

• New Annotation view: Now it is very easy add JAX-WS annotations to Java file using Annotation view.

• Multiple deployment options: A CXF project can now be deployed on Tomcat (3.x, 4.x, 5.x, 6.x) and also on FUSE ESB (ServiceMix) service.

With lot of new features and improvements to existing tools in the new FUSE Integration designer, I like you to take a look by downloading it from http://fusesource.com/.

What's new in FID 1.1

FUSE Integration Designer (FID) is a graphical editor for Camel Spring XML files.
Current version of FID (1.0) can be download from FUSE Source
The next version FID 1.1 - which is yet to be released - has lot of new features, enhancements and bug fixes.

Here is brief outline of new features in FID 1.1

1. New Patterns added:
   
1. Routing Slip
2. Splitter
3. Recipient List
4. Aggregator
5. Resequencer
2. New Endpoints:
1. Jetty Component
3. FID is migrated to the latest Eclipse version (i.e, 3.4.1)
4. Improvements to launch configurations
1. Run/Debug configuration now has a new Classpath tab (see the screen shot below). Components that require external jars files like for example JMS component requires ActiveMQ libraries can be given here.
5. Importing Camel XML files
1. Import camel xml files is now integrated to Eclipse Import wizard. It is now possible to import Camel XML files that are not present in the workspace.
   
6. Support for Error handling
1. A new tab called "Advanced Properties" is added to all Patterns and user can provide the error handler bean ref in that tab. For more information about Error Handling have a look at Camel documentation
   

However this is not a complete list - lot of bug fixes, minor enhancements - check the complete list of bugs fixed in 1.1 at http://fusesource.com/issues/secure/Dashboard.jspa

Classpath Tab in Launch configuration:


Error Handler Ref for patterns


Screenshot of FID editor