[JBoss JIRA] Created: (JBRULES-593) Rule names must be globally unique, even if they come from different packages
by Jeff Lansing (JIRA)
Rule names must be globally unique, even if they come from different packages
-----------------------------------------------------------------------------
Key: JBRULES-593
URL: http://jira.jboss.com/jira/browse/JBRULES-593
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 3.0.5
Environment: NA
Reporter: Jeff Lansing
Assigned To: Mark Proctor
When 2 DRL rule files with different package names (the name following the 'package' keyword) each have a rule with the same name (the name being the quoted string that follows the 'rule' keyword), then the following exception occurs:
org.drools.rule.InvalidRulePackage: Rule Compilation error The type Rule_Incident__Vehicle_0 is already defined
at org.drools.rule.Package.checkValidity(Unknown Source)
at org.drools.common.AbstractRuleBase.addPackage(Unknown Source)
at driver.RulesTest.readRule(RulesTest.java:256)
This occurs when using a single org.drools.rule.Package object, as in:
private void test(Reader source1, Reader source2) throws Exception {
PackageBuilder builder = new PackageBuilder();
builder.addPackageFromDrl( source1 );
builder.addPackageFromDrl( source2 );
Package pkg = builder.getPackage();
RuleBase ruleBase = RuleBaseFactory.newRuleBase();
ruleBase.addPackage( pkg );
}
If, on the other hand two org.drools.rule.Package objects are used, as in:
private void test2(Reader source1, Reader source2) throws Exception {
PackageBuilder builder1 = new PackageBuilder();
PackageBuilder builder2 = new PackageBuilder();
builder1.addPackageFromDrl( source1 );
builder2.addPackageFromDrl( source2 );
Package pkg1 = builder1.getPackage();
Package pkg2 = builder2.getPackage();
RuleBase ruleBase = RuleBaseFactory.newRuleBase();
ruleBase.addPackage( pkg1 );
ruleBase.addPackage( pkg2 );
}
then one of the identically named rules is simply ignored.
In either case, rule names must be globally unique.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months
[JBoss JIRA] Created: (EJBTHREE-827) creating timers inside start() creates duplicate timers.
by David Owens (JIRA)
creating timers inside start() creates duplicate timers.
--------------------------------------------------------
Key: EJBTHREE-827
URL: http://jira.jboss.com/jira/browse/EJBTHREE-827
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Environment: Windows 2000, JBoss 4.0.5 (jems installer), Java 1.5
Reporter: David Owens
Calling ctx.getTimerService().createTimer(...) within the start() method of a managed service bean creates duplicate timers. In other words, I have a bean which is both @Management and @Service which has a method which is @Timeout. In the start method of the bean (when the bean is deployed) I create a new timer. But then the method marked @Timeout is called twice. When I investigate the timers in by calling ctx.getTimerService().getTimers(), I find there are actually 2 timers with different ids, but with the exact same info.
I have attached an example. You will see the start() method getting called once when the bean is deployed, but then the timeout method getting called twice.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months
[JBoss JIRA] Created: (JBPORTAL-1312) Urgent --- Issue creating a Portlet with JSF
by Vijaya Kumar Aalati (JIRA)
Urgent --- Issue creating a Portlet with JSF
--------------------------------------------
Key: JBPORTAL-1312
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1312
Project: JBoss Portal
Issue Type: Release
Security Level: Public (Everyone can see)
Components: Portal Core, Portal Portlet
Affects Versions: 2.4.1 Final
Environment: Windows
Reporter: Vijaya Kumar Aalati
Assigned To: Julien Viet
Priority: Blocker
Hi,
I am trying to use JSF to develop a portlet and when I load the Portlet in a page I get an error which says:
javax.portlet.PortletException: Org.apache.jasper.JasperException:Exception in JSP
And this exception points to the line in the JSP where the <f:view> tag is defined. I have pasted the code in my JSP below. Could some one please tell me what is wrong with it and why I am getting the error.
I am extending the GenericPortlet to write my own Portlet class. I hope this should not be an issue, correct? In my own Portlet class that I wrote, I am setting the response.setContentType("text/html"). Would this cause any issue?
Thanks much,
Vijay
<%@ page language="java" session="true" %>
<%@ page import = "java.util.HashMap" %>
<%@ page import = "javax.swing.*" %>
<%@ page import = "javax.portlet.PortletSession" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="/WEB-INF/tld/portlet.tld" prefix="portlet" %>
<portlet:defineObjects/>
<portlet:actionURL var="loginAction">
<portlet:param name="command" value="doLogin" />
</portlet:actionURL>
<f:view>
</f:view>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months