I think I looked at this so long I got tunnel vision. Thank you very much.

On 3/4/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Found your problem.

Inside SearchForm.html:

<t:comp type="SearchForm"
xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>

The first thing your SearchForm says is that another SearchForm is
nested inside it.  There's your infinite recursion.

This has already been identified as a bug:

https://issues.apache.org/jira/browse/TAPESTRY-1275

I think you want to recode it as:

        <div id="searchFormContainer
xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd"";>
                <form t:type="Form">
                        <fieldset>
                                <legend>Search Form</legend>
                                <div id="searchStringContainer">
                                        <label t:type="Label"
t:for="searchString">Search Text</label>
                                        <input t:type="TextField"
t:id="searchString" type="text" />
                                </div>
                                <div id="searchFormControlsContainer">
                                        <input id="submitSearch"
type="submit" value="Search" />
                                </div>
                        </fieldset>
                </form>
        </div>



On 3/3/07, Todd Orr <[EMAIL PROTECTED]> wrote:
> 1. start jboss or tomcat
> 2. deploy war (using mvn tomcat:deploy, for example)
> 3. attempt to resolve url
> 4. OOME
>
> Seems to be something about this particular component. I created a
> simple Border component that uses no dynamic data, property access,
> etc. It seemed to work. However, this component that is included in
> the project is trouble.
>
> Is there some specific information I could provide that would be more
> useful? Is the exception not reproducible?
>
> On 3/4/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> > That's nice but please identify what led up to the OOME.
> >
> > On 3/3/07, Todd Orr <[EMAIL PROTECTED]> wrote:
> > > It seems that even a simple component causes an OutOfMemoryError
> > > exception to be thrown. This happens with both JBoss4.0.4GA and Tomcat
> > > 5.5.
> > >
> > > I've attached a simple sample project.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > Howard M. Lewis Ship
> > TWD Consulting, Inc.
> > Independent J2EE / Open-Source Java Consultant
> > Creator and PMC Chair, Apache Tapestry
> > Creator, Apache 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
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache 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]

Reply via email to