David, Go for it, Dude! Who knows, you might come up with something new. With a Scala encoding as the 'informal spec' i can tell you what semantics are already out there and how yours compares.
Best wishes, --greg On Mon, Aug 17, 2009 at 11:19 AM, David Pollak < [email protected]> wrote: > > > On Mon, Aug 17, 2009 at 10:37 AM, Meredith Gregory < > [email protected]> wrote: > >> Dear David, >> >> *This* is a can of night-crawlers. Do you have a specification of the >> abstract syntax of your flow language? Do you have a semantics? > > > No & No. Flying by the seat of my pants (as usual). Always happy for > pointers to the works of people with bigger brains than me. > > >> >> >> Best wishes, >> >> --greg >> >> On Mon, Aug 17, 2009 at 10:20 AM, David Pollak < >> [email protected]> wrote: >> >>> >>> >>> On Mon, Aug 17, 2009 at 9:25 AM, Derek Chen-Becker < >>> [email protected]> wrote: >>> >>>> I think that that's a general issue with SOAP, not particular to Lift ;) >>>> >>>> >>>> On Sat, Aug 15, 2009 at 1:04 PM, Timothy Perrett >>>> <[email protected]> wrote: >>>> >>>>> >>>>> Id be interested to hear those stories... all the ones i've heard so >>>>> far that involve anything to do with SOAP have usually been tales of >>>>> woe ;-) >>>>> >>>> >>> With Goat Rodeo, you can define message flow with an abstract source >>> (input) and sink (output) in the form: >>> >>> Foo %> Bar %> (Baz * Distribution) >>> >>> You can define fork/join constructs, tee constructs, etc. in the high >>> level flow description. The flow description defines the type-safe >>> progression from each logic unit. The location of each logic unit and the >>> threading/transport model is decided at runtime. This means that you can >>> define logic models and plug in an "Akka distribution and threading" >>> strategy for production or a "single threaded" strategy for your local test >>> harness. >>> >>> You'll also be able to register the composed modules that can be composed >>> into larger flows. >>> >>> So, how does this work with SOAP? Well.. the SOAP piece is just a source >>> and sink for the logic flow. >>> >>> >>> >>>> >>>>> Cheers, Tim >>>>> >>>>> On Aug 15, 6:47 pm, David Pollak <[email protected]> >>>>> wrote: >>>>> > I think there will be an important Goat Rodeo/Lift/SOAP story that >>>>> I'll be >>>>> > able to tell in a week or so... integrating WS into Lift (rather than >>>>> > running on the side) will, I think, have benefits. >>>>> > >>>>> > On Sat, Aug 15, 2009 at 9:45 AM, Timothy Perrett >>>>> <[email protected]>wrote: >>>>> > >>>>> > > Sounds like a classic situation.... what is technically possible is >>>>> > > one thing but what you should do to preserve your sanity is most >>>>> > > probably another ;-) >>>>> > >>>>> > > Good luck! >>>>> > >>>>> > > Cheers, Tim >>>>> > >>>>> > > On Aug 15, 4:29 am, Meredith Gregory <[email protected]> >>>>> wrote: >>>>> > > > Tim, Viktor, >>>>> > >>>>> > > > Thanks for the insights and sharing of experience. i'm in a >>>>> situation >>>>> > > where >>>>> > > > i'm working with legacy stuff. i was just wondering how deeply >>>>> into lift >>>>> > > i >>>>> > > > could push the WSDL-based Java handlers. >>>>> > >>>>> > > > Best wishes, >>>>> > >>>>> > > > --greg >>>>> > >>>>> > > > On Fri, Aug 14, 2009 at 2:54 PM, Timothy Perrett >>>>> <[email protected] >>>>> > > >wrote: >>>>> > >>>>> > > > > I agree with Viktor - in a similar vein, this is exactly what I >>>>> > > > > implemented with Akka; the servlet runs in conjunction with >>>>> lifts >>>>> > > > > filter and lift just hands off stuff it doesnt know what to do >>>>> with. >>>>> > > > > So if you want to use AxisServlet or whatever its real easy. >>>>> > >>>>> > > > > From my point of view, you'd need a good reason to bring the >>>>> SOAP >>>>> > > > > stuff into lift; right now i havent found one... I write a lot >>>>> of lift >>>>> > > > > apps that consume SOAP services, but as yet have no good reason >>>>> to >>>>> > > > > write a SOAP serving app with lift - If i were to do one, id do >>>>> > > > > exactly as with the JAX-RS stuff in Akka and >>>>> passNotFoundToChain. >>>>> > >>>>> > > > > Cheers, Tim >>>>> > >>>>> > > > > On Aug 14, 10:24 pm, Viktor Klang <[email protected]> >>>>> wrote: >>>>> > > > > > Gregory, >>>>> > >>>>> > > > > > Depending on what WS-* stuff you're using, you _should_ be >>>>> able to >>>>> > > wire >>>>> > > > > the >>>>> > > > > > AxisServlet in web.xml under /ws/* or something like that, >>>>> and then >>>>> > > have >>>>> > > > > > lift passNotFoundToChain=true >>>>> > >>>>> > > > > > But I guess it boils down to what liftiness you're planning >>>>> to do. >>>>> > > Can >>>>> > > > > you >>>>> > > > > > elaborate a bit on what you're aiming for? >>>>> > >>>>> > > > > > On Fri, Aug 14, 2009 at 9:00 PM, Meredith Gregory >>>>> > > > > > <[email protected]>wrote: >>>>> > >>>>> > > > > > > Tim, Viktor, >>>>> > >>>>> > > > > > > Do you wire your SOAP services into lift or do you keep >>>>> that >>>>> > > > > independent? i >>>>> > > > > > > was just talking to DPP and according to him it appears you >>>>> can >>>>> > > > > successfully >>>>> > > > > > > wire WS-generated code anywhere along in the http-request >>>>> > > processing >>>>> > > > > > > pipeline. He pointed out a gotcha that i think can be >>>>> circumvented >>>>> > > with >>>>> > > > > > > HttpServletResponse trampoline. Both lift and the >>>>> WS-generated code >>>>> > > are >>>>> > > > > > > likely to want to be in the driver's seat regarding who's >>>>> returning >>>>> > > the >>>>> > > > > > > bytes. But, i think you can just fool the WS-generated code >>>>> into >>>>> > > > > thinking >>>>> > > > > > > it's got an HttpServletResponse that is really a widget >>>>> that will >>>>> > > just >>>>> > > > > write >>>>> > > > > > > into the one lift returns. In this way you can write a >>>>> > > 1-size-fits-all >>>>> > > > > > > return adapter. Is this what you guys are doing, or am i >>>>> making >>>>> > > this >>>>> > > > > too >>>>> > > > > > > complicated? >>>>> > >>>>> > > > > > > Best wishes, >>>>> > >>>>> > > > > > > --greg >>>>> > >>>>> > > > > > > -- >>>>> > > > > > > L.G. Meredith >>>>> > > > > > > Managing Partner >>>>> > > > > > > Biosimilarity LLC >>>>> > > > > > > 1219 NW 83rd St >>>>> > > > > > > Seattle, WA 98117 >>>>> > >>>>> > > > > > > +1 206.650.3740 >>>>> > >>>>> > > > > > >http://biosimilarity.blogspot.com >>>>> > >>>>> > > > > > -- >>>>> > > > > > Viktor Klang >>>>> > >>>>> > > > > > Rogue Scala-head >>>>> > >>>>> > > > > > Blog: klangism.blogspot.com >>>>> > > > > > Twttr: viktorklang >>>>> > >>>>> > > > -- >>>>> > > > L.G. Meredith >>>>> > > > Managing Partner >>>>> > > > Biosimilarity LLC >>>>> > > > 1219 NW 83rd St >>>>> > > > Seattle, WA 98117 >>>>> > >>>>> > > > +1 206.650.3740 >>>>> > >>>>> > > >http://biosimilarity.blogspot.com >>>>> > >>>>> > -- >>>>> > Lift, the simply functional web frameworkhttp://liftweb.net >>>>> > Beginning Scalahttp://www.apress.com/book/view/1430219890 >>>>> > Follow me:http://twitter.com/dpp >>>>> > Git some:http://github.com/dpp >>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> -- >>> Lift, the simply functional web framework http://liftweb.net >>> Beginning Scala http://www.apress.com/book/view/1430219890 >>> >>> Follow me: http://twitter.com/dpp >>> Git some: http://github.com/dpp >>> >>> >>> >> >> >> -- >> L.G. Meredith >> Managing Partner >> Biosimilarity LLC >> 1219 NW 83rd St >> Seattle, WA 98117 >> >> +1 206.650.3740 >> >> http://biosimilarity.blogspot.com >> >> >> > > > -- > Lift, the simply functional web framework http://liftweb.net > Beginning Scala http://www.apress.com/book/view/1430219890 > Follow me: http://twitter.com/dpp > Git some: http://github.com/dpp > > > > -- L.G. Meredith Managing Partner Biosimilarity LLC 1219 NW 83rd St Seattle, WA 98117 +1 206.650.3740 http://biosimilarity.blogspot.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
