You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Tyler Southwick <no...@gmail.com> on 2005/08/17 00:21:46 UTC

component id naming conflicts?

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: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: component id naming conflicts?

Posted by Mark Dillon <md...@gmail.com>.
Tyler, can you send the actual stacktrace that you get when this problem occurs?

Thanks,
Mark

On 8/17/05, Jesse Kuhnert <jk...@gmail.com> wrote:
> 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 <no...@gmail.com> 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 <no...@gmail.com> 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 <jk...@gmail.com> 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 <no...@gmail.com> 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 <jk...@gmail.com> 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 <no...@gmail.com> 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: tapestry-user-unsubscribe@jakarta.apache.org
> > > > > > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > > > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > The pile is the hole's natural enemy
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > The pile is the hole's natural enemy
> > >
> >
> >
> > --
> > The pile is the hole's natural enemy
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: component id naming conflicts?

Posted by Jesse Kuhnert <jk...@gmail.com>.
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 <no...@gmail.com> 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 <no...@gmail.com> 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 <jk...@gmail.com> 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 <no...@gmail.com> 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 <jk...@gmail.com> 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 <no...@gmail.com> 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: tapestry-user-unsubscribe@jakarta.apache.org
> > > > > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > The pile is the hole's natural enemy
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > >
> > >
> >
> >
> > --
> > The pile is the hole's natural enemy
> >
> 
> 
> --
> The pile is the hole's natural enemy
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: component id naming conflicts?

Posted by Tyler Southwick <no...@gmail.com>.
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 <no...@gmail.com> 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 <jk...@gmail.com> 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 <no...@gmail.com> 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 <jk...@gmail.com> 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 <no...@gmail.com> 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: tapestry-user-unsubscribe@jakarta.apache.org
> > > > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > The pile is the hole's natural enemy
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
> 
> 
> --
> The pile is the hole's natural enemy
> 


-- 
The pile is the hole's natural enemy

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: component id naming conflicts?

Posted by Tyler Southwick <no...@gmail.com>.
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 <jk...@gmail.com> 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 <no...@gmail.com> 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 <jk...@gmail.com> 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 <no...@gmail.com> 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: tapestry-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > >
> > >
> >
> >
> > --
> > The pile is the hole's natural enemy
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> 
> 


-- 
The pile is the hole's natural enemy

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: component id naming conflicts?

Posted by Jesse Kuhnert <jk...@gmail.com>.
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 <no...@gmail.com> 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 <jk...@gmail.com> 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 <no...@gmail.com> 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: tapestry-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
> 
> 
> --
> The pile is the hole's natural enemy
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: component id naming conflicts?

Posted by Tyler Southwick <no...@gmail.com>.
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 <jk...@gmail.com> 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 <no...@gmail.com> 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: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> 
> 


-- 
The pile is the hole's natural enemy

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: component id naming conflicts?

Posted by Jesse Kuhnert <jk...@gmail.com>.
What do you mean by "Can't find them" ? Could you provide an example
of your page spec...
On 8/16/05, Tyler Southwick <no...@gmail.com> 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: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org