[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-890) JBDS 2.1 GA, Seam 2.2, and Drools Integration

Gary Lamperillo (JIRA) jira-events at lists.jboss.org
Wed Nov 25 11:09:38 EST 2009


    [ https://jira.jboss.org/jira/browse/JBDS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12496664#action_12496664 ] 

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.

> JBDS 2.1 GA, Seam 2.2, and Drools Integration
> ---------------------------------------------
>
>                 Key: JBDS-890
>                 URL: https://jira.jboss.org/jira/browse/JBDS-890
>             Project: JBoss Developer Studio
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>         Environment: EAP 5 , Seam 2.2, Drools 5, BRMS
>            Reporter: Gary Lamperillo
>            Assignee: Snjezana Peco
>            Priority: Critical
>             Fix For: 3.0.0.CR1
>
>         Attachments: components.xml, CreditRunBean.java
>
>
> When integrating drools into Seam there are 2 compliation errors:
> >Description	Resource	Path	Location	Type
> The project was not built since its build path is incomplete. Cannot find the class file for org.drools.runtime.rule.WorkingMemoryEntryPoint. Fix the build path then try building this project	SeamwithRules-ejb		Unknown	Java Problem
> >Description	Resource	Path	Location	Type
> The type org.drools.runtime.rule.WorkingMemoryEntryPoint cannot be resolved. It is indirectly referenced from required .class files	CreditRunBean.java	SeamwithRules-ejb/ejbModule/org/domain/seamwithrules/session	line 33	Java Problem
> I will attach the components.xml and the source file.
> It appears that the WorkingMemoryEntryPoint can not be found.  I tried bringing in enternal drools jars, but it did not help

-- 
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

        


More information about the jbosstools-issues mailing list