[
https://issues.jboss.org/browse/WFWIP-59?page=com.atlassian.jira.plugin.s...
]
Rostislav Svoboda commented on WFWIP-59:
----------------------------------------
If this is "no-go" to enable CDI, we should notify users if they are using MP
Config annotations while CDI is not enabled. This would be new issue not to mix it.
Enable CDI by default when MP Config usage is detected in the
deployment
------------------------------------------------------------------------
Key: WFWIP-59
URL:
https://issues.jboss.org/browse/WFWIP-59
Project: WildFly WIP
Issue Type: Enhancement
Components: MP Config
Reporter: Rostislav Svoboda
Assignee: Jeff Mesnil
Priority: Critical
Enable CDI by default when MP Config usage is detected in the deployment.
Currently users are forced to add empty {{beans.xml}} to the deployment every time they
want to use MP Config - e.g. in simple servlet scenario
{code}
@WebServlet("/")
public class HelloServlet extends HttpServlet {
@Inject
@ConfigProperty(name = "port_number")
Integer port;
@Override
protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws
IOException {
resp.getWriter().println("Value of port: " + port);
}
}
{code}
MP Config without CDI makes no sense to me. MP Config subsystem should be able to ensure
CDI is enabled. CCing [~manovotn] [~brian.stansberry]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)