Thanks Thiago. I was just wondering wether doing the integration at the front end, using tapestry for offering rest services, would be easier than the approach i took.
Never did it before, nor i have experience with js client frameworks, that's why i asked . What you have to do is identiftying the requests in the html web app, and call the appropiate ws of the tapestry app, that will return json? On Tue, 02 Aug 2016 14:41:24 -0300, Juan M Garrido de Paz <[hidden email] <http:///user/SendEmail.jtp?type=node&node=5732810&i=0>> wrote: > How is the approach of use tapestry just to offer web services to the > frontend? In this case tapestry just serves json objects? Then you dont > need tapestry components and other features for anything , do you? I dont > see the point of using tapestry in this case. Live class reloading makes your development way faster. > And using tapestry pages instead of web services? Pages here are for > nothing but to hold the event listener method that do the job by calling > the model service, arent they? In this case, yes. > I dont see why to use tapestry as the web framework in this cases, as you > just use it as a middleware to call model services. You dont use pages, > components, zones, etc. You lose using the Tapestry pipelines (specially RequestFilter) for access control, profiling, logging, etc. > Anyway what do you think is better, using tapestry generating the > required front end code? Or using tapestry just to offer the services to > the front > end ? (either by web services or by page listeners). > > Which approach do you prefer? I believe the answer is very dependent on the actual scenario you have to implement, so I won't give any broad answers. I'm just saying that REST services can be done. I'm not saying it's the best solution. -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] <http:///user/SendEmail.jtp?type=node&node=5732810&i=1> For additional commands, e-mail: [hidden email] <http:///user/SendEmail.jtp?type=node&node=5732810&i=2> ------------------------------ If you reply to this email, your message will be added to the discussion below: http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Tapestry-vs-Spring-MVC-REST-Angular-tp5732799p5732810.html To unsubscribe from Apache Tapestry Mailing List Archives, click here <http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2375124&code=anVhbm0uZ2Fycmlkby5wYXpAZ21haWwuY29tfDIzNzUxMjR8LTU2NTA3OTQwOQ==> . NAML <http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
