Wow that sounds like a mess! Re: the # at the end that just means your extensions
filter is probably not binding the _javascript_ properly. All links (generally) in
JSF are just to # on the current page, then _javascript_ traps the action and converts
it to a form POST (because HTML does not support anything like <a href=""
method=”post”>). The fact that it’s not taking you
anywhere (except #) means the _javascript_ did not catch the click properly. I
would guess this is something to do with the way in which you’ve setup
the filters. Are you managing your backing beans with
spring? Or simply trying to inject spring beans into JSF beans? Can you show
more examples of your code? As for Robert Cambell’s issue—I
thought of something—the order in which the listeners occur is important.
Make sure ContextLoaderListener is right at the top. Otherwise if it’s a
MyFaces 1.1.3 issue I cant speak to it directly as my tests have been with
Myfaces 1.0.x with spring 2.0. One thing that comes to mind is that all the packages
changed for myfaces 1.1(?) from net.sourceforge.myfaces to org.apache.myfaces. Can anyone else verify they’ve got a
similar setup with 1.1.3? From:
Wolf Benz [mailto:[EMAIL PROTECTED] I have this feeling that under the covers, some things really changed
over the last few versions. (& I also wonder wheter regression test are done. :-) Before, my JSF beans got properly ijected with Sping beans. --> has anything changed at JSF variable resolver level? Also before, t:inputHTML worked fine. Now all it passes to my backing
bean, is null "values" (in all browsers) To finish, when I add the streaming resource, follwong the MF site, my
entire navigation is not working. The only thing that changes, is the URL in
the address bar: an "#" is added there. ... These are the issues I'm currently stuck with. And I don't even use too
many components! - Wolf On 18 Jul 2006, at 10:23, Wolf Benz wrote: You said that it never used to happen? Do you think it could be related
to an upgrade in JSF, Spring, or something else? -- Hi Robert, I upgraded to Tomcat v.5.5.17 from v.5.5.12 I also upgraded from MyFaces 1.1.1 to 1.1.3. So, at first sight, I'd say it's that. Apart from that, the only thing I added was a
"AddResourceFilter" in the web.xml. (4
procedure: see MyFaces site) Donno if that helps you. Wolf, On 7/17/06, Wolf
Benz < [EMAIL PROTECTED]>
wrote:
|
- Re: JSF/Spring integration - managed-property problem Wolf Benz
- RE: JSF/Spring integration - managed-property prob... Dhananjay Prasanna
- Re: JSF/Spring integration - managed-property ... Wolf Benz
- Re: JSF/Spring integration - managed-prope... Robert Campbell
- RE: JSF/Spring integration - managed-property prob... Dhananjay Prasanna