You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Scott F. Walter" <sc...@vivare.com> on 2005/07/01 14:59:52 UTC
Tapestry 4 Impressions
Before migrating my apps to Tapestry 4, I thought I would create a
little sandbox app just to test everything out (kind of like a mini
workbench).
Here are the good points for beta 1:
* New Listener format--Much improved, works flawlessly
* Application State Objects
* Subdirectories--Works great! I was able to create pages in seperate
directories
* Validation--I like the new validation, seems simplier
* Annotations-Very powerful!
Here are some of the issues/bugs I have encountered withe beta 1:
* Can't seem to have 2 Application State Objects
* Can't create a component without a specification file (.jwc)
* Can't access messages from a Page Message Calo unless there's a page
specification file present
* If I try to access an asset I setup using @Asset annotation, I get an
null pointer exception
* I setup friendely urls and can access a page with the friendly url,
however none of the codebehind the page is executed (I may have a setup
issue though)
I am very impressed and will continue testing Tapestry 4 to help get it
to a soldi 4.0 producion release.
--
Scott F. Walter Scott F. Walter
Principal Consultant
Vivare, Inc.
E: scott.walter@vivare.com
E: scott@scottwalter.com
Visit scottwalter.com <http://scottwalter.com> --Point. Click. Explore!
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Tapestry 4 Impressions
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On Jul 1, 2005, at 2:52 PM, Howard Lewis Ship wrote:
>> * Application State Objects
>> * Subdirectories--Works great! I was able to create pages in
>> seperate
>> directories
>>
>
> Erik was going to fix the parser to allow folder names in component
> types as well, but I don't remember seeing those changes
I was?! At this point in time I can't get to this - I'm not actively
building a Tapestry application so it wouldn't be wise of me to go
mucking around underneath without a real application to try it on.
Sorry.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Tapestry 4 Impressions
Posted by Jer Kah <je...@gmail.com>.
...And that's great service. :)
On 7/1/05, Howard Lewis Ship <hl...@gmail.com> wrote:
> On 7/1/05, Scott F. Walter <sc...@vivare.com> wrote:
> > Before migrating my apps to Tapestry 4, I thought I would create a
> > little sandbox app just to test everything out (kind of like a mini
> > workbench).
>
> A good plan at this point.
>
> > Here are the good points for beta 1:
> > * New Listener format--Much improved, works flawlessly
>
> I'm really happy with this as well; what I really like is getting to
> the point of writing listeners without even seein the IRequestCycle.
>
> > * Application State Objects
> > * Subdirectories--Works great! I was able to create pages in seperate
> > directories
>
> Erik was going to fix the parser to allow folder names in component
> types as well, but I don't remember seeing those changes
>
> > * Validation--I like the new validation, seems simplier
>
> Paul did a stand up job here; over dinner last night we hashed out a
> few minor tweaks for it.
>
> > * Annotations-Very powerful!
>
> My original plan was to host annotations on a java.net project, but
> I'm now very happy I invested the time to have these as part of the
> framework proper.
>
> >
> > Here are some of the issues/bugs I have encountered withe beta 1:
> >
> > * Can't seem to have 2 Application State Objects
>
> I've updated the bug you added with something to try. I think method
> overloading in JDK 1.5 is the culprit here.
>
> > * Can't create a component without a specification file (.jwc)
>
> A bug (I found it first!)
>
> > * Can't access messages from a Page Message Calo unless there's a page
> > specification file present
>
> I've updated the bug.
>
> > * If I try to access an asset I setup using @Asset annotation, I get an
> > null pointer exception
>
> Now fixed.
>
> > * I setup friendely urls and can access a page with the friendly url,
> > however none of the codebehind the page is executed (I may have a setup
> > issue though)
>
> Please check the bug; looked like you didn't map *.html to ApplicationServlet.
> >
> > I am very impressed and will continue testing Tapestry 4 to help get it
> > to a soldi 4.0 producion release.
>
> Thanks for the feedback!
>
> >
> >
> >
> > --
> >
> > Scott F. Walter Scott F. Walter
> > Principal Consultant
> > Vivare, Inc.
> >
> > E: scott.walter@vivare.com
> > E: scott@scottwalter.com
> > Visit scottwalter.com <http://scottwalter.com> --Point. Click. Explore!
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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: Tapestry 4 Impressions
Posted by Howard Lewis Ship <hl...@gmail.com>.
On 7/1/05, Scott F. Walter <sc...@vivare.com> wrote:
> Before migrating my apps to Tapestry 4, I thought I would create a
> little sandbox app just to test everything out (kind of like a mini
> workbench).
A good plan at this point.
> Here are the good points for beta 1:
> * New Listener format--Much improved, works flawlessly
I'm really happy with this as well; what I really like is getting to
the point of writing listeners without even seein the IRequestCycle.
> * Application State Objects
> * Subdirectories--Works great! I was able to create pages in seperate
> directories
Erik was going to fix the parser to allow folder names in component
types as well, but I don't remember seeing those changes
> * Validation--I like the new validation, seems simplier
Paul did a stand up job here; over dinner last night we hashed out a
few minor tweaks for it.
> * Annotations-Very powerful!
My original plan was to host annotations on a java.net project, but
I'm now very happy I invested the time to have these as part of the
framework proper.
>
> Here are some of the issues/bugs I have encountered withe beta 1:
>
> * Can't seem to have 2 Application State Objects
I've updated the bug you added with something to try. I think method
overloading in JDK 1.5 is the culprit here.
> * Can't create a component without a specification file (.jwc)
A bug (I found it first!)
> * Can't access messages from a Page Message Calo unless there's a page
> specification file present
I've updated the bug.
> * If I try to access an asset I setup using @Asset annotation, I get an
> null pointer exception
Now fixed.
> * I setup friendely urls and can access a page with the friendly url,
> however none of the codebehind the page is executed (I may have a setup
> issue though)
Please check the bug; looked like you didn't map *.html to ApplicationServlet.
>
> I am very impressed and will continue testing Tapestry 4 to help get it
> to a soldi 4.0 producion release.
Thanks for the feedback!
>
>
>
> --
>
> Scott F. Walter Scott F. Walter
> Principal Consultant
> Vivare, Inc.
>
> E: scott.walter@vivare.com
> E: scott@scottwalter.com
> Visit scottwalter.com <http://scottwalter.com> --Point. Click. Explore!
>
>
>
>
> ---------------------------------------------------------------------
> 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: Tapestry 4 Impressions
Posted by Ron Piterman <mp...@vollbio.de>.
Thats a great feedback...
ציטוט Scott F. Walter:
> Before migrating my apps to Tapestry 4, I thought I would create a
> little sandbox app just to test everything out (kind of like a mini
> workbench). Here are the good points for beta 1:
> * New Listener format--Much improved, works flawlessly
> * Application State Objects
> * Subdirectories--Works great! I was able to create pages in seperate
> directories
> * Validation--I like the new validation, seems simplier
> * Annotations-Very powerful!
>
> Here are some of the issues/bugs I have encountered withe beta 1:
>
> * Can't seem to have 2 Application State Objects
> * Can't create a component without a specification file (.jwc)
> * Can't access messages from a Page Message Calo unless there's a page
> specification file present
> * If I try to access an asset I setup using @Asset annotation, I get an
> null pointer exception
> * I setup friendely urls and can access a page with the friendly url,
> however none of the codebehind the page is executed (I may have a setup
> issue though)
>
> I am very impressed and will continue testing Tapestry 4 to help get it
> to a soldi 4.0 producion release.
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org