Hmmm..I'd have to see the rest of your page spec to give an opinion
then...Maybe your components are nested within something else other
than your page? I use getComponent() occassionally and don't see this
problem. Hmmm...
On 8/17/05, Tyler Southwick <[EMAIL PROTECTED]> wrote:
> oh and i forgot to mention that if the component id name is changed to
> some other string, tapestry can find it.
> 
> On 8/17/05, Tyler Southwick <[EMAIL PROTECTED]> wrote:
> > yeah- i have all the properties defined in the page spec and the page
> > class (as abstract getters/setters).  When I run
> > 'getComponent("streetDirections")' I get a component back.  It seems
> > that its just when Tapestry tries to render the page, it cannot find
> > the component.
> >
> > On 8/17/05, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> > > Hmmmm...Are you using tapestry3 I guess? Maybe if you provided the
> > > stack trace error message as well....
> > >
> > > But, could it be that the error you're getting is something about not
> > > being able to find streetDirection or directionModel on your page
> > > class? Does your page define (exactly) the method getDirectionModel()
> > > ? Or...Did you specify a property in your page spec to hold
> > > "streetDirection" or "streetName" ?
> > >
> > > On 8/17/05, Tyler Southwick <[EMAIL PROTECTED]> wrote:
> > > > these are two of the components:
> > > >   <component id="streetDirections" type="PropertySelection">
> > > >     <binding name="value" expression="streetDirection" />
> > > >     <binding name="model" expression="directionModel" />
> > > >   </component>
> > > >
> > > >   <component id="streetNames" type="PropertySelection">
> > > >     <binding name="value" expression="streetName" />
> > > >     <binding name="model" expression="streetNameModel" />
> > > >   </component>
> > > >
> > > > the page does not think that they exist.
> > > >
> > > > On 8/16/05, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> > > > > What do you mean by "Can't find them" ? Could you provide an example
> > > > > of your page spec...
> > > > > On 8/16/05, Tyler Southwick <[EMAIL PROTECTED]> wrote:
> > > > > > I'm trying to create a couple of components in the page 
> > > > > > specification,
> > > > > > but tapestry cannot seem to find them.  The id's are "streetNames" 
> > > > > > and
> > > > > > "streetDirections".  any ideas to solve this problem?
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > --
> > > > > > The pile is the hole's natural enemy
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > 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]
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > The pile is the hole's natural enemy
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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]
> > >
> > >
> >
> >
> > --
> > The pile is the hole's natural enemy
> >
> 
> 
> --
> The pile is the hole's natural enemy
> 
> ---------------------------------------------------------------------
> 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