[JBoss JIRA] Created: (JBRULES-794) ArrayIndexOutOfBoundException if duplicate declarations in rule
by Juergen none (JIRA)
ArrayIndexOutOfBoundException if duplicate declarations in rule
---------------------------------------------------------------
Key: JBRULES-794
URL: http://jira.jboss.com/jira/browse/JBRULES-794
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.0.6
Reporter: Juergen none
Assigned To: Mark Proctor
Priority: Minor
rule "yields-out-of-bound-exception"
when
a : A(
b : b
)
C(b == b,
n : n // FIRST DECLARATION
)
n : D(self == n) //SECOND DECLARATION
hen ...
valid rule file, rule is parsed, but yields exception
corrected (remove second declaration):
...
C(b == b,
n : n // FIRST DECLARATION
)
D(self == n)
then ...
valid rule file, rule is parsed, no exception
Exception stacktrace fragment:
java.lang.ArrayIndexOutOfBoundsException: 2
at org.drools.reteoo.FactHandleList.get(FactHandleList.java:114)
at org.drools.reteoo.TupleKey.get(TupleKey.java:98)
at org.drools.reteoo.ReteTuple.get(ReteTuple.java:160)
at org.drools.reteoo.ReteTuple.get(ReteTuple.java:167)
at org.drools.rule.BoundVariableConstraint.isAllowed(BoundVariableConstraint.java:79)
at org.drools.common.BetaNodeBinder.isAllowed(BetaNodeBinder.java:63)
at org.drools.reteoo.TupleSource.attemptJoin(TupleSource.java:99)
at org.drools.reteoo.JoinNode.assertObject(JoinNode.java:166)
at org.drools.reteoo.ObjectSource.propagateAssertObject(ObjectSource.java:119)
at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:158)
at org.drools.reteoo.Rete.assertObject(Rete.java:120)
at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:180)
at org.drools.reteoo.ReteooWorkingMemory.doAssertObject(ReteooWorkingMemory.java:68)
at org.drools.common.AbstractWorkingMemory.assertObject(AbstractWorkingMemory.java:537)
at org.drools.base.DefaultKnowledgeHelper.assertLogicalObject(DefaultKnowledgeHelper.java:70)
at org.drools.base.DefaultKnowledgeHelper.assertLogicalObject(DefaultKnowledgeHelper.java:64)
at Rule_assert_Child_from_TreeNodeIF_0.consequence(Rule_assert_Child_from_TreeNodeIF_0.java:65)
--
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
17 years, 6 months
[JBoss JIRA] Updated: (JBRULES-257) Audit logger to optionally use java.util.logging
by Mark Proctor (JIRA)
[ http://jira.jboss.com/jira/browse/JBRULES-257?page=all ]
Mark Proctor updated JBRULES-257:
---------------------------------
Component/s: Reteoo
Fix Version/s: FUTURE
(was: 4.0.0.MR4)
Affects Version/s: (was: 3.0-rc2)
> Audit logger to optionally use java.util.logging
> ------------------------------------------------
>
> Key: JBRULES-257
> URL: http://jira.jboss.com/jira/browse/JBRULES-257
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Reteoo
> Reporter: Michael Neale
> Assigned To: Kris Verlaenen
> Priority: Optional
> Fix For: FUTURE
>
>
> As we are java 1.4 and up, we can use java.util.logging package to look audit messages.
> This means people can use the normal way to configure any sort of logging they dream of, including viewers, bridges to other logging systems, files, database and so on.
> I think logging in JDK is the best choice, even though log4j is better, it would be best not to add any dependencies to core other then JRE itself.
--
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
17 years, 6 months
[JBoss JIRA] Created: (JBPORTAL-1369) problem with mission-critical and render set to divRenderNoAjax
by Prabhat Jha (JIRA)
problem with mission-critical and render set to divRenderNoAjax
---------------------------------------------------------------
Key: JBPORTAL-1369
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1369
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Theme
Affects Versions: 2.6.CR2
Reporter: Prabhat Jha
Assigned To: Julien Viet
1. Login as admin
2. Click on Theme for default portal
3. Change theme to mission-critical and render set to divRenderNoAjax
4. Logout
It takes you to http://localhost:8080/portal/portal/default and you can not see/do a thing. :-( Did I do something stupid or there is something wrong?
The error I see is
2007-04-30 10:56:35,187 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/portal-core].[jsp]] Servlet.service() for servlet jsp threw exception
java.lang.NullPointerException
at org.jboss.portal.theme.impl.render.dynamic.DynaMergeBehavior.mergeForWindow(DynaMergeBehavior.java:51)
at org.jboss.portal.theme.impl.render.dynamic.DynaWindowRenderer.render(DynaWindowRenderer.java:70)
at org.jboss.portal.theme.render.RendererContext.render(RendererContext.java:225)
at org.jboss.portal.theme.impl.JSPRendererContext.render(JSPRendererContext.java:66)
at org.jboss.portal.theme.impl.render.div.DivRegionRenderer.renderBody(DivRegionRenderer.java:69)
at org.jboss.portal.theme.render.RendererContext.render(RendererContext.java:234)
at org.jboss.portal.theme.impl.JSPRendererContext.render(JSPRendererContext.java:66)
[ Show » ]
Prabhat Jha [30/Apr/07 12:13 PM] The error I see is 2007-04-30 10:56:35,187 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/portal-core].[jsp]] Servlet.service() for servlet jsp threw exception java.lang.NullPointerException at org.jboss.portal.theme.impl.render.dynamic.DynaMergeBehavior.mergeForWindow(DynaMergeBehavior.java:51) at org.jboss.portal.theme.impl.render.dynamic.DynaWindowRenderer.render(DynaWindowRenderer.java:70) at org.jboss.portal.theme.render.RendererContext.render(RendererContext.java:225) at org.jboss.portal.theme.impl.JSPRendererContext.render(JSPRendererContext.java:66) at org.jboss.portal.theme.impl.render.div.DivRegionRenderer.renderBody(DivRegionRenderer.java:69) at org.jboss.portal.theme.render.RendererContext.render(RendererContext.java:234) at org.jboss.portal.theme.impl.JSPRendererContext.render(JSPRendererContext.java:66)
--
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
17 years, 6 months
[JBoss JIRA] Resolved: (JBPORTAL-859) Support portlet which use GET method in forms.
by Julien Viet (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-859?page=all ]
Julien Viet resolved JBPORTAL-859.
----------------------------------
Resolution: Rejected
was commented as non feasible, but not resolved
> Support portlet which use GET method in forms.
> ----------------------------------------------
>
> Key: JBPORTAL-859
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-859
> Project: JBoss Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Portal WSRP
> Affects Versions: 2.4 Final
> Reporter: Chris Laprun
> Assigned To: Chris Laprun
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> We probably need to add an element similar to remotable to the jboss portlet descriptors...
> From WSRP spec (10.2.4 Method=get in HTML forms):
> User-Agents often throw away any query string from the URL indicated with the form's action attribute when generating the URL they will activate when the form's method is "get". This is the simplest means for them to generate a valid query string. The difficulty this causes is that Consumer's often prefer to store the information they will use when a portlet URL is activated as query string parameters. As a result, Portlets that include HTML forms with method=get in their markup MUST specify usesMethodGet as "true" in their PortletDescription. Consumers choosing to use such Portlets need to format their portlet URLs such that portlet URL activations are processed correctly, regardless of whether Consumer or Producer URL writing is in use.
--
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
17 years, 6 months