You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Groovie <gr...@groovesytems.de> on 2008/09/28 13:32:21 UTC
[TOBAGO] serious problems with managed-bean's
Dear sirs,
i have the problem, that i can only read from managed-beans, but
unable to change their attribute values, nor i am able to call
a action. It looks like a one-dataflow.
Here is the managed-beans config:
<managed-bean>
<managed-bean-name>loginBean</managed-bean-name>
<managed-bean-class>org.blueprint01.app.ui.login.LoginBean</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>loginController</managed-bean-name>
<managed-bean-class>de.axa.wz.blueprint01.app.ui.login.LoginController</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
The first bean is used to keep a session long data, where my controller
is only needed to ... perform a callback in my attached Controller-Bean.
I have the impression, that the exposed date, that is beeing sent back
(modified) cannot be correctly identified. The Log-File shows a strange
message:
ERROR ViewHandlerImpl:101 - renderView - view id '/pages/login.jsp'; view
root: 'org.apache.myfaces.tobago.component.UIViewRoot@89ffb18'
You may noticed, that /pages/login.jsp is the Page, that was used
to sent out the data, and finally also needed to decorde the invoming
HTML-Message.
Somebody has a idea, what's the problem or how i get can
get it!
Thanks in advance....
___
PS: The bean attributes are of course writable.
--
View this message in context: http://www.nabble.com/-TOBAGO--serious-problems-with-managed-bean%27s-tp19710817p19710817.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [TOBAGO] serious problems with managed-bean's
Posted by Groovie <gr...@groovesytems.de>.
Groovie wrote:
>
> Dear sirs,
>
> i have the problem, that i can only read from managed-beans, but
> unable to change their attribute values, nor i am able to call
> a action. It looks like a one-dataflow.
>
> Here is the managed-beans config:
>
> <managed-bean>
> <managed-bean-name>loginBean</managed-bean-name>
>
> <managed-bean-class>org.blueprint01.app.ui.login.LoginBean</managed-bean-class>
> <managed-bean-scope>session</managed-bean-scope>
> </managed-bean>
>
> <managed-bean>
> <managed-bean-name>loginController</managed-bean-name>
>
> <managed-bean-class>de.axa.wz.blueprint01.app.ui.login.LoginController</managed-bean-class>
> <managed-bean-scope>session</managed-bean-scope>
> </managed-bean>
>
> The first bean is used to keep a session long data, where my controller
> is only needed to ... perform a callback in my attached Controller-Bean.
>
> I have the impression, that the exposed date, that is beeing sent back
> (modified) cannot be correctly identified. The Log-File shows a strange
> message:
>
> ERROR ViewHandlerImpl:101 - renderView - view id '/pages/login.jsp'; view
> root: 'org.apache.myfaces.tobago.component.UIViewRoot@89ffb18'
>
> You may noticed, that /pages/login.jsp is the Page, that was used
> to sent out the data, and finally also needed to decorde the invoming
> HTML-Message.
>
> Somebody has a idea, what's the problem or how i get can
> get it! Yes i do use 2.0.18.
>
> Thanks in advance....
>
> ___
> PS: The bean attributes are of course writable.
>
--
View this message in context: http://www.nabble.com/-TOBAGO--serious-problems-with-managed-bean%27s-tp19710817p19710822.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [TOBAGO] serious problems with managed-bean's
Posted by Simon Kitching <sk...@apache.org>.
Do you have an h:messages page in your page so you can see
conversion/validation error messages? If not, try adding one..
Regards,
Simon
Arvid Hülsebus schrieb:
> Hello
>
> The log message in ViewHandlerImpl:101 has the wrong level. It's just debug info, not an error. I fixed that in the code.
>
> I think we need more info to determine, what goes wrong: Java and JSP snippets of the relevant areas. Perhaps a bigger chunk of the log file could help, too.
>
> Best regards
> Arvid
>
>
> -----Original Message-----
> From: Groovie [mailto:groovie@groovesytems.de]
> Sent: Sunday, September 28, 2008 1:32 PM
> To: users@myfaces.apache.org
> Subject: [TOBAGO] serious problems with managed-bean's
>
>
> Dear sirs,
>
> i have the problem, that i can only read from managed-beans, but
> unable to change their attribute values, nor i am able to call
> a action. It looks like a one-dataflow.
>
> Here is the managed-beans config:
>
> <managed-bean>
> <managed-bean-name>loginBean</managed-bean-name>
>
> <managed-bean-class>org.blueprint01.app.ui.login.LoginBean</managed-bean-class>
> <managed-bean-scope>session</managed-bean-scope>
> </managed-bean>
>
> <managed-bean>
> <managed-bean-name>loginController</managed-bean-name>
>
> <managed-bean-class>de.axa.wz.blueprint01.app.ui.login.LoginController</managed-bean-class>
> <managed-bean-scope>session</managed-bean-scope>
> </managed-bean>
>
> The first bean is used to keep a session long data, where my controller
> is only needed to ... perform a callback in my attached Controller-Bean.
>
> I have the impression, that the exposed date, that is beeing sent back
> (modified) cannot be correctly identified. The Log-File shows a strange
> message:
>
> ERROR ViewHandlerImpl:101 - renderView - view id '/pages/login.jsp'; view
> root: 'org.apache.myfaces.tobago.component.UIViewRoot@89ffb18'
>
> You may noticed, that /pages/login.jsp is the Page, that was used
> to sent out the data, and finally also needed to decorde the invoming
> HTML-Message.
>
> Somebody has a idea, what's the problem or how i get can
> get it!
>
> Thanks in advance....
>
> ___
> PS: The bean attributes are of course writable.
>
>
RE: [TOBAGO] CLOSED serious problems with managed-bean's
Posted by Groovie <gr...@groovesytems.de>.
Salut Arvid,
in advance, thanks for your help.
When i started with Tobago i had the problem, that i wasn't able to find
a good introduction, who the tags could be used to buid an nice webapp.
See the knowledge is somehow distributed in the java/tld Doc, but for a
newbee this was nogood!
So i decided to get the Demo http://tobago.atanion.net/tobago-example-demo/
und try to change is step by step. Finally, that was also not a good idea,
cause this apps uses its own navigation handle, that is a little bit complex
but good enough to understand its existence.
I remember, that i dropped some code off. Anayway i was trying to
goon with the layout-tag. I think there was still some old setting, that
prevented MyFaces/Tobago read the form-variables into the beans.
Anyway, it seems, that i still have a problem with the transition from one
JSP-page to another, only the first page is loaded, regardless what the
controller returns as a string.
Would it be a better solution to rewrite the JSP code, without the
beautifil layout tag of the demo application?
Does there exist a log-fascility, that reports the state/jsp-page change
with regard to the received Controller return value ?
Arvid Hülsebus wrote:
>
> The DebugPhaseListener just prints out debug information in the log file
> -- for example timing information about the phases in the JSF life cycle
> and messages found in the Faces Context.
>
> The TobagoMultipartFormdataFilter is used to handle file upload and is
> more or less transparent in other occasions.
>
> These two actions you described shouldn't have an effect on the problem
> you described.
>
> Which navigation handler did you remove? Was it a Tobago
> DebugNavigationHandler? That one shouldn't have an effect either, because
> it's just logging debug information, too.
>
> Strange indeed.
>
> Best regards
> Arvid
>
> -----Original Message-----
> From: Groovie [mailto:groovie@groovesytems.de]
> Sent: Monday, September 29, 2008 10:20 PM
> To: users@myfaces.apache.org
> Subject: RE: [TOBAGO] CLOSED serious problems with managed-bean's
>
>
> Salut Arvid,
>
> i fixed that strange behaviour by saving the ole state
> in my CVS und uploading a simple(1) Tobago test over
> it.
> Lucky guy i was, seeing the test application running.
> Then i reintregrated my application into the test app
> and finally removed the test app components.
> Doing this step by step with a functional test of
> the demo-app and mine.
>
> Ok, this took 25Hours in one go 1 litre tee and 2 litres
> of best brewed bavarian beer.
>
> There are two files, that could cause the impact:
>
> 1) faces-config.xml
>
> 1.1)removed the navigation-handler from application tag
>
> 1.2)added
> <lifecycle>
> <phase-listener>
> org.apache.myfaces.tobago.util.DebugPhaseListener
> </phase-listener>
> </lifecycle>
>
> 2) in web.xml
> 2.1 removd
> <filter-mapping>
> <filter-name>multipartFormdataFilter</filter-name>
> <url-pattern>/faces/*</url-pattern>
> </filter-mapping>
>
> strange strange but its done.
>
> --
> View this message in context:
> http://www.nabble.com/-TOBAGO--serious-problems-with-managed-bean%27s-tp19710817p19730967.html
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
>
>
>
--
View this message in context: http://www.nabble.com/-TOBAGO--serious-problems-with-managed-bean%27s-tp19710817p19757570.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: [TOBAGO] CLOSED serious problems with managed-bean's
Posted by Arvid Hülsebus <ar...@atanion.com>.
The DebugPhaseListener just prints out debug information in the log file -- for example timing information about the phases in the JSF life cycle and messages found in the Faces Context.
The TobagoMultipartFormdataFilter is used to handle file upload and is more or less transparent in other occasions.
These two actions you described shouldn't have an effect on the problem you described.
Which navigation handler did you remove? Was it a Tobago DebugNavigationHandler? That one shouldn't have an effect either, because it's just logging debug information, too.
Strange indeed.
Best regards
Arvid
-----Original Message-----
From: Groovie [mailto:groovie@groovesytems.de]
Sent: Monday, September 29, 2008 10:20 PM
To: users@myfaces.apache.org
Subject: RE: [TOBAGO] CLOSED serious problems with managed-bean's
Salut Arvid,
i fixed that strange behaviour by saving the ole state
in my CVS und uploading a simple(1) Tobago test over
it.
Lucky guy i was, seeing the test application running.
Then i reintregrated my application into the test app
and finally removed the test app components.
Doing this step by step with a functional test of
the demo-app and mine.
Ok, this took 25Hours in one go 1 litre tee and 2 litres
of best brewed bavarian beer.
There are two files, that could cause the impact:
1) faces-config.xml
1.1)removed the navigation-handler from application tag
1.2)added
<lifecycle>
<phase-listener>
org.apache.myfaces.tobago.util.DebugPhaseListener
</phase-listener>
</lifecycle>
2) in web.xml
2.1 removd
<filter-mapping>
<filter-name>multipartFormdataFilter</filter-name>
<url-pattern>/faces/*</url-pattern>
</filter-mapping>
strange strange but its done.
--
View this message in context: http://www.nabble.com/-TOBAGO--serious-problems-with-managed-bean%27s-tp19710817p19730967.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: [TOBAGO] CLOSED serious problems with managed-bean's
Posted by Groovie <gr...@groovesytems.de>.
Salut Arvid,
i fixed that strange behaviour by saving the ole state
in my CVS und uploading a simple(1) Tobago test over
it.
Lucky guy i was, seeing the test application running.
Then i reintregrated my application into the test app
and finally removed the test app components.
Doing this step by step with a functional test of
the demo-app and mine.
Ok, this took 25Hours in one go 1 litre tee and 2 litres
of best brewed bavarian beer.
There are two files, that could cause the impact:
1) faces-config.xml
1.1)removed the navigation-handler from application tag
1.2)added
<lifecycle>
<phase-listener>
org.apache.myfaces.tobago.util.DebugPhaseListener
</phase-listener>
</lifecycle>
2) in web.xml
2.1 removd
<filter-mapping>
<filter-name>multipartFormdataFilter</filter-name>
<url-pattern>/faces/*</url-pattern>
</filter-mapping>
strange strange but its done.
--
View this message in context: http://www.nabble.com/-TOBAGO--serious-problems-with-managed-bean%27s-tp19710817p19730967.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: [TOBAGO] serious problems with managed-bean's
Posted by Arvid Hülsebus <ar...@atanion.com>.
Hello
The log message in ViewHandlerImpl:101 has the wrong level. It's just debug info, not an error. I fixed that in the code.
I think we need more info to determine, what goes wrong: Java and JSP snippets of the relevant areas. Perhaps a bigger chunk of the log file could help, too.
Best regards
Arvid
-----Original Message-----
From: Groovie [mailto:groovie@groovesytems.de]
Sent: Sunday, September 28, 2008 1:32 PM
To: users@myfaces.apache.org
Subject: [TOBAGO] serious problems with managed-bean's
Dear sirs,
i have the problem, that i can only read from managed-beans, but
unable to change their attribute values, nor i am able to call
a action. It looks like a one-dataflow.
Here is the managed-beans config:
<managed-bean>
<managed-bean-name>loginBean</managed-bean-name>
<managed-bean-class>org.blueprint01.app.ui.login.LoginBean</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>loginController</managed-bean-name>
<managed-bean-class>de.axa.wz.blueprint01.app.ui.login.LoginController</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
The first bean is used to keep a session long data, where my controller
is only needed to ... perform a callback in my attached Controller-Bean.
I have the impression, that the exposed date, that is beeing sent back
(modified) cannot be correctly identified. The Log-File shows a strange
message:
ERROR ViewHandlerImpl:101 - renderView - view id '/pages/login.jsp'; view
root: 'org.apache.myfaces.tobago.component.UIViewRoot@89ffb18'
You may noticed, that /pages/login.jsp is the Page, that was used
to sent out the data, and finally also needed to decorde the invoming
HTML-Message.
Somebody has a idea, what's the problem or how i get can
get it!
Thanks in advance....
___
PS: The bean attributes are of course writable.
--
View this message in context: http://www.nabble.com/-TOBAGO--serious-problems-with-managed-bean%27s-tp19710817p19710817.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.