If you are looking for developers with Scala and/or lift experience, I'd suggest asking on the lift list (http://groups.google.com/group/liftweb?pli=1). It is a very active list or ask David Pollack directly.
If you wish, I can introduce you to David. D. On Sat, Feb 6, 2010 at 10:31 PM, Uday Subbarayan <[email protected]> wrote: > Hi Ethan, > Thanks. I am not wed to any one language/platform. But when designing > new products, I need to understand the pros & cons of each & well. > > As I said, I like ESME.But forming an engineering team with Scala expertise > is going to be challenging. > > Best, > -Uday. > > ------------------------- > > I do not blog but e-write: > > http://uds-web.blogspot.com > > --- On Sat, 2/6/10, Ethan Jewett <[email protected]> wrote: > > From: Ethan Jewett <[email protected]> > Subject: Re: Class Diagram > To: [email protected] > Date: Saturday, February 6, 2010, 5:40 PM > > Hi Uday, > > It is complicated, isn't it :-) Scala has some conventions that were a > bit confusing for me, coming from other pure object-oriented and > functional languages. None of those languages were Java, so that may > have been part of the problem :-) In order to pick up ESME, I found > it very helpful to first read a complete introductory Scala book. > > However, the real point of this email is a word of warning: If you are > trying to understand ESME from the angle of the class hierarchy, you > aren't going to get there. The reason is that ESME is a messaging > system and for pretty much all message operations ESME uses an actor > model to manage interactions in a scalable manner. > > Understanding the classes (under the "model" folder) will help you > understand the objects ESME uses, but you'll have to understand the > actors (in the "actor" folder) in order to see how ESME does anything > with these objects. I started a basic diagram of the actor model ESME > uses on the wiki, which you might find helpful: > http://cwiki.apache.org/confluence/display/ESME/Actor+Model > > Cheers! > Ethan > > On Sat, Feb 6, 2010 at 10:25 AM, Uday Subbarayan > <[email protected]> wrote: >> I totally agree with you- this is not the place to discuss about language.. >> >> I was trying to learn internals of ESME and as you said, this is very >> complicated code. I also noticed some 40+ jar's are included in the war!! >> >> I like ESME and if i can't learn the code structure, then it will be risk to >> use in a product. Maintenance will be challenging. I am looking around to >> see if i can find a light weight ESME or roll up my own. >> >> Best, >> Uday. >> >> ------------------------- >> >> I do not blog but e-write: >> >> http://uds-web.blogspot.com >> >> --- On Sat, 2/6/10, Vassil Dichev <[email protected]> wrote: >> >> From: Vassil Dichev <[email protected]> >> Subject: Re: Class Diagram >> To: [email protected] >> Date: Saturday, February 6, 2010, 7:46 AM >> >> Regarding the UML diagram, if code is gerenated from the UML, then it >> *might* make sense. If not, practice shows that the diagram will be >> always outdated. >> >> Analyzing Scala code is fairly complicated because of Scala's >> extensibility. Besides, Scala is evolving fast and the syntax is a >> moving target. I doubt there are any tools which can generate an UML >> diagram from Scala code. >> >> As for opinions about the Scala language, Richard is right- this is >> not the rigth place to discuss language viability. Most folks >> concentrate on an in-depth analysis of what features they don't like >> in Scala rather than trying to guess whether Scala will succeed. Note >> that many people claimed that Java would be a failure some 10-15 years >> ago- these things are not easy to predict. >> >> >> On Sat, Feb 6, 2010 at 6:22 AM, Richard Hirsch <[email protected]> wrote: >>> On Fri, Feb 5, 2010 at 4:44 PM, Uday Subbarayan >>> <[email protected]> wrote: >>>> Ok. I like the high level design of ESME. It's a good product. >>>> >>>> Since it's written in Scala, I don't know the internals. I don't even know >>>> whether Scala can survive in the long run. I just wrote a blog about it- >>>> http://uds-web.blogspot.com/2010/02/what-is-scala.html >>> >>> If you have questions about scala and its merits, I'd suggest looking >>> here: http://www.scala-lang.org/. There are a series of excellent >>> blogs about the new language and a comparison with other languages. >>> One of the advantages is its compactness. >>> >>> D. >>> >>>> Best, >>>> -Uday. >>>> >>>> ------------------------- >>>> >>>> I do not blog but e-write: >>>> >>>> http://uds-web.blogspot.com >>>> >>>> --- On Fri, 2/5/10, Richard Hirsch <[email protected]> wrote: >>>> >>>> From: Richard Hirsch <[email protected]> >>>> Subject: Re: Class Diagram >>>> To: [email protected] >>>> Date: Friday, February 5, 2010, 6:15 AM >>>> >>>> Not yet. Definitely would be good to have. >>>> >>>> I'll look for some tool that generates a class diagram from existing scala >>>> code >>>> >>>> On Fri, Feb 5, 2010 at 4:46 AM, Uday Subbarayan >>>> <[email protected]> wrote: >>>>> Is there a class/uml diagram for the server? >>>>> >>>>> Thanks, >>>>> Uday. >>>>> >>>>> ------------------------- >>>>> >>>>> I do not blog but e-write: >>>>> >>>>> http://uds-web.blogspot.com >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >> >> >> >> > > > >
