You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Jean-Yves Sironneau <ep...@gmail.com> on 2005/03/23 13:32:27 UTC
3.1 and abstract properties
Hello,
I don't know if i miss something or not but i'am testing 3.1 alpha1
and i have a question about it.
I have a page that implements an interface that defines a property of
my page. And i get an
AbstractMethodError when trying to call a method defined in this
interface (same thing
if the property is explicit in the page specificatrion or not). Do you
think it's the attended behavior or should Tapestry dynamically create
a property for it ?
Jean-Yves
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: 3.1 and abstract properties
Posted by Howard Lewis Ship <hl...@gmail.com>.
I need to check up on this and ensure that the new enhancement
pipeline "sees" properties that are inherted from interfaces and/or
base classes.
On Wed, 23 Mar 2005 10:30:09 -0800, Derick Fernando
<de...@thelabllc.com> wrote:
> Quoting Derick Fernando <de...@thelabllc.com>:
>
> > Quoting jys <jy...@fr.st>:
> >
> > > Yes, but i think that as generics are "erased" at runtime Tapestry is
> > > able to create properties using generics. And generics property worked
> > > for 3.0.
> > >
> > >
> > > Derick Fernando wrote:
> > >
> > > >Quoting Erik Hatcher <er...@ehatchersolutions.com>:
> > > >
> > > >
> > > >
> > > >>*shrugs*.... Howard?
> > > >>
> > > >> Erik
> > > >>
> > > >>On Mar 23, 2005, at 9:02 AM, jyjeanyves@free.fr wrote:
> > > >>
> > > >>
> > > >>
> > > >>>Hum, i think it worked with 3.0.
> > > >>>
> > > >>>Here is the example :
> > > >>>
> > > >>>public interface IDocumentProperty extends IPage {
> > > >>>
> > > >>> public Photo getDocument();
> > > >>>
> > > >>> public void setDocument(Photo doc);
> > > >>>
> > > >>> public void setDocumentsIds(List<String> docsIds);
> > > >>>
> > > >>> public List<String> getDocumentsIds();
> > > >>>
> > > >>>}
> > > >>>
> > > >>>public abstract class DocumentPage extends JPhotoWikiBasePage
> > > >>>implements
> > > >>> PageBeginRenderListener, IDocumentProperty {
> > > >>>
> > > >>>........
> > > >>>}
> > > >>>
> > > >>>public abstract class ViewDocumentPage extends DocumentPage {
> > > >>>
> > > >>>......
> > > >>>}
> > > >>>
> > > >>>ViewDocumentPage specification :
> > > >>>
> > > >>> <property name="documentsIds" persist="session"/>
> > > >>>
> > > >>>
> > > >>>If i declare an abstract method in setDocumentsIds in ViewDocumentPage
> > > >>>it works,
> > > >>>but the goal was to make tapestry create things on the fly.
> > > >>>
> > > >>>Hope it's more understandable.
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>Quoting Erik Hatcher <er...@ehatchersolutions.com>:
> > > >>>
> > > >>>
> > > >>>
> > > >>>>Did this work with 3.0?
> > > >>>>
> > > >>>>Please provide a concrete example.
> > > >>>>
> > > >>>> Erik
> > > >>>>
> > > >>>>On Mar 23, 2005, at 7:32 AM, Jean-Yves Sironneau wrote:
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>>Hello,
> > > >>>>>
> > > >>>>>I don't know if i miss something or not but i'am testing 3.1 alpha1
> > > >>>>>and i have a question about it.
> > > >>>>>
> > > >>>>>I have a page that implements an interface that defines a property of
> > > >>>>>my page. And i get an
> > > >>>>>AbstractMethodError when trying to call a method defined in this
> > > >>>>>interface (same thing
> > > >>>>>if the property is explicit in the page specificatrion or not). Do
> > > >>>>>you
> > > >>>>>think it's the attended behavior or should Tapestry dynamically
> > > >>>>>create
> > > >>>>>a property for it ?
> > > >>>>>
> > > >>>>>Jean-Yves
> > > >>>>>
> > > >>>>>---------------------------------------------------------------------
> > > >>>>>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
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>--
> > > >>>Jean-Yves Sironneau
> > > >>>jys@fr.st
> > > >>>06.16.18.71.63
> > > >>>
> > > >>>---------------------------------------------------------------------
> > > >>>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
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > > >Just a guess, but I'm thinking JDK 1.5 Generics arent supported.
> > > >
> > > >........................
> > > >Derick Fernando
> > > >Lead Architect
> > > >TheLab, LLC
> > > >http://www.thelabllc.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
> > >
> > >
> >
> > I guess tapestry only implements the interface methods if they are abstract.
> >
> > ........................
> > Derick Fernando
> > Lead Architect
> > TheLab, LLC
> > http://www.thelabllc.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
>
> Ignore my last message, thats incorrect.
>
> ........................
> Derick Fernando
> Lead Architect
> TheLab, LLC
> http://www.thelabllc.com
>
> ---------------------------------------------------------------------
> 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
Re: 3.1 and abstract properties
Posted by Derick Fernando <de...@thelabllc.com>.
Quoting Derick Fernando <de...@thelabllc.com>:
> Quoting jys <jy...@fr.st>:
>
> > Yes, but i think that as generics are "erased" at runtime Tapestry is
> > able to create properties using generics. And generics property worked
> > for 3.0.
> >
> >
> > Derick Fernando wrote:
> >
> > >Quoting Erik Hatcher <er...@ehatchersolutions.com>:
> > >
> > >
> > >
> > >>*shrugs*.... Howard?
> > >>
> > >> Erik
> > >>
> > >>On Mar 23, 2005, at 9:02 AM, jyjeanyves@free.fr wrote:
> > >>
> > >>
> > >>
> > >>>Hum, i think it worked with 3.0.
> > >>>
> > >>>Here is the example :
> > >>>
> > >>>public interface IDocumentProperty extends IPage {
> > >>>
> > >>> public Photo getDocument();
> > >>>
> > >>> public void setDocument(Photo doc);
> > >>>
> > >>> public void setDocumentsIds(List<String> docsIds);
> > >>>
> > >>> public List<String> getDocumentsIds();
> > >>>
> > >>>}
> > >>>
> > >>>public abstract class DocumentPage extends JPhotoWikiBasePage
> > >>>implements
> > >>> PageBeginRenderListener, IDocumentProperty {
> > >>>
> > >>>........
> > >>>}
> > >>>
> > >>>public abstract class ViewDocumentPage extends DocumentPage {
> > >>>
> > >>>......
> > >>>}
> > >>>
> > >>>ViewDocumentPage specification :
> > >>>
> > >>> <property name="documentsIds" persist="session"/>
> > >>>
> > >>>
> > >>>If i declare an abstract method in setDocumentsIds in ViewDocumentPage
> > >>>it works,
> > >>>but the goal was to make tapestry create things on the fly.
> > >>>
> > >>>Hope it's more understandable.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>Quoting Erik Hatcher <er...@ehatchersolutions.com>:
> > >>>
> > >>>
> > >>>
> > >>>>Did this work with 3.0?
> > >>>>
> > >>>>Please provide a concrete example.
> > >>>>
> > >>>> Erik
> > >>>>
> > >>>>On Mar 23, 2005, at 7:32 AM, Jean-Yves Sironneau wrote:
> > >>>>
> > >>>>
> > >>>>
> > >>>>>Hello,
> > >>>>>
> > >>>>>I don't know if i miss something or not but i'am testing 3.1 alpha1
> > >>>>>and i have a question about it.
> > >>>>>
> > >>>>>I have a page that implements an interface that defines a property of
> > >>>>>my page. And i get an
> > >>>>>AbstractMethodError when trying to call a method defined in this
> > >>>>>interface (same thing
> > >>>>>if the property is explicit in the page specificatrion or not). Do
> > >>>>>you
> > >>>>>think it's the attended behavior or should Tapestry dynamically
> > >>>>>create
> > >>>>>a property for it ?
> > >>>>>
> > >>>>>Jean-Yves
> > >>>>>
> > >>>>>---------------------------------------------------------------------
> > >>>>>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
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>--
> > >>>Jean-Yves Sironneau
> > >>>jys@fr.st
> > >>>06.16.18.71.63
> > >>>
> > >>>---------------------------------------------------------------------
> > >>>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
> > >>
> > >>
> > >>
> > >>
> > >
> > >Just a guess, but I'm thinking JDK 1.5 Generics arent supported.
> > >
> > >........................
> > >Derick Fernando
> > >Lead Architect
> > >TheLab, LLC
> > >http://www.thelabllc.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
> >
> >
>
> I guess tapestry only implements the interface methods if they are abstract.
>
> ........................
> Derick Fernando
> Lead Architect
> TheLab, LLC
> http://www.thelabllc.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
Ignore my last message, thats incorrect.
........................
Derick Fernando
Lead Architect
TheLab, LLC
http://www.thelabllc.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: 3.1 and abstract properties
Posted by Derick Fernando <de...@thelabllc.com>.
Quoting jys <jy...@fr.st>:
> Yes, but i think that as generics are "erased" at runtime Tapestry is
> able to create properties using generics. And generics property worked
> for 3.0.
>
>
> Derick Fernando wrote:
>
> >Quoting Erik Hatcher <er...@ehatchersolutions.com>:
> >
> >
> >
> >>*shrugs*.... Howard?
> >>
> >> Erik
> >>
> >>On Mar 23, 2005, at 9:02 AM, jyjeanyves@free.fr wrote:
> >>
> >>
> >>
> >>>Hum, i think it worked with 3.0.
> >>>
> >>>Here is the example :
> >>>
> >>>public interface IDocumentProperty extends IPage {
> >>>
> >>> public Photo getDocument();
> >>>
> >>> public void setDocument(Photo doc);
> >>>
> >>> public void setDocumentsIds(List<String> docsIds);
> >>>
> >>> public List<String> getDocumentsIds();
> >>>
> >>>}
> >>>
> >>>public abstract class DocumentPage extends JPhotoWikiBasePage
> >>>implements
> >>> PageBeginRenderListener, IDocumentProperty {
> >>>
> >>>........
> >>>}
> >>>
> >>>public abstract class ViewDocumentPage extends DocumentPage {
> >>>
> >>>......
> >>>}
> >>>
> >>>ViewDocumentPage specification :
> >>>
> >>> <property name="documentsIds" persist="session"/>
> >>>
> >>>
> >>>If i declare an abstract method in setDocumentsIds in ViewDocumentPage
> >>>it works,
> >>>but the goal was to make tapestry create things on the fly.
> >>>
> >>>Hope it's more understandable.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>Quoting Erik Hatcher <er...@ehatchersolutions.com>:
> >>>
> >>>
> >>>
> >>>>Did this work with 3.0?
> >>>>
> >>>>Please provide a concrete example.
> >>>>
> >>>> Erik
> >>>>
> >>>>On Mar 23, 2005, at 7:32 AM, Jean-Yves Sironneau wrote:
> >>>>
> >>>>
> >>>>
> >>>>>Hello,
> >>>>>
> >>>>>I don't know if i miss something or not but i'am testing 3.1 alpha1
> >>>>>and i have a question about it.
> >>>>>
> >>>>>I have a page that implements an interface that defines a property of
> >>>>>my page. And i get an
> >>>>>AbstractMethodError when trying to call a method defined in this
> >>>>>interface (same thing
> >>>>>if the property is explicit in the page specificatrion or not). Do
> >>>>>you
> >>>>>think it's the attended behavior or should Tapestry dynamically
> >>>>>create
> >>>>>a property for it ?
> >>>>>
> >>>>>Jean-Yves
> >>>>>
> >>>>>---------------------------------------------------------------------
> >>>>>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
> >>>>
> >>>>
> >>>>
> >>>>
> >>>--
> >>>Jean-Yves Sironneau
> >>>jys@fr.st
> >>>06.16.18.71.63
> >>>
> >>>---------------------------------------------------------------------
> >>>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
> >>
> >>
> >>
> >>
> >
> >Just a guess, but I'm thinking JDK 1.5 Generics arent supported.
> >
> >........................
> >Derick Fernando
> >Lead Architect
> >TheLab, LLC
> >http://www.thelabllc.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
>
>
I guess tapestry only implements the interface methods if they are abstract.
........................
Derick Fernando
Lead Architect
TheLab, LLC
http://www.thelabllc.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: 3.1 and abstract properties
Posted by jys <jy...@fr.st>.
Yes, but i think that as generics are "erased" at runtime Tapestry is
able to create properties using generics. And generics property worked
for 3.0.
Derick Fernando wrote:
>Quoting Erik Hatcher <er...@ehatchersolutions.com>:
>
>
>
>>*shrugs*.... Howard?
>>
>> Erik
>>
>>On Mar 23, 2005, at 9:02 AM, jyjeanyves@free.fr wrote:
>>
>>
>>
>>>Hum, i think it worked with 3.0.
>>>
>>>Here is the example :
>>>
>>>public interface IDocumentProperty extends IPage {
>>>
>>> public Photo getDocument();
>>>
>>> public void setDocument(Photo doc);
>>>
>>> public void setDocumentsIds(List<String> docsIds);
>>>
>>> public List<String> getDocumentsIds();
>>>
>>>}
>>>
>>>public abstract class DocumentPage extends JPhotoWikiBasePage
>>>implements
>>> PageBeginRenderListener, IDocumentProperty {
>>>
>>>........
>>>}
>>>
>>>public abstract class ViewDocumentPage extends DocumentPage {
>>>
>>>......
>>>}
>>>
>>>ViewDocumentPage specification :
>>>
>>> <property name="documentsIds" persist="session"/>
>>>
>>>
>>>If i declare an abstract method in setDocumentsIds in ViewDocumentPage
>>>it works,
>>>but the goal was to make tapestry create things on the fly.
>>>
>>>Hope it's more understandable.
>>>
>>>
>>>
>>>
>>>
>>>Quoting Erik Hatcher <er...@ehatchersolutions.com>:
>>>
>>>
>>>
>>>>Did this work with 3.0?
>>>>
>>>>Please provide a concrete example.
>>>>
>>>> Erik
>>>>
>>>>On Mar 23, 2005, at 7:32 AM, Jean-Yves Sironneau wrote:
>>>>
>>>>
>>>>
>>>>>Hello,
>>>>>
>>>>>I don't know if i miss something or not but i'am testing 3.1 alpha1
>>>>>and i have a question about it.
>>>>>
>>>>>I have a page that implements an interface that defines a property of
>>>>>my page. And i get an
>>>>>AbstractMethodError when trying to call a method defined in this
>>>>>interface (same thing
>>>>>if the property is explicit in the page specificatrion or not). Do
>>>>>you
>>>>>think it's the attended behavior or should Tapestry dynamically
>>>>>create
>>>>>a property for it ?
>>>>>
>>>>>Jean-Yves
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>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
>>>>
>>>>
>>>>
>>>>
>>>--
>>>Jean-Yves Sironneau
>>>jys@fr.st
>>>06.16.18.71.63
>>>
>>>---------------------------------------------------------------------
>>>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
>>
>>
>>
>>
>
>Just a guess, but I'm thinking JDK 1.5 Generics arent supported.
>
>........................
>Derick Fernando
>Lead Architect
>TheLab, LLC
>http://www.thelabllc.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: 3.1 and abstract properties
Posted by Derick Fernando <de...@thelabllc.com>.
Quoting Erik Hatcher <er...@ehatchersolutions.com>:
> *shrugs*.... Howard?
>
> Erik
>
> On Mar 23, 2005, at 9:02 AM, jyjeanyves@free.fr wrote:
>
> > Hum, i think it worked with 3.0.
> >
> > Here is the example :
> >
> > public interface IDocumentProperty extends IPage {
> >
> > public Photo getDocument();
> >
> > public void setDocument(Photo doc);
> >
> > public void setDocumentsIds(List<String> docsIds);
> >
> > public List<String> getDocumentsIds();
> >
> > }
> >
> > public abstract class DocumentPage extends JPhotoWikiBasePage
> > implements
> > PageBeginRenderListener, IDocumentProperty {
> >
> > ........
> > }
> >
> > public abstract class ViewDocumentPage extends DocumentPage {
> >
> > ......
> > }
> >
> > ViewDocumentPage specification :
> >
> > <property name="documentsIds" persist="session"/>
> >
> >
> > If i declare an abstract method in setDocumentsIds in ViewDocumentPage
> > it works,
> > but the goal was to make tapestry create things on the fly.
> >
> > Hope it's more understandable.
> >
> >
> >
> >
> >
> > Quoting Erik Hatcher <er...@ehatchersolutions.com>:
> >
> >> Did this work with 3.0?
> >>
> >> Please provide a concrete example.
> >>
> >> Erik
> >>
> >> On Mar 23, 2005, at 7:32 AM, Jean-Yves Sironneau wrote:
> >>
> >>> Hello,
> >>>
> >>> I don't know if i miss something or not but i'am testing 3.1 alpha1
> >>> and i have a question about it.
> >>>
> >>> I have a page that implements an interface that defines a property of
> >>> my page. And i get an
> >>> AbstractMethodError when trying to call a method defined in this
> >>> interface (same thing
> >>> if the property is explicit in the page specificatrion or not). Do
> >>> you
> >>> think it's the attended behavior or should Tapestry dynamically
> >>> create
> >>> a property for it ?
> >>>
> >>> Jean-Yves
> >>>
> >>> ---------------------------------------------------------------------
> >>> 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
> >>
> >>
> >
> >
> > --
> > Jean-Yves Sironneau
> > jys@fr.st
> > 06.16.18.71.63
> >
> > ---------------------------------------------------------------------
> > 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
>
>
Just a guess, but I'm thinking JDK 1.5 Generics arent supported.
........................
Derick Fernando
Lead Architect
TheLab, LLC
http://www.thelabllc.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: 3.1 and abstract properties
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
*shrugs*.... Howard?
Erik
On Mar 23, 2005, at 9:02 AM, jyjeanyves@free.fr wrote:
> Hum, i think it worked with 3.0.
>
> Here is the example :
>
> public interface IDocumentProperty extends IPage {
>
> public Photo getDocument();
>
> public void setDocument(Photo doc);
>
> public void setDocumentsIds(List<String> docsIds);
>
> public List<String> getDocumentsIds();
>
> }
>
> public abstract class DocumentPage extends JPhotoWikiBasePage
> implements
> PageBeginRenderListener, IDocumentProperty {
>
> ........
> }
>
> public abstract class ViewDocumentPage extends DocumentPage {
>
> ......
> }
>
> ViewDocumentPage specification :
>
> <property name="documentsIds" persist="session"/>
>
>
> If i declare an abstract method in setDocumentsIds in ViewDocumentPage
> it works,
> but the goal was to make tapestry create things on the fly.
>
> Hope it's more understandable.
>
>
>
>
>
> Quoting Erik Hatcher <er...@ehatchersolutions.com>:
>
>> Did this work with 3.0?
>>
>> Please provide a concrete example.
>>
>> Erik
>>
>> On Mar 23, 2005, at 7:32 AM, Jean-Yves Sironneau wrote:
>>
>>> Hello,
>>>
>>> I don't know if i miss something or not but i'am testing 3.1 alpha1
>>> and i have a question about it.
>>>
>>> I have a page that implements an interface that defines a property of
>>> my page. And i get an
>>> AbstractMethodError when trying to call a method defined in this
>>> interface (same thing
>>> if the property is explicit in the page specificatrion or not). Do
>>> you
>>> think it's the attended behavior or should Tapestry dynamically
>>> create
>>> a property for it ?
>>>
>>> Jean-Yves
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>>
>
>
> --
> Jean-Yves Sironneau
> jys@fr.st
> 06.16.18.71.63
>
> ---------------------------------------------------------------------
> 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: 3.1 and abstract properties
Posted by jy...@free.fr.
Hum, i think it worked with 3.0.
Here is the example :
public interface IDocumentProperty extends IPage {
public Photo getDocument();
public void setDocument(Photo doc);
public void setDocumentsIds(List<String> docsIds);
public List<String> getDocumentsIds();
}
public abstract class DocumentPage extends JPhotoWikiBasePage implements
PageBeginRenderListener, IDocumentProperty {
........
}
public abstract class ViewDocumentPage extends DocumentPage {
......
}
ViewDocumentPage specification :
<property name="documentsIds" persist="session"/>
If i declare an abstract method in setDocumentsIds in ViewDocumentPage it works,
but the goal was to make tapestry create things on the fly.
Hope it's more understandable.
Quoting Erik Hatcher <er...@ehatchersolutions.com>:
> Did this work with 3.0?
>
> Please provide a concrete example.
>
> Erik
>
> On Mar 23, 2005, at 7:32 AM, Jean-Yves Sironneau wrote:
>
> > Hello,
> >
> > I don't know if i miss something or not but i'am testing 3.1 alpha1
> > and i have a question about it.
> >
> > I have a page that implements an interface that defines a property of
> > my page. And i get an
> > AbstractMethodError when trying to call a method defined in this
> > interface (same thing
> > if the property is explicit in the page specificatrion or not). Do you
> > think it's the attended behavior or should Tapestry dynamically create
> > a property for it ?
> >
> > Jean-Yves
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
Jean-Yves Sironneau
jys@fr.st
06.16.18.71.63
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: 3.1 and abstract properties
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
Did this work with 3.0?
Please provide a concrete example.
Erik
On Mar 23, 2005, at 7:32 AM, Jean-Yves Sironneau wrote:
> Hello,
>
> I don't know if i miss something or not but i'am testing 3.1 alpha1
> and i have a question about it.
>
> I have a page that implements an interface that defines a property of
> my page. And i get an
> AbstractMethodError when trying to call a method defined in this
> interface (same thing
> if the property is explicit in the page specificatrion or not). Do you
> think it's the attended behavior or should Tapestry dynamically create
> a property for it ?
>
> Jean-Yves
>
> ---------------------------------------------------------------------
> 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