AjaxFormLoop
Hello, I would like to know if it is possible in an t:AjaxFormLoop to replace the Addrowlink by a t:Select that adds different values depending on what is chosen in the list ?
Re: [T5.4] split Tapestry application into separate modules
On Wed, 09 Jul 2014 17:38:04 -0300, Ilya Obshadko ilya.obsha...@gmail.com wrote: - component that was moved into separate module can't be loaded by main application using standard namespace; is there any way to fix that? (that is, t:mycomponent/ results in UknownValueException); That's expected: When you changed the component from the application to a component library, you've changed its namespace. You can advise or decorate ComponentClassResolver.resolveComponentTypeToClassName() and resolveMixinTypeToClassName() (for mixins), which are the methods which map logical names to component or mixin class names. - is that possible to run the whole thing within Eclipse without having to install 'module' project into local repository? Yes. Just make sure the webapp module has the component modules in its classpath. Module class autoloading won't work, as there's no JAR for the component libraries included in this way, but then you can use the tapestry.modules VM argument to specify comma-separated fully qualified module class names to be loaded. Another option is to use @Submodule in your AppModule. -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [T5.4] split Tapestry application into separate modules
I think in T 5.4 @Submodule has been deprecated in favor of @ImportModule On Wed, Jul 9, 2014 at 6:05 PM, Thiago H de Paula Figueiredo thiag...@gmail.com wrote: On Wed, 09 Jul 2014 17:38:04 -0300, Ilya Obshadko ilya.obsha...@gmail.com wrote: - component that was moved into separate module can't be loaded by main application using standard namespace; is there any way to fix that? (that is, t:mycomponent/ results in UknownValueException); That's expected: When you changed the component from the application to a component library, you've changed its namespace. You can advise or decorate ComponentClassResolver.resolveComponentTypeToClassName() and resolveMixinTypeToClassName() (for mixins), which are the methods which map logical names to component or mixin class names. - is that possible to run the whole thing within Eclipse without having to install 'module' project into local repository? Yes. Just make sure the webapp module has the component modules in its classpath. Module class autoloading won't work, as there's no JAR for the component libraries included in this way, but then you can use the tapestry.modules VM argument to specify comma-separated fully qualified module class names to be loaded. Another option is to use @Submodule in your AppModule. -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
