[
https://jira.jboss.org/jira/browse/WELD-297?page=com.atlassian.jira.plugi...
]
Pete Muir closed WELD-297.
--------------------------
Fix Version/s: 1.0.1.CR1
Resolution: Rejected
Assignee: Pete Muir
We won't be doing this to Weld core. We are currently planning to split out the seam
JSF support into a seam-faces module.
Reasons:
1) JSF introduces no additional runtime dependencies on Weld core (if there are any, it is
a bug). IOW you do not need jsf-api.jar to run a CDI app using Weld
2) the JSF support takes up 9.3k of disk space, and so would not significantly reduce jar
size
3) this would increase complexity of Weld for beginners
If you have any other good arguments, please comment and I will consider them
A weld-jsf.jar should be created to cleanly and clearly separate the
part of Weld that is JSF dependant
-------------------------------------------------------------------------------------------------------
Key: WELD-297
URL:
https://jira.jboss.org/jira/browse/WELD-297
Project: Weld
Issue Type: Feature Request
Affects Versions: 1.0.0.GA
Reporter: Francisco Jose Peredo Noguez
Assignee: Pete Muir
Fix For: 1.0.1.CR1
While it would have been great to have Weld do everything Seam does, I think a very clear
line should be painted to prevent bloating.
I think Weld should get thinner, and its boundaries clearly defined, one way to do that
would be to create a weld-jsf.jar (the JSF equivalent of weld-wicket.jar) to cleanly and
clearly separate the part of Weld that is JSF dependent (and the part that is not)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira