December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1389) using eval after using or causes ClassCastException

by Jan Boboli (JIRA)

using eval after using or causes ClassCastException --------------------------------------------------- Key: JBRULES-1389 URL: http://jira.jboss.com/jira/browse/JBRULES-1389 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.3 Environment: Windows XP, Linux, Reporter: Jan Boboli Priority: Blocker when using eval after using or the ClassCastException occurs. Here is a code of the rule causing classcast : when CccObject() BbbObject($bbb:bbb) $aaa:AaaObject(aaa==$bbb) or AaaObject(aaa=="ccc") eval($aaa.getAaa().equals($bbb)) then System.out.println( "Success!!" ); end here is the stacktrace: org.drools.RuntimeDroolsException: java.lang.ClassCastException: com.sample.CccObjectShadowProxy cannot be cast to com.sample.BbbObject at org.drools.rule.EvalCondition.isAllowed(EvalCondition.java:76) ... -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1164) Move Annotation Impls in EJB3 Core org.jboss.ejb into ejb3-impl

by Andrew Lee Rubinger (JIRA)

Move Annotation Impls in EJB3 Core org.jboss.ejb into ejb3-impl --------------------------------------------------------------- Key: EJBTHREE-1164 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1164 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.CR1 Package org.jboss.ejb contains Annotation implementation classes, some of which have naming conflicts with those in the ejb3-impl package. Move these into ejb3-impl (svn cp) and resolve the conflicts as necessary. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1167) Resolve API leak for @Clustered

by Andrew Lee Rubinger (JIRA)

Resolve API leak for @Clustered ------------------------------- Key: EJBTHREE-1167 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1167 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.CR1 @Clustered (in ext-api) has references to LoadBalancePolicy from the HA module. Remove this explicit dependency, make into a String, configure as registry in EJB3 Deployer XML, and move @ClusteredImpl to ejb3-impl from EJB3 Core. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1359) mouseover CSS

by Michael Neale (JIRA)

mouseover CSS ------------- Key: JBRULES-1359 URL: http://jira.jboss.com/jira/browse/JBRULES-1359 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.3 Reporter: Michael Neale Assigned To: Fernando Meyer someone suggested it may be more "friendly" to have elements that perform actions (eg clicking on an icon, expanding a tree etc) "highlight" as the mouse hovers over (so its obvious it does something). JIRA does not do this, but this would be nice to have. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-626) Add Pagination to SortableTable (the iterators support skipping already)

by Michael Neale (JIRA)

Add Pagination to SortableTable (the iterators support skipping already) ------------------------------------------------------------------------ Key: JBRULES-626 URL: http://jira.jboss.com/jira/browse/JBRULES-626 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1326) Archive and restore archive to work with packages as well as assets

by Michael Neale (JIRA)

Archive and restore archive to work with packages as well as assets ------------------------------------------------------------------- Key: JBRULES-1326 URL: http://jira.jboss.com/jira/browse/JBRULES-1326 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.3 Reporter: Michael Neale Assigned To: Fernando Meyer Need this to work with packages as well (doesn't seem to, wich is not surprising was only initially intended for assets). -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4951) Retry debug message within UnifiedInvokerHAProxy.invoke() is misleading

by Galder Zamarreno (JIRA)

Retry debug message within UnifiedInvokerHAProxy.invoke() is misleading ----------------------------------------------------------------------- Key: JBAS-4951 URL: http://jira.jboss.com/jira/browse/JBAS-4951 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta2 Reporter: Galder Zamarreno Assigned To: Brian Stansberry Priority: Minor UnifiedInvokerHAProxy.invoke(): ... failoverAuthorized = txContextAllowsFailover(invocation); failoverCounter++; invocation.setValue("FAILOVER_COUNTER", new Integer(failoverCounter), PayloadKey.AS_IS); log.debug("Received GenericClusteringException where request was not completed. Will retry."); continue; ... The debug message before continue is misleading. The call will only be retried if the failover is authorised and there're any targets available, otherwise it won't. The log message should be reworded. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-5043) Don't find the good persistence unit when multiple ear with same pu name

by Jerome Poittevin (JIRA)

Don't find the good persistence unit when multiple ear with same pu name ------------------------------------------------------------------------ Key: JBAS-5043 URL: http://jira.jboss.com/jira/browse/JBAS-5043 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA Environment: JBoss 4.2.2 on linux Red Hat 4 AS 4 or Windows XP, using Sun JVM version 5 Reporter: Jerome Poittevin Assigned To: Carlo de Wolf When using multiple ear with multiple persistence unit having the same name, Jboss uses the wrong persistence unit when deploying ejb and the exception "Entity is not mapped" occures when entities are accessed. This behaviour seams to be in contradiction with the Java Persistence API Spec (see § 6.2.2). Example : app1.ear and app2.ear with two persistence unit having the same persistence unit name "pu". While deploying app2.ear, the following message can be seen in the JBoss log : 2007-11-30 15:13:03,865 DEBUG [org.jboss.injection.PersistenceUnitHandler] ***** adding PU dependency from located persistence unit: persistence.units:ear=app1.ear,unitName=pu When accessing EJB deployed in app2.ear, the following exception occures : javax.ejb.EJBTransactionRolledbackException: org.hibernate.hql.ast.QuerySyntaxException: TestEntity is not mapped [From TestEntity t where t.id = :id] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166) at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:240) at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:210) at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:84) The following patch seems to make JBoss find the good persistence unit : In file org.jboss.ejb3.enc.DeploymentPersistenceUnitResolver.java on line 106 : replace : if (deployment.getEntityManagerName().equals(unitName)) return deployment; with : if (deployment.getEntityManagerName().equals(unitName) && deployment.getKernelName().contains(deploymentScope.getBaseName())) return deployment; -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1250) Allow option to completely remove an asset from the repository

by Shahad Ahmed (JIRA)

Allow option to completely remove an asset from the repository -------------------------------------------------------------- Key: JBRULES-1250 URL: http://jira.jboss.com/jira/browse/JBRULES-1250 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.1 Reporter: Shahad Ahmed Assigned To: Mark Proctor If you use the archive feature to remove a rule or package from the BRMS it is not really seen as gone, as if you attempt to create a new rule or package with the same name as the archived rules or package then you get an error saying that the rule or package already exists (looking at the source code, the repository does not care if an item is archived or not, so it will always throw an error if an asset with an existing name is created). I'm assuming this is the designed behaviour and not a bug (I've asked about this a couple of times on the user list and got no replies to the contrary). However, it would be very useful to be able to remove a rule or package so that you can then recreate it (e.g by importing new versions from a drl file). At present, you have to laboriously rename the rules and packages you want to remove, so that when they are archived their names do not clash with the new versions of the rules and packages you want to import or recreate. Perhaps all that is involved in implementing this new remove feature is to just automatically rename the package and its rules before archiving it? -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1192) Hiding old versions of documents

by Nils Kassube (JIRA)

Hiding old versions of documents --------------------------------- Key: JBPORTAL-1192 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1192 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4.1 Final Reporter: Nils Kassube Assigned To: Roy Russo To improve usability it's a good idea to hide old versions of a document, e.g. using paging or a "More versions..." link. Currently you have to export and import stuff to get rid of the distracting display of dozens of old versions. -- 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, 3 months

6
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007