You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Michael Rimov <ri...@centercomp.com> on 2005/11/11 17:53:15 UTC
Checking for JSP page modification
Hi All,
I wanted to drop this idea here to see what people thought of feasibility:
The situation: (Especially true with last release of MyFaces)
Nearly every time I make a modification to a JSF page, it seems that I need
to close and reopen my browser to flush the session because it won't render
the new page (for minor layout changes), or throw an exception about
duplicate ids (for major changes).
It seems to me that if a JSF page checked (optionally, of course, this would
be like 'reloadable' for a webapp) its modification date and found changes,
that it would flush its own saved state and start afresh. (Logging what it
did of course to help people figure out what might have happened).
For me this would dramatically increase development speed, which is starting
to get bogged down with all the session restarts required.
Is this idea doable? Does it open up too many cans of worms?
If its doable, I'll file a Jira ticket, but I wanted to check here first.
Thanks!
-Mike
Re: Checking for JSP page modification
Posted by Mike Kienenberger <mk...@gmail.com>.
Facelets does this already. Perhaps there's some ideas or code that
could be borrowed from that project.
On 11/11/05, Travis Reeder <tr...@gmail.com> wrote:
> I would also love to see this, i know the pain. Another thing it could do
> is try to recreate the tree a single time if a duplicate id is found. Not
> sure how if that could handle the minor changes though.
>
> Travis
>
>
> On 11/11/05, Martin Marinschek <ma...@gmail.com> wrote:
> > I would love to have a thing like that. Plus a possibility to reload
> > the configuration files during development.
> >
> > So add this to your jira-request - even better would be if you would
> > implement it ;)
> >
> > regards,
> >
> > Martin
> >
> > On 11/11/05, Michael Rimov <ri...@centercomp.com> wrote:
> > >
> > >
> > >
> > > Hi All,
> > >
> > >
> > >
> > > I wanted to drop this idea here to see what people thought of
> feasibility:
> > >
> > >
> > >
> > > The situation: (Especially true with last release of MyFaces)
> > >
> > >
> > >
> > > Nearly every time I make a modification to a JSF page, it seems that I
> need
> > > to close and reopen my browser to flush the session because it won't
> render
> > > the new page (for minor layout changes), or throw an exception about
> > > duplicate ids (for major changes).
> > >
> > >
> > >
> > > It seems to me that if a JSF page checked (optionally, of course, this
> would
> > > be like 'reloadable' for a webapp) its modification date and found
> changes,
> > > that it would flush its own saved state and start afresh. (Logging what
> it
> > > did of course to help people figure out what might have happened).
> > >
> > >
> > >
> > > For me this would dramatically increase development speed, which is
> starting
> > > to get bogged down with all the session restarts required.
> > >
> > >
> > >
> > > Is this idea doable? Does it open up too many cans of worms?
> > >
> > >
> > >
> > > If its doable, I'll file a Jira ticket, but I wanted to check here
> first.
> > >
> > >
> > >
> > > Thanks!
> > >
> > >
> > > -Mike
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> >
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and
> > Courses in English and German
> >
> > Professional Support for Apache MyFaces
> >
>
>
Re: Checking for JSP page modification
Posted by Travis Reeder <tr...@gmail.com>.
I would also love to see this, i know the pain. Another thing it could do is
try to recreate the tree a single time if a duplicate id is found. Not sure
how if that could handle the minor changes though.
Travis
On 11/11/05, Martin Marinschek <ma...@gmail.com> wrote:
>
> I would love to have a thing like that. Plus a possibility to reload
> the configuration files during development.
>
> So add this to your jira-request - even better would be if you would
> implement it ;)
>
> regards,
>
> Martin
>
> On 11/11/05, Michael Rimov <ri...@centercomp.com> wrote:
> >
> >
> >
> > Hi All,
> >
> >
> >
> > I wanted to drop this idea here to see what people thought of
> feasibility:
> >
> >
> >
> > The situation: (Especially true with last release of MyFaces)
> >
> >
> >
> > Nearly every time I make a modification to a JSF page, it seems that I
> need
> > to close and reopen my browser to flush the session because it won't
> render
> > the new page (for minor layout changes), or throw an exception about
> > duplicate ids (for major changes).
> >
> >
> >
> > It seems to me that if a JSF page checked (optionally, of course, this
> would
> > be like 'reloadable' for a webapp) its modification date and found
> changes,
> > that it would flush its own saved state and start afresh. (Logging what
> it
> > did of course to help people figure out what might have happened).
> >
> >
> >
> > For me this would dramatically increase development speed, which is
> starting
> > to get bogged down with all the session restarts required.
> >
> >
> >
> > Is this idea doable? Does it open up too many cans of worms?
> >
> >
> >
> > If its doable, I'll file a Jira ticket, but I wanted to check here
> first.
> >
> >
> >
> > Thanks!
> >
> >
> > -Mike
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
Re: Checking for JSP page modification
Posted by Martin Marinschek <ma...@gmail.com>.
I would love to have a thing like that. Plus a possibility to reload
the configuration files during development.
So add this to your jira-request - even better would be if you would
implement it ;)
regards,
Martin
On 11/11/05, Michael Rimov <ri...@centercomp.com> wrote:
>
>
>
> Hi All,
>
>
>
> I wanted to drop this idea here to see what people thought of feasibility:
>
>
>
> The situation: (Especially true with last release of MyFaces)
>
>
>
> Nearly every time I make a modification to a JSF page, it seems that I need
> to close and reopen my browser to flush the session because it won't render
> the new page (for minor layout changes), or throw an exception about
> duplicate ids (for major changes).
>
>
>
> It seems to me that if a JSF page checked (optionally, of course, this would
> be like 'reloadable' for a webapp) its modification date and found changes,
> that it would flush its own saved state and start afresh. (Logging what it
> did of course to help people figure out what might have happened).
>
>
>
> For me this would dramatically increase development speed, which is starting
> to get bogged down with all the session restarts required.
>
>
>
> Is this idea doable? Does it open up too many cans of worms?
>
>
>
> If its doable, I'll file a Jira ticket, but I wanted to check here first.
>
>
>
> Thanks!
>
>
> -Mike
>
>
>
>
>
>
>
>
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces