Hi, I've a few question regarding the changes made. - Firstly, with the changes made, how do I have a method which can now accept both scala Actor as well as a CometActor?? Prior to the changes, I had a function "def registerActor(act: Actor) which could handle both scala Actor as well as CometActor,; now if I change this to "def registerActor(act: GenericActor)" it throws compilation error asking to a type to be specified for the GenericActor. What change would you suggest to have my code compile? - Secondly, I also get compilation error for calling scheduleAtFixedRate method on ActorPing. Says no such method. Has this method been deprecated and if so, what is the method I should be calling instead?
Thanks, Soumik On Oct 22, 10:35 am, Indrajit Raychaudhuri <indraj...@gmail.com> wrote: > Code change should suffice. > > pom.xml updates won't be necessary since lift-util has lift-common as > dependency and your application (which must be having lift-util as > dependency) would resolve the lift-common dependency transitively. > > Cheers, Indrajit > > On 22/10/09 10:57 AM, Jonathan Ferguson wrote: > > > Do we need to update our pom's or should it be code changes only ? > > > Cheers > > > Jono > > > 2009/10/22 David Pollak <feeder.of.the.be...@gmail.com > > <mailto:feeder.of.the.be...@gmail.com>> > > > Folks, > > > As the title of this email indicates, there are breaking changes in > > Lift that just got pushed to master. > > > We've migrated from Scala Actors to Lift Actors and included a > > series of traits that allow Lift to use its own Actors or Akka > > Actors (or anything else that implements that interface.) > > > The two big changes that you'll have to work with are: > > > * Box/Full/Empty/Failure was moved from the > > lift-util/net.liftweb.util package to the > > lift-common/net.liftweb.common package. The reason for this > > change is that we're going to make the lift-common package a > > more generic, non-web related package. It currently contains > > Box and Actor, but in the future may contain other interfaces > > that will have concrete implementations outside of Lift. We > > moved Box there because Box is richer than Scala's Option > > class and being able to carry Exceptions around in a Box while > > still being able to map/flatMap/foreach over a Box (these are > > unavailable for Scala's Either). Some we're going to actively > > promote using Box as a replacement for Option in all Scala > > apps. What this means for you is you have to import > > net.liftweb.common._ in any file that you also import > > net.liftweb.util.? > > * Lift no longer support Scala Actors for Comet Actors. The > > GenericActor API offers pretty much the same client interface > > to Lift's Actors, so ! and !? work the same way. However, > > there's no link, self, start or exit methods. > > > Please do an "mvn -U clean install" on your code and run it against > > the new code. If you have any Comet-related weirdness, please > > report it immediately. We're planning M7 in 2 weeks, so we've got > > lots of time to iron any kinks out of this code. > > > Thanks, > > > David > > > -- > > Lift, the simply functional web frameworkhttp://liftweb.net > > Beginning Scalahttp://www.apress.com/book/view/1430219890 > > Follow me:http://twitter.com/dpp > > Surf the harmonics --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
