[ https://jira.jboss.org/jira/browse/JBDS-890?page=com.atlassian.jira.plugi... ] Gary Lamperillo updated JBDS-890: --------------------------------- Attachment: CreditRunBean.java -- 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/JBDS-890?page=com.atlassian.jira.plugi... ] Tihomir Surdilovic commented on JBDS-890: ----------------------------------------- Gary, org.drools.runtime.rule.WorkingMemoryEntryPoint.class is contained in drools-api.jar which ships with Seam 2.2. I do not fully understand what you mean with "When integrating drools into Seam" because Drools is integrated into Seam already. If you are talking about adding classpath libs to your JBDS project, just make sure that you get the jars from your seam-distro/lib directory and that you do not have any other drools jars on the classpath. -- 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/JBDS-890?page=com.atlassian.jira.plugi... ] Gary Lamperillo commented on JBDS-890: -------------------------------------- adding drools-api.jar, drool-core.jar and mvel2.jar to the ear level of the project and exposing drools-core.jar and drools-api.jar in the runtime classpath solved the issues. all of these jars must come from the BRMS version used. It is very picky about serialuids for classes. I'm not closing the Jira, since this is about the combination working out of the box. -- 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/JBDS-890?page=com.atlassian.jira.plugi... ] Gary Lamperillo commented on JBDS-890: -------------------------------------- What do you suggest we do about it ? I would like the effort to get Rules to work with Seam be easier in JBDS 2.1. This would entail bringing in all the Rules Jars at the correct levels (EJB,WAR, or EAR level). The developer should not need to have to figure this out. The seam examples work with community seam and seam included in EAP and also SOA-P. Yes, when the libraries are brought in at the right level, it does work. What is BRMS in this regard ? I'm talking about the BRMS product which includes drools 5. Mostly it is about the setup of Drools 5 for the integration as discussed in the Seam Reference Manual. Something you install on top, right ? I would like either the Drools libraries in place, or a better approach is to make the libraries pluggable as in a drools project thru the project properties setting. We need something that work for EAP/SOA-P. Yes, both should work. My test cases have been only on EAP, so far. -- 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/JBDS-890?page=com.atlassian.jira.plugi... ] Gary Lamperillo commented on JBDS-890: -------------------------------------- Yes, I agree. For now, it needs to be tied to the version Seam supports, but it would be better if we can untie that link. -- 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/JBDS-890?page=com.atlassian.jira.plugi... ] Gary Lamperillo commented on JBDS-890: -------------------------------------- Adding the Drools API Jar at the EAR level does help. But, there is another issue which is more about the Seam use of rules in the Security component. It would be great if we can use a classloader scoping to allow Seam Security to use its own (don't know if that is possible). As the Drools changes (5.0, 5.01, 5.1,...), We have incompatibilities with the Seam project and Drools (or BRMS). I'm going on a bit, but my main point is that this coupling is too tight! For a Developer to add the drools api jar, he/she adds it to the ear level by copy and then adds it to the build path of the ejb and war. After that the server classpath needs to be modified to have the drools api jar. Now to upgrade the seam application to Drools 5.1, I have had some success in adding the drools api, drools core, and mvel from the Drools 5.1 libraries. After that the build path gets modified at the ejb and war levels and the server classpath gets modified. I rather see an approach using classloader scoping, but this approach may work for 5.x, as long as the drools compiler library does not change substantially. Basically, I'd like to see what JBDS does for Drools Project been done for Seam Projects, that is, the developer selects the drools runtime. -- 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/JBDS-890?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBDS-890: ------------------------------------------ I can't do anything about classloader scoping and breaking api changes in Drools minor releases causing havoc to seam. That's something you should raise against Seam and Drools runtime team. The wizard creation make sense to me to fix - i..e add the proper libraries for seam 2.2 wizards. -- 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