tag:blogger.com,1999:blog-368809342011-07-28T15:13:23.104-07:00I'm doing an experiment, developing an enterprise application in Java and Ruby in parallel, trying to evaluate whether Ruby is enterprise ready, or Java must still remain my weapon of choice.Eladhttp://www.blogger.com/profile/12617633728938132957noreply@blogger.comBlogger101100tag:blogger.com,1999:blog-36880934.post-76490270080465392962007-01-09T05:54:00.000-08:002007-01-09T05:56:49.335-08:00

As the title suggests, it turns out that using web services with Java is not as simple as you’d expect. Executive Summary: Axis 1.x is no good. I tested Axis2 and in many ways it’s worse. I tried XFire and it’s pretty good, but missing some functionality I needed. Finally, I moved to Sun’s JAX-WS RI (reference implementation), which turned out to be a good solution. The process took way

Eladhttp://www.blogger.com/profile/12617633728938132957noreply@blogger.com6tag:blogger.com,1999:blog-36880934.post-37491727338175934242006-12-11T01:48:00.000-08:002006-12-11T01:49:42.494-08:00

I did a lot of work on our data model the past two weeks, a little with Ruby, a little with Java, and back again. I thought I should share some insights regarding the different approaches they take towards modeling your data, and their pros and cons. In general, with Java and Hibernate you’re supposed to start with the objects, then add the relational mappings. With Ruby on Rails you start with

Eladhttp://www.blogger.com/profile/12617633728938132957noreply@blogger.com16tag:blogger.com,1999:blog-36880934.post-54421722662092448612006-11-30T07:46:00.000-08:002006-11-30T07:51:51.553-08:00

It had to come at some point, I just didn’t expect it so fast.I regret to report that I came across my first hurdle with Rails today.The idea was to quickly finish prototyping my web services (see previous post), so that I could give the client application team a WSDL they can already work with. However, when I took a good look at the WSDL file, I realized that it’s RPC/encoded, rather than the

Eladhttp://www.blogger.com/profile/12617633728938132957noreply@blogger.com5tag:blogger.com,1999:blog-36880934.post-83610167488345849432006-11-29T05:50:00.000-08:002006-11-30T06:58:58.525-08:00

This week we finally began to do some real work. I focused on designing the services I need to expose to the client application, and figured that it could be a great chance to try Rails out as a platform for rapid prototyping. The original plan was to write Java code first, Ruby second, but since I’m pretty comfortable with Rails by now, I figured that I should experiment with the other way

Eladhttp://www.blogger.com/profile/12617633728938132957noreply@blogger.com0tag:blogger.com,1999:blog-36880934.post-48429670916485537662006-11-20T08:05:00.000-08:002006-11-20T08:10:01.951-08:00

So, why am I doing this? I’ve been using Java for nine years now. I never used it exclusively – I wrote lots of code with C, C++ and Delphi, but Java’s always been my bread and butter. Nevertheless, I’ve become more and more disenchanted with it lately. I’m going to skip the Java rants though – an entire book was written about Java’s problems, and Bruce Tate writes better than I do.

Eladhttp://www.blogger.com/profile/12617633728938132957noreply@blogger.com0tag:blogger.com,1999:blog-36880934.post-26888794591132206882006-11-16T06:30:00.000-08:002006-11-16T06:31:44.415-08:00

The first iteration in our project is over, and so is the first part of my experiment. The result: Ruby (Rails actually) wins by knockout! I’ll start with the summary, in case you don’t want to read through the whole story: It took me roughly 1 day to implement with Ruby on Rails what took me roughly a week of coding (net) in Java with Spring/Hibernate/Axis. Actually, that’s not entirely

Eladhttp://www.blogger.com/profile/12617633728938132957noreply@blogger.com0tag:blogger.com,1999:blog-36880934.post-22429668159489093782006-11-08T11:15:00.000-08:002006-11-08T11:18:04.018-08:00

It’s been roughly 2.5 weeks since the beginning of the project’s first iteration, and it’s time for a little progress report. The objectives of this first iteration are rather simple: set up the entire stack and see it in action. On the server side that means a single database table, entity bean, DAO, business logic and a few web services. Those services provide basic RUD functionality for

Eladhttp://www.blogger.com/profile/12617633728938132957noreply@blogger.com0tag:blogger.com,1999:blog-36880934.post-4360808851084956102006-11-05T07:42:00.000-08:002006-11-08T07:58:03.915-08:00

In order to determine in the future whether this experiment has been a success I should set success criteria up front. I gave it some thought, and here’s what I came up with: 1. Interchangeability:I should be able to use either the Java application or the Ruby one interchangeably, without any apparent impact. I could test this by setting up two servers, working with the same database and other

Eladhttp://www.blogger.com/profile/12617633728938132957noreply@blogger.com0tag:blogger.com,1999:blog-36880934.post-1162990727867828352006-11-02T04:56:00.000-08:002006-11-08T05:04:13.880-08:00

We work in four-week long iterations, each of which has some pre-defined deliverables. In each iteration, I’m going to write the Java code first, then implement the same features with Ruby. It may make better sense to code in Ruby first, since it’s supposedly better for rapid prototyping. However, my deliverable as far as my employer’s concerned is the Java app. In other words, I have deadlines

Eladhttp://www.blogger.com/profile/12617633728938132957noreply@blogger.com0tag:blogger.com,1999:blog-36880934.post-1162282698181926332006-10-30T23:49:00.000-08:002006-11-08T05:04:13.822-08:00

My name is Elad Kehat, and I'm a developer for a large ISV.The name of this blog implies it's subject, so I'll go directly to trying to explain why this isn't YARJC:I recently started working on a completely new product, where I'm in charge of ther server side. I'm going to code it twice, in parallel - one time in Java and another in Ruby. So this isn't just a comparison based on the a posteriori

Eladhttp://www.blogger.com/profile/12617633728938132957noreply@blogger.com3