You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by "Oellien, F (Frank)" <Fr...@Intervet.com> on 2007/02/22 15:37:59 UTC
PPRPanelGroup
I have a question regarding the PPRPanelGroup.
When I use the Sandbox-example.war file I can use the PPRPanelGroup
example as expected. However when I implement the corresponding jsp file
and the backing bean in my own application every action like pressing a
commandlink or a commandbutton will be followed by a request and a
complete side refresh.
What I have to keep in mind when working with the Ajax functionilities?
By reading the source code it is also unclear for me why PPRSubmit
button will not led to a whole page refresh and the button in the
secondform does.
Regards
Frank
--------------------------------------
This message, including attachments, is confidential and may be privileged.
If you are not an intended recipient, please notify the sender then delete
and destroy the original message and all copies. You should not copy, forward
and/or disclose this message, in whole or in part, without permission of
the sender.
--------------------------------------
RE: PPRPanelGroup - Additional Info
Posted by "Oellien, F (Frank)" <Fr...@Intervet.com>.
I have just figured out, that the PPRPanelGroup shows only this strange behavior, if used with Sun Standard implementation. When I use myfaces instead the resukts are different:
Now I receive an alert window with the message: 'an error occurred during the ajax-request XMLHttpTransport Error: 500 Internal Server Error
Frank
> -----Original Message-----
> From: Oellien, F (Frank) [mailto:Frank.Oellien@Intervet.com]
> Sent: Montag, 26. Februar 2007 13:27
> To: MyFaces Discussion
> Subject: RE: PPRPanelGroup
>
> Hello,
>
> That is what I have done so far.
> I have tried both 1.1.4 and 1.1.5 in a new web application
> that only contains the original JSP file and the
> corresponding Backing Bean.
>
> And these are the results:
>
> PPRSumit button -> Request/Page Refresh
> ConfiguredSubmit Button -> Request/Page Refresh Update first
> group partially checkbox -> Request/Page Refresh testAction
> Button -> Request/Page Refresh Partial testAction button ->
> Request/Page Refresh Partially submit by change combobox ->
> OK, Ajax Partially submit by change checkbox -> OK, Ajax
> Command link -> OK, Ajax Second PPRPanelGroup Button ->
> Request/Page Refresh
>
> Any explanation for that?
>
> Frank
>
> > -----Original Message-----
> > From: Gerald Müllan [mailto:bierbrauen@gmail.com]
> > Sent: Donnerstag, 22. Februar 2007 17:26
> > To: MyFaces Discussion
> > Subject: Re: PPRPanelGroup
> >
> > Hi,
> >
> > you have to register every component which should fire a
> ppr-request.
> > This can be done in an exactly manner via the "partialTriggers"
> > attribute:
> >
> > E.g. id of a commandButton is "nextWizardStep";
> Consequently if going
> > to the next wizard step should occur via a ppr-request (the whole
> > wizard page is embedded in the
> > s:pprPanelGroup) "partialTriggers" has to be set to
> "nextWizardStep".
> >
> > The other possibility is to use the "partialTriggerPattern"
> attribute:
> >
> > E.g. if you want to use "nextWizardStep" and "previousWizardStep"
> > buttons, just write "*WizardStep" as the "partialTriggerPattern"
> > attribute.
> >
> > Every component which is registered via one of the above attributes
> > should fire a ppr-request, because of the interception point before
> > the regular form post.
> >
> > If it does not, there maybe a bug or another problem. E.g.
> > you cannot use aliasBeans in combination with ppr because of the
> > scoping. But please post the corresponding code, maybe we
> can then say
> > something more on that.
> >
> > Regarding the sandbox examples:
> >
> > You are right, the secondFormButton does one time a ppr-request and
> > the other time a regular submit. It seems to steem from the
> fact that
> > the value of the button is changing after activating a command
> > component from the first form.
> >
> > But don`t waste time on this, your problem should be another one..
> >
> > cheers,
> >
> > Gerald
> >
> > On 2/22/07, Oellien, F (Frank) <Fr...@intervet.com> wrote:
> > > I have a question regarding the PPRPanelGroup.
> > > When I use the Sandbox-example.war file I can use the
> PPRPanelGroup
> > > example as expected. However when I implement the
> corresponding jsp
> > > file and the backing bean in my own application every action like
> > > pressing a commandlink or a commandbutton will be followed by a
> > > request and a complete side refresh.
> > >
> > > What I have to keep in mind when working with the Ajax
> > functionilities?
> > > By reading the source code it is also unclear for me why
> PPRSubmit
> > > button will not led to a whole page refresh and the button in the
> > > secondform does.
> > >
> > > Regards
> > > Frank
> > > --------------------------------------
> > > This message, including attachments, is confidential and
> > may be privileged.
> > > If you are not an intended recipient, please notify the
> sender then
> > > delete and destroy the original message and all copies. You
> > should not
> > > copy, forward and/or disclose this message, in whole or in part,
> > > without permission of the sender.
> > > --------------------------------------
> > >
> >
> >
> > --
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and
> > Courses in English and German
> >
> > Professional Support for Apache MyFaces
> >
> --------------------------------------
> This message, including attachments, is confidential and may
> be privileged.
> If you are not an intended recipient, please notify the
> sender then delete and destroy the original message and all
> copies. You should not copy, forward and/or disclose this
> message, in whole or in part, without permission of the sender.
> --------------------------------------
>
--------------------------------------
This message, including attachments, is confidential and may be privileged.
If you are not an intended recipient, please notify the sender then delete
and destroy the original message and all copies. You should not copy, forward
and/or disclose this message, in whole or in part, without permission of
the sender.
--------------------------------------
RE: PPRPanelGroup
Posted by "Oellien, F (Frank)" <Fr...@Intervet.com>.
I have used a standard faces-config.xml with not myfaces specific parameters.
The reason is that I have also not used the MyFaces API but the JSF RI jar files.
I think that the PPRPanelGroup can only work with the Myfaces package and not with the JSF RI.
Frank Oellien
Scientist
Intervet Innovation GmbH
Zur Propstei
55270 Schwabenheim, Germany
E-Mail: frank.oellien@intervet.com
Phone: +49 (6130) 948 365
Fax: +49 (6130) 948 517
Home http://www.intervet.com
Intervet Innovation GmbH is an Akzo Nobel company
Sitz der Gesellschaft: Schwabenheim Amtsgericht Mainz, HRB 23 166 Geschäftsführer: Dr. Peter Schmid
> -----Original Message-----
> From: Gerald Müllan [mailto:bierbrauen@gmail.com]
> Sent: Freitag, 2. März 2007 09:32
> To: MyFaces Discussion
> Subject: Re: PPRPanelGroup
>
> Have you set the parameter
> "org.apache.myfaces.SERIALIZE_STATE_IN_SESSION" before to
> false? The default is true by the way. Maybe the example bean
> requires to be serialized.
>
> The above three "SCHWERWIEGEND" error logs don`t matter, they
> are common since a few months.
>
> cheers,
>
> Gerald
>
> On 3/1/07, Oellien, F (Frank) <Fr...@intervet.com> wrote:
> > Hello Gerald,
> >
> > I have now tested the jar files from the nightly build and
> observed the following:
> > Obviously all action components (buttons, links, etc) in
> the page that have been configured as partialTrigger will
> fire a partialRequest. I can see this, because the text of
> the 'Pattern Matching PPRPanelGroup:' is changing to
> 'Loading...'. However, that's all. The label does not change
> again and also all fields that should be updated like
> Message, First PPRPanelGroup will not be updated.
> > The tomcat server throws several errors:
> > When I start the page the first time I get the following message:
> >
> > 01.03.2007 12:34:25
> > org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader
> > serveResource
> > SCHWERWIEGEND: Unable to find resource
> src/dom/__package__.js for component dojo.DojoResourceLoader.
> Check that this file is available in the classpath in
> sub-directory /resource of the package-directory.
> > 01.03.2007 12:34:25
> > org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader
> > serveResource
> > SCHWERWIEGEND: Unable to find resource src/__package__.js
> for component dojo.DojoResourceLoader. Check that this file
> is available in the classpath in sub-directory /resource of
> the package-directory.
> > 01.03.2007 12:34:25
> > org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader
> > serveResource
> > SCHWERWIEGEND: Unable to find resource __package__.js for
> component dojo.DojoResourceLoader. Check that this file is
> available in the classpath in sub-directory /resource of the
> package-directory.
> >
> > And also
> >
> > 01.03.2007 12:38:28 org.apache.catalina.session.StandardSession
> > writeObject
> > WARNUNG: Cannot serialize session attribute
> >
> org.apache.myfaces.custom.redirectTracker.RedirectTrackerManager for
> > session D0B469D072F4BC3530FEA91193D62CE9
> > java.io.NotSerializableException: test.PPRExampleBean
> > at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
> > at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
> > at java.util.TreeMap.writeObject(TreeMap.java:1475)
> > at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> orImpl.java:39)
> > at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> odAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.
> java:917)
> > at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.
> java:1339)
> > at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStr
> eam.java:1290)
> > at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
> > at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStre
> am.java:1375)
> > at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.
> java:1347)
> > at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStr
> eam.java:1290)
> > at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
> > at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
> > at
> org.apache.catalina.session.StandardSession.writeObject(Standa
> rdSession.java:1462)
> > at
> org.apache.catalina.session.StandardSession.writeObjectData(St
> andardSession.java:938)
> > at
> org.apache.catalina.session.StandardManager.doUnload(StandardM
> anager.java:516)
> > at
> org.apache.catalina.session.StandardManager.unload(StandardMan
> ager.java:462)
> > at
> org.apache.catalina.session.StandardManager.stop(StandardManag
> er.java:666)
> > at
> org.apache.catalina.core.StandardContext.stop(StandardContext.
> java:4345)
> > at
> org.apache.catalina.core.ContainerBase.removeChild(ContainerBa
> se.java:892)
> > at
> org.apache.catalina.startup.HostConfig.undeployApps(HostConfig
> .java:1164)
> > at
> org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1135)
> > at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConf
> ig.java:312)
> > at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(L
> ifecycleSupport.java:119)
> > at
> org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1054)
> > at
> org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1066)
> > at
> org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:447)
> > at
> org.apache.catalina.core.StandardService.stop(StandardService.
> java:512)
> > at
> org.apache.catalina.core.StandardServer.stop(StandardServer.java:743)
> > at
> org.apache.catalina.startup.Catalina.stop(Catalina.java:601)
> > at
> org.apache.catalina.startup.Catalina.start(Catalina.java:576)
> > at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> orImpl.java:39)
> > at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> odAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
> > at
> > org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
> >
> > Clicking a partial Trigger lead to the following message:
> > 01.03.2007 12:35:12
> > org.apache.myfaces.application.jsp.JspStateManagerImpl
> > restoreComponentState
> > SCHWERWIEGEND: No serialized component state found in
> client request!
> >
> > In the next step, I have copied the web.xml file of the
> example war file to my application replacing the old web.xml file.
> > Now the application is working as expectet. Only the
> 'Update first group partially' checkbox will force a request.
> > All error messages except the resource error messages from
> the beginning of this mail have disappeared. Which kind of
> configuration changes in the web.xml file have this influence?
> >
> > Frank
> >
> >
> > > -----Original Message-----
> > > From: Gerald Müllan [mailto:bierbrauen@gmail.com]
> > > Sent: Mittwoch, 28. Februar 2007 11:33
> > > To: MyFaces Discussion
> > > Subject: Re: PPRPanelGroup
> > >
> > > Hi,
> > >
> > > i think you mean the examples from the following url:
> > >
> > > http://example.irian.at/example-sandbox-20070228/pprPanelGroup.jsf
> > >
> > > To me all the links and buttons are working fine with a
> ppr-request.
> > > Have you tried out this latest build?
> > >
> > > cheers,
> > >
> > > Gerald
> > >
> > > On 2/26/07, Oellien, F (Frank) <Fr...@intervet.com> wrote:
> > > > Hello,
> > > >
> > > > That is what I have done so far.
> > > > I have tried both 1.1.4 and 1.1.5 in a new web application
> > > that only contains the original JSP file and the corresponding
> > > Backing Bean.
> > > >
> > > > And these are the results:
> > > >
> > > > PPRSumit button -> Request/Page Refresh
> ConfiguredSubmit Button ->
> > > > Request/Page Refresh Update first group partially checkbox ->
> > > > Request/Page Refresh testAction Button -> Request/Page
> > > Refresh Partial
> > > > testAction button -> Request/Page Refresh Partially submit
> > > by change
> > > > combobox -> OK, Ajax Partially submit by change checkbox ->
> > > OK, Ajax
> > > > Command link -> OK, Ajax Second PPRPanelGroup Button ->
> > > Request/Page
> > > > Refresh
> > > >
> > > > Any explanation for that?
> > > >
> > > > Frank
> > > >
> > > > > -----Original Message-----
> > > > > From: Gerald Müllan [mailto:bierbrauen@gmail.com]
> > > > > Sent: Donnerstag, 22. Februar 2007 17:26
> > > > > To: MyFaces Discussion
> > > > > Subject: Re: PPRPanelGroup
> > > > >
> > > > > Hi,
> > > > >
> > > > > you have to register every component which should fire a
> > > ppr-request.
> > > > > This can be done in an exactly manner via the
> "partialTriggers"
> > > > > attribute:
> > > > >
> > > > > E.g. id of a commandButton is "nextWizardStep";
> Consequently if
> > > > > going to the next wizard step should occur via a ppr-request
> > > > > (the whole wizard page is embedded in the
> > > > > s:pprPanelGroup) "partialTriggers" has to be set to
> > > "nextWizardStep".
> > > > >
> > > > > The other possibility is to use the
> > > "partialTriggerPattern" attribute:
> > > > >
> > > > > E.g. if you want to use "nextWizardStep" and
> "previousWizardStep"
> > > > > buttons, just write "*WizardStep" as the
> "partialTriggerPattern"
> > > > > attribute.
> > > > >
> > > > > Every component which is registered via one of the above
> > > attributes
> > > > > should fire a ppr-request, because of the interception
> > > point before
> > > > > the regular form post.
> > > > >
> > > > > If it does not, there maybe a bug or another problem. E.g.
> > > > > you cannot use aliasBeans in combination with ppr
> because of the
> > > > > scoping. But please post the corresponding code, maybe we
> > > can then
> > > > > say something more on that.
> > > > >
> > > > > Regarding the sandbox examples:
> > > > >
> > > > > You are right, the secondFormButton does one time a
> > > ppr-request and
> > > > > the other time a regular submit. It seems to steem
> from the fact
> > > > > that the value of the button is changing after activating
> > > a command
> > > > > component from the first form.
> > > > >
> > > > > But don`t waste time on this, your problem should be
> another one..
> > > > >
> > > > > cheers,
> > > > >
> > > > > Gerald
> > > > >
> > > > > On 2/22/07, Oellien, F (Frank)
> <Fr...@intervet.com> wrote:
> > > > > > I have a question regarding the PPRPanelGroup.
> > > > > > When I use the Sandbox-example.war file I can use the
> > > > > > PPRPanelGroup example as expected. However when I implement
> > > > > > the corresponding jsp file and the backing bean in my own
> > > application
> > > > > > every action like pressing a commandlink or a
> > > commandbutton will
> > > > > > be followed by a request and a complete side refresh.
> > > > > >
> > > > > > What I have to keep in mind when working with the Ajax
> > > > > functionilities?
> > > > > > By reading the source code it is also unclear for me
> > > why PPRSubmit
> > > > > > button will not led to a whole page refresh and the
> > > button in the
> > > > > > secondform does.
> > > > > >
> > > > > > Regards
> > > > > > Frank
> > > > > > --------------------------------------
> > > > > > This message, including attachments, is confidential and
> > > > > may be privileged.
> > > > > > If you are not an intended recipient, please notify
> the sender
> > > > > > then delete and destroy the original message and
> all copies.
> > > > > > You
> > > > > should not
> > > > > > copy, forward and/or disclose this message, in whole or
> > > in part,
> > > > > > without permission of the sender.
> > > > > > --------------------------------------
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > http://www.irian.at
> > > > >
> > > > > Your JSF powerhouse -
> > > > > JSF Consulting, Development and
> > > > > Courses in English and German
> > > > >
> > > > > Professional Support for Apache MyFaces
> > > > >
> > > > --------------------------------------
> > > > This message, including attachments, is confidential and
> > > may be privileged.
> > > > If you are not an intended recipient, please notify the sender
> > > > then delete and destroy the original message and all copies. You
> > > should not
> > > > copy, forward and/or disclose this message, in whole or
> in part,
> > > > without permission of the sender.
> > > > --------------------------------------
> > > >
> > >
> > >
> > > --
> > > http://www.irian.at
> > >
> > > Your JSF powerhouse -
> > > JSF Consulting, Development and
> > > Courses in English and German
> > >
> > > Professional Support for Apache MyFaces
> > >
> >
> > Frank Oellien
> > Scientist
> > Intervet Innovation GmbH
> > Zur Propstei
> > 55270 Schwabenheim, Germany
> >
> > E-Mail: frank.oellien@intervet.com
> > Phone: +49 (6130) 948 365
> > Fax: +49 (6130) 948 517
> >
> > Home http://www.intervet.com
> >
> > Intervet Innovation GmbH is an Akzo Nobel company
> >
> > Sitz der Gesellschaft: Schwabenheim Amtsgericht
> Mainz, HRB 23 166 Geschäftsführer: Dr. Peter Schmid
> >
> > --------------------------------------
> > This message, including attachments, is confidential and
> may be privileged.
> > If you are not an intended recipient, please notify the sender then
> > delete and destroy the original message and all copies. You
> should not
> > copy, forward and/or disclose this message, in whole or in part,
> > without permission of the sender.
> > --------------------------------------
> >
>
>
> --
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
--------------------------------------
This message, including attachments, is confidential and may be privileged.
If you are not an intended recipient, please notify the sender then delete
and destroy the original message and all copies. You should not copy, forward
and/or disclose this message, in whole or in part, without permission of
the sender.
--------------------------------------
Re: PPRPanelGroup
Posted by Gerald Müllan <bi...@gmail.com>.
Have you set the parameter
"org.apache.myfaces.SERIALIZE_STATE_IN_SESSION" before to false? The
default is true by the way. Maybe the example bean requires to be
serialized.
The above three "SCHWERWIEGEND" error logs don`t matter, they are
common since a few months.
cheers,
Gerald
On 3/1/07, Oellien, F (Frank) <Fr...@intervet.com> wrote:
> Hello Gerald,
>
> I have now tested the jar files from the nightly build and observed the following:
> Obviously all action components (buttons, links, etc) in the page that have been configured as partialTrigger will fire a partialRequest. I can see this, because the text of the 'Pattern Matching PPRPanelGroup:' is changing to 'Loading...'. However, that's all. The label does not change again and also all fields that should be updated like Message, First PPRPanelGroup will not be updated.
> The tomcat server throws several errors:
> When I start the page the first time I get the following message:
>
> 01.03.2007 12:34:25 org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource
> SCHWERWIEGEND: Unable to find resource src/dom/__package__.js for component dojo.DojoResourceLoader. Check that this file is available in the classpath in sub-directory /resource of the package-directory.
> 01.03.2007 12:34:25 org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource
> SCHWERWIEGEND: Unable to find resource src/__package__.js for component dojo.DojoResourceLoader. Check that this file is available in the classpath in sub-directory /resource of the package-directory.
> 01.03.2007 12:34:25 org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource
> SCHWERWIEGEND: Unable to find resource __package__.js for component dojo.DojoResourceLoader. Check that this file is available in the classpath in sub-directory /resource of the package-directory.
>
> And also
>
> 01.03.2007 12:38:28 org.apache.catalina.session.StandardSession writeObject
> WARNUNG: Cannot serialize session attribute org.apache.myfaces.custom.redirectTracker.RedirectTrackerManager for session D0B469D072F4BC3530FEA91193D62CE9
> java.io.NotSerializableException: test.PPRExampleBean
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
> at java.util.TreeMap.writeObject(TreeMap.java:1475)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
> at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
> at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
> at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
> at org.apache.catalina.session.StandardSession.writeObject(StandardSession.java:1462)
> at org.apache.catalina.session.StandardSession.writeObjectData(StandardSession.java:938)
> at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:516)
> at org.apache.catalina.session.StandardManager.unload(StandardManager.java:462)
> at org.apache.catalina.session.StandardManager.stop(StandardManager.java:666)
> at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4345)
> at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:892)
> at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1164)
> at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1135)
> at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:312)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
> at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1054)
> at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1066)
> at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:447)
> at org.apache.catalina.core.StandardService.stop(StandardService.java:512)
> at org.apache.catalina.core.StandardServer.stop(StandardServer.java:743)
> at org.apache.catalina.startup.Catalina.stop(Catalina.java:601)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:576)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
>
> Clicking a partial Trigger lead to the following message:
> 01.03.2007 12:35:12 org.apache.myfaces.application.jsp.JspStateManagerImpl restoreComponentState
> SCHWERWIEGEND: No serialized component state found in client request!
>
> In the next step, I have copied the web.xml file of the example war file to my application replacing the old web.xml file.
> Now the application is working as expectet. Only the 'Update first group partially' checkbox will force a request.
> All error messages except the resource error messages from the beginning of this mail have disappeared. Which kind of configuration changes in the web.xml file have this influence?
>
> Frank
>
>
> > -----Original Message-----
> > From: Gerald Müllan [mailto:bierbrauen@gmail.com]
> > Sent: Mittwoch, 28. Februar 2007 11:33
> > To: MyFaces Discussion
> > Subject: Re: PPRPanelGroup
> >
> > Hi,
> >
> > i think you mean the examples from the following url:
> >
> > http://example.irian.at/example-sandbox-20070228/pprPanelGroup.jsf
> >
> > To me all the links and buttons are working fine with a ppr-request.
> > Have you tried out this latest build?
> >
> > cheers,
> >
> > Gerald
> >
> > On 2/26/07, Oellien, F (Frank) <Fr...@intervet.com> wrote:
> > > Hello,
> > >
> > > That is what I have done so far.
> > > I have tried both 1.1.4 and 1.1.5 in a new web application
> > that only contains the original JSP file and the
> > corresponding Backing Bean.
> > >
> > > And these are the results:
> > >
> > > PPRSumit button -> Request/Page Refresh ConfiguredSubmit Button ->
> > > Request/Page Refresh Update first group partially checkbox ->
> > > Request/Page Refresh testAction Button -> Request/Page
> > Refresh Partial
> > > testAction button -> Request/Page Refresh Partially submit
> > by change
> > > combobox -> OK, Ajax Partially submit by change checkbox ->
> > OK, Ajax
> > > Command link -> OK, Ajax Second PPRPanelGroup Button ->
> > Request/Page
> > > Refresh
> > >
> > > Any explanation for that?
> > >
> > > Frank
> > >
> > > > -----Original Message-----
> > > > From: Gerald Müllan [mailto:bierbrauen@gmail.com]
> > > > Sent: Donnerstag, 22. Februar 2007 17:26
> > > > To: MyFaces Discussion
> > > > Subject: Re: PPRPanelGroup
> > > >
> > > > Hi,
> > > >
> > > > you have to register every component which should fire a
> > ppr-request.
> > > > This can be done in an exactly manner via the "partialTriggers"
> > > > attribute:
> > > >
> > > > E.g. id of a commandButton is "nextWizardStep"; Consequently if
> > > > going to the next wizard step should occur via a ppr-request (the
> > > > whole wizard page is embedded in the
> > > > s:pprPanelGroup) "partialTriggers" has to be set to
> > "nextWizardStep".
> > > >
> > > > The other possibility is to use the
> > "partialTriggerPattern" attribute:
> > > >
> > > > E.g. if you want to use "nextWizardStep" and "previousWizardStep"
> > > > buttons, just write "*WizardStep" as the "partialTriggerPattern"
> > > > attribute.
> > > >
> > > > Every component which is registered via one of the above
> > attributes
> > > > should fire a ppr-request, because of the interception
> > point before
> > > > the regular form post.
> > > >
> > > > If it does not, there maybe a bug or another problem. E.g.
> > > > you cannot use aliasBeans in combination with ppr because of the
> > > > scoping. But please post the corresponding code, maybe we
> > can then
> > > > say something more on that.
> > > >
> > > > Regarding the sandbox examples:
> > > >
> > > > You are right, the secondFormButton does one time a
> > ppr-request and
> > > > the other time a regular submit. It seems to steem from the fact
> > > > that the value of the button is changing after activating
> > a command
> > > > component from the first form.
> > > >
> > > > But don`t waste time on this, your problem should be another one..
> > > >
> > > > cheers,
> > > >
> > > > Gerald
> > > >
> > > > On 2/22/07, Oellien, F (Frank) <Fr...@intervet.com> wrote:
> > > > > I have a question regarding the PPRPanelGroup.
> > > > > When I use the Sandbox-example.war file I can use the
> > > > > PPRPanelGroup example as expected. However when I implement the
> > > > > corresponding jsp file and the backing bean in my own
> > application
> > > > > every action like pressing a commandlink or a
> > commandbutton will
> > > > > be followed by a request and a complete side refresh.
> > > > >
> > > > > What I have to keep in mind when working with the Ajax
> > > > functionilities?
> > > > > By reading the source code it is also unclear for me
> > why PPRSubmit
> > > > > button will not led to a whole page refresh and the
> > button in the
> > > > > secondform does.
> > > > >
> > > > > Regards
> > > > > Frank
> > > > > --------------------------------------
> > > > > This message, including attachments, is confidential and
> > > > may be privileged.
> > > > > If you are not an intended recipient, please notify the sender
> > > > > then delete and destroy the original message and all copies. You
> > > > should not
> > > > > copy, forward and/or disclose this message, in whole or
> > in part,
> > > > > without permission of the sender.
> > > > > --------------------------------------
> > > > >
> > > >
> > > >
> > > > --
> > > > http://www.irian.at
> > > >
> > > > Your JSF powerhouse -
> > > > JSF Consulting, Development and
> > > > Courses in English and German
> > > >
> > > > Professional Support for Apache MyFaces
> > > >
> > > --------------------------------------
> > > This message, including attachments, is confidential and
> > may be privileged.
> > > If you are not an intended recipient, please notify the sender then
> > > delete and destroy the original message and all copies. You
> > should not
> > > copy, forward and/or disclose this message, in whole or in part,
> > > without permission of the sender.
> > > --------------------------------------
> > >
> >
> >
> > --
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and
> > Courses in English and German
> >
> > Professional Support for Apache MyFaces
> >
>
> Frank Oellien
> Scientist
> Intervet Innovation GmbH
> Zur Propstei
> 55270 Schwabenheim, Germany
>
> E-Mail: frank.oellien@intervet.com
> Phone: +49 (6130) 948 365
> Fax: +49 (6130) 948 517
>
> Home http://www.intervet.com
>
> Intervet Innovation GmbH is an Akzo Nobel company
>
> Sitz der Gesellschaft: Schwabenheim Amtsgericht Mainz, HRB 23 166 Geschäftsführer: Dr. Peter Schmid
>
> --------------------------------------
> This message, including attachments, is confidential and may be privileged.
> If you are not an intended recipient, please notify the sender then delete
> and destroy the original message and all copies. You should not copy, forward
> and/or disclose this message, in whole or in part, without permission of
> the sender.
> --------------------------------------
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
RE: PPRPanelGroup
Posted by "Oellien, F (Frank)" <Fr...@Intervet.com>.
Hello Gerald,
I have now tested the jar files from the nightly build and observed the following:
Obviously all action components (buttons, links, etc) in the page that have been configured as partialTrigger will fire a partialRequest. I can see this, because the text of the 'Pattern Matching PPRPanelGroup:' is changing to 'Loading...'. However, that's all. The label does not change again and also all fields that should be updated like Message, First PPRPanelGroup will not be updated.
The tomcat server throws several errors:
When I start the page the first time I get the following message:
01.03.2007 12:34:25 org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource
SCHWERWIEGEND: Unable to find resource src/dom/__package__.js for component dojo.DojoResourceLoader. Check that this file is available in the classpath in sub-directory /resource of the package-directory.
01.03.2007 12:34:25 org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource
SCHWERWIEGEND: Unable to find resource src/__package__.js for component dojo.DojoResourceLoader. Check that this file is available in the classpath in sub-directory /resource of the package-directory.
01.03.2007 12:34:25 org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource
SCHWERWIEGEND: Unable to find resource __package__.js for component dojo.DojoResourceLoader. Check that this file is available in the classpath in sub-directory /resource of the package-directory.
And also
01.03.2007 12:38:28 org.apache.catalina.session.StandardSession writeObject
WARNUNG: Cannot serialize session attribute org.apache.myfaces.custom.redirectTracker.RedirectTrackerManager for session D0B469D072F4BC3530FEA91193D62CE9
java.io.NotSerializableException: test.PPRExampleBean
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at java.util.TreeMap.writeObject(TreeMap.java:1475)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at org.apache.catalina.session.StandardSession.writeObject(StandardSession.java:1462)
at org.apache.catalina.session.StandardSession.writeObjectData(StandardSession.java:938)
at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:516)
at org.apache.catalina.session.StandardManager.unload(StandardManager.java:462)
at org.apache.catalina.session.StandardManager.stop(StandardManager.java:666)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4345)
at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:892)
at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1164)
at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1135)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:312)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1054)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1066)
at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:447)
at org.apache.catalina.core.StandardService.stop(StandardService.java:512)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:743)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:601)
at org.apache.catalina.startup.Catalina.start(Catalina.java:576)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Clicking a partial Trigger lead to the following message:
01.03.2007 12:35:12 org.apache.myfaces.application.jsp.JspStateManagerImpl restoreComponentState
SCHWERWIEGEND: No serialized component state found in client request!
In the next step, I have copied the web.xml file of the example war file to my application replacing the old web.xml file.
Now the application is working as expectet. Only the 'Update first group partially' checkbox will force a request.
All error messages except the resource error messages from the beginning of this mail have disappeared. Which kind of configuration changes in the web.xml file have this influence?
Frank
> -----Original Message-----
> From: Gerald Müllan [mailto:bierbrauen@gmail.com]
> Sent: Mittwoch, 28. Februar 2007 11:33
> To: MyFaces Discussion
> Subject: Re: PPRPanelGroup
>
> Hi,
>
> i think you mean the examples from the following url:
>
> http://example.irian.at/example-sandbox-20070228/pprPanelGroup.jsf
>
> To me all the links and buttons are working fine with a ppr-request.
> Have you tried out this latest build?
>
> cheers,
>
> Gerald
>
> On 2/26/07, Oellien, F (Frank) <Fr...@intervet.com> wrote:
> > Hello,
> >
> > That is what I have done so far.
> > I have tried both 1.1.4 and 1.1.5 in a new web application
> that only contains the original JSP file and the
> corresponding Backing Bean.
> >
> > And these are the results:
> >
> > PPRSumit button -> Request/Page Refresh ConfiguredSubmit Button ->
> > Request/Page Refresh Update first group partially checkbox ->
> > Request/Page Refresh testAction Button -> Request/Page
> Refresh Partial
> > testAction button -> Request/Page Refresh Partially submit
> by change
> > combobox -> OK, Ajax Partially submit by change checkbox ->
> OK, Ajax
> > Command link -> OK, Ajax Second PPRPanelGroup Button ->
> Request/Page
> > Refresh
> >
> > Any explanation for that?
> >
> > Frank
> >
> > > -----Original Message-----
> > > From: Gerald Müllan [mailto:bierbrauen@gmail.com]
> > > Sent: Donnerstag, 22. Februar 2007 17:26
> > > To: MyFaces Discussion
> > > Subject: Re: PPRPanelGroup
> > >
> > > Hi,
> > >
> > > you have to register every component which should fire a
> ppr-request.
> > > This can be done in an exactly manner via the "partialTriggers"
> > > attribute:
> > >
> > > E.g. id of a commandButton is "nextWizardStep"; Consequently if
> > > going to the next wizard step should occur via a ppr-request (the
> > > whole wizard page is embedded in the
> > > s:pprPanelGroup) "partialTriggers" has to be set to
> "nextWizardStep".
> > >
> > > The other possibility is to use the
> "partialTriggerPattern" attribute:
> > >
> > > E.g. if you want to use "nextWizardStep" and "previousWizardStep"
> > > buttons, just write "*WizardStep" as the "partialTriggerPattern"
> > > attribute.
> > >
> > > Every component which is registered via one of the above
> attributes
> > > should fire a ppr-request, because of the interception
> point before
> > > the regular form post.
> > >
> > > If it does not, there maybe a bug or another problem. E.g.
> > > you cannot use aliasBeans in combination with ppr because of the
> > > scoping. But please post the corresponding code, maybe we
> can then
> > > say something more on that.
> > >
> > > Regarding the sandbox examples:
> > >
> > > You are right, the secondFormButton does one time a
> ppr-request and
> > > the other time a regular submit. It seems to steem from the fact
> > > that the value of the button is changing after activating
> a command
> > > component from the first form.
> > >
> > > But don`t waste time on this, your problem should be another one..
> > >
> > > cheers,
> > >
> > > Gerald
> > >
> > > On 2/22/07, Oellien, F (Frank) <Fr...@intervet.com> wrote:
> > > > I have a question regarding the PPRPanelGroup.
> > > > When I use the Sandbox-example.war file I can use the
> > > > PPRPanelGroup example as expected. However when I implement the
> > > > corresponding jsp file and the backing bean in my own
> application
> > > > every action like pressing a commandlink or a
> commandbutton will
> > > > be followed by a request and a complete side refresh.
> > > >
> > > > What I have to keep in mind when working with the Ajax
> > > functionilities?
> > > > By reading the source code it is also unclear for me
> why PPRSubmit
> > > > button will not led to a whole page refresh and the
> button in the
> > > > secondform does.
> > > >
> > > > Regards
> > > > Frank
> > > > --------------------------------------
> > > > This message, including attachments, is confidential and
> > > may be privileged.
> > > > If you are not an intended recipient, please notify the sender
> > > > then delete and destroy the original message and all copies. You
> > > should not
> > > > copy, forward and/or disclose this message, in whole or
> in part,
> > > > without permission of the sender.
> > > > --------------------------------------
> > > >
> > >
> > >
> > > --
> > > http://www.irian.at
> > >
> > > Your JSF powerhouse -
> > > JSF Consulting, Development and
> > > Courses in English and German
> > >
> > > Professional Support for Apache MyFaces
> > >
> > --------------------------------------
> > This message, including attachments, is confidential and
> may be privileged.
> > If you are not an intended recipient, please notify the sender then
> > delete and destroy the original message and all copies. You
> should not
> > copy, forward and/or disclose this message, in whole or in part,
> > without permission of the sender.
> > --------------------------------------
> >
>
>
> --
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
Frank Oellien
Scientist
Intervet Innovation GmbH
Zur Propstei
55270 Schwabenheim, Germany
E-Mail: frank.oellien@intervet.com
Phone: +49 (6130) 948 365
Fax: +49 (6130) 948 517
Home http://www.intervet.com
Intervet Innovation GmbH is an Akzo Nobel company
Sitz der Gesellschaft: Schwabenheim Amtsgericht Mainz, HRB 23 166 Geschäftsführer: Dr. Peter Schmid
--------------------------------------
This message, including attachments, is confidential and may be privileged.
If you are not an intended recipient, please notify the sender then delete
and destroy the original message and all copies. You should not copy, forward
and/or disclose this message, in whole or in part, without permission of
the sender.
--------------------------------------
Re: PPRPanelGroup
Posted by Gerald Müllan <bi...@gmail.com>.
Hi,
i think you mean the examples from the following url:
http://example.irian.at/example-sandbox-20070228/pprPanelGroup.jsf
To me all the links and buttons are working fine with a ppr-request.
Have you tried out this latest build?
cheers,
Gerald
On 2/26/07, Oellien, F (Frank) <Fr...@intervet.com> wrote:
> Hello,
>
> That is what I have done so far.
> I have tried both 1.1.4 and 1.1.5 in a new web application that only contains the original JSP file and the corresponding Backing Bean.
>
> And these are the results:
>
> PPRSumit button -> Request/Page Refresh
> ConfiguredSubmit Button -> Request/Page Refresh
> Update first group partially checkbox -> Request/Page Refresh
> testAction Button -> Request/Page Refresh
> Partial testAction button -> Request/Page Refresh
> Partially submit by change combobox -> OK, Ajax
> Partially submit by change checkbox -> OK, Ajax
> Command link -> OK, Ajax
> Second PPRPanelGroup Button -> Request/Page Refresh
>
> Any explanation for that?
>
> Frank
>
> > -----Original Message-----
> > From: Gerald Müllan [mailto:bierbrauen@gmail.com]
> > Sent: Donnerstag, 22. Februar 2007 17:26
> > To: MyFaces Discussion
> > Subject: Re: PPRPanelGroup
> >
> > Hi,
> >
> > you have to register every component which should fire a ppr-request.
> > This can be done in an exactly manner via the "partialTriggers"
> > attribute:
> >
> > E.g. id of a commandButton is "nextWizardStep"; Consequently
> > if going to the next wizard step should occur via a
> > ppr-request (the whole wizard page is embedded in the
> > s:pprPanelGroup) "partialTriggers" has to be set to "nextWizardStep".
> >
> > The other possibility is to use the "partialTriggerPattern" attribute:
> >
> > E.g. if you want to use "nextWizardStep" and "previousWizardStep"
> > buttons, just write "*WizardStep" as the "partialTriggerPattern"
> > attribute.
> >
> > Every component which is registered via one of the above
> > attributes should fire a ppr-request, because of the
> > interception point before the regular form post.
> >
> > If it does not, there maybe a bug or another problem. E.g.
> > you cannot use aliasBeans in combination with ppr because of
> > the scoping. But please post the corresponding code, maybe we
> > can then say something more on that.
> >
> > Regarding the sandbox examples:
> >
> > You are right, the secondFormButton does one time a
> > ppr-request and the other time a regular submit. It seems to
> > steem from the fact that the value of the button is changing
> > after activating a command component from the first form.
> >
> > But don`t waste time on this, your problem should be another one..
> >
> > cheers,
> >
> > Gerald
> >
> > On 2/22/07, Oellien, F (Frank) <Fr...@intervet.com> wrote:
> > > I have a question regarding the PPRPanelGroup.
> > > When I use the Sandbox-example.war file I can use the PPRPanelGroup
> > > example as expected. However when I implement the corresponding jsp
> > > file and the backing bean in my own application every action like
> > > pressing a commandlink or a commandbutton will be followed by a
> > > request and a complete side refresh.
> > >
> > > What I have to keep in mind when working with the Ajax
> > functionilities?
> > > By reading the source code it is also unclear for me why PPRSubmit
> > > button will not led to a whole page refresh and the button in the
> > > secondform does.
> > >
> > > Regards
> > > Frank
> > > --------------------------------------
> > > This message, including attachments, is confidential and
> > may be privileged.
> > > If you are not an intended recipient, please notify the sender then
> > > delete and destroy the original message and all copies. You
> > should not
> > > copy, forward and/or disclose this message, in whole or in part,
> > > without permission of the sender.
> > > --------------------------------------
> > >
> >
> >
> > --
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and
> > Courses in English and German
> >
> > Professional Support for Apache MyFaces
> >
> --------------------------------------
> This message, including attachments, is confidential and may be privileged.
> If you are not an intended recipient, please notify the sender then delete
> and destroy the original message and all copies. You should not copy, forward
> and/or disclose this message, in whole or in part, without permission of
> the sender.
> --------------------------------------
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
RE: PPRPanelGroup
Posted by "Oellien, F (Frank)" <Fr...@Intervet.com>.
Hello,
That is what I have done so far.
I have tried both 1.1.4 and 1.1.5 in a new web application that only contains the original JSP file and the corresponding Backing Bean.
And these are the results:
PPRSumit button -> Request/Page Refresh
ConfiguredSubmit Button -> Request/Page Refresh
Update first group partially checkbox -> Request/Page Refresh
testAction Button -> Request/Page Refresh
Partial testAction button -> Request/Page Refresh
Partially submit by change combobox -> OK, Ajax
Partially submit by change checkbox -> OK, Ajax
Command link -> OK, Ajax
Second PPRPanelGroup Button -> Request/Page Refresh
Any explanation for that?
Frank
> -----Original Message-----
> From: Gerald Müllan [mailto:bierbrauen@gmail.com]
> Sent: Donnerstag, 22. Februar 2007 17:26
> To: MyFaces Discussion
> Subject: Re: PPRPanelGroup
>
> Hi,
>
> you have to register every component which should fire a ppr-request.
> This can be done in an exactly manner via the "partialTriggers"
> attribute:
>
> E.g. id of a commandButton is "nextWizardStep"; Consequently
> if going to the next wizard step should occur via a
> ppr-request (the whole wizard page is embedded in the
> s:pprPanelGroup) "partialTriggers" has to be set to "nextWizardStep".
>
> The other possibility is to use the "partialTriggerPattern" attribute:
>
> E.g. if you want to use "nextWizardStep" and "previousWizardStep"
> buttons, just write "*WizardStep" as the "partialTriggerPattern"
> attribute.
>
> Every component which is registered via one of the above
> attributes should fire a ppr-request, because of the
> interception point before the regular form post.
>
> If it does not, there maybe a bug or another problem. E.g.
> you cannot use aliasBeans in combination with ppr because of
> the scoping. But please post the corresponding code, maybe we
> can then say something more on that.
>
> Regarding the sandbox examples:
>
> You are right, the secondFormButton does one time a
> ppr-request and the other time a regular submit. It seems to
> steem from the fact that the value of the button is changing
> after activating a command component from the first form.
>
> But don`t waste time on this, your problem should be another one..
>
> cheers,
>
> Gerald
>
> On 2/22/07, Oellien, F (Frank) <Fr...@intervet.com> wrote:
> > I have a question regarding the PPRPanelGroup.
> > When I use the Sandbox-example.war file I can use the PPRPanelGroup
> > example as expected. However when I implement the corresponding jsp
> > file and the backing bean in my own application every action like
> > pressing a commandlink or a commandbutton will be followed by a
> > request and a complete side refresh.
> >
> > What I have to keep in mind when working with the Ajax
> functionilities?
> > By reading the source code it is also unclear for me why PPRSubmit
> > button will not led to a whole page refresh and the button in the
> > secondform does.
> >
> > Regards
> > Frank
> > --------------------------------------
> > This message, including attachments, is confidential and
> may be privileged.
> > If you are not an intended recipient, please notify the sender then
> > delete and destroy the original message and all copies. You
> should not
> > copy, forward and/or disclose this message, in whole or in part,
> > without permission of the sender.
> > --------------------------------------
> >
>
>
> --
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
--------------------------------------
This message, including attachments, is confidential and may be privileged.
If you are not an intended recipient, please notify the sender then delete
and destroy the original message and all copies. You should not copy, forward
and/or disclose this message, in whole or in part, without permission of
the sender.
--------------------------------------
Re: PPRPanelGroup
Posted by Gerald Müllan <bi...@gmail.com>.
Hi,
you have to register every component which should fire a ppr-request.
This can be done in an exactly manner via the "partialTriggers"
attribute:
E.g. id of a commandButton is "nextWizardStep"; Consequently if going
to the next wizard step should occur via a ppr-request (the whole
wizard page is embedded in the s:pprPanelGroup) "partialTriggers" has
to be set to "nextWizardStep".
The other possibility is to use the "partialTriggerPattern" attribute:
E.g. if you want to use "nextWizardStep" and "previousWizardStep"
buttons, just write "*WizardStep" as the "partialTriggerPattern"
attribute.
Every component which is registered via one of the above attributes
should fire a ppr-request, because of the interception point before
the regular form post.
If it does not, there maybe a bug or another problem. E.g. you cannot
use aliasBeans in combination with ppr because of the scoping. But
please post the corresponding code, maybe we can then say something
more on that.
Regarding the sandbox examples:
You are right, the secondFormButton does one time a ppr-request and
the other time a regular submit. It seems to steem from the fact that
the value of the button is changing after activating a command
component from the first form.
But don`t waste time on this, your problem should be another one..
cheers,
Gerald
On 2/22/07, Oellien, F (Frank) <Fr...@intervet.com> wrote:
> I have a question regarding the PPRPanelGroup.
> When I use the Sandbox-example.war file I can use the PPRPanelGroup
> example as expected. However when I implement the corresponding jsp file
> and the backing bean in my own application every action like pressing a
> commandlink or a commandbutton will be followed by a request and a
> complete side refresh.
>
> What I have to keep in mind when working with the Ajax functionilities?
> By reading the source code it is also unclear for me why PPRSubmit
> button will not led to a whole page refresh and the button in the
> secondform does.
>
> Regards
> Frank
> --------------------------------------
> This message, including attachments, is confidential and may be privileged.
> If you are not an intended recipient, please notify the sender then delete
> and destroy the original message and all copies. You should not copy, forward
> and/or disclose this message, in whole or in part, without permission of
> the sender.
> --------------------------------------
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces