Re: Tapestry Session Service
On Fri, 25 Jan 2013 19:45:31 -0200, Tony Nelson tnel...@starpoint.com wrote: Aren't all the javascript changes in 5.4 going to break compatibility anyways? What server-side backward compatibility has to do with client-side one? Specially in this case, in which someone expected something to be a service because it was in a package named services? The less we break backward compatibility, the better. -- Thiago H. de Paula Figueiredo - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry Session Service
I think Tony wants us to go Gung Ho on the code base. Oh, so tempting, but I think we'll stay the course instead. I'm sure I could build a better IoC and framework than Tapestry 5 now, it's T5+5 years, but that wouldn't prove anything. On Fri, Jan 25, 2013 at 2:16 PM, Thiago H de Paula Figueiredo thiag...@gmail.com wrote: On Fri, 25 Jan 2013 19:45:31 -0200, Tony Nelson tnel...@starpoint.com wrote: Aren't all the javascript changes in 5.4 going to break compatibility anyways? What server-side backward compatibility has to do with client-side one? Specially in this case, in which someone expected something to be a service because it was in a package named services? The less we break backward compatibility, the better. -- Thiago H. de Paula Figueiredo --**--**- To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.orgusers-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
Re: Tapestry Session Service
I don't really want you to go all Gung Ho :). Remember I've been with you since Tapestry 3. I know how you go Gung Ho. I've just already allotted plenty of time in our schedule for the 5.3 to 5.4 upgrade under the guise of Introducing SASS/Coffee. We are heavily invested in tapestry-jquery especially the DataTables integration so any changes there are going to affect my project. As to Theo's comments about the difference between front end or back end changes, it really is immaterial what I'm editing. Java, HTML, JavaScript, heck even groovy. It's still all code that has to be changed. I was just trying to suggest that if you are going to break something, from 5.3 to 5.4 isn't a bad time to consider it. Have a great weekend guys and sorry if I inadvertently poked an old scab. -Tony On Jan 25, 2013, at 8:00 PM, Howard Lewis Ship hls...@gmail.com wrote: I think Tony wants us to go Gung Ho on the code base. Oh, so tempting, but I think we'll stay the course instead. I'm sure I could build a better IoC and framework than Tapestry 5 now, it's T5+5 years, but that wouldn't prove anything. On Fri, Jan 25, 2013 at 2:16 PM, Thiago H de Paula Figueiredo thiag...@gmail.com wrote: On Fri, 25 Jan 2013 19:45:31 -0200, Tony Nelson tnel...@starpoint.com wrote: Aren't all the javascript changes in 5.4 going to break compatibility anyways? What server-side backward compatibility has to do with client-side one? Specially in this case, in which someone expected something to be a service because it was in a package named services? The less we break backward compatibility, the better. -- Thiago H. de Paula Figueiredo --**--**- To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.orgusers-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com Since 1982, Starpoint Solutions has been a trusted source of human capital and solutions. We are committed to our clients, employees, environment, community and social concerns. We foster an inclusive culture based on trust, respect, honesty and solid performance. Learn more about Starpoint and our social responsibility at http://www.starpoint.com/social_responsibility This email message from Starpoint Solutions LLC is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Opinions, conclusions and other information in this message that do not relate to the official business of Starpoint Solutions shall be understood as neither given nor endorsed by it. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry Session Service
On Fri, Jan 25, 2013 at 5:46 PM, Tony Nelson tnel...@starpoint.com wrote: I don't really want you to go all Gung Ho :). Remember I've been with you since Tapestry 3. I know how you go Gung Ho. :) I've just already allotted plenty of time in our schedule for the 5.3 to 5.4 upgrade under the guise of Introducing SASS/Coffee. We are heavily invested in tapestry-jquery especially the DataTables integration so any changes there are going to affect my project. SASS as in sass 3/scss? If so, I'm interested in bringing framework level support for it. There's been some discussion on different approaches, what's your take on it? Kalle
Re: Tapestry Session Service
On Thu, 24 Jan 2013 14:03:52 -0200, Matías Blasi matias.bl...@gmail.com wrote: Hi all! Hi! I'm a little stuck with trying to inject the Tapestry Session Service (org.apache.tapestry.services.Session) Session is not a service nor something that can injected right now. @Inject Request and use its getSession(boolean create) method. If we cannot @Inject the Session, should it be in the .services interfaces package? Not every service is injectable. Not everything that is injectable is a service. -- Thiago H. de Paula Figueiredo - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry Session Service
On Fri, Jan 25, 2013 at 3:10 AM, Thiago H de Paula Figueiredo thiag...@gmail.com wrote: On Thu, 24 Jan 2013 14:03:52 -0200, Matías Blasi matias.bl...@gmail.com wrote: Hi all! Hi! I'm a little stuck with trying to inject the Tapestry Session Service (org.apache.tapestry.services.**Session) Session is not a service nor something that can injected right now. @Inject Request and use its getSession(boolean create) method. If we cannot @Inject the Session, should it be in the .services interfaces package? Not every service is injectable. Not everything that is injectable is a service. I would love to reorganize the Tapestry package structure, but doing so would break backwards compatibility in a large way. Instead, we've taken to using lots of documentation annotations to be more precise about how interfaces are meant to be used. -- Thiago H. de Paula Figueiredo --**--**- To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.orgusers-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
Re: Tapestry Session Service
On Fri, 25 Jan 2013 16:13:18 -0200, Howard Lewis Ship hls...@gmail.com wrote: Not every service is injectable. Not everything that is injectable is a service. I was wrong in the sentence above. Every service is injectable, but not everything in a .services package is a service. A service is something that is configured and obtained through Tapestry-IoC. Session is in .services but isn't configured in Tapestry-IoC as a service. -- Thiago H. de Paula Figueiredo - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
RE: Tapestry Session Service
Aren't all the javascript changes in 5.4 going to break compatibility anyways? -Original Message- From: Howard Lewis Ship [mailto:hls...@gmail.com] Sent: Friday, January 25, 2013 1:13 PM To: Tapestry users Subject: Re: Tapestry Session Service On Fri, Jan 25, 2013 at 3:10 AM, Thiago H de Paula Figueiredo thiag...@gmail.com wrote: On Thu, 24 Jan 2013 14:03:52 -0200, Matías Blasi matias.bl...@gmail.com wrote: Hi all! Hi! I'm a little stuck with trying to inject the Tapestry Session Service (org.apache.tapestry.services.**Session) Session is not a service nor something that can injected right now. @Inject Request and use its getSession(boolean create) method. If we cannot @Inject the Session, should it be in the .services interfaces package? Not every service is injectable. Not everything that is injectable is a service. I would love to reorganize the Tapestry package structure, but doing so would break backwards compatibility in a large way. Instead, we've taken to using lots of documentation annotations to be more precise about how interfaces are meant to be used. -- Thiago H. de Paula Figueiredo --**--**-- --- To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.orgusers-unsubscr...@tapestry.apa che.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com Since 1982, Starpoint Solutions has been a trusted source of human capital and solutions. We are committed to our clients, employees, environment, community and social concerns. We foster an inclusive culture based on trust, respect, honesty and solid performance. Learn more about Starpoint and our social responsibility at http://www.starpoint.com/social_responsibility This email message from Starpoint Solutions LLC is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Opinions, conclusions and other information in this message that do not relate to the official business of Starpoint Solutions shall be understood as neither given nor endorsed by it. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry Session Service
There have been limited server-side changes, nearly all backwards compatible (with a few backwards incompatible changes in neglected corners, unfortunately). If you stick to vanilla Tapestry out of the box, then your Tapestry 5.3 application should work in 5.4, even with the client-side changes. A few components have had minor changes (or removals) of rarely used client-side logic. Also, form validation is always on submit now, never on blur. If you were using code out of the T5 or Tapestry client-side namespaces, you will need to recode a bit. In many cases, things that required JavaScript code in 5.3 can be accomplished with just new data- attributes on elements (possibly, provided by a mixin). The majority of the client-side logic in 5.4 is based on document-level event handlers whose behavior is triggered by data- attributes in specific elements. On Fri, Jan 25, 2013 at 1:45 PM, Tony Nelson tnel...@starpoint.com wrote: Aren't all the javascript changes in 5.4 going to break compatibility anyways? -Original Message- From: Howard Lewis Ship [mailto:hls...@gmail.com] Sent: Friday, January 25, 2013 1:13 PM To: Tapestry users Subject: Re: Tapestry Session Service On Fri, Jan 25, 2013 at 3:10 AM, Thiago H de Paula Figueiredo thiag...@gmail.com wrote: On Thu, 24 Jan 2013 14:03:52 -0200, Matías Blasi matias.bl...@gmail.com wrote: Hi all! Hi! I'm a little stuck with trying to inject the Tapestry Session Service (org.apache.tapestry.services.**Session) Session is not a service nor something that can injected right now. @Inject Request and use its getSession(boolean create) method. If we cannot @Inject the Session, should it be in the .services interfaces package? Not every service is injectable. Not everything that is injectable is a service. I would love to reorganize the Tapestry package structure, but doing so would break backwards compatibility in a large way. Instead, we've taken to using lots of documentation annotations to be more precise about how interfaces are meant to be used. -- Thiago H. de Paula Figueiredo --**--**-- --- To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.orgusers-unsubscr...@tapestry.apa che.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com Since 1982, Starpoint Solutions has been a trusted source of human capital and solutions. We are committed to our clients, employees, environment, community and social concerns. We foster an inclusive culture based on trust, respect, honesty and solid performance. Learn more about Starpoint and our social responsibility at http://www.starpoint.com/social_responsibility This email message from Starpoint Solutions LLC is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Opinions, conclusions and other information in this message that do not relate to the official business of Starpoint Solutions shall be understood as neither given nor endorsed by it. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
Re: Tapestry Session Service
I'm guessing the reason why you can't inject the Session is exactly for the reason you stated - how do you inject it if you don't want it to be created? Can't say I've ever explicitly needed the Session obj myself - see here: http://tapestry.apache.org/session-storage.html As to why it's in the service package - well, I could ask the same of the @Traditional and @Core annotations. I guess because they relate to services if not actually a T5 service themselves. Steve. On 25 January 2013 00:03, Matías Blasi matias.bl...@gmail.com wrote: Hi all! I'm a little stuck with trying to inject the Tapestry Session Service (org.apache.tapestry.services.Session) I simply added in my page: @Inject private Session session; I'm getting: Caused by: java.lang.RuntimeException: No service implements the interface org.apache.tapestry5.services.Session. at org.apache.tapestry5.ioc.internal.RegistryImpl.getServiceByTypeAlone(RegistryImpl.java:664) at org.apache.tapestry5.ioc.internal.RegistryImpl.getServiceByTypeAndMarkers(RegistryImpl.java:684) at org.apache.tapestry5.ioc.internal.RegistryImpl.getService(RegistryImpl.java:643) at org.apache.tapestry5.ioc.internal.ObjectLocatorImpl.getService(ObjectLocatorImpl.java:47) at org.apache.tapestry5.internal.services.ServiceInjectionProvider.provideInjection(ServiceInjectionProvider.java:43) at $InjectionProvider2_ac1a0adc404.provideInjection(Unknown Source) at $InjectionProvider2_ac1a0adc3d0.provideInjection(Unknown Source) at org.apache.tapestry5.internal.transform.InjectWorker$2.run(InjectWorker.java:73) ... 127 more Is there any particular thing with the session service? I was able to get it by injecting the Request service, and asking for the session through it (with no forced creation), and it worked! I browsed into the code, and it is asking for the session to the TapestrySessionFactory service... If we cannot @Inject the Session, should it be in the .services interfaces package? Regards, Matias. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
