You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Gregg D Bolinger <gt...@gmail.com> on 2005/02/27 08:29:40 UTC
IComponent getString() deprecated
On all my page classes that extend BasePage I get the following
warning when compiling
getString() in org.apache.tapestry.IComponent has been deprecated.
Is there something I should be using/doing instead? Even a page as simple as
public abstract class SomePage extends BasePage {
}
If I compile that, I get the warning.
Thanks.
Gregg
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: IComponent getString() deprecated
Posted by Paul Jungwirth <pa...@hotmail.com>.
I have noticed this, too. It is very annoying! But we should gripe to Sun
about it. It is a bug with the Java 5 compiler:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5086088
This will produce a warning compiling just B.java:
public interface IA {
/** @deprecated */
void f();
}
public class A implements IA {
public void f() { }
}
public class B extends A {
}
Paul
>From: sales <sales1@digiatlas.net>
>Reply-To: "Tapestry users"
<tapestry-user@jakarta.apache.org>
>To: Tapestry users <tapestry-user@jakarta.apache.org>
>Subject: Re: IComponent getString() deprecated
>Date: Sun, 27 Feb 2005 19:35:55 +0000
>
>Are you sure you are looking in the right place. You said:
>
>"Even a page as simple as:
>
>public abstract class SomePage extends BasePage {}
>
>"
>
>produces the error. What happens if you start a new project and just
>have one page with the above? Do you get it then?
>
>Unless someone can see something obvious here that I can't from the
>info you've given, I think you need to pin it down a bit more with
>some simple tests.
>
>dd
>
>
>Gregg D Bolinger wrote:
>>Ok, show me where I am using getString()..
>>
>>public abstract class EmployeeSearch extends BasePage implements
>>PageRenderListener {
>>
>> public abstract void setEmployee(Employee employee);
>> public abstract Employee getEmployee();
>> public abstract void setIssue(Issue issue);
>> public abstract Issue getIssue();
>> public abstract boolean isEmployeeFound();
>> public abstract void setEmployeeFound(boolean found);
>> public abstract boolean isIssuesFound();
>> public abstract void setIssuesFound(boolean found);
>>
>> public void pageBeginRender(PageEvent event){
>> if (getEmployee() == null)
>> setEmployee(new Employee());
>> if (getIssue() == null)
>> setIssue(new Issue());
>> }
>>
>> public void doSearch(IRequestCycle cycle){
>> Integer empId = getEmployee().getEmployeeId();
>> try {
>> Employee employee = new EmployeeDAO().getEmployee(empId);
>> setEmployeeFound(true);
>> setEmployee(employee);
>> ArrayList issueList = new ArrayList(new
>>IssueDAO().getAllIssesForEmployee(empId));
>> setIssuesFound(true);
>> }catch(ObjectNotFoundException oe){
>> setEmployeeFound(false);
>> setIssuesFound(false);
>> String errorMessage =
getMessage("empNotFoundError");
>> IValidationDelegate validationDelegate =
>>(IValidationDelegate)getBeans().getBean("delegate");
>> validationDelegate.record(errorMessage,
>>ValidationConstraint.CONSISTENCY);
>> }catch(ServiceException se){
>> setEmployeeFound(false);
>> setIssuesFound(false);
>> }catch(NumberFormatException ne){
>> setEmployeeFound(false);
>> setIssuesFound(false);
>> }
>> }
>>}
>>
>>
>>Gregg Bolinger
>>
>>
>>
>>On Sun, 27 Feb 2005 11:38:58 -0600, Geoff Longman
>><glongman@gmail.com> wrote:
>>
>>>The change from getString to getMessage came in 3.0 so use that.
>>>
>>>Geoff
>>>
>>>
>>>On Sun, 27 Feb 2005 09:22:23 -0600, Gregg D Bolinger
>>><gthought@gmail.com> wrote:
>>>
>>>>Ok, so I see that it is to be replaced in 3.1 with
getMessage().
>>>>So
>>>>do I just live with the warnings for now or is there
something I
>>>>can
>>>>change to force getMessage() now instead of getString().
I'm not
>>>>using that method specifically at all in my code.
>>>>
>>>>Thanks.
>>>>
>>>>Gregg
>>>>
>>>>
>>>>On Sun, 27 Feb 2005 07:33:07 -0500, Howard Lewis Ship
>>>><hlship@gmail.com > wrote:
>>>>
>>>>>http://jakarta.apache.org/tapestry/doc/api/org/apache/tapestry/IComponent.html#getString(java.lang.String
>>>>>)
>>>>>
>>>>>
>>>>>On Sun, 27 Feb 2005 01:29:40 -0600, Gregg D Bolinger
>>>>><gthought@gmail.com > wrote:
>>>>>
>>>>>>On all my page classes that extend BasePage I get
the following
>>>>>>warning when compiling
>>>>>>
>>>>>>getString() in org.apache.tapestry.IComponent has
been
>>>>>>deprecated.
>>>>>>
>>>>>>Is there something I should be using/doing instead?
Even a
>>>>>>page as simple as
>>>>>>
>>>>>>public abstract class SomePage extends BasePage {
>>>>>>
>>>>>>}
>>>>>>
>>>>>>If I compile that, I get the warning.
>>>>>>
>>>>>>Thanks.
>>>>>>
>>>>>>Gregg
>>>>>>
>>>>>>---------------------------------------------------------------------
>>>>>>To unsubscribe, e-mail:
>>>>>>tapestry-user-unsubscribe@jakarta.apache.org
>>>>>>For additional commands, e-mail:
>>>>>>tapestry-user-help@jakarta.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>--
>>>>>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:
>>>>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: IComponent getString() deprecated
Posted by sales <sa...@digiatlas.net>.
Are you sure you are looking in the right place. You said:
"Even a page as simple as:
public abstract class SomePage extends BasePage {}
"
produces the error. What happens if you start a new project and just
have one page with the above? Do you get it then?
Unless someone can see something obvious here that I can't from the info
you've given, I think you need to pin it down a bit more with some
simple tests.
dd
Gregg D Bolinger wrote:
> Ok, show me where I am using getString()..
>
> public abstract class EmployeeSearch extends BasePage implements
> PageRenderListener {
>
> public abstract void setEmployee(Employee employee);
> public abstract Employee getEmployee();
> public abstract void setIssue(Issue issue);
> public abstract Issue getIssue();
> public abstract boolean isEmployeeFound();
> public abstract void setEmployeeFound(boolean found);
> public abstract boolean isIssuesFound();
> public abstract void setIssuesFound(boolean found);
>
> public void pageBeginRender(PageEvent event){
> if (getEmployee() == null)
> setEmployee(new Employee());
> if (getIssue() == null)
> setIssue(new Issue());
> }
>
> public void doSearch(IRequestCycle cycle){
> Integer empId = getEmployee().getEmployeeId();
> try {
> Employee employee = new EmployeeDAO().getEmployee(empId);
> setEmployeeFound(true);
> setEmployee(employee);
> ArrayList issueList = new ArrayList(new
> IssueDAO().getAllIssesForEmployee(empId));
> setIssuesFound(true);
> }catch(ObjectNotFoundException oe){
> setEmployeeFound(false);
> setIssuesFound(false);
> String errorMessage = getMessage("empNotFoundError");
> IValidationDelegate validationDelegate =
> (IValidationDelegate)getBeans().getBean("delegate");
> validationDelegate.record(errorMessage,
> ValidationConstraint.CONSISTENCY);
> }catch(ServiceException se){
> setEmployeeFound(false);
> setIssuesFound(false);
> }catch(NumberFormatException ne){
> setEmployeeFound(false);
> setIssuesFound(false);
> }
> }
> }
>
>
> Gregg Bolinger
>
>
>
> On Sun, 27 Feb 2005 11:38:58 -0600, Geoff Longman <gl...@gmail.com> wrote:
>
>>The change from getString to getMessage came in 3.0 so use that.
>>
>>Geoff
>>
>>
>>On Sun, 27 Feb 2005 09:22:23 -0600, Gregg D Bolinger <gt...@gmail.com> wrote:
>>
>>>Ok, so I see that it is to be replaced in 3.1 with getMessage(). So
>>>do I just live with the warnings for now or is there something I can
>>>change to force getMessage() now instead of getString(). I'm not
>>>using that method specifically at all in my code.
>>>
>>>Thanks.
>>>
>>>Gregg
>>>
>>>
>>>On Sun, 27 Feb 2005 07:33:07 -0500, Howard Lewis Ship <hlship@gmail.com > wrote:
>>>
>>>>http://jakarta.apache.org/tapestry/doc/api/org/apache/tapestry/IComponent.html#getString(java.lang.String )
>>>>
>>>>
>>>>On Sun, 27 Feb 2005 01:29:40 -0600, Gregg D Bolinger <gthought@gmail.com > wrote:
>>>>
>>>>>On all my page classes that extend BasePage I get the following
>>>>>warning when compiling
>>>>>
>>>>>getString() in org.apache.tapestry.IComponent has been deprecated.
>>>>>
>>>>>Is there something I should be using/doing instead? Even a page as simple as
>>>>>
>>>>>public abstract class SomePage extends BasePage {
>>>>>
>>>>>}
>>>>>
>>>>>If I compile that, I get the warning.
>>>>>
>>>>>Thanks.
>>>>>
>>>>>Gregg
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>--
>>>>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: 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: IComponent getString() deprecated
Posted by Gregg D Bolinger <gt...@gmail.com>.
Ok, show me where I am using getString()..
public abstract class EmployeeSearch extends BasePage implements
PageRenderListener {
public abstract void setEmployee(Employee employee);
public abstract Employee getEmployee();
public abstract void setIssue(Issue issue);
public abstract Issue getIssue();
public abstract boolean isEmployeeFound();
public abstract void setEmployeeFound(boolean found);
public abstract boolean isIssuesFound();
public abstract void setIssuesFound(boolean found);
public void pageBeginRender(PageEvent event){
if (getEmployee() == null)
setEmployee(new Employee());
if (getIssue() == null)
setIssue(new Issue());
}
public void doSearch(IRequestCycle cycle){
Integer empId = getEmployee().getEmployeeId();
try {
Employee employee = new EmployeeDAO().getEmployee(empId);
setEmployeeFound(true);
setEmployee(employee);
ArrayList issueList = new ArrayList(new
IssueDAO().getAllIssesForEmployee(empId));
setIssuesFound(true);
}catch(ObjectNotFoundException oe){
setEmployeeFound(false);
setIssuesFound(false);
String errorMessage = getMessage("empNotFoundError");
IValidationDelegate validationDelegate =
(IValidationDelegate)getBeans().getBean("delegate");
validationDelegate.record(errorMessage,
ValidationConstraint.CONSISTENCY);
}catch(ServiceException se){
setEmployeeFound(false);
setIssuesFound(false);
}catch(NumberFormatException ne){
setEmployeeFound(false);
setIssuesFound(false);
}
}
}
Gregg Bolinger
On Sun, 27 Feb 2005 11:38:58 -0600, Geoff Longman <gl...@gmail.com> wrote:
> The change from getString to getMessage came in 3.0 so use that.
>
> Geoff
>
>
> On Sun, 27 Feb 2005 09:22:23 -0600, Gregg D Bolinger <gt...@gmail.com> wrote:
> > Ok, so I see that it is to be replaced in 3.1 with getMessage(). So
> > do I just live with the warnings for now or is there something I can
> > change to force getMessage() now instead of getString(). I'm not
> > using that method specifically at all in my code.
> >
> > Thanks.
> >
> > Gregg
> >
> >
> > On Sun, 27 Feb 2005 07:33:07 -0500, Howard Lewis Ship <hlship@gmail.com > wrote:
> > > http://jakarta.apache.org/tapestry/doc/api/org/apache/tapestry/IComponent.html#getString(java.lang.String )
> > >
> > >
> > > On Sun, 27 Feb 2005 01:29:40 -0600, Gregg D Bolinger <gthought@gmail.com > wrote:
> > > > On all my page classes that extend BasePage I get the following
> > > > warning when compiling
> > > >
> > > > getString() in org.apache.tapestry.IComponent has been deprecated.
> > > >
> > > > Is there something I should be using/doing instead? Even a page as simple as
> > > >
> > > > public abstract class SomePage extends BasePage {
> > > >
> > > > }
> > > >
> > > > If I compile that, I get the warning.
> > > >
> > > > Thanks.
> > > >
> > > > Gregg
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > 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: 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: IComponent getString() deprecated
Posted by Geoff Longman <gl...@gmail.com>.
The change from getString to getMessage came in 3.0 so use that.
Geoff
On Sun, 27 Feb 2005 09:22:23 -0600, Gregg D Bolinger <gt...@gmail.com> wrote:
> Ok, so I see that it is to be replaced in 3.1 with getMessage(). So
> do I just live with the warnings for now or is there something I can
> change to force getMessage() now instead of getString(). I'm not
> using that method specifically at all in my code.
>
> Thanks.
>
> Gregg
>
>
> On Sun, 27 Feb 2005 07:33:07 -0500, Howard Lewis Ship <hlship@gmail.com > wrote:
> > http://jakarta.apache.org/tapestry/doc/api/org/apache/tapestry/IComponent.html#getString(java.lang.String )
> >
> >
> > On Sun, 27 Feb 2005 01:29:40 -0600, Gregg D Bolinger <gthought@gmail.com > wrote:
> > > On all my page classes that extend BasePage I get the following
> > > warning when compiling
> > >
> > > getString() in org.apache.tapestry.IComponent has been deprecated.
> > >
> > > Is there something I should be using/doing instead? Even a page as simple as
> > >
> > > public abstract class SomePage extends BasePage {
> > >
> > > }
> > >
> > > If I compile that, I get the warning.
> > >
> > > Thanks.
> > >
> > > Gregg
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > >
> > >
> >
> >
> > --
> > 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: 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: How to make a component that uses another component?
Posted by Vince Marco <vm...@mac.com>.
I led a small team which built several webapps on Tapestry 3.0 before
TIA was released. The trick is not trying to apply everything in
Tapestry and focus on the basic webapp functions needed. You can
always grow into the rest of Tapestry as you go. Of course that isn't
much comfort to folks who are "top-down" learners.
I do agree that there still are some essentials to learn for basic
Tapestry apps, and now that TIA is out it is an almost necessary path
for Tapestry development.
Vince
On Mar 1, 2005, at 8:01 AM, Kevin Menard wrote:
> Yeah, it's taken me a while to get somewhat decent with it, but I
> don't think the learning curve is that high. Perhaps having a
> background in GUI programming was a help, but Tapestry immediately
> felt more natural to me than servlets & JSP. What I didn't like is
> the "barrier to entry". By this I mean I basically went with Tapestry
> based upon some reviews I had read. I really couldn't grasp how it
> worked until I paid for TIA. Typically, I try a new technology a bit
> first and then buy a book if necessary. Here, I had to buy the book
> before I could do much of anything, so I was taking a lot on blind
> faith. With that being said though, there have been a few great
> tutorials that have popped up since then. Additionally, the email
> list is immeasurably helpful.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: How to make a component that uses another component?
Posted by Kevin Menard <ni...@negativetwenty.net>.
On Mar 1, 2005, at 4:00 AM, Cin Peng wrote:
> Yup.. now I get it.. actually tapestry apps are no more than small
> components interwovened with each other to function as a complete
> apps...
>
> I am still trying to unlearn my JSPs.. but I can feel it that the
> learning curve is almost over. I am glad I took the time to learn
> tapestry (which has pretty high learning curve I must admit).
Yeah, it's taken me a while to get somewhat decent with it, but I don't
think the learning curve is that high. Perhaps having a background in
GUI programming was a help, but Tapestry immediately felt more natural
to me than servlets & JSP. What I didn't like is the "barrier to
entry". By this I mean I basically went with Tapestry based upon some
reviews I had read. I really couldn't grasp how it worked until I paid
for TIA. Typically, I try a new technology a bit first and then buy a
book if necessary. Here, I had to buy the book before I could do much
of anything, so I was taking a lot on blind faith. With that being
said though, there have been a few great tutorials that have popped up
since then. Additionally, the email list is immeasurably helpful.
--
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: How to make a component that uses another component?
Posted by Cin Peng <ro...@onepixel.com.my>.
Yup.. now I get it.. actually tapestry apps are no more than small
components interwovened with each other to function as a complete apps...
I am still trying to unlearn my JSPs.. but I can feel it that the learning
curve is almost over. I am glad I took the time to learn tapestry (which has
pretty high learning curve I must admit).
----- Original Message -----
From: "Kevin Menard" <ni...@negativetwenty.net>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Tuesday, March 01, 2005 1:45 PM
Subject: Re: How to make a component that uses another component?
>
> On Feb 28, 2005, at 7:50 AM, Kevin Menard wrote:
>
>> Hope that helps you out a bit. It's really a custom component containing
>> a custom component, but the idea is the same.
>
> Oops. It's not really a custom component containing a custom component.
> It's a custom component containing a Form component. The general idea is
> still the same though.
>
> --
> Kevin
>
>
> ---------------------------------------------------------------------
> 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: How to make a component that uses another component?
Posted by Kevin Menard <ni...@negativetwenty.net>.
On Feb 28, 2005, at 7:50 AM, Kevin Menard wrote:
> Hope that helps you out a bit. It's really a custom component
> containing a custom component, but the idea is the same.
Oops. It's not really a custom component containing a custom
component. It's a custom component containing a Form component. The
general idea is still the same though.
--
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: How to make a component that uses another component?
Posted by Jamie Orchard-Hays <ja...@dang.com>.
Just to add the the concept of this--a Tapestry page is a special sort
of component and every page uses components in it. So using a component
in a component is conceptually the same thing.
On Feb 28, 2005, at 7:50 AM, Kevin Menard wrote:
> On Feb 28, 2005, at 4:20 AM, Cin Peng wrote:
>
>> However I am trying to create another component that makes use of
>> this component (sort of component 1 read a text file and then
>> component 2 displays the file in the browser).
>>
>> Is this possible? any example somewhere? Or can anyone point me to
>> any tutorial that does this?
>
> Sure, you can have components of components. I'm not aware of a
> tutorial, but I can point you at an example. Note that in this
> example, I have a custom component that wraps around a form. It's
> used to abstract the common username & password form. Have a look at
> the UserAuthPanel files at:
>
> http://www.negativetwenty.net/svn/bookmarker/trunk/context/WEB-INF/
>
> and an example of the component's use on the Login page:
>
> http://www.negativetwenty.net/svn/bookmarker/trunk/context/WEB-INF/
> pages/Login.html
>
> Hope that helps you out a bit. It's really a custom component
> containing a custom component, but the idea is the same.
>
> --
> Kevin
>
>
> ---------------------------------------------------------------------
> 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: How to make a component that uses another component?
Posted by Kevin Menard <ni...@negativetwenty.net>.
On Feb 28, 2005, at 4:20 AM, Cin Peng wrote:
> However I am trying to create another component that makes use of this
> component (sort of component 1 read a text file and then component 2
> displays the file in the browser).
>
> Is this possible? any example somewhere? Or can anyone point me to any
> tutorial that does this?
Sure, you can have components of components. I'm not aware of a
tutorial, but I can point you at an example. Note that in this
example, I have a custom component that wraps around a form. It's used
to abstract the common username & password form. Have a look at the
UserAuthPanel files at:
http://www.negativetwenty.net/svn/bookmarker/trunk/context/WEB-INF/
and an example of the component's use on the Login page:
http://www.negativetwenty.net/svn/bookmarker/trunk/context/WEB-INF/
pages/Login.html
Hope that helps you out a bit. It's really a custom component
containing a custom component, but the idea is the same.
--
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
How to make a component that uses another component?
Posted by Cin Peng <ro...@onepixel.com.my>.
Hi,
I am a Tapestry newbie.., I have just created a component myself and it
works fine.
However I am trying to create another component that makes use of this
component (sort of component 1 read a text file and then component 2
displays the file in the browser).
Is this possible? any example somewhere? Or can anyone point me to any
tutorial that does this?
Thanks & Cheers.
Cin Peng.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: IComponent getString() deprecated
Posted by Gregg D Bolinger <gt...@gmail.com>.
Ok, so I see that it is to be replaced in 3.1 with getMessage(). So
do I just live with the warnings for now or is there something I can
change to force getMessage() now instead of getString(). I'm not
using that method specifically at all in my code.
Thanks.
Gregg
On Sun, 27 Feb 2005 07:33:07 -0500, Howard Lewis Ship <hl...@gmail.com> wrote:
> http://jakarta.apache.org/tapestry/doc/api/org/apache/tapestry/IComponent.html#getString(java.lang.String)
>
>
> On Sun, 27 Feb 2005 01:29:40 -0600, Gregg D Bolinger <gt...@gmail.com> wrote:
> > On all my page classes that extend BasePage I get the following
> > warning when compiling
> >
> > getString() in org.apache.tapestry.IComponent has been deprecated.
> >
> > Is there something I should be using/doing instead? Even a page as simple as
> >
> > public abstract class SomePage extends BasePage {
> >
> > }
> >
> > If I compile that, I get the warning.
> >
> > Thanks.
> >
> > Gregg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
>
>
> --
> 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: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
New edition Tapestry in Action book?
Posted by Francis Amanfo <fa...@tydex.com>.
Hi Howard,
With all the major changes coming up in 3.1, is there also a concurrent
update of Tapestry in Action book to reflect all those changes? In other
words, is there a new edition of the book already in the works? I know at
Manning there is a way to subscribe to these early works, which is something I
would really want to do.
Regards,
Francis
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: IComponent getString() deprecated
Posted by Howard Lewis Ship <hl...@gmail.com>.
http://jakarta.apache.org/tapestry/doc/api/org/apache/tapestry/IComponent.html#getString(java.lang.String)
On Sun, 27 Feb 2005 01:29:40 -0600, Gregg D Bolinger <gt...@gmail.com> wrote:
> On all my page classes that extend BasePage I get the following
> warning when compiling
>
> getString() in org.apache.tapestry.IComponent has been deprecated.
>
> Is there something I should be using/doing instead? Even a page as simple as
>
> public abstract class SomePage extends BasePage {
>
> }
>
> If I compile that, I get the warning.
>
> Thanks.
>
> Gregg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
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: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org