]
Sent: Friday, 21 July 2006 6:35 PM
To: MyFaces
Discussion
Subject: Re: JSF/Spring
integration - managed-property problem
Lol.. i know the code
looks like crap - it's just for a quick proof of concept, no worries.
Since time is an issue for me, I gave up this problem a few days ago and
Lol.. i know the code looks like crap - it's just for a quick proof of concept, no worries.Since time is an issue for me, I gave up this problem a few days ago and just used a crappy work-around:In the constructor of SearchForm (the JSF Managed Bean that I tried injecting the Spring bean into) I ju
Wow that sounds like a mess!
-- Now that's a nice thing to say about someone else's code ;-)
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
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, 18 July 2006 10:59
PM
To: MyFaces
Discussion
Subject: Re: JSF/Spring
integration - managed-property problem
I have this feeling that under the covers, some things really changed
over the last few versions.
(& I also wonder wheter regression test
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
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.12I 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 adde
You said that it never used to happen? Do you think it could be related to an upgrade in JSF, Spring, or something else?On 7/17/06, Wolf Benz <
[EMAIL PROTECTED]> wrote:
The variable resolver needs to go in faces-config.xml not web.xml…
-- That's the case. (indeed not in
web.xml)
This correspo
The variable resolver needs to go in faces-config.xml not web.xml…-- That's the case. (indeed not in web.xml)This correspondence is for the named persons only. It may contain confidential or privileged information or both. No confidentiality or privilege is waived or lost by any mis transmission.
From:
Wolf Benz [mailto:[EMAIL PROTECTED]
Sent: Monday, 17 July 2006 2:22 PM
To: MyFaces
Discussion
Subject: Re: JSF/Spring
integration - managed-property problem
I have this prob too, and I don't use AppFuse.
I also use Tomcat 5.5.17
I also get NPEs. (@ S
is a with org.springframework.blah….ContextLoaderListener). From: Robert Campbell [mailto:[EMAIL PROTECTED]] Sent: Friday, 14 July 2006 6:10 PM To: MyFaces Discussion Subject: Re: JSF/Spring integration - managed-property problem I'm using Spring 1.2.7 under AppFuse 1.9.1 I think I'm using a re
there is a with org.springframework.blah….ContextLoaderListener).
From:
Robert Campbell [mailto:[EMAIL PROTECTED]
Sent: Friday, 14 July 2006 6:10 PM
To: MyFaces
Discussion
Subject: Re: JSF/Spring
integration - managed-property problem
I'm using Spring 1.2.7 under AppFuse
I'm using Spring 1.2.7 under AppFuse 1.9.1I think I'm using a regular spring context.. how do I check for sure? Here is the Spring context config in web.xml:
contextConfigLocation /WEB-INF/applicationContext-*.xml
I tried to resolve it from a jsp page and it worked okay.I
What version of spring is this?
Can you resolve spring beans from anywhere
else? Say from a JSP page if you use the same EL _expression_? If you cant then
you know it’s a problem with appfuse and how it’s set up.
Also are you using a spring webapp context
or a regular spring context (e
13 matches
Mail list logo
