News

Trilog eases Domino to Java transition

Trilog Group has rolled out an integrated J2EE development framework designed to let IBM Lotus Notes developers use their existing skills for J2EE development projects.
 
FlowBuilder 3.5 taps web services technologies to reproduce the Domino development model and developer experience for open-standards platforms, according to Trilog officials.

The goal of the framework is to let Domino developers use existing skills to build the same class of collaborative applications, but for newer IBM platforms including Workplace and WebSphere, said David Hughes, Trilog's vice-president of sales and marketing.

With FlowBuilder 3.5, developers do not have to learn Java to work with the J2EE-based platforms, he said.

"We provide a bridge from the Domino world to the J2EE world for Domino developers and Domino solutions. [Domino organisations] need to migrate people and their skills. This enables them to leverage the skills of existing developers and avoid staff re-training and replacement classes," said Hughes.

Using a service-oriented architecture, FlowBuilder 3.5 offers a visual representation of Soap for a point-and-click integration of web services. UDDI and WSDL are also supported.

"FlowBuilder is built upon a visual component-oriented development and assembly model. In 3.5 we have extended this even further to let people integrate web services into their applications in a graphical way," he said.

Additionally, FlowBuilder includes a new Eclipse plug-in that makes the framework available as an Eclipse perspective for Java developers. This lets Java developers seamlessly reuse FlowBuilder's framework services and components, said Trilog.
  
Cathleen Moore writes for InfoWorld
 

 


Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
 

COMMENTS powered by Disqus  //  Commenting policy