You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Eric Everman <ev...@precedadesign.com> on 2003/04/25 23:10:27 UTC
Non-Rendered Component
I have a CRUD (Create, Update, Delete) component that I built to handle
persistence for any class. The component encapsulates the persistence
functions, handling form submissions, and can be used in any page. The
component itself has no visible aspects - either template or direct writing.
Is this a reasonable application of a component in Tapestry, or am I headed
for problems down the road? I see from a previous post that components
that don't show up in the page template somewhere generate server log
warnings - will this continue, or was this an oversight?
Right now my component is generating "Could not find template for component
Home/editor in locale en_US." errors. I'm sure that components aren't
required to have templates, is there some other reason that I might be
getting this error?
Thanks as always,
Eric Everman
Preceda Design LLC
www.precedadesign.com
RE: Non-Rendered Component
Posted by Eric Everman <ev...@precedadesign.com>.
Hey, I like that!
I give it a shot - thanks,
Eric Everman
At 4/25/2003, you wrote:
>Maybe it should be a component used instead of a Form component? That would
>give it a natural place on the page. It could even have a template that
>included a "captive" Form and a RenderBody.
>
>--
>Howard M. Lewis Ship
>Creator, Tapestry: Java Web Components
>http://jakarta.apache.org/tapestry
>
>
>
> > -----Original Message-----
> > From: Eric Everman [mailto:everman@precedadesign.com]
> > Sent: Friday, April 25, 2003 6:24 PM
> > To: Tapestry users
> > Subject: RE: Non-Rendered Component
> >
> >
> > There are a few things that keep me from making it a bean.
> > First, I want
> > access to parameters passed from an externalLink - in this
> > case a parentID,
> > an entityID, a role, and an operation. Second, I wanted to use a
> > persistent state for some editing preferences. Also, I need
> > to get to the
> > IMonitor so that I can use my persistence provider.
> >
> > I could pass enough parameters to a separate CRUD handler
> > bean to make this
> > work, but it seems like some of the Component functionality would be
> > useful. Am I just fighting the system too much here?
> >
> > ee
> >
> > At 4/25/2003, you wrote:
> > >Seems to me this is more of a helper bean than a component. Does it
> > >use any methods inherited from AbstractComponent?
> > >
> > >--
> > >Howard M. Lewis Ship
> > >Creator, Tapestry: Java Web Components
> > >http://jakarta.apache.org/tapestry
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Eric Everman [mailto:everman@precedadesign.com]
> > > > Sent: Friday, April 25, 2003 5:10 PM
> > > > To: Tapestry users
> > > > Subject: Non-Rendered Component
> > > >
> > > >
> > > > I have a CRUD (Create, Update, Delete) component that I built to
> > > > handle persistence for any class. The component encapsulates the
> > > > persistence
> > > > functions, handling form submissions, and can be used in any
> > > > page. The
> > > > component itself has no visible aspects - either template or
> > > > direct writing.
> > > >
> > > > Is this a reasonable application of a component in
> > Tapestry, or am I
> > > > headed for problems down the road? I see from a previous
> > post that
> > > > components
> > > > that don't show up in the page template somewhere
> > generate server log
> > > > warnings - will this continue, or was this an oversight?
> > > >
> > > > Right now my component is generating "Could not find template for
> > > > component Home/editor in locale en_US." errors. I'm sure that
> > > > components aren't
> > > > required to have templates, is there some other reason that I
> > > > might be
> > > > getting this error?
> > > >
> > > > Thanks as always,
> > > >
> > > > Eric Everman
> > > >
> > > > Preceda Design LLC
> > > > www.precedadesign.com
> > > >
> > > >
> > > >
> > --------------------------------------------------------------------
> > > > -
> > > > 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
> >
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: Non-Rendered Component
Posted by "Howard M. Lewis Ship" <hl...@attbi.com>.
Maybe it should be a component used instead of a Form component? That would
give it a natural place on the page. It could even have a template that
included a "captive" Form and a RenderBody.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
> -----Original Message-----
> From: Eric Everman [mailto:everman@precedadesign.com]
> Sent: Friday, April 25, 2003 6:24 PM
> To: Tapestry users
> Subject: RE: Non-Rendered Component
>
>
> There are a few things that keep me from making it a bean.
> First, I want
> access to parameters passed from an externalLink - in this
> case a parentID,
> an entityID, a role, and an operation. Second, I wanted to use a
> persistent state for some editing preferences. Also, I need
> to get to the
> IMonitor so that I can use my persistence provider.
>
> I could pass enough parameters to a separate CRUD handler
> bean to make this
> work, but it seems like some of the Component functionality would be
> useful. Am I just fighting the system too much here?
>
> ee
>
> At 4/25/2003, you wrote:
> >Seems to me this is more of a helper bean than a component. Does it
> >use any methods inherited from AbstractComponent?
> >
> >--
> >Howard M. Lewis Ship
> >Creator, Tapestry: Java Web Components
> >http://jakarta.apache.org/tapestry
> >
> >
> >
> > > -----Original Message-----
> > > From: Eric Everman [mailto:everman@precedadesign.com]
> > > Sent: Friday, April 25, 2003 5:10 PM
> > > To: Tapestry users
> > > Subject: Non-Rendered Component
> > >
> > >
> > > I have a CRUD (Create, Update, Delete) component that I built to
> > > handle persistence for any class. The component encapsulates the
> > > persistence
> > > functions, handling form submissions, and can be used in any
> > > page. The
> > > component itself has no visible aspects - either template or
> > > direct writing.
> > >
> > > Is this a reasonable application of a component in
> Tapestry, or am I
> > > headed for problems down the road? I see from a previous
> post that
> > > components
> > > that don't show up in the page template somewhere
> generate server log
> > > warnings - will this continue, or was this an oversight?
> > >
> > > Right now my component is generating "Could not find template for
> > > component Home/editor in locale en_US." errors. I'm sure that
> > > components aren't
> > > required to have templates, is there some other reason that I
> > > might be
> > > getting this error?
> > >
> > > Thanks as always,
> > >
> > > Eric Everman
> > >
> > > Preceda Design LLC
> > > www.precedadesign.com
> > >
> > >
> > >
> --------------------------------------------------------------------
> > > -
> > > 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: Non-Rendered Component
Posted by Eric Everman <ev...@precedadesign.com>.
There are a few things that keep me from making it a bean. First, I want
access to parameters passed from an externalLink - in this case a parentID,
an entityID, a role, and an operation. Second, I wanted to use a
persistent state for some editing preferences. Also, I need to get to the
IMonitor so that I can use my persistence provider.
I could pass enough parameters to a separate CRUD handler bean to make this
work, but it seems like some of the Component functionality would be
useful. Am I just fighting the system too much here?
ee
At 4/25/2003, you wrote:
>Seems to me this is more of a helper bean than a component. Does it use any
>methods inherited from AbstractComponent?
>
>--
>Howard M. Lewis Ship
>Creator, Tapestry: Java Web Components
>http://jakarta.apache.org/tapestry
>
>
>
> > -----Original Message-----
> > From: Eric Everman [mailto:everman@precedadesign.com]
> > Sent: Friday, April 25, 2003 5:10 PM
> > To: Tapestry users
> > Subject: Non-Rendered Component
> >
> >
> > I have a CRUD (Create, Update, Delete) component that I built
> > to handle
> > persistence for any class. The component encapsulates the
> > persistence
> > functions, handling form submissions, and can be used in any
> > page. The
> > component itself has no visible aspects - either template or
> > direct writing.
> >
> > Is this a reasonable application of a component in Tapestry,
> > or am I headed
> > for problems down the road? I see from a previous post that
> > components
> > that don't show up in the page template somewhere generate server log
> > warnings - will this continue, or was this an oversight?
> >
> > Right now my component is generating "Could not find template
> > for component
> > Home/editor in locale en_US." errors. I'm sure that
> > components aren't
> > required to have templates, is there some other reason that I
> > might be
> > getting this error?
> >
> > Thanks as always,
> >
> > Eric Everman
> >
> > Preceda Design LLC
> > www.precedadesign.com
> >
> >
> > ---------------------------------------------------------------------
> > 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: Non-Rendered Component
Posted by "Howard M. Lewis Ship" <hl...@attbi.com>.
Seems to me this is more of a helper bean than a component. Does it use any
methods inherited from AbstractComponent?
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
> -----Original Message-----
> From: Eric Everman [mailto:everman@precedadesign.com]
> Sent: Friday, April 25, 2003 5:10 PM
> To: Tapestry users
> Subject: Non-Rendered Component
>
>
> I have a CRUD (Create, Update, Delete) component that I built
> to handle
> persistence for any class. The component encapsulates the
> persistence
> functions, handling form submissions, and can be used in any
> page. The
> component itself has no visible aspects - either template or
> direct writing.
>
> Is this a reasonable application of a component in Tapestry,
> or am I headed
> for problems down the road? I see from a previous post that
> components
> that don't show up in the page template somewhere generate server log
> warnings - will this continue, or was this an oversight?
>
> Right now my component is generating "Could not find template
> for component
> Home/editor in locale en_US." errors. I'm sure that
> components aren't
> required to have templates, is there some other reason that I
> might be
> getting this error?
>
> Thanks as always,
>
> Eric Everman
>
> Preceda Design LLC
> www.precedadesign.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>