[ https://issues.jboss.org/browse/FORGE-372?page=com.atlassian.jira.plugin.... ] Paul Dijou commented on FORGE-372: ---------------------------------- Hi, In fact, I've test several solutions in the last few days and find some solutions. The main question is : do you want Forge plugins to use the EntityManager provided by Forge (in its package) or the "default" EntityManager of the application (define by the user) ? The first one is probably safer since you know exactly how the EntityManager is parametrized, but the second one seems more logic since it's the user's application, so if he wants an extended Seam EntityManager, good for him, the plugins should use it too (hoping all will be good). In the first case, easy to do : add a qualifier on the producer of the Forge EntityManager, add it also on the @Inject point, and you're done. In the second case, I have several propositions : 1) Delete the DatasourceProducer class in your package and generate it when the user initialize the project : in this configuration, the user can override it or delete it without any problem. A new command in the console like "restore datasourceProducer" would delete and re-create DatasourceProducer class with the default configuration provide by Forge. 2) Keep the DatasourceProducer class in your package but add an @Alternative annotation in the producer and put it in the beans.xml alternative list. So the day the user want to use it's own EntityManager, he just has to edit the beans.xml and remove the correct line. 3) There is also a solution by adding an @Veto annotation at runtime with Seam Solder but since, perhaps, the project does not require Solder, it's not good enough. In any case, you have to generate something in the user project in order to let him change it when he needs to. Hope my french-english will not kill your eyes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-372?page=com.atlassian.jira.plugin.... ] Daniel Sachse commented on FORGE-372: ------------------------------------- Hey Lincoln, no problem at all! Was a bit busy by myself. Yeah of course, I will work on it soon! Thanks pal, Daniel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-372?page=com.atlassian.jira.plugin.... ] Daniel Sachse edited comment on FORGE-372 at 12/10/11 11:45 AM: ---------------------------------------------------------------- Hi, I think the second case with the second propositions sounds most reasonable to me. I would go with this solution. Is everybody in with me so I can go and realize it? Cheers, Daniel was (Author: sachsedaniel): Hi, I think the second case with the second propositions sounds most reasonable to me. I would go with this solution. Is everybody in with me so I can go and realize it? cheers, Daniel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-372?page=com.atlassian.jira.plugin.... ] Work on FORGE-372 stopped by Daniel Sachse. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-372?page=com.atlassian.jira.plugin.... ] Daniel Sachse commented on FORGE-372: ------------------------------------- Realized Solution: Now adding @Alternative to the Producer and the producing class and the class is listed in the beans.xml as an Alternative. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-372?page=com.atlassian.jira.plugin.... ] Daniel Sachse updated FORGE-372: -------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/forge/plugin-seam-persistence/pull/2 (was: https://github.com/forge/plugin-seam-persistence/pull/1) I now fixed it they way we discussed it. I had to slightly change the api and the implementation a little bit more, thats why i raised the other following pullrequest: https://github.com/forge/core/pull/86 Hope everything is fine as expected! Thanks, Daniel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/FORGE-372?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-372: ------------------------------------------ Hey Daniel, This is great work! It looks like the original intent of this JIRA is out of date with Richard's new scaffold. But updating the persistence plugin will help lots of folks! ~Lincoln -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira