Rob Windsor on WCF with REST, JSON and RSS
WCF is not just for SOAP based services and can be used with popular protocols like RSS, REST and JSON. Join Rob Windsor as he introduces WCF 3.5 and its new native support for non-SOAP services.
Tracking change and innovation in the enterprise software development community
Posted by Mark Figley on Jul 31, 2007 04:14 PM
Lifehacker, a popular personal productivity blog site, recently announced that OpenOffice would be using Groovy for their user facing macro/scripting language, the equivalent of VB/VBA in MS Office:Free OpenOffice extension Groovy makes it possible to record and run Macros in OpenOffice. Don't confuse Groovy for a cheap Visual Basic knockoff. Groovy has its own syntax similar to bash mixed with Java. If you were sticking to Microsoft Office solely for its macro capabilities, you may be able to break away with Groovy. Unfortunately, Groovy is not nearly as beginner friendly as VB/VBA. However, beginners will have no problem getting started with simple macros. Groovy is a free extension for all platforms with OpenOffice.For Architects there are a couple of things that are really interesting about this post:
If nothing else, it is interesting to note that because of the OpenOffice integration Groovy my gain a whole new class of users that understand Groovy from a completely different perspective than your typical Java developer would. But from an Enterprise Architecture perspective, the application platform implications are more significant. For a long time Microsoft has been positioning it’s office suite as a rich client platform upon which power users can develop workgroup support applications that can integrate with backend applications, business services and databases. For Java shops there have always been issues with embracing that strategy because many Java shops aren’t fluent with the Microsoft stack. Now Groovy is giving OpenOffice the ability to compete with Microsoft in this space, and because of Groovy’s native integration with Java, OpenOffice/Groovy may now become even better positioned than MS Office as a rich client stack for Java shops.
A Layered Approach to Creating Business Agility with SOA
Efffective Design, DSLs in Practice, DDD, Cloud Computing and more tracks @ QCon SF Nov 19-21
The Agile Business Analyst: Skills and Techniques needed for Agile
Mmm. Functionally, it sounds great. But I can imagine the memory usage and performance being "less than spectacular", which might just annoy all those influential power business users, undoing all the good work in a stroke unfortunately.
Not that I have tried this in OpenOffice, but in general... Groovy's performance is more than adequate for scripting applications, and I imagine memory would be a non-issue for anyone with more than 512MB of RAM. I'd be interested to hear first impressions of anyone who's actually tried it.
Why can't we use JavaScript? If we use Rhino based JavaScript engine, we have all power of Java with easy usability of javascript. Any one out there to listen?
JavaScript has no such powerfull language capabilities like Groovy has. Also Groovy uses power of JVM HotSpot throught compilation to bytecode.
Vadim, could you elaborate? What features are missing?
Groovy`s superiority - the JVM backend (HotSpot compilation and powerfull JDK) + much of language features (OOP, Clousers, native collections support, etc), that makes your code more readable, clear and easy to support.
WCF is not just for SOAP based services and can be used with popular protocols like RSS, REST and JSON. Join Rob Windsor as he introduces WCF 3.5 and its new native support for non-SOAP services.
Christophe Coenraets discusses Flex 3, Flex Builder, AIR, BlazeDS, Adobe and open source, integrating Flex with existing applications, and integrating RIAs with search engines and browsers.
Danijel Arsenovski attempts to dispel some of the myths around refactoring and how it applies to .NET developers.
In this presentation, recorded at QCon San Francisco, CORBA guru Steve Vinoski explains REST from the view of someone who comes to SOA from a traditional, RPC-oriented background.
Feature teams are key to scaling agility for large teams. In an excerpt from "Scaling Lean and Agile Development," Larman & Vodde show how feature teams resolve traditional problems & raise new issues
Billy Newport talks about virtualization, eXtreme Transaction Processing (XTP) and WebSphere Virtual Enterprise. He discusses hardware, hypervisor, JVM, application and data virtualization.
While virtualization provides many benefits, security can not be a forgotten concept in its application.
This session is specifically aimed at traditionally trained project managers who are new to Agile, and who would like to be able to relate the PMI's best practices to their Agile equivalents.
7 comments
Reply