- This topic has 67 replies, 30 voices, and was last updated 19 years, 5 months ago by
.
-
Posts
-
It would be really nice to use the deployment tools with my Tapestry projects and then add in Hibernate support.
Well guys I couldn’t really have better news for you, so here goes:
Geoff, the author of the Tapestry plugin Spindle (http://sourceforge.net/projects/spindle) for Eclipse will be working with the MyEclispe team to not only bring Spindle into the mix for our 4.0 release, but further enhance and integrate his work into our existing (and soon-to-be-enhanced) editors and other project framework for the remainder of the 4.x series and likely 5.0 release. We are excited to have Geoff’s tallent on the team and we are looking forward to working together.😀 Great news, because of this thread I decided to have a look at Tapesty. Liked what I saw, bought the book and now these is no going back to Stuts/JSP’s.
The one problem area is that as far as I can tell all my HTML files need to be in the root folder and all the page files in the WEB-INF folder (I could be wrong as I new to tapestry). It would be better if I could split them into multiple sub-folders to group releated pages together?,
Keep up the good work.
Richard
Richard,
I am not terribly versed with Tapestry either but I believe that is merely to protect the page files from being downloaded, so you hide them under WEB-INF. I’m sure you could likely put them under a subdir like WEB-INF/pages.@rgordon wrote:
The one problem area is that as far as I can tell all my HTML files need to be in the root folder and all the page files in the WEB-INF folder (I could be wrong as I new to tapestry). It would be better if I could split them into multiple sub-folders to group releated pages together?,
Keep up the good work.
Richard
Tapestry 3.0 has some pretty complex heuristics available for locating pages, but luckily few people need to know the nitty gritty as it “just works” most of the time.
The complete scheme for locating pages is documented here:
public class PageSpecificationResolver
extends AbstractSpecificationResolverPerforms the tricky work of resolving a page name to a page specification. The search for pages in the application namespace is the most complicated, since Tapestry searches for pages that aren’t explicitly defined in the application specification. The search, based on the simple-name of the page, goes as follows:
* As declared in the application specification
* simple-name.page in the same folder as the application specification
* simple-name page in the WEB-INF/servlet-name directory of the context root
* simple-name.page in WEB-INF
* simple-name.page in the application root (within the context root)
* simple-name.html as a template in the application root, for which an implicit specification is generated
* By searching the framework namespace
* By invoking ISpecificationResolverDelegate.findPageSpecification(IRequestCycle, INamespace, String)Pages in a component library are searched for in a more abbreviated fashion:
* As declared in the library specification
* simple-name.page in the same folder as the library specification
* By searching the framework namespace
* By invoking ISpecificationResolverDelegate.findPageSpecification(IRequestCycle, INamespace, String)For more info on the nitty gritty on this, see the Tapestry docs over at jakarta (or Howard’s Book).
Caveat: The above lookup is for application pages only in Tapestry 3.0. This scheme has been augmented for Tapestry 4.0 (which is not yet supported by Spindle). Similar (but sightly different) lookup schemes exist for Application Components and Library Components – refer to the Tapestry docs!
Also: Spindle does not support the use of
ISpecificationResolverDelegateTemplate files for pages are usually put in the same folder as the .page file or into the context root. There is a special Asset name called $template which allows you to place templates in arbitrary locations (see the docs or the Book for more info).
Hope this helps.
Geoff
Geoff,
can you tell when Tapestry 4.0 will be integrated ? Any chance it will be for 4.0M3 ?
Thanx
saki@sakiss wrote:
Geoff,
can you tell when Tapestry 4.0 will be integrated ? Any chance it will be for 4.0M3 ?
Thanx
sakiI can only speak at this time about Tapestry support in the SF version of Spindle. That work has been delayed and will appear a month or two after the T4 goes final.
Geoff
