well, this is just a very specific situation when refactoring out to a component actually isnt the best way of avoiding duplicated html/code. The java code behind it is in superclass that is a page class and if I pull it out into a component I loose a lot of what's in place in my page classes.
On Fri, 2005-10-14 at 13:46 -0700, Robert Zeigler wrote: > I've never personally used the delegator component. > Q: Why do you not want to make the html a component? > > Robert > > Dan Adams wrote: > > Yeah, I want to html to be included and processed as it were in the > > original page. How do you do this with delegator? > > > > On Thu, 2005-10-13 at 15:39 -0700, Robert Zeigler wrote: > > > >>Depends on whether you want tapestry to process the html or not. > >>Somebody mentioned the delegator, which may handle the case where the > >>text being included contains tapestry components, etc. > >>In the case where you're dealing with a .html that does /not/ utilize > >>any "tapestry-isms", you can try "Include" from tassel. > >>Something like: > >><div jwcid="@incl:Include" file="ognl:assets.myHtmlFile"/> > >> > >>Robert > >> > > > > > > > > > > --------------------------------------------------------------------- > > 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] > -- Dan Adams Software Engineer Interactive Factory --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
