Re: Splitting Tapestry IOC out as a separate project
Try Tynamo Resteasy! I think you'll like it. We use it to support a extjs front end we have (served in its raw form (html and js) as part of a Tapestry web application. We jave tapestry pages working right alongside the raw html/js page. Even better is that our rest resources use the same services that our tapestry pages use! On Oct 2, 2014 11:10 AM, "Thiago H de Paula Figueiredo" wrote: > On Thu, 02 Oct 2014 11:38:39 -0300, wrote: > > I expect to use something like Jersey to support a REST API (both >> internal and external) instead of Tapestry pages to handle requests. >> > > Ok! Just giving an suggestion. :) Have you seen > http://tynamo.org/tapestry-resteasy+guide? > > Perhaps I worded my question incorrectly. I’m really wondering if IOC >> will always be tied to Tapestry core in terms of releases, or will it be >> spun off into its own self-contained project with a release cycle >> independent of Tapestry core? >> > > We have no plans of spinning it off nor having a independent release cycle > because, so far, we haven't felt the need for that. Tapestry-IoC is mature > and very flexible, so almost all new features you could think won't need > changes to T-IoC code itself, so they can be implemented in separate > projects. In the last years, the only major changes were live class > reloading for services and copying service implementation class annotations > to its proxies (both at class- and method-level). For example, I've > implemented the support of JCache (JSR 107) annotations as a separate > projects because since the latest betas it didn't need anything > Tapestry-IoC already provides. In addition, nothing prevents us from > generating a new Tapestry release because of a Tapestry-IoC new feature or > improvement. > > Any suggestions on how to improve Tapestry-IoC? We'd love to hear them. :) > > -- > 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 > >
Re: Splitting Tapestry IOC out as a separate project
On Thu, 02 Oct 2014 11:38:39 -0300, wrote: I expect to use something like Jersey to support a REST API (both internal and external) instead of Tapestry pages to handle requests. Ok! Just giving an suggestion. :) Have you seen http://tynamo.org/tapestry-resteasy+guide? Perhaps I worded my question incorrectly. I’m really wondering if IOC will always be tied to Tapestry core in terms of releases, or will it be spun off into its own self-contained project with a release cycle independent of Tapestry core? We have no plans of spinning it off nor having a independent release cycle because, so far, we haven't felt the need for that. Tapestry-IoC is mature and very flexible, so almost all new features you could think won't need changes to T-IoC code itself, so they can be implemented in separate projects. In the last years, the only major changes were live class reloading for services and copying service implementation class annotations to its proxies (both at class- and method-level). For example, I've implemented the support of JCache (JSR 107) annotations as a separate projects because since the latest betas it didn't need anything Tapestry-IoC already provides. In addition, nothing prevents us from generating a new Tapestry release because of a Tapestry-IoC new feature or improvement. Any suggestions on how to improve Tapestry-IoC? We'd love to hear them. :) -- 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
Re: Splitting Tapestry IOC out as a separate project
I expect to use something like Jersey to support a REST API (both internal and external) instead of Tapestry pages to handle requests. Perhaps I worded my question incorrectly. I’m really wondering if IOC will always be tied to Tapestry core in terms of releases, or will it be spun off into its own self-contained project with a release cycle independent of Tapestry core? — Sent from Mailbox On Thu, Oct 2, 2014 at 9:21 AM, Thiago H de Paula Figueiredo wrote: > On Thu, 02 Oct 2014 01:14:27 -0300, raygarsta...@gmail.com > wrote: >> Just curious - are there any plans to carve out the IOC portion of >> Tapestry and release that as a separate project? Since I’m moving >> towards client-side frameworks (such as angular and ember) for future >> projects, I don’t have much need for TML, page, and component-related >> logic. But, I’m quite find of Tapestry IOC. I suspect this approach >> will become more common over time. > Tapestry-IoC is a separate project (as in separate source code tree in SVN > then Git) and JAR since it was born, around 7.5 years ago. See > http://search.maven.org/#search%7Cgav%7C3%7Cg%3A%22org.apache.tapestry%22%20AND%20a%3A%22tapestry-ioc%22. > > What made you think it was a part of tapestry-core (the web framework)? > Even using client-side frameworks, you still need something on the > server-side to receive and respond to requests, so you can still use > Tapestry pages for it, or at least the Tapestry request pipelines. > And yes, Tapestry-IoC is awesome! :D > -- > 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
Re: Splitting Tapestry IOC out as a separate project
On Thu, 02 Oct 2014 01:14:27 -0300, raygarsta...@gmail.com wrote: Just curious - are there any plans to carve out the IOC portion of Tapestry and release that as a separate project? Since I’m moving towards client-side frameworks (such as angular and ember) for future projects, I don’t have much need for TML, page, and component-related logic. But, I’m quite find of Tapestry IOC. I suspect this approach will become more common over time. Tapestry-IoC is a separate project (as in separate source code tree in SVN then Git) and JAR since it was born, around 7.5 years ago. See http://search.maven.org/#search%7Cgav%7C3%7Cg%3A%22org.apache.tapestry%22%20AND%20a%3A%22tapestry-ioc%22. What made you think it was a part of tapestry-core (the web framework)? Even using client-side frameworks, you still need something on the server-side to receive and respond to requests, so you can still use Tapestry pages for it, or at least the Tapestry request pipelines. And yes, Tapestry-IoC is awesome! :D -- 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
Re: Splitting Tapestry IOC out as a separate project
Tapestry IOC is a separate module and can be used standalone. On 2 Oct 2014 06:38, "raygarsta...@gmail.com" wrote: > Just curious - are there any plans to carve out the IOC portion of > Tapestry and release that as a separate project? Since I’m moving towards > client-side frameworks (such as angular and ember) for future projects, I > don’t have much need for TML, page, and component-related logic. But, I’m > quite find of Tapestry IOC. I suspect this approach will become more > common over time. > > — > Sent from Mailbox
Splitting Tapestry IOC out as a separate project
Just curious - are there any plans to carve out the IOC portion of Tapestry and release that as a separate project? Since I’m moving towards client-side frameworks (such as angular and ember) for future projects, I don’t have much need for TML, page, and component-related logic. But, I’m quite find of Tapestry IOC. I suspect this approach will become more common over time. — Sent from Mailbox
