Re: [ANN] Tapestry IOC for Wicket
Hi, Correct me if i am wrong but wicket and tapestry are based on different philosophies. Tapestry IOC is the recognition by tapestry that there are certain services that are presentation services and require an exclusive support in the presentation layer. That does not mean that tapestry IOC cannot be used in other layers but the mere inclusion of an IOC into tapestry web-framework broadly speaks of the recognition. Also tapestry's internal design is based on IOC (it avoids inheritance as much as possible.) and that is what tapestry promotes. Wicket, on the other hand, is more close to swing. It is more about inheritance than ioc. Rather there is no use of IOC in the internals. It is pure and pure inheritance. These is no concept of presentation services, everything is inheritance. The difference between these two frameworks is clearer when one looks into the implementation of jasper report support implementation for the two frameworks. When one embraces a framework, the philosophy comes with it and as a wicket user I don't see any need for Tapestry IOC in my presentation layer and even if there is I have spring & guice. Alternatively as a tapestry user I find little need for inheritance when I have the pleasure of injecting services, environmental etc. Now I am more of a tapestry user but still when i think as a wicket user i find these services as not part of its philosophy.. I hope I have brought some of the wicket user's point of view into picture. regards Taha On Mon, Nov 22, 2010 at 8:56 PM, Christian Riedel wrote: > > > > >> Could it help Tapestry to find adoption in the Wicket-world? > > > > I don't think so. Both frameworks have similarities (components and pages > treated as objects), but very different approaches. > > The web-frameworks have different approaches, yes, but Wicket has no own > IOC module. What I see is that a Wicket user has the choice between Spring > and Guice for DI. > > People do mostly evaluate both, Tapestry and Wicket, don't they? So in the > future they could see a third DI provider, which is fortunately part of one > of the frameworks they are just evaluating... > I find that being a psychological advantage to have a Tapestry (IOC) > integration for Wicket (and possibly other frameworks, too). You could read > it as "Tapestry is so advanced you can use it everywhere" or "Development > with Tapestry means to have no need for more web frameworks...". I mean we > have to advertise it a little more :-) It's such a huge advantage to have > that perfectly fitting IOC framework shipped with the web-framework. > > The basic integration was actually very very simple. Much simpler than > Spring's or Guice's. It's just missing @CommitAfter support for hibernate > and better approach of injecting the values into fields - not by reflection. > On the other hand, Spring and Guice are doing the same, so this could become > a unique feature if I find some byte-code-manipulating solution! > > And I also think an integration for play! or other frameworks could be > pretty much the same effort. Tapestry is so easy to use :-) > > Well, I'll continue with that experiment! > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
how do i access ComponentResources in a service?
Hi all, I am writing a service I intend to inject into some pages and components: public MyPage { @Inject private MyService myService; } I want MyServiceImpl to have access to ComponentResources public MyServiceImpl implements MyService { @Inject private ComponentResources componentResources; } however this causes an exception: Caused by: java.lang.RuntimeException: No service implements the interface org.apache.tapestry5.ComponentResources. at org.apache.tapestry5.ioc.internal.RegistryImpl.getService(RegistryImpl.java:560) at org.apache.tapestry5.ioc.internal.ObjectLocatorImpl.getService(ObjectLocatorImpl.java:44) at org.apache.tapestry5.ioc.internal.services.MasterObjectProviderImpl$1.invoke(MasterObjectProviderImpl.java:56) at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:68) ... 123 more Obviously I'm missing some special plumbing in my AppModule. What is it? Thanks, Paul. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
tapestry4 session integrate with springsecurity
hi i need advice on this, i use springsecurity to authenticiate user, then if success, on Home.page, copy the user object to tapestry4 user. this work fine. but sometime, the tapestry4 session timeout. what is the proper way to integrate tapestry 4 session user with springsecurity? need change the hivemodule.xml? - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: ObjectProvider called to often
Hallo Sebastian, Well, you will always need the ObjectProvider, and it in turn will always need a number of services, either virtual or realized. Maybe there is a way to draw dependency diagrams so you can really see what is going on (but as far as I know, this information isn't available from the IoC right now, it's on my list of things to do and be excited about) But again, these services aren't actually instantiated yet; at least not until they are needed. Op 22-11-2010 22:20, Sebastian Hennebrueder schreef: Hi Tom, I wasn't surprised by the number of services to be prepared either as proxy or to be created. I just don't see a reason why the object provider which I add as last provider is called for framework internal services. There is just no need to call it at all for those services. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [ANN] Tapestry on Twitter
On Mon, 22 Nov 2010 21:19:01 -0200, Igor Drobiazko wrote: Tapestry team created a shared Twitter account to post news on Tapestry. Please follow us and retwitt, if you want to help us to make the framework more successful. https://twitter.com/#!/ApacheTapestry/ By the way, if you write a post or article about Tapestry or want to announce a Tapestry-related package or any other news, such as new websites using our favorite framework, we'll retweet them. ;) -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
[ANN] Tapestry on Twitter
Tapestry team created a shared Twitter account to post news on Tapestry. Please follow us and retwitt, if you want to help us to make the framework more successful. https://twitter.com/#!/ApacheTapestry/ -- Best regards, Igor Drobiazko http://tapestry5.de
Re: T5.2.4 classpath asset issue
Per your request, issue filed: https://issues.apache.org/jira/browse/TAP5-1353 Adam On Mon, Nov 22, 2010 at 2:29 PM, Adam Zimowski wrote: > Will do and agreed. > > On Mon, Nov 22, 2010 at 2:19 PM, Howard Lewis Ship wrote: >> Please add an issue, but I don't see this as a blocker for Tapestry 5.2. >> >> On Mon, Nov 22, 2010 at 11:48 AM, Adam Zimowski wrote: >> >>> Thank You Howard ! Yes, I moved the file to subfolder "resources", >>> changed my annotation to: >>> >>> @Import(library="classpath:/resources/util.js") >>> >>> Modified the module: >>> >>> configuration.add("js", "resources"); >>> >>> And Viola ! Works. I guess I exercised extreme scenario :) >>> >>> Adam >>> >>> On Mon, Nov 22, 2010 at 1:04 PM, Howard Lewis Ship >>> wrote: >>> > Looks like a bug; you should move around the assets to deeper folders, >>> that >>> > should solve the problem. Alternate, the ClasspathAssetManager should >>> > reject your contribution ... you really should package these things >>> deeper, >>> > somewhere inside your library or applications' root package; that was the >>> > intent of how the new aliasing works. >>> > >>> > On Mon, Nov 22, 2010 at 9:15 AM, Adam Zimowski >>> wrote: >>> > >>> >> Minor typo... I also had a stylesheet which is inconsequential to this >>> >> and I removed it from the e-mail. The import really is: >>> >> >>> >> @Import(library="classpath:util.js") >>> >> >>> >> Adam >>> >> >>> >> On Mon, Nov 22, 2010 at 11:13 AM, Adam Zimowski >>> >> wrote: >>> >> > Hi, >>> >> > >>> >> > In my component class I have: >>> >> > >>> >> > @Import(stylesheet="library="classpath:util.js") >>> >> > >>> >> > In the module: >>> >> > >>> >> > public static void >>> >> > contributeClasspathAssetAliasManager(MappedConfiguration>> >> > String> configuration) { >>> >> > // see http://markmail.org/thread/rq4vp7hi437smsrh >>> >> > configuration.add("js", "/"); >>> >> > } >>> >> > >>> >> > The file util.js lives directly under src/ >>> >> > >>> >> > Page renders fine, but tapestry rendered reference trims first >>> >> > character from my file name: >>> >> > >> >> > type="text/javascript"> >>> >> > >>> >> > Of course the file is inaccessible that way, but if I manually add the >>> >> > missing 'u' I can see it. >>> >> > >>> >> > Is this a bug or am I doing something wrong? >>> >> > >>> >> > Adam >>> >> > >>> >> >>> >> - >>> >> 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 >>> > >>> >>> - >>> 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 >> > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: AJAX zone refresh error messages
is the error message you're referring to the 'BlackBird' error popup? if you want to disable it set SymbolConstants.BLACKBIRD_ENABLED to false in your Module. p. On 23/11/2010 5:51 AM, Michael Taylor wrote: Greetings Tapestry users, I have a question about ajax refreshing zones. I have a page that contains a number of custom components each of which has its own zone that gets refreshed via ajax. I've noticed that if there is a problem on the server side when executing the ajax refresh tapestry dynamically pops up a read error message box at the top of the page which is visible for a few seconds and then fades out. The problem I'm having is that this error message is showing the stack trace of the exception that got thrown on the sever side which isn't particularly user friendly. I'd like to customize what this error message says, but I'm not sure how to do it. I'd tried poking around in the documentation, but all I could find was information on form validation error messages which didn't seem quite applicable. Could anyone give me any tips on how to customize these ajax refresh error messages (or point me at the relevant documentation). Thanks in advance, Mike T - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: tynamo tapestry-security / shiro help
Alejandro, Would you mind posting your Realm implementation? I tried just providing a CacheManager to the constructor for AuthorizingRealm but there must be something else missing as i still have 2 problems: 1. The SimpleAccount is not being cached after the credentials have been checked (ie after doGetAuthenticationInfo) but is then being requested for the 'hasRole' check 2. I get an exception: Caused by: java.lang.IllegalArgumentException: Cache name cannot be null or empty. at org.apache.shiro.cache.AbstractCacheManager.getCache(AbstractCacheManager.java:61) at org.apache.shiro.realm.AuthorizingRealm.getAuthorizationCacheLazy(AuthorizingRealm.java:245) at org.apache.shiro.realm.AuthorizingRealm.getAvailableAuthorizationCache(AuthorizingRealm.java:260) at org.apache.shiro.realm.AuthorizingRealm.getAuthorizationInfo(AuthorizingRealm.java:322) at org.apache.shiro.realm.AuthorizingRealm.hasRole(AuthorizingRealm.java:567) Also, could you explain how the cache entries are evicted? would this happen at exactly the time the httpsession is invalidated? Thanks, Paul. On 23/11/2010 1:28 AM, Alejandro Scandroli wrote: Hi Paul The AuthorizingRealm constructor can take a CacheManager as a parameter. In our case we use the EhCacheManager. That's all you need! Cheers. Alejandro On Fri, Nov 19, 2010 at 12:58 AM, Paul Stanton wrote: Kalle, I'm think I'm making progress however I haven't found a good guide to confirm I'm on the right track. I have a persistent User entity (db+hibernate). The user has multiple roles. I only really want to use the RequiresRoles annotation on pages (and some methods) at this point. So what I've done so far: AuthorizingRealm and my doGetAuthenticationInfo creates a SimpleAccount with the roles set populated. But once the code hits a RequiresRole annotation, the realm.doGetAuthorizationInfo is called. I don't want to go back to my persistent entity at this point since I've already told the security module about the user's roles. How do I make AuthorizingRealm cache the SimpleAccount returned from doGetAuthenticationInfo and use it for doGetAuthorizationInfo? Also, I'd expect this cache element to have the same lifecycle as the user's session, is that the case? Thanks, Paul. - 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
Hot reloading and mvn:gae:run
Hi, I use tapestry for more than one year now, and I'm very pleased with. I use it daily at work with mvn jetty:run and I much appreciate hot class reloading for pages and components. But at home I'm trying to use it to develop a Google App Engine Application, and I use the maven plugin net.kindleit:maven-gae-plugin with the target mvn gae:run. The hot reload is not working, because this plugin doesn't work the same way as jetty:run : it assemble the war in a directory and run from there. Did anybody get the hot component reloading working in that configuration ? Thanks. Nicolas.
Re: [ANNOUNCEMENT] tapestry-security 0.2.1 and 0.3.0 released!
This is a very good day! Congrats! 2010/11/22 Kalle Korhonen > Ta daa! This time we are announcing a dual release of > tapestry-security, versions 0.2.1 for T5.1.x and 0.3.0 for T5.2.x! > Probably not much of a surprise anymore as I've hinted at numerous > occasions about the new releases but announcing still has its place > since major dependencies changed. Most importantly, these versions > pull in and integrate with Apache Shiro 1.1.0, the first Shiro release > as a top level Apache project. I'm also happy to report that some of > Tynamo-born annotations made their way to Shiro core so > tapestry-security doesn't need to supplement Shiro annotations with > our own extensions anymore. If you were using previous > tapestry-security releases, you are advised to upgrade immediately as > there were some security vulnerabilities in Shiro 1.0.0-incubating > (which don't directly affect tapestry-security but you should still > upgrade). > > Tapestry-security 0.3.0 uses the brand new T5.2.4, the best Tapestry > release yet. 0.2.1 and 0.3.0 are functionally equivalent, the only > difference is that 0.3.0 moved onto newer APIs (thanks Massimo) and we > started using some T5.2 features in the tests ourselves. Testament to > the backwards compatibility of Tapestry 5.x, tapestry-security 0.2.1 > will work for T5.2 just the same but it pulls in T5.1.0.5 and is > tested against that version. Both versions will be maintained going > forward but 0.3.x will start using more of T5.2 features in the > future. Read more at http://tynamo.org/tapestry-security+guide. > Release notes (from > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12041&version=16804 > ) > are for both versions except for TYNAMO-66: > > Bug >* [TYNAMO-56] - tapestry-security sources missing from central repo > > Improvement >* [TYNAMO-61] - tynamo-security: bypass security check during > application start >* [TYNAMO-66] - Update tapestry-security to use T5.2.x APIs >* [TYNAMO-55] - Rewrite ShiroExceptionHandler for T5.2 > > Task >* [TYNAMO-62] - Update tapestry-security to use Shiro 1.1.0 APIs > > > Enjoy, > Tynamo Team > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
Re: ObjectProvider called to often
Hi Tom, I wasn't surprised by the number of services to be prepared either as proxy or to be created. I just don't see a reason why the object provider which I add as last provider is called for framework internal services. There is just no need to call it at all for those services. -- Best Regards / Viele Grüße Sebastian Hennebrueder - http://www.laliluna.de Java software developer and trainer for Hibernate and Java Persistence Am 22.11.2010 um 00:37 schrieb Tom van Dijk: > And obviously, I meant "every service that it somehow depends on" instead of > the other thing which is not true. > > Op 22-11-2010 0:34, Tom van Dijk schreef: >> Well, no, you will see that a lot of services depend on each other, so in >> order to create an object that just happens to depend on stuff like object >> providers, many other services need to be created. This is not an >> inefficiency in Tapestry (The services are first only "virtual" before they >> are realized) but it may be that the lifecycle it not efficient in >> guice/tapestry integration as it is in tapestry. >> >> When you ask for a service, every service that somehow depends on it (via >> field/constructor initialization) is created as a VIRTUAL object. Then when >> they are actually used (you call a method) they are REALIZED (by the virtual >> proxy object). This is why it's not inefficient to create all these virtual >> proxies. That part is easy. And when they are actually used, well, then you >> need to have the realized object anyway, so it's still efficient. >> >> Op 21-11-2010 23:59, Sebastian Hennebrueder schreef: >>> Hello, >>> >>> I added an object provider to integrate the Guice IOC Framework. Though I >>> have added it at the end, it is called for many Tapestry related pieces. Is >>> this not a very big inefficiency? >>> >>> my integration stuff in AppModule >>>public static void >>> contributeMasterObjectProvider(OrderedConfiguration >>> configuration) { >>>configuration.add("GuiceObjectProvider", new GuiceObjectProvider(), >>> "after:*"); >>>} >>> >>> >>> Here is the list of services asked to build: >>> >>> 23:56:54,194 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.ioc.services.PipelineBuilder >>> 23:56:54,224 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.ioc.services.PropertyShadowBuilder >>> 23:56:54,243 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.services.RequestGlobals >>> 23:56:54,263 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.services.ApplicationGlobals >>> 23:56:54,270 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.ioc.services.ChainBuilder >>> 23:56:54,275 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.services.Environment >>> 23:56:54,280 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.ioc.services.StrategyBuilder >>> 23:56:54,285 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.ioc.services.PropertyAccess >>> 23:56:54,293 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.services.Request >>> 23:56:54,311 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.services.Response >>> 23:56:54,318 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.services.EnvironmentalShadowBuilder >>> 23:56:54,323 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.internal.services.EndOfRequestEventHub >>> 23:56:54,335 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.ioc.services.DefaultImplementationBuilder >>> 23:56:54,345 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.ioc.services.TypeCoercer >>> 23:56:54,346 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.services.ComponentClassResolver >>> 23:56:54,362 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.services.Request >>> 23:56:54,384 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.internal.services.ComponentInstantiatorSource >>> 23:56:54,389 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.services.UpdateListenerHub >>> 23:56:54,407 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.services.RequestGlobals >>> 23:56:54,408 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.tapestry5.internal.services.ComponentClassTransformer >>> 23:56:54,412 DEBUG GuiceObjectProvider:24 - guice asked to provide: >>> interface org.apache.ta
Re: T5.2.4 classpath asset issue
Will do and agreed. On Mon, Nov 22, 2010 at 2:19 PM, Howard Lewis Ship wrote: > Please add an issue, but I don't see this as a blocker for Tapestry 5.2. > > On Mon, Nov 22, 2010 at 11:48 AM, Adam Zimowski wrote: > >> Thank You Howard ! Yes, I moved the file to subfolder "resources", >> changed my annotation to: >> >> @Import(library="classpath:/resources/util.js") >> >> Modified the module: >> >> configuration.add("js", "resources"); >> >> And Viola ! Works. I guess I exercised extreme scenario :) >> >> Adam >> >> On Mon, Nov 22, 2010 at 1:04 PM, Howard Lewis Ship >> wrote: >> > Looks like a bug; you should move around the assets to deeper folders, >> that >> > should solve the problem. Alternate, the ClasspathAssetManager should >> > reject your contribution ... you really should package these things >> deeper, >> > somewhere inside your library or applications' root package; that was the >> > intent of how the new aliasing works. >> > >> > On Mon, Nov 22, 2010 at 9:15 AM, Adam Zimowski >> wrote: >> > >> >> Minor typo... I also had a stylesheet which is inconsequential to this >> >> and I removed it from the e-mail. The import really is: >> >> >> >> @Import(library="classpath:util.js") >> >> >> >> Adam >> >> >> >> On Mon, Nov 22, 2010 at 11:13 AM, Adam Zimowski >> >> wrote: >> >> > Hi, >> >> > >> >> > In my component class I have: >> >> > >> >> > @Import(stylesheet="library="classpath:util.js") >> >> > >> >> > In the module: >> >> > >> >> > public static void >> >> > contributeClasspathAssetAliasManager(MappedConfiguration> >> > String> configuration) { >> >> > // see http://markmail.org/thread/rq4vp7hi437smsrh >> >> > configuration.add("js", "/"); >> >> > } >> >> > >> >> > The file util.js lives directly under src/ >> >> > >> >> > Page renders fine, but tapestry rendered reference trims first >> >> > character from my file name: >> >> > > >> > type="text/javascript"> >> >> > >> >> > Of course the file is inaccessible that way, but if I manually add the >> >> > missing 'u' I can see it. >> >> > >> >> > Is this a bug or am I doing something wrong? >> >> > >> >> > Adam >> >> > >> >> >> >> - >> >> 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 >> > >> >> - >> 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 > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [T5.2.4] Service ambiguity does not get resolved, when Marker annotations are defined inside of an service implementation
I think you are right. Easy way out is to add withMarker(...).preventReloading(); Service reloading enabled by default can be frustrating when you hit issues, but overall I think the benefits outweigh the harms. Kalle On Mon, Nov 22, 2010 at 11:57 AM, Felix Gonschorek wrote: > hi all, > > we are currently in progress to migrate our application from tapestry 5.1.0.5 > to > tapestry 5.2.4 - we encounter some minor challenges, but the following was > hard > to solve: > > In Tapestry 5.2.4 a service with a single interface and multiple > implemenations > which are discriminated with an marker annotation get not resolved when the > marker annotation is defined inside a service implementation: > > binder.bind(AddressValidationStrategy.class, > NoChecksAddressValidationStrategy.class).withId(Invoice.class.getName()).withMarker(Invoice.class); > binder.bind(AddressValidationStrategy.class, > DefaultAddressValidationStrategy.class).withId(Shipping.class.getName()).withMarker(Shipping.class); > > > The marker "Invoice.class" and "Shipping.class" (which are annotations) are > defined within another service. This service uses both > AddressValidationStrategies. > > While writing this message i am getting an assumption why this error occurs: > Its > because of the live class reloading of the service implementations. > > When definging the annotations in a separate java file outside of the service > implementation, the services get resolved. > > i don't know if this is an error or bad design to define the annotations > inside > of an service implemenation, but maybe one should add a hint to the api of the > servicebinder methods, that the marker annotations need to be defined in > separate java files or at least not as a member of a service implementation. > > keep up the good work, > > felix< > > - > 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
Re: [T5.2.4] Service ambiguity does not get resolved, when Marker annotations are defined inside of an service implementation
I would document this as a "gotcha". The idea of putting the marker annotation right in the service implementation class seems odd ... it ends up creating a binding from the clients of the service to the implementation, which can't be moved, renamed, or have its visibility changed without breaking those clients. With a top-level annotation, rather than a nested, inner class annotation, that problem goes away (just the marker annotation has to be stable, not the service implementation class). On Mon, Nov 22, 2010 at 11:57 AM, Felix Gonschorek < felix.gonscho...@gmail.com> wrote: > hi all, > > we are currently in progress to migrate our application from tapestry > 5.1.0.5 to > tapestry 5.2.4 - we encounter some minor challenges, but the following was > hard > to solve: > > In Tapestry 5.2.4 a service with a single interface and multiple > implemenations > which are discriminated with an marker annotation get not resolved when the > marker annotation is defined inside a service implementation: > > binder.bind(AddressValidationStrategy.class, > > NoChecksAddressValidationStrategy.class).withId(Invoice.class.getName()).withMarker(Invoice.class); > binder.bind(AddressValidationStrategy.class, > > DefaultAddressValidationStrategy.class).withId(Shipping.class.getName()).withMarker(Shipping.class); > > > The marker "Invoice.class" and "Shipping.class" (which are annotations) are > defined within another service. This service uses both > AddressValidationStrategies. > > While writing this message i am getting an assumption why this error > occurs: Its > because of the live class reloading of the service implementations. > > When definging the annotations in a separate java file outside of the > service > implementation, the services get resolved. > > i don't know if this is an error or bad design to define the annotations > inside > of an service implemenation, but maybe one should add a hint to the api of > the > servicebinder methods, that the marker annotations need to be defined in > separate java files or at least not as a member of a service > implementation. > > keep up the good work, > > felix< > > - > 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: T5.2.4 classpath asset issue
Please add an issue, but I don't see this as a blocker for Tapestry 5.2. On Mon, Nov 22, 2010 at 11:48 AM, Adam Zimowski wrote: > Thank You Howard ! Yes, I moved the file to subfolder "resources", > changed my annotation to: > > @Import(library="classpath:/resources/util.js") > > Modified the module: > > configuration.add("js", "resources"); > > And Viola ! Works. I guess I exercised extreme scenario :) > > Adam > > On Mon, Nov 22, 2010 at 1:04 PM, Howard Lewis Ship > wrote: > > Looks like a bug; you should move around the assets to deeper folders, > that > > should solve the problem. Alternate, the ClasspathAssetManager should > > reject your contribution ... you really should package these things > deeper, > > somewhere inside your library or applications' root package; that was the > > intent of how the new aliasing works. > > > > On Mon, Nov 22, 2010 at 9:15 AM, Adam Zimowski > wrote: > > > >> Minor typo... I also had a stylesheet which is inconsequential to this > >> and I removed it from the e-mail. The import really is: > >> > >> @Import(library="classpath:util.js") > >> > >> Adam > >> > >> On Mon, Nov 22, 2010 at 11:13 AM, Adam Zimowski > >> wrote: > >> > Hi, > >> > > >> > In my component class I have: > >> > > >> > @Import(stylesheet="library="classpath:util.js") > >> > > >> > In the module: > >> > > >> > public static void > >> > contributeClasspathAssetAliasManager(MappedConfiguration >> > String> configuration) { > >> > // see http://markmail.org/thread/rq4vp7hi437smsrh > >> > configuration.add("js", "/"); > >> > } > >> > > >> > The file util.js lives directly under src/ > >> > > >> > Page renders fine, but tapestry rendered reference trims first > >> > character from my file name: > >> > >> > type="text/javascript"> > >> > > >> > Of course the file is inaccessible that way, but if I manually add the > >> > missing 'u' I can see it. > >> > > >> > Is this a bug or am I doing something wrong? > >> > > >> > Adam > >> > > >> > >> - > >> 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 > > > > - > 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 Web Site Updated
Good points ! 2010/11/22 Javier Molina > I haven't explored the site thoroughly, but here are some comments: > > - in general, the new site looks prettier > > - it doesn't look good to have a "Tapestry 5.2.3 -- canceled" post on the > front page. It's scary and you have to read the rest to know that it's just > a release that didn't pass the vote. I know there's now a post above that > saying 5.2.4 beta release, I'm commenting about the concept of > "fear-about-the-future-of-tapestry" content with such visibility. Do we want > things like that to see what potential new users get on their first visit? > > - news feed titles have too large a font > > - there's too much text in the left column. I know there are a lot of > benefits and features to tapestry, but it looks intimidating. > > - in the "create your first tapestry project" tutorial, don't make the user > choose an archetype or a tapestry version. Write the instructions for the > latest stable version. It's better to have that be out of date when a new > version comes out (because it still will work) than have the user decide at > this stage. Same for the groupId, artifactId, version and package. It's a > test project the user is creating, those values are not going to matter. > Give the defaults so people can copy and paste the command and have the > project created, built and run. > > - the big red scary warning about the project layout changing across > different versions has no reason to be. By the time the user has this > problem he will know how to solve it. > > - after the test project has been created, give the user some pointers on > where to find things (pages go in src/main/java/com/example/pages, page > templates go in webapp). I know there is a link to the tutorial but if this > first experience is too frustrating, people might not even bother to go > there. > > - add something to the archetype with commented out code that the user can > uncomment and see something cool happen. It has to be a few lines only, to > be easily understandable, and clearly link components in the template with > their methods in the page class. > > - the tapestry tutorial starts unnecessarily verbose about topics not > really related to me getting code running and out the door. Strip it to the > essentials. If you want to mention Struts and the Servlet API compared to > the tapestry way, mention them in a separate chapter so they are easy to > find / skip as needed. > > - there is no table of contents for the tutorial and no indication of how > long it takes to complete. > > - there are too many callouts, warnings and decorations in the tutorial. It > is very distracting visually and that makes it hard to follow. It's > impossible to scan the pages to get a feel for what you've got ahead of you. > > Basically, what most of the above boils down to is: make the barrier to > entry as absolutely low as possible. All the magic tapestry does for you and > how great a framework it is will not matter if people don't get past the > initial experience. > > El 19/11/10 22:15, Howard Lewis Ship escribió: > > We're still working out the kinks ... and I've been working hard on >> revising >> the tutorial ... but at long last, we're debuting the new Tapestry Web >> Site: >> >> http://tapestry.apache.org/ >> >> Feedback is encouraged; just post to users@tapestry.apache.org with >> [SITE] >> in the subject. >> >> > > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Regards, Christophe Cordenier. Committer on Apache Tapestry 5 Co-creator of wooki @wookicentral.com
[T5.2.4] Service ambiguity does not get resolved, when Marker annotations are defined inside of an service implementation
hi all, we are currently in progress to migrate our application from tapestry 5.1.0.5 to tapestry 5.2.4 - we encounter some minor challenges, but the following was hard to solve: In Tapestry 5.2.4 a service with a single interface and multiple implemenations which are discriminated with an marker annotation get not resolved when the marker annotation is defined inside a service implementation: binder.bind(AddressValidationStrategy.class, NoChecksAddressValidationStrategy.class).withId(Invoice.class.getName()).withMarker(Invoice.class); binder.bind(AddressValidationStrategy.class, DefaultAddressValidationStrategy.class).withId(Shipping.class.getName()).withMarker(Shipping.class); The marker "Invoice.class" and "Shipping.class" (which are annotations) are defined within another service. This service uses both AddressValidationStrategies. While writing this message i am getting an assumption why this error occurs: Its because of the live class reloading of the service implementations. When definging the annotations in a separate java file outside of the service implementation, the services get resolved. i don't know if this is an error or bad design to define the annotations inside of an service implemenation, but maybe one should add a hint to the api of the servicebinder methods, that the marker annotations need to be defined in separate java files or at least not as a member of a service implementation. keep up the good work, felix< - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T5.2.4 classpath asset issue
Thank You Howard ! Yes, I moved the file to subfolder "resources", changed my annotation to: @Import(library="classpath:/resources/util.js") Modified the module: configuration.add("js", "resources"); And Viola ! Works. I guess I exercised extreme scenario :) Adam On Mon, Nov 22, 2010 at 1:04 PM, Howard Lewis Ship wrote: > Looks like a bug; you should move around the assets to deeper folders, that > should solve the problem. Alternate, the ClasspathAssetManager should > reject your contribution ... you really should package these things deeper, > somewhere inside your library or applications' root package; that was the > intent of how the new aliasing works. > > On Mon, Nov 22, 2010 at 9:15 AM, Adam Zimowski wrote: > >> Minor typo... I also had a stylesheet which is inconsequential to this >> and I removed it from the e-mail. The import really is: >> >> @Import(library="classpath:util.js") >> >> Adam >> >> On Mon, Nov 22, 2010 at 11:13 AM, Adam Zimowski >> wrote: >> > Hi, >> > >> > In my component class I have: >> > >> > @Import(stylesheet="library="classpath:util.js") >> > >> > In the module: >> > >> > public static void >> > contributeClasspathAssetAliasManager(MappedConfiguration> > String> configuration) { >> > // see http://markmail.org/thread/rq4vp7hi437smsrh >> > configuration.add("js", "/"); >> > } >> > >> > The file util.js lives directly under src/ >> > >> > Page renders fine, but tapestry rendered reference trims first >> > character from my file name: >> > > > type="text/javascript"> >> > >> > Of course the file is inaccessible that way, but if I manually add the >> > missing 'u' I can see it. >> > >> > Is this a bug or am I doing something wrong? >> > >> > Adam >> > >> >> - >> 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 > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T5.1 +tapestry-googleanalytics - Get the current page classname from inside a MarkupRendererFilter.
In 5.2 there is a new method in RequestGlobals named getActivePageName(). See here: http://tapestry.apache.org/tapestry5.2-dev/apidocs/org/apache/tapestry5/services/RequestGlobals.html#getActivePageName%28%29 2010/11/22 Antonio Fernández > > Hi all, Greetings from Málaga :) !!! > > - Congratulations for the new Layout of the Web Site. > > - Thanks for this really active/useful mailing list, I founded a lot of > solutions > and interesting news about 3rd Libraries, upgradings and books ( here we > continue > waiting the english translation of the Igor´s Book :-* ... ) > > - We are using the 'tapestry-googleanalytics' Library to obtain the > statistics of our > website. It works great, but now we need an specific customization to > discard > the work done by the GAnalyticsScriptsInjector class in some specific > Pages. This > class is an implementation of the _MarkupRendererFilter _interface, so here > is the key. How > could we know the classname of the page that is being rendered inside a > MarkupRendererFilter ? Is it possible ? > > We tried by inyecting the ComponentResources service inside ( inspired in > the typical Layout component, > that uses this service to determine the current page ) , but don´t works, > T5 says that this service is not available. > > Thanks in advance & Have a nive day, > Antonio > > P.D.: If you want to see another little example of > what you can do EASILY with Tapestry 5, please > take a look of our website ;-) > > -- > Antonio Miguel Fernández Rodríguez > Jaraxa Software, SL > Administrator, Software analyst > www.jaraxa.com > > > > -- Best regards, Igor Drobiazko http://tapestry5.de
Re: T5.2.4 classpath asset issue
Looks like a bug; you should move around the assets to deeper folders, that should solve the problem. Alternate, the ClasspathAssetManager should reject your contribution ... you really should package these things deeper, somewhere inside your library or applications' root package; that was the intent of how the new aliasing works. On Mon, Nov 22, 2010 at 9:15 AM, Adam Zimowski wrote: > Minor typo... I also had a stylesheet which is inconsequential to this > and I removed it from the e-mail. The import really is: > > @Import(library="classpath:util.js") > > Adam > > On Mon, Nov 22, 2010 at 11:13 AM, Adam Zimowski > wrote: > > Hi, > > > > In my component class I have: > > > > @Import(stylesheet="library="classpath:util.js") > > > > In the module: > > > > public static void > > contributeClasspathAssetAliasManager(MappedConfiguration > String> configuration) { > > // see http://markmail.org/thread/rq4vp7hi437smsrh > > configuration.add("js", "/"); > > } > > > > The file util.js lives directly under src/ > > > > Page renders fine, but tapestry rendered reference trims first > > character from my file name: > > > type="text/javascript"> > > > > Of course the file is inaccessible that way, but if I manually add the > > missing 'u' I can see it. > > > > Is this a bug or am I doing something wrong? > > > > Adam > > > > - > 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
AJAX zone refresh error messages
Greetings Tapestry users, I have a question about ajax refreshing zones. I have a page that contains a number of custom components each of which has its own zone that gets refreshed via ajax. I've noticed that if there is a problem on the server side when executing the ajax refresh tapestry dynamically pops up a read error message box at the top of the page which is visible for a few seconds and then fades out. The problem I'm having is that this error message is showing the stack trace of the exception that got thrown on the sever side which isn't particularly user friendly. I'd like to customize what this error message says, but I'm not sure how to do it. I'd tried poking around in the documentation, but all I could find was information on form validation error messages which didn't seem quite applicable. Could anyone give me any tips on how to customize these ajax refresh error messages (or point me at the relevant documentation). Thanks in advance, Mike T
Re: [ANNOUNCEMENT] tapestry-security 0.2.1 and 0.3.0 released!
OpenID is well within our scope. I have done Oauth & Oauth 2 integrations but haven't found the time yet to generalize the implementation. There's quite a bit more work to do for general use compared to making it work just for your webapplication. I trust in code and patches are always welcome. Kalle On Mon, Nov 22, 2010 at 10:09 AM, Werner Keil wrote: > Great, > > Congratulations on that. Although used in a closed-source commercial > project based on T5, if the general idea of using OpenID or similar Identity > standards was also within scope for tapestry-security or something to build > on it, I'd be glad to share my experience and thoughts where the information > isn't confidential[?] > > Werner >
Re: [ANNOUNCEMENT] tapestry-security 0.2.1 and 0.3.0 released!
Great, Congratulations on that. Although used in a closed-source commercial project based on T5, if the general idea of using OpenID or similar Identity standards was also within scope for tapestry-security or something to build on it, I'd be glad to share my experience and thoughts where the information isn't confidential[?] Werner
Re: My response to Matt Raible's presentation at Devoxx 2010
Katia, I'm neither obsessed with ATG or Oracle, nor with SpringSource and their products (as some may feel a little bit about Matt's ranking [?]) just putting some of the more "Vertical" or Business capable examples into a much smaller list, than he did there with a whole lot of different frameworks both in- and outside the browser. If you'd claim anything I was especially interested in, that "Domain Driven" or "Vertical" aspect of some frameworks is clearly among them. I help shape some framworks or base libraries even the "darlings" like Grails or Spring like to use sometimes, and some of them are likely to get a slightly wider use from Java 7 onwards... Werner On Mon, Nov 22, 2010 at 10:57 PM, Katia Aresti wrote: > @Werner : > > It might be a matter of my low English level, but I can't even understand > the half of your thoughts. Moreover, I still don't get your obsession with > ATG, which is a commercial product not a framework and which has a very very > very expensive license. > But It doesn't matter, I quit this pointless discussion with this last > sentence: > maybe you are right and I will come back to ATG product one day, with > glassfish or maybe *Wickestry IoC*. > However, what I really hope is to come back to real world Tapestry 5 actual > work :) > > Katia > > 2010/11/22 Werner Keil > > Back to the DevoXX discussion, it has clearly lost some momentum now, that >> JavaOne was moved to the Sep/Oct timeslot, and DevoXX itself was even >> shifted almost a month itself. While even the announcements and great news >> of last year (Java getting Closures[?]) were not as close to becoming >> reality as it then may have sounded, everything discussed or presented this >> year on Java was only the aftermath of JavaOne. The JSRs being out just this >> week probably being the only "gossip" for the bloggers and "Parvez Hiltons" >> of the Java Community who have gathered there much more than on JavaOne or >> other conferences by the vendors itself. >> >> Guess Matt has moved himself a step closer to such "Parvenism" with that >> presentation ?[?] >> > >
Re: [tynamo-user] [ANNOUNCEMENT] tapestry-security 0.2.1 and 0.3.0 released!
Hi, Congratulations for your work ! @Kalle and Tynamo users Is somebody interested on finishing the Tynamo Hotel-Booking-Demo ? Security works fine, but it will be vry interesting to finish the work using conversations module too. Just drop me an e-mail if somebody is interested on working on that. I just have no time right now to finish the version of this demo. Cheers, Katia 2010/11/22 Kalle Korhonen > Ta daa! This time we are announcing a dual release of > tapestry-security, versions 0.2.1 for T5.1.x and 0.3.0 for T5.2.x! > Probably not much of a surprise anymore as I've hinted at numerous > occasions about the new releases but announcing still has its place > since major dependencies changed. Most importantly, these versions > pull in and integrate with Apache Shiro 1.1.0, the first Shiro release > as a top level Apache project. I'm also happy to report that some of > Tynamo-born annotations made their way to Shiro core so > tapestry-security doesn't need to supplement Shiro annotations with > our own extensions anymore. If you were using previous > tapestry-security releases, you are advised to upgrade immediately as > there were some security vulnerabilities in Shiro 1.0.0-incubating > (which don't directly affect tapestry-security but you should still > upgrade). > > Tapestry-security 0.3.0 uses the brand new T5.2.4, the best Tapestry > release yet. 0.2.1 and 0.3.0 are functionally equivalent, the only > difference is that 0.3.0 moved onto newer APIs (thanks Massimo) and we > started using some T5.2 features in the tests ourselves. Testament to > the backwards compatibility of Tapestry 5.x, tapestry-security 0.2.1 > will work for T5.2 just the same but it pulls in T5.1.0.5 and is > tested against that version. Both versions will be maintained going > forward but 0.3.x will start using more of T5.2 features in the > future. Read more at http://tynamo.org/tapestry-security+guide. > Release notes (from > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12041&version=16804 > ) > are for both versions except for TYNAMO-66: > > Bug >* [TYNAMO-56] - tapestry-security sources missing from central repo > > Improvement >* [TYNAMO-61] - tynamo-security: bypass security check during > application start >* [TYNAMO-66] - Update tapestry-security to use T5.2.x APIs >* [TYNAMO-55] - Rewrite ShiroExceptionHandler for T5.2 > > Task >* [TYNAMO-62] - Update tapestry-security to use Shiro 1.1.0 APIs > > > Enjoy, > Tynamo Team > > - > To unsubscribe from this list, please visit: > >http://xircles.codehaus.org/manage_email > > >
[ANNOUNCEMENT] tapestry-security 0.2.1 and 0.3.0 released!
Ta daa! This time we are announcing a dual release of tapestry-security, versions 0.2.1 for T5.1.x and 0.3.0 for T5.2.x! Probably not much of a surprise anymore as I've hinted at numerous occasions about the new releases but announcing still has its place since major dependencies changed. Most importantly, these versions pull in and integrate with Apache Shiro 1.1.0, the first Shiro release as a top level Apache project. I'm also happy to report that some of Tynamo-born annotations made their way to Shiro core so tapestry-security doesn't need to supplement Shiro annotations with our own extensions anymore. If you were using previous tapestry-security releases, you are advised to upgrade immediately as there were some security vulnerabilities in Shiro 1.0.0-incubating (which don't directly affect tapestry-security but you should still upgrade). Tapestry-security 0.3.0 uses the brand new T5.2.4, the best Tapestry release yet. 0.2.1 and 0.3.0 are functionally equivalent, the only difference is that 0.3.0 moved onto newer APIs (thanks Massimo) and we started using some T5.2 features in the tests ourselves. Testament to the backwards compatibility of Tapestry 5.x, tapestry-security 0.2.1 will work for T5.2 just the same but it pulls in T5.1.0.5 and is tested against that version. Both versions will be maintained going forward but 0.3.x will start using more of T5.2 features in the future. Read more at http://tynamo.org/tapestry-security+guide. Release notes (from http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12041&version=16804) are for both versions except for TYNAMO-66: Bug * [TYNAMO-56] - tapestry-security sources missing from central repo Improvement * [TYNAMO-61] - tynamo-security: bypass security check during application start * [TYNAMO-66] - Update tapestry-security to use T5.2.x APIs * [TYNAMO-55] - Rewrite ShiroExceptionHandler for T5.2 Task * [TYNAMO-62] - Update tapestry-security to use Shiro 1.1.0 APIs Enjoy, Tynamo Team - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: My response to Matt Raible's presentation at Devoxx 2010
@Werner : It might be a matter of my low English level, but I can't even understand the half of your thoughts. Moreover, I still don't get your obsession with ATG, which is a commercial product not a framework and which has a very very very expensive license. But It doesn't matter, I quit this pointless discussion with this last sentence: maybe you are right and I will come back to ATG product one day, with glassfish or maybe *Wickestry IoC*. However, what I really hope is to come back to real world Tapestry 5 actual work :) Katia 2010/11/22 Werner Keil > Back to the DevoXX discussion, it has clearly lost some momentum now, that > JavaOne was moved to the Sep/Oct timeslot, and DevoXX itself was even > shifted almost a month itself. While even the announcements and great news > of last year (Java getting Closures[?]) were not as close to becoming > reality as it then may have sounded, everything discussed or presented this > year on Java was only the aftermath of JavaOne. The JSRs being out just this > week probably being the only "gossip" for the bloggers and "Parvez Hiltons" > of the Java Community who have gathered there much more than on JavaOne or > other conferences by the vendors itself. > > Guess Matt has moved himself a step closer to such "Parvenism" with that > presentation ?[?] >
Re: T5.2.4 classpath asset issue
Minor typo... I also had a stylesheet which is inconsequential to this and I removed it from the e-mail. The import really is: @Import(library="classpath:util.js") Adam On Mon, Nov 22, 2010 at 11:13 AM, Adam Zimowski wrote: > Hi, > > In my component class I have: > > @Import(stylesheet="library="classpath:util.js") > > In the module: > > public static void > contributeClasspathAssetAliasManager(MappedConfiguration String> configuration) { > // see http://markmail.org/thread/rq4vp7hi437smsrh > configuration.add("js", "/"); > } > > The file util.js lives directly under src/ > > Page renders fine, but tapestry rendered reference trims first > character from my file name: > type="text/javascript"> > > Of course the file is inaccessible that way, but if I manually add the > missing 'u' I can see it. > > Is this a bug or am I doing something wrong? > > Adam > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
T5.2.4 classpath asset issue
Hi, In my component class I have: @Import(stylesheet="library="classpath:util.js") In the module: public static void contributeClasspathAssetAliasManager(MappedConfiguration configuration) { // see http://markmail.org/thread/rq4vp7hi437smsrh configuration.add("js", "/"); } The file util.js lives directly under src/ Page renders fine, but tapestry rendered reference trims first character from my file name: Of course the file is inaccessible that way, but if I manually add the missing 'u' I can see it. Is this a bug or am I doing something wrong? Adam - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: My response to Matt Raible's presentation at Devoxx 2010
Back to the DevoXX discussion, it has clearly lost some momentum now, that JavaOne was moved to the Sep/Oct timeslot, and DevoXX itself was even shifted almost a month itself. While even the announcements and great news of last year (Java getting Closures[?]) were not as close to becoming reality as it then may have sounded, everything discussed or presented this year on Java was only the aftermath of JavaOne. The JSRs being out just this week probably being the only "gossip" for the bloggers and "Parvez Hiltons" of the Java Community who have gathered there much more than on JavaOne or other conferences by the vendors itself. Guess Matt has moved himself a step closer to such "Parvenism" with that presentation ?[?]
T5.1 +tapestry-googleanalytics - Get the current page classname from inside a MarkupRendererFilter.
Hi all, Greetings from Málaga :) !!! - Congratulations for the new Layout of the Web Site. - Thanks for this really active/useful mailing list, I founded a lot of solutions and interesting news about 3rd Libraries, upgradings and books ( here we continue waiting the english translation of the Igor´s Book :-* ... ) - We are using the 'tapestry-googleanalytics' Library to obtain the statistics of our website. It works great, but now we need an specific customization to discard the work done by the GAnalyticsScriptsInjector class in some specific Pages. This class is an implementation of the _MarkupRendererFilter _interface, so here is the key. How could we know the classname of the page that is being rendered inside a MarkupRendererFilter ? Is it possible ? We tried by inyecting the ComponentResources service inside ( inspired in the typical Layout component, that uses this service to determine the current page ) , but don´t works, T5 says that this service is not available. Thanks in advance & Have a nive day, Antonio P.D.: If you want to see another little example of what you can do EASILY with Tapestry 5, please take a look of our website ;-) -- Antonio Miguel Fernández Rodríguez Jaraxa Software, SL Administrator, Software analyst www.jaraxa.com
Re: My response to Matt Raible's presentation at Devoxx 2010
Thanks for sharing those. >From the "complete stack" point of view, it clearly exceeds Tapestry, Spring MVC, Seam and most others, but given the aggressive product policy SpringSource/vmware follows with almost everything wrapped in Spring now (yesterday Social Networking, today Android) they have alternatives (most of them Open Source) to many of these components. Which is most likely, why Oracle bolstered up its "arsenal". Although they have other alternatives and who knows, some day we might even see ATG running on Glassfish [?] On Mon, Nov 22, 2010 at 5:10 AM, Katia Aresti wrote: > I know ATG, I worked with the product for a couple of years, I didn't know > oracle purchased ATG. > > You can not compare ATG with any other fw described by Matt Raidle, neither > Tapestry at all. ATG is a full stack e-commerce solution, portal, > publishing. And not opensource at all, but J2EE standard. There is no point > comparing with Spring fw either. > > ATG is not a webframework, it is built in in his own webframework, own IoC, > own ORM etc ... They even had their own application server, but they moved > to weblogic. All that in order to provide the real functionality you pay > for > : the way to develop really big e-commerce sites. > > well, this is another discussion, it does not really belong to this thread. > > Katia > > > 2010/11/21 Werner Keil > > > ATG Web Framework, a commercial solution from a company just purchased by > > Oracle. > > > > Some of its features were described as superior to Spring Framework, > which > > its stakeholders clearly deny. > > > > It is not Open Source, but others, especially Seam are. > > >
Re: Tapestry 5.2.4 issue
Hey, yeah, that is exactly what I am seeing. Thanks for that - looking into it now. Regards, Zubair -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-5-2-4-issue-tp3273778p3275616.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry Web Site Updated
thx - scrolling is fine now in IE On Mon, Nov 22, 2010 at 17:16, Ulrich Stärk wrote: > Andreas, > > if you commit the fix to > https://svn.apache.org/repos/asf/tapestry/tapestry-site/branches/post-5.2-site/styles/style.css > the problem will be fixed immediately. > > Thanks, > > Uli > > Am 22.11.2010 16:07, schrieb Andreas Andreou: >> >> thx for pointing that out - i see similar problem in IE8 and have >> tracked it down to >> a css rule that seems to mess up IE... should be fixed in a little while >> >> On Mon, Nov 22, 2010 at 16:37, Yunhua Sang wrote: >>> >>> Congratulations for the new site, it looks a lot better. >>> >>> One problem, The new site does not work properly with IE7, which is the >>> only >>> one I can use in my company. Somehow I cannot scroll the page down, and >>> "page down" key also doesn't work. >>> >>> >>> On Fri, Nov 19, 2010 at 4:15 PM, Howard Lewis Ship >>> wrote: >>> We're still working out the kinks ... and I've been working hard on revising the tutorial ... but at long last, we're debuting the new Tapestry Web Site: http://tapestry.apache.org/ Feedback is encouraged; just post to users@tapestry.apache.org with [SITE] in the subject. -- 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 >>> >> >> >> > > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr Tapestry PMC / Tacos developer Open Source / JEE Consulting - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [ANN] Tapestry IOC for Wicket
> >> Could it help Tapestry to find adoption in the Wicket-world? > > I don't think so. Both frameworks have similarities (components and pages > treated as objects), but very different approaches. The web-frameworks have different approaches, yes, but Wicket has no own IOC module. What I see is that a Wicket user has the choice between Spring and Guice for DI. People do mostly evaluate both, Tapestry and Wicket, don't they? So in the future they could see a third DI provider, which is fortunately part of one of the frameworks they are just evaluating... I find that being a psychological advantage to have a Tapestry (IOC) integration for Wicket (and possibly other frameworks, too). You could read it as "Tapestry is so advanced you can use it everywhere" or "Development with Tapestry means to have no need for more web frameworks...". I mean we have to advertise it a little more :-) It's such a huge advantage to have that perfectly fitting IOC framework shipped with the web-framework. The basic integration was actually very very simple. Much simpler than Spring's or Guice's. It's just missing @CommitAfter support for hibernate and better approach of injecting the values into fields - not by reflection. On the other hand, Spring and Guice are doing the same, so this could become a unique feature if I find some byte-code-manipulating solution! And I also think an integration for play! or other frameworks could be pretty much the same effort. Tapestry is so easy to use :-) Well, I'll continue with that experiment! - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry Web Site Updated
Andreas, if you commit the fix to https://svn.apache.org/repos/asf/tapestry/tapestry-site/branches/post-5.2-site/styles/style.css the problem will be fixed immediately. Thanks, Uli Am 22.11.2010 16:07, schrieb Andreas Andreou: thx for pointing that out - i see similar problem in IE8 and have tracked it down to a css rule that seems to mess up IE... should be fixed in a little while On Mon, Nov 22, 2010 at 16:37, Yunhua Sang wrote: Congratulations for the new site, it looks a lot better. One problem, The new site does not work properly with IE7, which is the only one I can use in my company. Somehow I cannot scroll the page down, and "page down" key also doesn't work. On Fri, Nov 19, 2010 at 4:15 PM, Howard Lewis Ship wrote: We're still working out the kinks ... and I've been working hard on revising the tutorial ... but at long last, we're debuting the new Tapestry Web Site: http://tapestry.apache.org/ Feedback is encouraged; just post to users@tapestry.apache.org with [SITE] in the subject. -- 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 - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [ANN] Tapestry IOC for Wicket
This is on my list for 5.3. I already started working on it but will commit it after 5.2 is final. I don't intend to pass the official TCK as there are too many differences. Just using JSR-330 annotations in Tapestry pages, components and service is fine. On Sun, Nov 21, 2010 at 9:48 PM, Werner Keil wrote: > For this bigger move, T5 IOC should really adopt to JSR 330 annotations > where those are included, or has it already happened for sure with 5.2? > -- Best regards, Igor Drobiazko http://tapestry5.de
Re: Tapestry Web Site Updated
thx for pointing that out - i see similar problem in IE8 and have tracked it down to a css rule that seems to mess up IE... should be fixed in a little while On Mon, Nov 22, 2010 at 16:37, Yunhua Sang wrote: > Congratulations for the new site, it looks a lot better. > > One problem, The new site does not work properly with IE7, which is the only > one I can use in my company. Somehow I cannot scroll the page down, and > "page down" key also doesn't work. > > > On Fri, Nov 19, 2010 at 4:15 PM, Howard Lewis Ship wrote: > >> We're still working out the kinks ... and I've been working hard on >> revising >> the tutorial ... but at long last, we're debuting the new Tapestry Web >> Site: >> >> http://tapestry.apache.org/ >> >> Feedback is encouraged; just post to users@tapestry.apache.org with [SITE] >> in the subject. >> >> -- >> 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 >> > -- Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr Tapestry PMC / Tacos developer Open Source / JEE Consulting - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry Web Site Updated
On Fri, 19 Nov 2010 19:15:27 -0200, Howard Lewis Ship wrote: We're still working out the kinks ... and I've been working hard on revising the tutorial ... but at long last, we're debuting the new Tapestry Web Site: http://tapestry.apache.org/ This is absolutely awesome. The weakest part of Tapestry has been documentation and this is a big improvement. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [ANN] Tapestry IOC for Wicket
On Sun, 21 Nov 2010 18:48:16 -0200, Werner Keil wrote: For this bigger move, T5 IOC should really adopt to JSR 330 annotations where those are included, I think there's a JIRA for that. or has it already happened for sure with 5.2? Not yet. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [ANN] Tapestry IOC for Wicket
On Sat, 20 Nov 2010 17:36:50 -0200, Christian Riedel wrote: Hi everyone, Hi! I started a little project today: I made a module for Wicket so that it uses Tapestry IOC for injection (I'm not joking, seriously :-))! Tapestry-IoC is not Tapestry-the-web-framework, the former is used by the letter and Tapestry-IoC is awesome, so I think it's a good idea. :) The code is quite simple, it's using reflection to do the injection (I was inspired by the guice integration). I'm looking for a way to do it similar to the ClassTransformationWorker. I only implemented @Inject and @InjectService - no hibernate until now. I can't see whey tapestry-hibernate wouldn't work without Tapestry. It provides Session as per-thread a service, so I guess it should work out-of-the-box. What do you think about it? Go ahead! :) Could it help Tapestry to find adoption in the Wicket-world? I don't think so. Both frameworks have similarities (components and pages treated as objects), but very different approaches. Or am I getting excommunicated by the community for that blasphemous chimera? (I could call it *Wickestry* but I don't dare to) Absolutely not. ;) -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry Web Site Updated
you should consider redirecting from http://tapestry.apache.org/tapestry5/ to http://tapestry.apache.org/ with code 301 so that it becomes result #1 here: http://www.google.de/search?hl=en&q=tapestry+5 what do you think? Am 22.11.2010 um 15:37 schrieb Yunhua Sang: > Congratulations for the new site, it looks a lot better. > > One problem, The new site does not work properly with IE7, which is the only > one I can use in my company. Somehow I cannot scroll the page down, and > "page down" key also doesn't work. > > > On Fri, Nov 19, 2010 at 4:15 PM, Howard Lewis Ship wrote: > >> We're still working out the kinks ... and I've been working hard on >> revising >> the tutorial ... but at long last, we're debuting the new Tapestry Web >> Site: >> >> http://tapestry.apache.org/ >> >> Feedback is encouraged; just post to users@tapestry.apache.org with [SITE] >> in the subject. >> >> -- >> 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 >> - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry Web Site Updated
Congratulations for the new site, it looks a lot better. One problem, The new site does not work properly with IE7, which is the only one I can use in my company. Somehow I cannot scroll the page down, and "page down" key also doesn't work. On Fri, Nov 19, 2010 at 4:15 PM, Howard Lewis Ship wrote: > We're still working out the kinks ... and I've been working hard on > revising > the tutorial ... but at long last, we're debuting the new Tapestry Web > Site: > > http://tapestry.apache.org/ > > Feedback is encouraged; just post to users@tapestry.apache.org with [SITE] > in the subject. > > -- > 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: tynamo tapestry-security / shiro help
Hi Paul The AuthorizingRealm constructor can take a CacheManager as a parameter. In our case we use the EhCacheManager. That's all you need! Cheers. Alejandro On Fri, Nov 19, 2010 at 12:58 AM, Paul Stanton wrote: > Kalle, > > I'm think I'm making progress however I haven't found a good guide to > confirm I'm on the right track. > > I have a persistent User entity (db+hibernate). The user has multiple roles. > I only really want to use the RequiresRoles annotation on pages (and some > methods) at this point. > > So what I've done so far: > > AuthorizingRealm and my doGetAuthenticationInfo creates a SimpleAccount with > the roles set populated. > > But once the code hits a RequiresRole annotation, the > realm.doGetAuthorizationInfo is called. > > I don't want to go back to my persistent entity at this point since I've > already told the security module about the user's roles. > > How do I make AuthorizingRealm cache the SimpleAccount returned from > doGetAuthenticationInfo and use it for doGetAuthorizationInfo? > > Also, I'd expect this cache element to have the same lifecycle as the user's > session, is that the case? > > Thanks, Paul. > > - > 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
Re: Tapestry 5.2.4 issue
Hi Zubair Is this your error: http://www.slf4j.org/faq.html#IllegalAccessError ? > This error is caused by the static initilizer of the LoggerFactory class > attempting to directly access the SINGLETON field of > org.slf4j.impl.StaticLoggerBinder. While this was allowed in SLF4J 1.5.5 and > earlier, in 1.5.6 and later the SINGLETON field has been marked as private > access. Take a look at this: http://tapestry.1045711.n5.nabble.com/slf4j-conflicting-versions-td3256861.html Cheers. Alejandro. On Sat, Nov 20, 2010 at 8:10 PM, Kalle Korhonen wrote: > If upgrading didn't help, you have multiple slf4j libs in the > classpath (newer api than impl). Using maven? Run mvn dependency:tree. > > Kalle > > > On Sat, Nov 20, 2010 at 10:55 AM, Zubair Nuamaan > wrote: >> >> Thanks, did that and same issue - upgraded to 1.6.1 >> >> How would I find out which libraries are using slf4j internally? >> >> Regards, >> >> Zubair >> -- >> View this message in context: >> http://tapestry.1045711.n5.nabble.com/Tapestry-5-2-4-issue-tp3273778p3273814.html >> Sent from the Tapestry - User mailing list archive at Nabble.com. >> >> - >> 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
RE: Tapestry Web Site Updated
I think the new site is an excellent start. I agree with Javier's comments and would like to add that the red stop signs in the tutorial are a worry. For instance, the first one: "This chapter may look long, but almost all of it is one-time setup for Maven and Eclipse. The actual Tapestry part is really small and simple. Enjoy!" It looks like there is a problem with the page, along the lines of Wikipedia's article warnings made by those editing the text, and with a cursory glance looks more like: "This article is too long and needs cleaning up". i.e.: an instruction aimed at the authors rather than the reader. It's also rather disconcerting, in this example, that the word "enjoy" appears in a big scary warning! There is also a problem with verbosity. I think it's great to have lengthy discussions, but possibly place some of the non-directly-related material and asides in separate boxes titled something like "Additional Information". c. -Original Message- From: Javier Molina [mailto:jav...@comunicamultimedia.com] Sent: 22 November 2010 09:37 To: users@tapestry.apache.org Subject: Re: Tapestry Web Site Updated I haven't explored the site thoroughly, but here are some comments: - in general, the new site looks prettier - it doesn't look good to have a "Tapestry 5.2.3 -- canceled" post on the front page. It's scary and you have to read the rest to know that it's just a release that didn't pass the vote. I know there's now a post above that saying 5.2.4 beta release, I'm commenting about the concept of "fear-about-the-future-of-tapestry" content with such visibility. Do we want things like that to see what potential new users get on their first visit? - news feed titles have too large a font - there's too much text in the left column. I know there are a lot of benefits and features to tapestry, but it looks intimidating. - in the "create your first tapestry project" tutorial, don't make the user choose an archetype or a tapestry version. Write the instructions for the latest stable version. It's better to have that be out of date when a new version comes out (because it still will work) than have the user decide at this stage. Same for the groupId, artifactId, version and package. It's a test project the user is creating, those values are not going to matter. Give the defaults so people can copy and paste the command and have the project created, built and run. - the big red scary warning about the project layout changing across different versions has no reason to be. By the time the user has this problem he will know how to solve it. - after the test project has been created, give the user some pointers on where to find things (pages go in src/main/java/com/example/pages, page templates go in webapp). I know there is a link to the tutorial but if this first experience is too frustrating, people might not even bother to go there. - add something to the archetype with commented out code that the user can uncomment and see something cool happen. It has to be a few lines only, to be easily understandable, and clearly link components in the template with their methods in the page class. - the tapestry tutorial starts unnecessarily verbose about topics not really related to me getting code running and out the door. Strip it to the essentials. If you want to mention Struts and the Servlet API compared to the tapestry way, mention them in a separate chapter so they are easy to find / skip as needed. - there is no table of contents for the tutorial and no indication of how long it takes to complete. - there are too many callouts, warnings and decorations in the tutorial. It is very distracting visually and that makes it hard to follow. It's impossible to scan the pages to get a feel for what you've got ahead of you. Basically, what most of the above boils down to is: make the barrier to entry as absolutely low as possible. All the magic tapestry does for you and how great a framework it is will not matter if people don't get past the initial experience. El 19/11/10 22:15, Howard Lewis Ship escribió: > We're still working out the kinks ... and I've been working hard on revising > the tutorial ... but at long last, we're debuting the new Tapestry Web Site: > > http://tapestry.apache.org/ > > Feedback is encouraged; just post to users@tapestry.apache.org with [SITE] > in the subject. > - 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
Re: Tapestry Web Site Updated
I agree. Well thought out Javier. Regards, Greg On 22/11/2010, at 9:11 PM, Geoff Callender wrote: > Very good observations, all of them. > > On 22/11/2010, at 8:37 PM, Javier Molina wrote: > >> I haven't explored the site thoroughly, but here are some comments: >> >> - in general, the new site looks prettier >> >> - it doesn't look good to have a "Tapestry 5.2.3 -- canceled" post on the >> front page. It's scary and you have to read the rest to know that it's just >> a release that didn't pass the vote. I know there's now a post above that >> saying 5.2.4 beta release, I'm commenting about the concept of >> "fear-about-the-future-of-tapestry" content with such visibility. Do we want >> things like that to see what potential new users get on their first visit? >> >> - news feed titles have too large a font >> >> - there's too much text in the left column. I know there are a lot of >> benefits and features to tapestry, but it looks intimidating. >> >> - in the "create your first tapestry project" tutorial, don't make the user >> choose an archetype or a tapestry version. Write the instructions for the >> latest stable version. It's better to have that be out of date when a new >> version comes out (because it still will work) than have the user decide at >> this stage. Same for the groupId, artifactId, version and package. It's a >> test project the user is creating, those values are not going to matter. >> Give the defaults so people can copy and paste the command and have the >> project created, built and run. >> >> - the big red scary warning about the project layout changing across >> different versions has no reason to be. By the time the user has this >> problem he will know how to solve it. >> >> - after the test project has been created, give the user some pointers on >> where to find things (pages go in src/main/java/com/example/pages, page >> templates go in webapp). I know there is a link to the tutorial but if this >> first experience is too frustrating, people might not even bother to go >> there. >> >> - add something to the archetype with commented out code that the user can >> uncomment and see something cool happen. It has to be a few lines only, to >> be easily understandable, and clearly link components in the template with >> their methods in the page class. >> >> - the tapestry tutorial starts unnecessarily verbose about topics not really >> related to me getting code running and out the door. Strip it to the >> essentials. If you want to mention Struts and the Servlet API compared to >> the tapestry way, mention them in a separate chapter so they are easy to >> find / skip as needed. >> >> - there is no table of contents for the tutorial and no indication of how >> long it takes to complete. >> >> - there are too many callouts, warnings and decorations in the tutorial. It >> is very distracting visually and that makes it hard to follow. It's >> impossible to scan the pages to get a feel for what you've got ahead of you. >> >> Basically, what most of the above boils down to is: make the barrier to >> entry as absolutely low as possible. All the magic tapestry does for you and >> how great a framework it is will not matter if people don't get past the >> initial experience. >> >> El 19/11/10 22:15, Howard Lewis Ship escribió: >>> We're still working out the kinks ... and I've been working hard on revising >>> the tutorial ... but at long last, we're debuting the new Tapestry Web Site: >>> >>> http://tapestry.apache.org/ >>> >>> Feedback is encouraged; just post to users@tapestry.apache.org with [SITE] >>> in the subject. >>> >> >> >> >> - >> 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
Re: Tapestry Web Site Updated
Javier, you are cordially invited to help out by contributing your proposed changes: Please file an ICLA [1] with secret...@apache.org and I'll grant you write access to the wiki. The same holds for everyone. Once your ICLA is on file you may start contributing to the documentation. Uli [1] http://www.apache.org/licenses/icla.pdf Am 22.11.2010 10:37, schrieb Javier Molina: I haven't explored the site thoroughly, but here are some comments: - in general, the new site looks prettier - it doesn't look good to have a "Tapestry 5.2.3 -- canceled" post on the front page. It's scary and you have to read the rest to know that it's just a release that didn't pass the vote. I know there's now a post above that saying 5.2.4 beta release, I'm commenting about the concept of "fear-about-the-future-of-tapestry" content with such visibility. Do we want things like that to see what potential new users get on their first visit? - news feed titles have too large a font - there's too much text in the left column. I know there are a lot of benefits and features to tapestry, but it looks intimidating. - in the "create your first tapestry project" tutorial, don't make the user choose an archetype or a tapestry version. Write the instructions for the latest stable version. It's better to have that be out of date when a new version comes out (because it still will work) than have the user decide at this stage. Same for the groupId, artifactId, version and package. It's a test project the user is creating, those values are not going to matter. Give the defaults so people can copy and paste the command and have the project created, built and run. - the big red scary warning about the project layout changing across different versions has no reason to be. By the time the user has this problem he will know how to solve it. - after the test project has been created, give the user some pointers on where to find things (pages go in src/main/java/com/example/pages, page templates go in webapp). I know there is a link to the tutorial but if this first experience is too frustrating, people might not even bother to go there. - add something to the archetype with commented out code that the user can uncomment and see something cool happen. It has to be a few lines only, to be easily understandable, and clearly link components in the template with their methods in the page class. - the tapestry tutorial starts unnecessarily verbose about topics not really related to me getting code running and out the door. Strip it to the essentials. If you want to mention Struts and the Servlet API compared to the tapestry way, mention them in a separate chapter so they are easy to find / skip as needed. - there is no table of contents for the tutorial and no indication of how long it takes to complete. - there are too many callouts, warnings and decorations in the tutorial. It is very distracting visually and that makes it hard to follow. It's impossible to scan the pages to get a feel for what you've got ahead of you. Basically, what most of the above boils down to is: make the barrier to entry as absolutely low as possible. All the magic tapestry does for you and how great a framework it is will not matter if people don't get past the initial experience. El 19/11/10 22:15, Howard Lewis Ship escribió: We're still working out the kinks ... and I've been working hard on revising the tutorial ... but at long last, we're debuting the new Tapestry Web Site: http://tapestry.apache.org/ Feedback is encouraged; just post to users@tapestry.apache.org with [SITE] in the subject. - 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
Re: Tapestry Web Site Updated
Very good observations, all of them. On 22/11/2010, at 8:37 PM, Javier Molina wrote: > I haven't explored the site thoroughly, but here are some comments: > > - in general, the new site looks prettier > > - it doesn't look good to have a "Tapestry 5.2.3 -- canceled" post on the > front page. It's scary and you have to read the rest to know that it's just a > release that didn't pass the vote. I know there's now a post above that > saying 5.2.4 beta release, I'm commenting about the concept of > "fear-about-the-future-of-tapestry" content with such visibility. Do we want > things like that to see what potential new users get on their first visit? > > - news feed titles have too large a font > > - there's too much text in the left column. I know there are a lot of > benefits and features to tapestry, but it looks intimidating. > > - in the "create your first tapestry project" tutorial, don't make the user > choose an archetype or a tapestry version. Write the instructions for the > latest stable version. It's better to have that be out of date when a new > version comes out (because it still will work) than have the user decide at > this stage. Same for the groupId, artifactId, version and package. It's a > test project the user is creating, those values are not going to matter. Give > the defaults so people can copy and paste the command and have the project > created, built and run. > > - the big red scary warning about the project layout changing across > different versions has no reason to be. By the time the user has this problem > he will know how to solve it. > > - after the test project has been created, give the user some pointers on > where to find things (pages go in src/main/java/com/example/pages, page > templates go in webapp). I know there is a link to the tutorial but if this > first experience is too frustrating, people might not even bother to go there. > > - add something to the archetype with commented out code that the user can > uncomment and see something cool happen. It has to be a few lines only, to be > easily understandable, and clearly link components in the template with their > methods in the page class. > > - the tapestry tutorial starts unnecessarily verbose about topics not really > related to me getting code running and out the door. Strip it to the > essentials. If you want to mention Struts and the Servlet API compared to the > tapestry way, mention them in a separate chapter so they are easy to find / > skip as needed. > > - there is no table of contents for the tutorial and no indication of how > long it takes to complete. > > - there are too many callouts, warnings and decorations in the tutorial. It > is very distracting visually and that makes it hard to follow. It's > impossible to scan the pages to get a feel for what you've got ahead of you. > > Basically, what most of the above boils down to is: make the barrier to entry > as absolutely low as possible. All the magic tapestry does for you and how > great a framework it is will not matter if people don't get past the initial > experience. > > El 19/11/10 22:15, Howard Lewis Ship escribió: >> We're still working out the kinks ... and I've been working hard on revising >> the tutorial ... but at long last, we're debuting the new Tapestry Web Site: >> >> http://tapestry.apache.org/ >> >> Feedback is encouraged; just post to users@tapestry.apache.org with [SITE] >> in the subject. >> > > > > - > 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
Re: Tapestry Web Site Updated
I haven't explored the site thoroughly, but here are some comments: - in general, the new site looks prettier - it doesn't look good to have a "Tapestry 5.2.3 -- canceled" post on the front page. It's scary and you have to read the rest to know that it's just a release that didn't pass the vote. I know there's now a post above that saying 5.2.4 beta release, I'm commenting about the concept of "fear-about-the-future-of-tapestry" content with such visibility. Do we want things like that to see what potential new users get on their first visit? - news feed titles have too large a font - there's too much text in the left column. I know there are a lot of benefits and features to tapestry, but it looks intimidating. - in the "create your first tapestry project" tutorial, don't make the user choose an archetype or a tapestry version. Write the instructions for the latest stable version. It's better to have that be out of date when a new version comes out (because it still will work) than have the user decide at this stage. Same for the groupId, artifactId, version and package. It's a test project the user is creating, those values are not going to matter. Give the defaults so people can copy and paste the command and have the project created, built and run. - the big red scary warning about the project layout changing across different versions has no reason to be. By the time the user has this problem he will know how to solve it. - after the test project has been created, give the user some pointers on where to find things (pages go in src/main/java/com/example/pages, page templates go in webapp). I know there is a link to the tutorial but if this first experience is too frustrating, people might not even bother to go there. - add something to the archetype with commented out code that the user can uncomment and see something cool happen. It has to be a few lines only, to be easily understandable, and clearly link components in the template with their methods in the page class. - the tapestry tutorial starts unnecessarily verbose about topics not really related to me getting code running and out the door. Strip it to the essentials. If you want to mention Struts and the Servlet API compared to the tapestry way, mention them in a separate chapter so they are easy to find / skip as needed. - there is no table of contents for the tutorial and no indication of how long it takes to complete. - there are too many callouts, warnings and decorations in the tutorial. It is very distracting visually and that makes it hard to follow. It's impossible to scan the pages to get a feel for what you've got ahead of you. Basically, what most of the above boils down to is: make the barrier to entry as absolutely low as possible. All the magic tapestry does for you and how great a framework it is will not matter if people don't get past the initial experience. El 19/11/10 22:15, Howard Lewis Ship escribió: We're still working out the kinks ... and I've been working hard on revising the tutorial ... but at long last, we're debuting the new Tapestry Web Site: http://tapestry.apache.org/ Feedback is encouraged; just post to users@tapestry.apache.org with [SITE] in the subject. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry Web Site Updated
On Fri, Nov 19, 2010 at 10:51 PM, Igor Drobiazko wrote: > Great. Thanks to all who was involved. Yep! ... If anyone of you will come here to Italy I owe you a bottle of red wine! Amazing job. Cheers -- Massimo http://meridio.blogspot.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org