It would be useful to see a view-source from when you've moved the Form into a component.
Also, it is always best to give ids to your components, especially anything form related. The URL generated for a form-inside-a-component is different than the URL for a form-on-the-page; you did run the app, let it build new HTML, and work from there, right? On 10/20/05, Derek Brown <[EMAIL PROTECTED]> wrote: > In my home page I have something like: > > <form jwcid="@Form"> > <span jwcid="@PropertySelection" > model="ognl:@[EMAIL PROTECTED]" > value="ognl:currentSelection" > onchange="literal:javascript:this.form.events.submit();"/> > </form> > > This code works fine when its on the home page. If I > move it into another component and then include the > component in the Home page, I always get the error, > component ($Form) not found in home page. > > Any Ideas? > > Component [EMAIL PROTECTED] does not contain > a component $Form. > org.apache.tapestry.AbstractComponent.getComponent(AbstractComponent.java:344) > org.apache.tapestry.AbstractPage.getNestedComponent(AbstractPage.java:229) > org.apache.tapestry.engine.DirectService.service(DirectService.java:101) > > Thanks > > > > __________________________________ > Start your day with Yahoo! - Make it your home page! > http://www.yahoo.com/r/hs > > --------------------------------------------------------------------- > 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]
