tag:blogger.com,1999:blog-4110180.post114343309081620940..comments2023-06-20T05:31:24.545-07:00Comments on Tapestry Central: New version of tapestry-springAnonymoushttp://www.blogger.com/profile/04486596490758986709noreply@blogger.comBlogger13125tag:blogger.com,1999:blog-4110180.post-77510734830402724372009-04-10T18:21:00.000-07:002009-04-10T18:21:00.000-07:00I ran some tests, with a prototype and a session b...I ran some tests, with a prototype and a session bean - and it looks like the documentation is correct. @Inject appears to cache and WebApplicationContext works correctly.Mahesh Lavannishttps://www.blogger.com/profile/06040659424710076459noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-17316877490915806212009-04-10T16:04:00.000-07:002009-04-10T16:04:00.000-07:00Hi Howard - does that mean, in T5, I can use @Inje...Hi Howard - does that mean, in T5, I can use @Inject for non-singleton spring beans? <BR/><BR/>Because I read the documentation:<BR/>http://tapestry.apache.org/tapestry5/tapestry-spring/<BR/><BR/>And it says (I quote):<BR/>For the moment, you should consider the non-singleton beans to be not-injectable. Instead, inject the WebApplicationContext service and obtain the non-singleton beans as needed.Mahesh Lavannishttps://www.blogger.com/profile/06040659424710076459noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-5617561550438825982009-04-10T14:56:00.000-07:002009-04-10T14:56:00.000-07:00Mahesh -- this is an old posting for Tapestry 4. T...Mahesh -- this is an old posting for Tapestry 4. Tapestry 5 has Spring compatibility built right in, via the tapestry-spring module.Anonymoushttps://www.blogger.com/profile/04486596490758986709noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-6644996774426003732009-04-10T14:49:00.000-07:002009-04-10T14:49:00.000-07:00Guys, what version of spring-tapestry do I specify...Guys, what version of spring-tapestry do I specify in my pom dependency to get the @injectSpring annotation? I am using 5.0.18 and it does not seem to contain this annotation. TIA.Mahesh Lavannishttps://www.blogger.com/profile/06040659424710076459noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1153064998527351042006-07-16T08:49:00.000-07:002006-07-16T08:49:00.000-07:00Do you know of a way to access HiveMind services f...Do you know of a way to access HiveMind services from Spring? For exmple, I often want access to tapestry.services.External to generate external URLs.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1145111735508429292006-04-15T07:35:00.000-07:002006-04-15T07:35:00.000-07:00No! What you do is define a HiveMind service that...No! What you do is define a HiveMind service that is the factory for the ASO, and you inject dependencies into that factory, which can then pass the dependencies to the ASO. HiveMind proxies are serializable (even if the underlying service implementation is not).Anonymoushttps://www.blogger.com/profile/04486596490758986709noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1144945077530428032006-04-13T09:17:00.000-07:002006-04-13T09:17:00.000-07:00If you have an investment in Spring, or are using ...If you have an investment in Spring, or are using the many great Spring libraries, then use Spring! This is a keen demonstration of the power of open source and POJOs ... it all just works together no muss, no fuss.Anonymoushttps://www.blogger.com/profile/04486596490758986709noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1144943723056008982006-04-13T08:55:00.000-07:002006-04-13T08:55:00.000-07:00It is working well for me, very easy to integrate....It is working well for me, very easy to integrate... set up the spring context via the listener in web.xml, add tapestry-spring .jar to WEB_INF/lib and start using the new annotation. Its not that I don't like hivemind, but when I am trying to add a web interface to a springified app, it just seems like a whole lot of extra work and duplicated configuration to inject service objects via hivemindAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1143609650425464262006-03-28T21:20:00.000-08:002006-03-28T21:20:00.000-08:00liigo -- please re-read the posting. There's a who...liigo -- please re-read the posting. There's a whole lifecycle issue with Spring that makes it not (always) work well with @InjectObject. Thus the need for @InjectSpring.Anonymoushttps://www.blogger.com/profile/04486596490758986709noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1143600216899875572006-03-28T18:43:00.000-08:002006-03-28T18:43:00.000-08:00hi, howard:at the last line, you use:<inject pr...hi, howard:<BR/><BR/>at the last line, you use:<BR/><BR/><inject property="myProperty" type="spring" object="mySpringBean"/><BR/><BR/>why not:<BR/><BR/><inject property="myProperty" object="spring:mySpringBean"/>Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1143481344103580242006-03-27T09:42:00.000-08:002006-03-27T09:42:00.000-08:00Thanks Howard!Thanks Howard!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1143445600538514382006-03-26T23:46:00.000-08:002006-03-26T23:46:00.000-08:00Well, @InsertObject is geared towards objects obta...Well, @InsertObject is geared towards objects obtained from HiveMind. HiveMind objects (that is, services and configurations) do their lifecycle on the inside, so it makes sense to only obtain them once. Spring beans have a different lifecycle, so a different kind of property injection is a good solution, and one that doesn't keep you waiting for release 4.0.1.Anonymoushttps://www.blogger.com/profile/04486596490758986709noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1143433670143045082006-03-26T20:27:00.000-08:002006-03-26T20:27:00.000-08:00Why isn't it possible to keep using object="spring...Why isn't it possible to keep using object="spring:userManager"? It seems like it should just be a matter of parsing the string instead of needing a new attribute.Matt Raiblehttps://www.blogger.com/profile/12657001730061724355noreply@blogger.com