[ https://jira.jboss.org/jira/browse/JBSEAM-4278?page=com.atlassian.jira.pl... ] Sanne Grinovero updated JBSEAM-4278: ------------------------------------ Description: Having a component annotated with @Scope(ScopeType.APPLICATION) and @Startup having a @Create method to do something at application startup is called correctly but there is no transaction around the method. (i.e. changes done trough an EntityManager are never applied) The transaction is created and committed if the component is a Stateful EJB, but in this case @In injection is not working. This breaks for example the Blog example's test as it rebuilds the initial Lucene index using this method. was: Having a component annotated with @Scope(ScopeType.APPLICATION) and @Startup having a @Create method to do something at application startup is called correctly but the transaction is never committed. The transaction is committed if the component is a Stateful EJB, but in this case @In injection is not working. This breaks for example the Blog example's test as it rebuilds the initial Lucene index using this method. I understood at first that the transaction was created but then not committed, I was wrong: the transaction is not created at all. I've updated the issue description. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4278?page=com.atlassian.jira.pl... ] Norman Richards closed JBSEAM-4278. ----------------------------------- Resolution: Rejected There's no expectation that a TX would exist in that context. In the example app, we need to add @Transactional to the method to cause the TX to be started. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4278?page=com.atlassian.jira.pl... ] Norman Richards commented on JBSEAM-4278: ----------------------------------------- This is a javabean component, not an EJB. TX management must be explicitly requested if needed. Seam happens to normally provide a TX for all HTTP requests, so it really only becomes critical to declare when you are not using seam-manged transactions or are working (as in this case) outside the scope of where you might happen to be in a TX already. App startup is such a case. This would be different for an EJB, where the expectation is that all invocations at any time would have a TX around it by default. -- 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