"Actually, I thought it would be a good joke to mix Wicket and Tapestry and make some die-hard-Wicket user use Tapestry to fill the IOC gap - instead of Spring and Guice.”
Funniest thing I’ve read in awhile. Thanks for the laugh. Robert > On Apr 22, 2016, at 4:35 AM, Christian Riedel <cr.ml...@googlemail.com> wrote: > > You would only need Tapestry IoC for the builders. > Many moons ago I replaced Spring with Tapestry IoC in a Wicket project: > https://github.com/criedel/WicketTap5IOC > I bet you can find the appropriate hooks in your project to do something > similar! APIs have changed since 5.2 though. > With what framework would you integrate Tapestry? > >> Am 22.04.2016 um 09:27 schrieb Adam X <vbgnm3c...@gmail.com>: >> >>> Why? Just curious. :) >> >> Well, that brings me to my problem. What I'm really after is >> Tapestry's ordered configuration and its chain builder service, so I >> thought I may as well use IOC since I don't think I can split them. Or >> let me ask my question differently. Is Tapestry registry, chain >> builder and ordered configuration in all in the core module? And if >> so, can I just bring in the core module to use it? >> >> My use case is a set of distributed plugins and chain of >> responsibility executing them within the engine of my project. I tried >> apache commons chain but it lacks several features that Tapestry's >> ordered list of chain commands. >> >> So in short, after reading: >> https://tapestry.apache.org/chainbuilder-service.html sounds like it's >> exactly what I need. If I bring in only tapestry core jar, will I get >> this? And if I need Tapestry IOC as well, I would happily replace my >> CDI with IOC. >> >> Adam >> >> On Thu, Apr 21, 2016 at 7:20 PM, Cezary Biernacki <cezary...@gmail.com> >> wrote: >>> I have used Tapestry-IOC in many non-gui tools including REST applications >>> based on Dropwizard, and it is very easy to do. Just in some place during >>> process initialisation build a IOC registry, retrieve some starting service >>> and call that service - later all dependencies can be handled by >>> Tapestry-IOC. I am not aware of any tutorials outside Tapestry website, so >>> ask if you need any more specific help. >>> >>> >>> Best regards, >>> Cezary >>> >>> On Thu, Apr 21, 2016 at 5:20 PM, Thiago H de Paula Figueiredo < >>> thiag...@gmail.com> wrote: >>> >>>> On Thu, 21 Apr 2016 04:18:30 -0300, Adam X <vbgnm3c...@gmail.com> wrote: >>>> >>>> Hi >>>>> >>>> >>>> Hi! >>>> >>>> I have a rest project (no gui) with CDI backed by Weld. I would like to >>>>> switch to Tapestry IOC instead. >>>>> >>>> >>>> Why? Just curious. :) I haven't used CDI so I cannot compare it to >>>> Tapestry-IoC. >>>> >>>> Are there any good tutorials that cover this? >>>>> >>>> >>>> It's mostly the same. Just the way you start the Registry is different. >>>> If http://tapestry.apache.org/starting-the-ioc-registry.html isn't >>>> enough, please let us know. >>>> >>>> -- >>>> Thiago H. de Paula Figueiredo >>>> Tapestry, Java and Hibernate consultant and developer >>>> http://machina.com.br >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>>> For additional commands, e-mail: users-h...@tapestry.apache.org >>>> >>>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org >
