Please add a bug in JIRA. It should accept component types with slashes, as you attempted in your HTML template.
On 8/19/05, Denis Souza <[EMAIL PROTECTED]> wrote: > When you said it was working I went back to my code to find out what was > wrong with it. I found out it really works pretty well if I reference the > component in my java code as an annotation, for example: > > @Component(id = "template", type = "templates/MyTemplate") > public abstract MyTemplate getTemplateComponent(); > > where in the html template I would have: > > <div jwcid="template"> > > > However, if I try to reference the component directly from the html template > like this: > > <div jwcid="@templates/MyTemplate"> > > I get: > > org.apache.tapestry.parse.TemplateParseException > Tag <div> on line 4 contains an invalid jwcid '@template/MyTemplate'. > > > -----Original Message----- > From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] > Sent: quinta-feira, 18 de agosto de 2005 17:11 > To: Tapestry users > Subject: Re: Components with no spec file > > There were some bugs that were fixed in 4.0 beta-4 (the currently > available release). I am using this in my production application, so > I'm pretty sure it works. > > On 8/18/05, Denis Souza <[EMAIL PROTECTED]> wrote: > > Has anyone here played around with components that don't have a > > specification file? I heard there was some bug in a previous version o > > Tapestry 4 (beta 2, I think) that wouldn't allow you to do it but I don't > > know what the status is today. > > > > > > > > I have been able to do it with pages with no problems. With components, I > > was able to do it by implementing an ITemplateSourceDelegate that did some > > magic. The problem is that if Tapestry will eventually support it, by > using > > my implementation I might end up with a bunch of pages that reference > > components my way, which may be incompatible with Tapestry's official > > implementation. (eg. a component inside the shopping cart folder would be > > referenced as: "shoppingcart/ProductList" but with Tapestry it may be > > different). Anyway, I didn't write an implementation of > > ITemplateSourceDelegate to do that, I wrote it so I could place my page > > templates in any folder I want to (other than Tapestry's defaults), the > > ability to use components without a spec file was just a bonus. > > > > > > > > So what I'd like to know is if there's already some standard Tapestry way > of > > creating components without the spec file and, if so, how do I do it? And > > how would I reference them from within my pages? > > > > > > > > Denis Souza > > > > > > > > > > > > > -- > Howard M. Lewis Ship > Independent J2EE / Open-Source Java Consultant > Creator, Jakarta Tapestry > Creator, Jakarta HiveMind > > Professional Tapestry training, mentoring, support > and project work. http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
