Skip to content

Problem integrating JSF with Spring [SPR-2525] #7214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
spring-projects-issues opened this issue Sep 1, 2006 · 3 comments
Closed

Problem integrating JSF with Spring [SPR-2525] #7214

spring-projects-issues opened this issue Sep 1, 2006 · 3 comments
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: declined A suggestion or change that we don't feel we should currently apply type: task A general task

Comments

@spring-projects-issues
Copy link
Collaborator

bansi opened SPR-2525 and commented

Hi All
I am having similar problem integrating JSF using Spring

As suggested by Rob and Mark , the managed property has a setter method initialized
I am using JSF 1.1_01, spring 1.2 , Tomcat 5.0 and MyEclipse 5.0 IDE

Wondering whether its the problem with spring 1.2 . Do i need to have Spring 2.0 or is it something else

Any pointers/suggestions at [email protected] will be highly appreciated

Regards
Bansi


Affects: 1.2.3

Attachments:

@spring-projects-issues
Copy link
Collaborator Author

bansi commented

Eclosing the files web.xml, faces-config.xml, application-context.xml

@spring-projects-issues
Copy link
Collaborator Author

Rick Evans commented

Hi Bansi

The Spring team are aware of this unassigned issue, and will be addressing it as soon as time permits.

You might want to try posting your issue on the forum as someone in the Spring user community may be able to pinpoint the issue.

http://forum.springframework.org/forumdisplay.php?f=25

Cjeers
Rick

@spring-projects-issues
Copy link
Collaborator Author

Rossen Stoyanchev commented

This issue has been resolved through a selective bulk update, as part of a larger effort to better manage unresolved issues. To qualify for the update, the issue was either created before Spring 3.0 or affects a version older than Spring 3.0 and is not a bug.

There is a good chance the request was made obsolete, or at least partly outdated, by changes in later versions of Spring including deprecations. It is also possible it didn't get enough traction or we didn't have enough time to address it. One way or another, we didn't get to it.

If you believe the issue, or some aspects of it, are still relevant and worth pursuing at present you may re-open this issue or create a new one with a more up-to-date description.

We thank you for your contributions and encourage you to become familiar with the current process of managing Spring Framework JIRA issues that has been in use for over a year.

@spring-projects-issues spring-projects-issues added status: declined A suggestion or change that we don't feel we should currently apply in: core Issues in core modules (aop, beans, core, context, expression) type: task A general task labels Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: declined A suggestion or change that we don't feel we should currently apply type: task A general task
Projects
None yet
Development

No branches or pull requests

1 participant