You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Leon <lm...@netzero.net> on 2006/09/12 02:57:24 UTC
Sun's Progress Bar with JSF and AJAX Sample
Hello everybody,
I am trying to make Sun's Progress Bar with JSF and AJAX Sample
(https://bpcatalog.dev.java.net/nonav/ajax/progress-bar-jsf/frames.html) run
on Tomcat with Myfaces libraries (instead of JSF-RI) but it fails to draw
the progress bar and skips to the last page without reporting any errors.
It appears that Myfaces library does not behave correctly when used with
AJAX. I am just wondering if somebody observed such problems already.
Thanks for the help.
Leon
--
View this message in context: http://www.nabble.com/Sun%27s-Progress-Bar-with-JSF-and-AJAX-Sample-tf2256196.html#a6257997
Sent from the MyFaces - Users forum at Nabble.com.
Re: incorrect behavior after responseComplete?
Posted by Leon <lm...@netzero.net>.
Mike,
I have submitted a JIRA issue:
http://issues.apache.org/jira/browse/MYFACES-1409
I hope I have done everything correctly.
Thanks,
Leon
>Leon,
>
>Can you open a JIRA issue on this against MyFaces core?
>
>Thanks.
--
View this message in context: http://www.nabble.com/Sun%27s-Progress-Bar-with-JSF-and-AJAX-Sample-tf2256196.html#a6394186
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: incorrect behavior after responseComplete?
Posted by Mike Kienenberger <mk...@gmail.com>.
Leon,
Can you open a JIRA issue on this against MyFaces core?
Thanks.
On 9/18/06, Leon <lm...@netzero.net> wrote:
>
> Martin,
>
> The following behavior appears to be incorrect in myfaces implementation of
> JSF.
>
> After FacesContext.responseComplete is issued in the afterPhase method of
> the PhaseListener at the RESTORE_VIEW phase, myfaces implementation skips to
> RENDER_RESPONSE phase. This appears to be incorrect, as following a call to
> FacesContext.responseComplete JSF implementation should exit JSF lifecycle
> completely, i.e. the next phase of the lifecycle should be again
> RESTORE_VIEW.
>
> This problem can be observed when running Sun's Progress Bar with JSF and
> AJAX Sample with myfaces libraries on Tomcat.
>
> Thanks for the help,
>
> Leon
>
>
>
>
> We are currently working hard on fixing whatever compatibility
> problems are remaining between Trinidad, MyFaces and the RI.
>
> I hope we'll have that sorted out with the next release of core (so 1.1.5)
>
> regards,
>
> Martin
>
>
> --
> View this message in context: http://www.nabble.com/Sun%27s-Progress-Bar-with-JSF-and-AJAX-Sample-tf2256196.html#a6370743
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
incorrect behavior after responseComplete?
Posted by Leon <lm...@netzero.net>.
Martin,
The following behavior appears to be incorrect in myfaces implementation of
JSF.
After FacesContext.responseComplete is issued in the afterPhase method of
the PhaseListener at the RESTORE_VIEW phase, myfaces implementation skips to
RENDER_RESPONSE phase. This appears to be incorrect, as following a call to
FacesContext.responseComplete JSF implementation should exit JSF lifecycle
completely, i.e. the next phase of the lifecycle should be again
RESTORE_VIEW.
This problem can be observed when running Sun's Progress Bar with JSF and
AJAX Sample with myfaces libraries on Tomcat.
Thanks for the help,
Leon
We are currently working hard on fixing whatever compatibility
problems are remaining between Trinidad, MyFaces and the RI.
I hope we'll have that sorted out with the next release of core (so 1.1.5)
regards,
Martin
--
View this message in context: http://www.nabble.com/Sun%27s-Progress-Bar-with-JSF-and-AJAX-Sample-tf2256196.html#a6370743
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Sun's Progress Bar with JSF and AJAX Sample
Posted by Martin Marinschek <ma...@gmail.com>.
We are currently working hard on fixing whatever compatibility
problems are remaining between Trinidad, MyFaces and the RI.
I hope we'll have that sorted out with the next release of core (so 1.1.5)
regards,
Martin
On 9/15/06, Leon <lm...@netzero.net> wrote:
>
> Martin,
>
> Thanks for trying to help. Basically this sample runs just fine on Tomcat
> with JSF-RI libraries, but when I substitute them with Myfaces it fails. Do
> I need to do some extra configuration when I am using Myfaces libraries?
>
> So far it appears to be some kind of incompatibility of MyFaces and JSF-RI.
> Our ADF which relies on JSF and AJAX similarly misbehaves when used with
> Myfaces.
> If so it is a problem for us as the ADF we are developing is not going to
> work on any of the servers which decide to preinstall Myfaces (like JBoss.)
>
> Leon
>
>
>
> Werner Punz wrote:
> >
> > Martin Marinschek schrieb:
> >> There are several AJAX-components in the MyFaces tomahawk library
> >> included, so this can't be a general problem. I rather suspect you've
> >> found some incompatibily between what the Sun components do and
> >> MyFaces, or there's something wrong in your setup.
> >>
> > I had a quick look at the progress bar javascripts again, since I
> > already once had it in my hands for a personal project.
> > This might be a configuration problem, the progress bar relies on a
> > servlet in the backend which handles the ajax communication on the
> > server side and handles the task handling for the registered tasks.
> >
> > This servlet has to be added to your configuration, if I recall it
> > correctly.
> >
> > Please check if the configuration is right.
> > There is not too much in the progress bar, which can interfere
> > with myfaces unless they have moved to jsf 1.2 already,
> > that would be an entirely different issue.
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Sun%27s-Progress-Bar-with-JSF-and-AJAX-Sample-tf2256196.html#a6317761
> Sent from the MyFaces - Users forum at Nabble.com.
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: Sun's Progress Bar with JSF and AJAX Sample
Posted by Leon <lm...@netzero.net>.
Martin,
Thanks for trying to help. Basically this sample runs just fine on Tomcat
with JSF-RI libraries, but when I substitute them with Myfaces it fails. Do
I need to do some extra configuration when I am using Myfaces libraries?
So far it appears to be some kind of incompatibility of MyFaces and JSF-RI.
Our ADF which relies on JSF and AJAX similarly misbehaves when used with
Myfaces.
If so it is a problem for us as the ADF we are developing is not going to
work on any of the servers which decide to preinstall Myfaces (like JBoss.)
Leon
Werner Punz wrote:
>
> Martin Marinschek schrieb:
>> There are several AJAX-components in the MyFaces tomahawk library
>> included, so this can't be a general problem. I rather suspect you've
>> found some incompatibily between what the Sun components do and
>> MyFaces, or there's something wrong in your setup.
>>
> I had a quick look at the progress bar javascripts again, since I
> already once had it in my hands for a personal project.
> This might be a configuration problem, the progress bar relies on a
> servlet in the backend which handles the ajax communication on the
> server side and handles the task handling for the registered tasks.
>
> This servlet has to be added to your configuration, if I recall it
> correctly.
>
> Please check if the configuration is right.
> There is not too much in the progress bar, which can interfere
> with myfaces unless they have moved to jsf 1.2 already,
> that would be an entirely different issue.
>
>
>
--
View this message in context: http://www.nabble.com/Sun%27s-Progress-Bar-with-JSF-and-AJAX-Sample-tf2256196.html#a6317761
Sent from the MyFaces - Users forum at Nabble.com.
Re: Sun's Progress Bar with JSF and AJAX Sample
Posted by Werner Punz <we...@gmx.at>.
Martin Marinschek schrieb:
> There are several AJAX-components in the MyFaces tomahawk library
> included, so this can't be a general problem. I rather suspect you've
> found some incompatibily between what the Sun components do and
> MyFaces, or there's something wrong in your setup.
>
I had a quick look at the progress bar javascripts again, since I
already once had it in my hands for a personal project.
This might be a configuration problem, the progress bar relies on a
servlet in the backend which handles the ajax communication on the
server side and handles the task handling for the registered tasks.
This servlet has to be added to your configuration, if I recall it
correctly.
Please check if the configuration is right.
There is not too much in the progress bar, which can interfere
with myfaces unless they have moved to jsf 1.2 already,
that would be an entirely different issue.
Re: Sun's Progress Bar with JSF and AJAX Sample
Posted by Martin Marinschek <ma...@gmail.com>.
There are several AJAX-components in the MyFaces tomahawk library
included, so this can't be a general problem. I rather suspect you've
found some incompatibily between what the Sun components do and
MyFaces, or there's something wrong in your setup.
regards,
Martin
On 9/12/06, Leon <lm...@netzero.net> wrote:
>
> Hello everybody,
>
> I am trying to make Sun's Progress Bar with JSF and AJAX Sample
> (https://bpcatalog.dev.java.net/nonav/ajax/progress-bar-jsf/frames.html) run
> on Tomcat with Myfaces libraries (instead of JSF-RI) but it fails to draw
> the progress bar and skips to the last page without reporting any errors.
>
> It appears that Myfaces library does not behave correctly when used with
> AJAX. I am just wondering if somebody observed such problems already.
>
> Thanks for the help.
>
> Leon
>
> --
> View this message in context: http://www.nabble.com/Sun%27s-Progress-Bar-with-JSF-and-AJAX-Sample-tf2256196.html#a6257997
> Sent from the MyFaces - Users forum at Nabble.com.
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Help!! actionListener not being called with a4j:commandLink and a4j:support
Posted by Stephen Osella <so...@austin.rr.com>.
Has anybody ever seen the behavior where the actionListener (or action for
that matter) are not being called for a4j:commandLink or a4j:support?
What is the magic???
The code snippets are the following as examples:
<a4j:commandLink id="serviceAddButton" ajaxSingle="true"
actionListener="#{SessionBean.serviceAddActionListener}"
reRender="ordersPG,commandButtons">
<h:graphicImage id="addServiceButton" value="images/other/add-16x16.gif"
style="border-style:none;" width="16" height="16"
alt="#{a4j_bundle.add_service}" />
<f:param id="serviceAddIdx" name="serviceIdx"
value="#{SessionBean.servicesTable.rowIndex}"/>
</a4j:commandLink>
and
<h:selectOneMenu id="endDayMenu" value="#{SessionBean.endDate.day}">
<f:selectItems value="#{SessionBean.endDate.dayItems}" />
<a4j:support event="onchange" ajaxSingle="true"
actionListener="#{SessionBean.changeDateActionListener}"
reRender="dateTimesDT,commandButtons" />
</h:selectOneMenu>
I am re-rendering lots of things: panelGroups, dataTables, outputTexts, etc.
There has to be something fundamental that I am not doing. What could it
be? *Any* ideas?
Thanks for your help!
RE: actionListener not being called with a4j:commandLink
Posted by Michael Heinen <mh...@recommind.com>.
I need more code snippets for support.
What are you rerendering? An a4j:outputPanel?
I would not use immediate=true.
It causes trouble most of the times.
What about ajaxSingle=true for your link?
If you want to process more fields on the server, user an a4j:region
around your link.
MH
-----Original Message-----
From: Stephen Osella [mailto:sosella@austin.rr.com]
Sent: Samstag, 4. November 2006 17:13
To: MyFaces Discussion
Subject: Re: actionListener not being called with a4j:commandLink
I got it to work when I specified immediate="true" on the
a4j:commandLink.
Now other wierd things are happening. The header does not appear on the
re-rendered "h:dataTable" component. Also, some the footers dont appear
if
they contain bundle references. I am going to try a4j:loadBundle. Any
suggestions there? I figure I dont have to load the entire bundle.
Maybe
have a small one just for re-rendering?
Re: actionListener not being called with a4j:commandLink
Posted by Stephen Osella <so...@austin.rr.com>.
I got it to work when I specified immediate="true" on the a4j:commandLink.
Now other wierd things are happening. The header does not appear on the
re-rendered "h:dataTable" component. Also, some the footers dont appear if
they contain bundle references. I am going to try a4j:loadBundle. Any
suggestions there? I figure I dont have to load the entire bundle. Maybe
have a small one just for re-rendering?
RE: actionListener not being called with a4j:commandLink
Posted by Michael Heinen <mh...@recommind.com>.
Did you try to use an af4j:actionparam or a t:actionListener instead of the f:param ?
Are you sure that the listener is not called or is only the rerendering not executed as expected?
Michael
-----Original Message-----
From: Stephen Osella [mailto:sosella@austin.rr.com]
Sent: Samstag, 4. November 2006 15:40
To: MyFaces Discussion
Cc: Gerald Müllan
Subject: actionListener not being called with a4j:commandLink
In my ongoing attempt to use ajax4jsf....
I have an "a4jcommandLink" within an "h:dataTable":
<h:dataTable
id="services"
styleClass="services"
value="#{SessionBean.services}"
var="service"
binding="#{SessionBean.servicesTable}"
cellspacing="0">
<h:column>
<f:facet name="header">
<h:outputText value="#{bundle.select_service}"/>
</f:facet>
<a4j:commandLink id="serviceAddButton"
actionListener="#{SessionBean.serviceAddButtonActionListener}"
reRender="ordersPG">
<f:param id="serviceAddButtonIdx" name="serviceIdx"
value="#{SessionBean.servicesTable.rowIndex}"/>
<h:graphicImage id="addServiceButton"
value="images/other/add-16x16.gif" width="16" height="16"
alt="#{bundle.add_service}" />
</a4j:commandLink>
</h:column>
</h:dataTable>
The actionListener "SessionBean.serviceAddButtonActionListener" is not being
called! The ordersPG is an "h:panelGroup" in the form.
I put an "a4jstatus" in the form and that does work...goes from "ready" to
"request under process" and back. Yet nothing happens. I even put an
"ajaxListener" in the "a4jregion" (that contains the entire form), and a log
message in there is getting logged. So it seems that ajax4jsf *is* being
invoked, yet the actionListener is not being called. The backing bean is
session scoped.
Any ideas or tips?
actionListener not being called with a4j:commandLink
Posted by Stephen Osella <so...@austin.rr.com>.
In my ongoing attempt to use ajax4jsf....
I have an "a4jcommandLink" within an "h:dataTable":
<h:dataTable
id="services"
styleClass="services"
value="#{SessionBean.services}"
var="service"
binding="#{SessionBean.servicesTable}"
cellspacing="0">
<h:column>
<f:facet name="header">
<h:outputText value="#{bundle.select_service}"/>
</f:facet>
<a4j:commandLink id="serviceAddButton"
actionListener="#{SessionBean.serviceAddButtonActionListener}"
reRender="ordersPG">
<f:param id="serviceAddButtonIdx" name="serviceIdx"
value="#{SessionBean.servicesTable.rowIndex}"/>
<h:graphicImage id="addServiceButton"
value="images/other/add-16x16.gif" width="16" height="16"
alt="#{bundle.add_service}" />
</a4j:commandLink>
</h:column>
</h:dataTable>
The actionListener "SessionBean.serviceAddButtonActionListener" is not being
called! The ordersPG is an "h:panelGroup" in the form.
I put an "a4jstatus" in the form and that does work...goes from "ready" to
"request under process" and back. Yet nothing happens. I even put an
"ajaxListener" in the "a4jregion" (that contains the entire form), and a log
message in there is getting logged. So it seems that ajax4jsf *is* being
invoked, yet the actionListener is not being called. The backing bean is
session scoped.
Any ideas or tips?
Re: AJAX for JSF
Posted by Gerald Müllan <bi...@gmail.com>.
Hi,
I would also suggest Ajax4Jsf!
Especially for beginners who are playing around with AJAX and JSF this
is the one framework which is most easy to understand. Also to get
AJAX into existing JSF web apps.
Furthermore AjaxAnywhere will be of value to have a look on.
cheers,
Gerald
On 9/12/06, Stephen Osella <so...@austin.rr.com> wrote:
> Is there a good (i.e., working!) AJAX for JSF framework? I have tried
> AjaxAnywhere and Ajax4jsf with varying degree (but not complete) success.
> Your opinion and recommendations would be greatly appreciated.
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: AJAX for JSF
Posted by Adam Brod <AB...@intralinks.com>.
Ajax4Jsf is really good. The DynamicFaces project in jsf-extensions is
very promising, but it isn't ready to be used in a real application yet.
I really think Ajax4Jsf is your best bet if you want to develop JSF + Ajax
today.
Adam Brod
Product Development Team
"Stephen Osella" <so...@austin.rr.com> wrote on 09/12/2006 09:18:48 AM:
> Is there a good (i.e., working!) AJAX for JSF framework? I have tried
> AjaxAnywhere and Ajax4jsf with varying degree (but not complete)
success.
> Your opinion and recommendations would be greatly appreciated.
>
Disclaimer: This electronic mail and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify the sender immediately by replying to this email, and destroy all copies of this email and any attachments. Thank you.
AJAX for JSF
Posted by Stephen Osella <so...@austin.rr.com>.
Is there a good (i.e., working!) AJAX for JSF framework? I have tried
AjaxAnywhere and Ajax4jsf with varying degree (but not complete) success.
Your opinion and recommendations would be greatly appreciated.
Re: ScheduleModel questions
Posted by Jurgen Lust <Ju...@gmail.com>.
I think you will find that you can save a lot of time when you just
extend the AbstractScheduleModel. See the SimpleScheduleModel for an
example.
I suggest you look at the code for those 2 classes, all the answers are
in there :)
Jurgen
Op wo, 13-09-2006 te 07:53 -0500, schreef Stephen Osella:
> Jurgen,
>
> Thank you for your answers. I wanted to get a clarification on your answer
> for question (2):
>
> >> 2) When do you actually call ScheduleModel.refresh()? What is its
> >> purpose?
> >
> > It is used to reload the entries in the schedule model. When you add an
> > entry to the database, you have to call ScheduleModel.refresh() so that
> > it will be shown in the schedule.
>
> I am trying to understand the model that underlies the ScheduleModel class.
> I am not binding the ScheduleModel to a database, but rather managing the
> relationship manually. When the user selects a date, I am adding the
> entries for that date (or dates if the mode is WEEK, etc.) and then calling
> model.refresh(). It seems like I am doing duplicate work when I re-add the
> entries for a date that has already been viewed (i.e., selected) by the
> user; however, I am doing that and it seems to work. I also do a
> model.refresh() when I change the schedule mode. Am I doing things remotely
> correctly?
>
> Thanks!
>
> Steve
>
Re: problem with
Posted by "tszpinda@gmail.com" <ts...@gmail.com>.
Hi Stephen:
My problem was casued by this part of code:
<%
String path = request.getContextPath();
String basePath = request.getScheme() + "://"
+ request.getServerName() + ":" + request.getServerPort()
+ path + "/";
%>
in the jsp file, then when I pressed schedule event I would redirect me
to my login page.
So check it out, if you have something similar there.
Tomek
Re: problem with
Posted by Stephen Osella <so...@austin.rr.com>.
Tomek,
I am using myfaces.1.1.3 and tomahawk.1.1.5 SNAPSHOT from 10/20
-----------------------------------------------------------------------------------------------------
The relavent part of the schedule JSP is exactly that used in the examples:
<t:div styleClass="schedule_view">
<h:form id="viewEventForm">
<t:schedule
id="subscriber_schedule_viewing_events"
value="#{SessionCalendar.scheduleHandler.model}"
binding="#{SessionCalendar.scheduleHandler.schedule}"
rendered="true"
visibleStartHour="#{SessionCalendar.scheduleSettings.visibleStartHour}"
visibleEndHour="#{SessionCalendar.scheduleSettings.visibleEndHour}"
workingStartHour="#{SessionCalendar.scheduleSettings.workingStartHour}"
workingEndHour="#{SessionCalendar.scheduleSettings.workingEndHour}"
readonly="#{SessionCalendar.scheduleSettings.readonly}"
theme="#{SessionCalendar.scheduleSettings.theme}"
tooltip="#{SessionCalendar.scheduleSettings.tooltip}"
submitOnClick="true"
mouseListener="#{SessionCalendar.scheduleHandler.scheduleClicked}"
action="#{SessionCalendar.scheduleHandler.scheduleAction}"
/>
</h:form>
</t:div>
-----------------------------------------------------------------------------------------------------
The schedule event handler code is:
public String scheduleAction()
{
logger.info("In scheduleAction()");
switch (this.eventType)
{
case ScheduleMouseEvent.SCHEDULE_BODY_CLICKED:
break;
case ScheduleMouseEvent.SCHEDULE_ENTRY_CLICKED:
break;
default:
break;
}
}
public void scheduleClicked(ScheduleMouseEvent event)
{
logger.info("In scheduleClicked(): event type="+event.getEventType());
logger.info("In scheduleClicked(): event date="+event.getClickedDate());
this.eventType = event.getEventType();
this.eventDate = event.getClickedDate();
}
-----------------------------------------------------------------------------------------------------
Below is the debug log when clicking on an event:
10:12:06,535 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
renderResponse in org.apache.myfaces.lifecycle.LifecycleImpl
10:12:06,535 - DEBUG javax.faces.webapp.FacesServlet - service end
10:12:06,535 - DEBUG
org.apache.myfaces.renderkit.html.util.ReducedHTMLParser - DOCTYPE found at
line 28
10:12:51,769 - DEBUG org.apache.catalina.core.StandardWrapper - Returning
non-STM instance
10:12:51,769 - DEBUG javax.faces.webapp.FacesServlet - service begin
10:12:51,769 - DEBUG
org.apache.myfaces.context.servlet.ServletExternalContextImpl - Incoming
request has Content-Type header without character encoding:
application/x-www-form-urlencoded
10:12:51,769 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
restoreView in org.apache.myfaces.lifecycle.LifecycleImpl
10:12:51,769 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
restoreView
10:12:51,769 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
restoreTreeStructure
10:12:51,769 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
deserializeView
10:12:51,769 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
deserializeView - deserializing serialized state. Bytes : 3214
10:12:51,785 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Tree structure
restored from server session
10:12:51,785 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
restoreTreeStructure
10:12:51,785 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
restoreComponentState
10:12:51,785 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
restoreComponentState
10:12:51,785 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting restoreView
10:12:51,785 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
restoreView in org.apache.myfaces.lifecycle.LifecycleImpl
10:12:51,785 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
applyRequestValues in org.apache.myfaces.lifecycle.LifecycleImpl
10:12:51,785 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
applyRequestValues in org.apache.myfaces.lifecycle.LifecycleImpl
10:12:51,785 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
processValidations in org.apache.myfaces.lifecycle.LifecycleImpl
10:12:51,785 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
processValidations in org.apache.myfaces.lifecycle.LifecycleImpl
10:12:51,785 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
updateModelValues in org.apache.myfaces.lifecycle.LifecycleImpl
10:12:51,785 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
updateModelValues in org.apache.myfaces.lifecycle.LifecycleImpl
10:12:51,785 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
invokeApplication in org.apache.myfaces.lifecycle.LifecycleImpl
10:12:51,785 - INFO com.myapp.app.component.SubscriberScheduleHandler - In
scheduleClicked(): event type=3
10:12:51,785 - INFO com.myapp.app.component.SubscriberScheduleHandler - In
scheduleClicked(): event date=null
10:12:51,785 - INFO com.myapp.app.component.SubscriberScheduleHandler - In
scheduleAction()
10:12:51,785 - INFO com.myapp.app.navigation.MyAppNavigationHandler -
viewId=/view_calendar_s.jsp
10:12:51,785 - INFO com.myapp.app.navigation.MyAppNavigationHandler -
actionMethod=#{SessionSubscriberCalendar.scheduleHandler.scheduleAction};
actionName=goto_subscriber_schedule_appointment
10:12:51,785 - DEBUG org.apache.myfaces.application.NavigationHandlerImpl -
handleNavigation
fromAction=#{SessionSubscriberCalendar.scheduleHandler.scheduleAction}
outcome=goto_subscriber_schedule_appointment toViewId
=/schedule_appointment_s.jsp redirect=true
10:12:51,785 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
from lifecycle.execute in invokeApplication because getResponseComplete is
true from one of the after listeners
10:12:51,785 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
from lifecycle.execute in render because getResponseComplete is true from
one of the before listeners
10:12:51,785 - DEBUG javax.faces.webapp.FacesServlet - service end
10:12:51,801 - DEBUG org.apache.catalina.core.StandardWrapper - Returning
non-STM instance
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet - JspEngine -->
/index.jsp
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet -
ServletPath: /index.jsp
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet -
PathInfo: null
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet -
RealPath: C:\Program Files\Apache Software Foundation\Tomcat
5.5\webapps\myapp\index.jsp
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet -
RequestURI: /myapp/
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet -
QueryString: null
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet - Request
Params:
10:12:51,801 - DEBUG org.apache.catalina.core.StandardWrapper - Returning
non-STM instance
10:12:51,801 - DEBUG javax.faces.webapp.FacesServlet - service begin
10:12:51,801 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
restoreView in org.apache.myfaces.lifecycle.LifecycleImpl
10:12:51,801 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
restoreView
10:12:51,801 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
restoreTreeStructure
10:12:51,801 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
restoreTreeStructure - No serialized view found in server session!
10:12:51,801 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting restoreView
10:12:51,801 - DEBUG org.apache.myfaces.application.jsp.JspViewHandlerImpl -
Created view /main.jsp
10:12:51,801 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
from lifecycle.execute in restoreView because getRenderResponse is true from
one of the after listeners
10:12:51,801 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
renderResponse in org.apache.myfaces.lifecycle.LifecycleImpl
10:12:51,801 - DEBUG org.apache.myfaces.application.jsp.JspViewHandlerImpl -
Dispatching to /main.jsp
10:12:51,801 - DEBUG org.apache.catalina.core.ApplicationDispatcher -
servletPath=/main.jsp, pathInfo=null, queryString=null, name=null
10:12:51,801 - DEBUG org.apache.catalina.core.ApplicationDispatcher - Path
Based Forward
10:12:51,801 - DEBUG org.apache.catalina.core.StandardWrapper - Returning
non-STM instance
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet - JspEngine -->
/main.jsp
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet -
ServletPath: /main.jsp
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet -
PathInfo: null
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet -
RealPath: C:\Program Files\Apache Software Foundation\Tomcat
5.5\webapps\myapp\main.jsp
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet -
RequestURI: /myapp/main.jsp
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet -
QueryString: null
10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet - Request
Params:
10:12:51,816 - DEBUG org.apache.myfaces.taglib.core.ViewTag - entering
ViewTag.doStartTag
10:12:51,816 - DEBUG org.apache.myfaces.taglib.core.ViewTag - leaving
ViewTag.doStartTag
10:12:51,816 - DEBUG javax.faces.webapp.UIComponentTag - Entered encodeBegin
for client-Id: _idJsp0
--- SKIPPING INTERIOR encodeBegin / encodeEnd ---
10:12:51,832 - DEBUG javax.faces.webapp.UIComponentTag - Exited encodeEnd
for client-Id: _idJsp1
10:12:51,832 - DEBUG org.apache.myfaces.taglib.core.ViewTag - entering
ViewTag.doAfterBody
10:12:51,832 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
saveSerializedView
10:12:51,832 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
saveSerializedView - Checked for duplicate Ids
10:12:51,832 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
saveSerializedView - create new serialized view
10:12:51,832 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
getTreeStructureToSave
10:12:51,832 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
getTreeStructureToSave
10:12:51,832 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
getComponentStateToSave
10:12:51,832 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
getComponentStateToSave
10:12:51,832 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
saveSerializedView - new serialized view created
10:12:51,832 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
saveSerializedView - server-side state saving - save state
10:12:51,832 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
serializeView
10:12:51,832 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
serializeView - serialize state in session
10:12:51,832 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
serializeView - serialize compressed
10:12:51,848 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
serializeView - serialized. Bytes : 4034
10:12:51,848 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
saveSerializedView - server-side state saving - saved state
10:12:51,848 - DEBUG org.apache.myfaces.taglib.core.ViewTag - leaving
ViewTag.doAfterBody
10:12:51,848 - DEBUG org.apache.myfaces.taglib.core.ViewTag - entering
ViewTag.doEndTag
10:12:51,848 - DEBUG org.apache.myfaces.taglib.core.ViewTag - leaving
ViewTag.doEndTag
10:12:51,848 - DEBUG org.apache.catalina.core.ApplicationDispatcher -
Disabling the response for futher output
10:12:51,848 - DEBUG org.apache.catalina.core.ApplicationDispatcher - The
Response is vehiculed using a wrapper:
org.apache.myfaces.webapp.filter.ExtensionsResponseWrapper
10:12:51,879 - DEBUG org.apache.myfaces.util.DebugUtils - View after
rendering
========================================
<UIViewRoot id="NULL" FORMER_CHILD_IDS="[_idJsp1, _idJsp0]"
family="javax.faces.ViewRoot" locale="en" renderKitId="HTML_BASIC"
rendered="true" rendererType="NULL" rendersChildren="false"
transient="false" viewId="/main.jsp">
</UIViewRoot>
========================================
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Below is the debug log when clicking on the schedule body, which works.
10:07:39,035 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
renderResponse in org.apache.myfaces.lifecycle.LifecycleImpl
10:07:39,035 - DEBUG javax.faces.webapp.FacesServlet - service end
10:07:39,035 - DEBUG
org.apache.myfaces.renderkit.html.util.ReducedHTMLParser - DOCTYPE found at
line 28
10:07:49,379 - DEBUG org.apache.catalina.core.StandardWrapper - Returning
non-STM instance
10:07:49,379 - DEBUG javax.faces.webapp.FacesServlet - service begin
10:07:49,379 - DEBUG
org.apache.myfaces.context.servlet.ServletExternalContextImpl - Incoming
request has Content-Type header without character encoding:
application/x-www-form-urlencoded
10:07:49,379 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
restoreView in org.apache.myfaces.lifecycle.LifecycleImpl
10:07:49,379 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
restoreView
10:07:49,379 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
restoreTreeStructure
10:07:49,379 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
deserializeView
10:07:49,379 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
deserializeView - deserializing serialized state. Bytes : 3214
10:07:49,394 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Tree structure
restored from server session
10:07:49,394 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
restoreTreeStructure
10:07:49,394 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
restoreComponentState
10:07:49,394 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
restoreComponentState
10:07:49,394 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting restoreView
10:07:49,394 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
restoreView in org.apache.myfaces.lifecycle.LifecycleImpl
10:07:49,394 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
applyRequestValues in org.apache.myfaces.lifecycle.LifecycleImpl
10:07:49,394 - DEBUG
org.apache.myfaces.custom.schedule.renderer.ScheduleDetailedDayRenderer -
last clicked datetime: Sun Oct 22 13:19:00 GMT 2006
10:07:49,394 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
applyRequestValues in org.apache.myfaces.lifecycle.LifecycleImpl
10:07:49,394 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
processValidations in org.apache.myfaces.lifecycle.LifecycleImpl
10:07:49,394 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
processValidations in org.apache.myfaces.lifecycle.LifecycleImpl
10:07:49,394 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
updateModelValues in org.apache.myfaces.lifecycle.LifecycleImpl
10:07:49,394 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
updateModelValues in org.apache.myfaces.lifecycle.LifecycleImpl
10:07:49,394 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
invokeApplication in org.apache.myfaces.lifecycle.LifecycleImpl
10:07:49,394 - INFO com.myapp.app.component.SubscriberScheduleHandler - In
scheduleClicked(): event type=1
10:07:49,394 - INFO com.myapp.app.component.SubscriberScheduleHandler - In
scheduleClicked(): event date=Sun Oct 22 13:19:00 GMT 2006
10:07:49,394 - INFO com.myapp.app.component.SubscriberScheduleHandler - In
scheduleAction()
10:07:49,566 - INFO com.myapp.app.navigation.MyyAppNavigationHandler -
viewId=/view_calendar_s.jsp
10:07:49,566 - INFO com.myapp.app.navigation.MyAppNavigationHandler -
actionMethod=#{SessionSubscriberCalendar.scheduleHandler.scheduleAction};
actionName=goto_subscriber_schedule_appointment
10:07:49,566 - DEBUG org.apache.myfaces.application.NavigationHandlerImpl -
handleNavigation
fromAction=#{SessionSubscriberCalendar.scheduleHandler.scheduleAction}
outcome=goto_subscriber_schedule_appointment toViewId
=/schedule_appointment_s.jsp redirect=true
10:07:49,566 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
from lifecycle.execute in invokeApplication because getResponseComplete is
true from one of the after listeners
10:07:49,566 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
from lifecycle.execute in render because getResponseComplete is true from
one of the before listeners
10:07:49,566 - DEBUG javax.faces.webapp.FacesServlet - service end
10:07:49,582 - DEBUG org.apache.catalina.core.StandardWrapper - Returning
non-STM instance
10:07:49,582 - DEBUG javax.faces.webapp.FacesServlet - service begin
10:07:49,582 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
restoreView in org.apache.myfaces.lifecycle.LifecycleImpl
10:07:49,582 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
restoreView
10:07:49,582 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
restoreTreeStructure
10:07:49,582 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
restoreTreeStructure - No serialized view found in server session!
10:07:49,582 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting restoreView
10:07:49,582 - DEBUG org.apache.myfaces.application.jsp.JspViewHandlerImpl -
Created view /schedule_appointment_s.jsp
10:07:49,582 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - exiting
from lifecycle.execute in restoreView because getRenderResponse is true from
one of the after listeners
10:07:49,582 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
renderResponse in org.apache.myfaces.lifecycle.LifecycleImpl
10:07:49,582 - DEBUG org.apache.myfaces.application.jsp.JspViewHandlerImpl -
Dispatching to /schedule_appointment_s.jsp
10:07:49,582 - DEBUG org.apache.catalina.core.ApplicationDispatcher -
servletPath=/schedule_appointment_s.jsp, pathInfo=null, queryString=null,
name=null
10:07:49,582 - DEBUG org.apache.catalina.core.ApplicationDispatcher - Path
Based Forward
10:07:49,582 - DEBUG org.apache.catalina.core.StandardWrapper - Returning
non-STM instance
10:07:49,582 - DEBUG org.apache.jasper.servlet.JspServlet - JspEngine -->
/schedule_appointment_s.jsp
10:07:49,582 - DEBUG org.apache.jasper.servlet.JspServlet -
ServletPath: /schedule_appointment_s.jsp
10:07:49,582 - DEBUG org.apache.jasper.servlet.JspServlet -
PathInfo: null
10:07:49,582 - DEBUG org.apache.jasper.servlet.JspServlet -
RealPath: C:\Program Files\Apache Software Foundation\Tomcat
5.5\webapps\myapp\schedule_appointment_s.jsp
10:07:49,582 - DEBUG org.apache.jasper.servlet.JspServlet -
RequestURI: /myapp/schedule_appointment_s.jsp
10:07:49,582 - DEBUG org.apache.jasper.servlet.JspServlet -
QueryString: null
10:07:49,582 - DEBUG org.apache.jasper.servlet.JspServlet - Request
Params:
10:07:49,582 - DEBUG org.apache.myfaces.taglib.core.ViewTag - entering
ViewTag.doStartTag
10:07:49,582 - DEBUG org.apache.myfaces.taglib.core.ViewTag - leaving
ViewTag.doStartTag
10:07:49,582 - DEBUG javax.faces.webapp.UIComponentTag - Entered encodeBegin
for client-Id: _idJsp0
--- SKIPPING INTERIOR encodeBegin / encodeEnd ---
10:07:49,723 - DEBUG javax.faces.webapp.UIComponentTag - Exited encodeEnd
for client-Id: _idJsp1
10:07:49,723 - DEBUG org.apache.myfaces.taglib.core.ViewTag - entering
ViewTag.doAfterBody
10:07:49,723 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
saveSerializedView
10:07:49,723 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
saveSerializedView - Checked for duplicate Ids
10:07:49,723 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
saveSerializedView - create new serialized view
10:07:49,723 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
getTreeStructureToSave
10:07:49,723 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
getTreeStructureToSave
10:07:49,723 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
getComponentStateToSave
10:07:49,738 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
getComponentStateToSave
10:07:49,738 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
saveSerializedView - new serialized view created
10:07:49,738 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
saveSerializedView - server-side state saving - save state
10:07:49,738 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Entering
serializeView
10:07:49,738 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
serializeView - serialize state in session
10:07:49,738 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Processing
serializeView - serialize compressed
10:07:49,801 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
serializeView - serialized. Bytes : 7790
10:07:49,801 - DEBUG
org.apache.myfaces.application.jsp.JspStateManagerImpl - Exiting
saveSerializedView - server-side state saving - saved state
10:07:49,801 - DEBUG org.apache.myfaces.taglib.core.ViewTag - leaving
ViewTag.doAfterBody
10:07:49,801 - DEBUG org.apache.myfaces.taglib.core.ViewTag - entering
ViewTag.doEndTag
10:07:49,801 - DEBUG org.apache.myfaces.taglib.core.ViewTag - leaving
ViewTag.doEndTag
10:07:49,801 - DEBUG org.apache.catalina.core.ApplicationDispatcher -
Disabling the response for futher output
10:07:49,801 - DEBUG org.apache.catalina.core.ApplicationDispatcher - The
Response is vehiculed using a wrapper:
org.apache.myfaces.webapp.filter.ExtensionsResponseWrapper
10:07:49,973 - DEBUG org.apache.myfaces.util.DebugUtils - View after
rendering
========================================
<UIViewRoot id="NULL" FORMER_CHILD_IDS="[_idJsp1, _idJsp0]"
family="javax.faces.ViewRoot" locale="en" renderKitId="HTML_BASIC"
rendered="true" rendererType="NULL" rendersChildren="false"
transient="false" viewId="/schedule_appointment_s.jsp">
</UIViewRoot>
========================================
Re: problem with
Posted by "tszpinda@gmail.com" <ts...@gmail.com>.
Stephen,
Could you post full .jsp page? I've got similar issue.
Tomek
Re: problem with
Posted by Stephen Osella <so...@austin.rr.com>.
Jurgen,
I have looked at the example5 and it is working on my system, which also
puzzled me. Could you make any sense of the log files I sent you?
One thing that I am doing in my faces_config.xml file that could be causing
a problem is that I have a navigation entry of:
<navigation-rule>
<from-view-id>/*</from-view-id>
<navigation-case>
<from-outcome>internal_error</from-outcome>
<to-view-id>/error.jsp</to-view-id>
<redirect/>
</navigation-case>
...
</navigation-rule>
which I use for "global" type actions. Could this be causing problems? Any
insight you could give would be very valuable.
Thanks!
Steve
Re: problem with -- found problem & solution
Posted by Jurgen Lust <Ju...@gmail.com>.
Hi Steven,
You should be able to get the Entry that was clicked on by calling
event.getSchedule().getModel().getSelectedEntry(); on the MouseEvent.
The last clicked entry becomes the selected entry before the
mouselistener is called, so this should work.
Jurgen
Op vrijdag 27-10-2006 om 15:48 uur [tijdzone -0500], schreef Stephen
Osella:
> Jurgen,
>
> A guy named Tomek (I think he's a guy) found the problem (and solution).
> Basically, because of automatically generated JSP code by the Myeclipse
> wizard, that HTML Base element is being set as in the following:
>
> <%
> String path = request.getContextPath();
> String basePath = request.getScheme() + "://"
> + request.getServerName() + ":" + request.getServerPort()
> + path + "/";
> %>
>
> <base href="<%=basePath%>"/>
>
>
> When this is removed, everything works just fine.
>
> I have another question....when the MouseListener method is invoked, how can
> I tell which Entry was actually clicked on? Is there a way to retrieve the
> UID of the entry?
>
> Thanks!
>
> Steve
>
--
____________________________________________________
Jurgen Lust
email: jlust@apache.org
blog: http://jroller.com/page/jurgenlust
____________________________________________________
Re: problem with
Posted by Jurgen Lust <Ju...@gmail.com>.
Hi Steven,
Have you checked example 5 in the tomahawk simple examples?
When you click the add sample entries button, and then click on one of
the entries, you will see something like this in the log file:
26-okt-2006 22:58:44 org.apache.myfaces.examples.schedule.BindingScheduleExampleHandler scheduleAction
INFO: The schedule was clicked
26-okt-2006 22:58:44 org.apache.myfaces.examples.schedule.BindingScheduleExampleHandler scheduleAction
INFO: selected entry: org.apache.myfaces.custom.schedule.model.DefaultScheduleEntry@edc33d
Which means, the action is called correctly, and the entry is also
selected like it should be. Now if you add this to the
examples-config.xml:
<navigation-rule>
<from-view-id>/schedule5.jsp</from-view-id>
<navigation-case>
<from-outcome>success</from-outcome>
<to-view-id>/div.jsp</to-view-id>
<redirect />
</navigation-case>
</navigation-rule>
You should be redirected to the /div.jsp after clicking either on the
schedule body or on an entry.
Jurgen
Op zondag 22-10-2006 om 10:45 uur [tijdzone -0500], schreef Stephen
Osella:
> Jurgen,
>
> I am having a problem with <t:schedule> when clicking on an event entry (vs.
> clicking on the body). When I click on an event entry, it renders the
> main.jsp (by way of index.jsp) rather than the page indicated for the
> outcome in the config file. This should not be happening, so I am thinking
> that the schedule renderer is doing something wrong, or something for which
> I have not setup the environment.
>
> I have attached the debug log for the 2 cases: click on body and click on
> entry. The clear thing is that after:
> 10:12:51,801 - DEBUG org.apache.catalina.core.StandardWrapper - Returning
> non-STM instance
>
> Click on body does:
>
> 10:07:49,582 - DEBUG javax.faces.webapp.FacesServlet - service begin
> 10:07:49,582 - DEBUG org.apache.myfaces.lifecycle.LifecycleImpl - entering
> restoreView in org.apache.myfaces.lifecycle.LifecycleImpl
>
> while click on entry does:
>
> 10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet - JspEngine -->
> /index.jsp
> 10:12:51,801 - DEBUG org.apache.jasper.servlet.JspServlet - ServletPath:
> /index.jsp
>
>
> Can you kindly look into this and help me out on this?
>
> Steve
--
____________________________________________________
Jurgen Lust
email: jlust@apache.org
blog: http://jroller.com/page/jurgenlust
____________________________________________________
Re: ScheduleModel questions
Posted by Jurgen Lust <Ju...@gmail.com>.
Op di, 12-09-2006 te 08:00 -0500, schreef Stephen Osella:
> 1) What does the containsDate(java.util.Date) actually main? That is, when
> is the Date set that this method considers it to be contained within the
> ScheduleModel? Is it when you use setSelectedDate() or when you use
> addEntry()?
Excellent question actually: I didn't know the answer immediately, so I
checked in the code and it turns out that it isn't used anymore! I think
it was used at some point to determine whether or not to render an entry
in a day column/cell.
>
> 2) When do you actually call ScheduleModel.refresh()? What is its purpose?
It is used to reload the entries in the schedule model. When you add an
entry to the database, you have to call ScheduleModel.refresh() so that
it will be shown in the schedule.
>
> 3) How are the java.util.Date's (i.e., in setStartTime & setEndTime)
> considered? Are they UTC or Local or Floating? Is there a way to use a
> converter such as when using <h:outputText> and <f:convertDateTime> or do I
> have to convert the dates to the internal representation (i.e., UTC or Local
> or Floating)?
See TOMAHAWK-619 for this:
http://issues.apache.org/jira/browse/TOMAHAWK-619
>
> 4) Is there any tutorial or more indepth documentation on ScheduleModel than
> the javadoc's?
Aside from the examples, no...
ScheduleModel questions
Posted by Stephen Osella <so...@austin.rr.com>.
1) What does the containsDate(java.util.Date) actually main? That is, when
is the Date set that this method considers it to be contained within the
ScheduleModel? Is it when you use setSelectedDate() or when you use
addEntry()?
2) When do you actually call ScheduleModel.refresh()? What is its purpose?
3) How are the java.util.Date's (i.e., in setStartTime & setEndTime)
considered? Are they UTC or Local or Floating? Is there a way to use a
converter such as when using <h:outputText> and <f:convertDateTime> or do I
have to convert the dates to the internal representation (i.e., UTC or Local
or Floating)?
4) Is there any tutorial or more indepth documentation on ScheduleModel than
the javadoc's?
Thanks in advance.