December 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7531) Make org.jboss.ejb3:ejb3_1 component the integration component with AS instead of org.jboss.ejb3:as-int

by jaikiran pai (JIRA)

Make org.jboss.ejb3:ejb3_1 component the integration component with AS instead of org.jboss.ejb3:as-int ------------------------------------------------------------------------------------------------------- Key: JBAS-7531 URL: https://jira.jboss.org/jira/browse/JBAS-7531 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: JBossAS-6.0.0.M2 Currently the AS uses org.jboss.ejb3:as-int as the EJB3 component which brings in the necessary EJB3 sub-components. Going forward as-int will be retired and instead org.jboss.ejb3:ejb3_1 will be the one which will have to used to bring in EJB3 components. Please refer to the referenced forum thread for details. -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2369) Subtle interaction between modify and no-loop causes dormant activations counter to get out of synch

by Edson Tirelli (JIRA)

Subtle interaction between modify and no-loop causes dormant activations counter to get out of synch ---------------------------------------------------------------------------------------------------- Key: JBRULES-2369 URL: https://jira.jboss.org/jira/browse/JBRULES-2369 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.0.M1, 5.0.1.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.0.2, 5.1.0.M2 A modify call in a no-loop rule's consequence causes the dormant activations counter to get out of synch. Customer portal ticket: 373895 -- 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

15 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-6961) simpleweb tests involving file-based cache loader fail if directories and/or files exist

by Richard Achmatowicz (JIRA)

simpleweb tests involving file-based cache loader fail if directories and/or files exist ----------------------------------------------------------------------------------------- Key: JBAS-6961 URL: https://jira.jboss.org/jira/browse/JBAS-6961 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.1.0.CR1 Environment: HPUX, risc architcture Reporter: Richard Achmatowicz Assignee: Brian Stansberry Priority: Minor The tests in org.jboss.test.cluster.defaultcfg.simpleweb.test which use a file-based cache loader fail if a directory and/or file is left over from a previous failed execution: Error Message init org.jboss.cache.config.Configuration@2f23dca failed Stacktrace org.jboss.cache.pojo.PojoCacheException: init org.jboss.cache.config.Configuration@2f23dca failed at org.jboss.cache.pojo.impl.PojoCacheImpl.<init>(PojoCacheImpl.java:75) at org.jboss.cache.pojo.PojoCacheFactory.createCache(PojoCacheFactory.java:54) at org.jboss.test.cluster.testutil.SessionTestUtil.createCache(SessionTestUtil.java:137) at org.jboss.test.cluster.testutil.CacheConfigTestSetup.setUp(CacheConfigTestSetup.java:84) at junit.extensions.TestSetup$1.protect(TestSetup.java:20) at junit.extensions.TestSetup.run(TestSetup.java:25) Caused by: org.jboss.cache.CacheException: java.lang.reflect.InvocationTargetException at org.jboss.cache.util.reflect.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:148) at org.jboss.cache.factories.ComponentRegistry$PrioritizedMethod.invoke(ComponentRegistry.java:1012) at org.jboss.cache.factories.ComponentRegistry.internalStart(ComponentRegistry.java:778) at org.jboss.cache.factories.ComponentRegistry.start(ComponentRegistry.java:632) at org.jboss.cache.invocation.CacheInvocationDelegate.start(CacheInvocationDelegate.java:345) at org.jboss.cache.DefaultCacheFactory.createCache(DefaultCacheFactory.java:121) at org.jboss.cache.pojo.impl.PojoCacheImpl.<init>(PojoCacheImpl.java:71) Caused by: java.lang.reflect.InvocationTargetException at org.jboss.cache.util.reflect.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:144) Caused by: org.jboss.cache.CacheException: Unable to start cache loaders at org.jboss.cache.loader.CacheLoaderManager.startCacheLoader(CacheLoaderManager.java:467) Caused by: java.io.IOException: Unable to create cache loader location /var/tmp/BuddyReplicationFailoverUnitTestCase/1242786803043 at org.jboss.cache.loader.FileCacheLoader.create(FileCacheLoader.java:171) at org.jboss.cache.loader.CacheLoaderManager.startCacheLoader(CacheLoaderManager.java:459) The file /var/tmp/BuddyReplicationFailoverUnitTestCase/1242786803043 cannot be created in order to initialise the cache. I have found that deleting the directory /var/tmp/BuddyReplicationFailoverUnitTestCase and rerunning the tests fixes the problem. I tried to recreate the problem by writing a small program which mimics the same file creation process, used, but even if I left files in place, I couldn't recreate the problem. The tests pass OK otherwise. -- 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

15 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2454) CMS identity queries with case sensitive DB fails

by Magesh Kumar B (JIRA)

CMS identity queries with case sensitive DB fails ------------------------------------------------- Key: JBPORTAL-2454 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2454 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.7.2 Final Environment: MS SQL Server 2005 Reporter: Magesh Kumar B Assignee: Sohil Shah Create a new user and login with the new user's id. We get the following exception ERROR [org.hibernate.util.JDBCExceptionReporter] Invalid column name 'id'. ERROR [org.jboss.portal.cms.security.AuthorizationProviderImpl] org.jboss.portal.cms.security.AuthorizationProviderImpl@3c205c org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:2223) at org.hibernate.loader.Loader.listUsingQueryCache(Loader.java:2136) at org.hibernate.loader.Loader.list(Loader.java:2096) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:289) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1695) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:142) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:152) at org.jboss.portal.cms.security.AuthorizationProviderImpl.findPermissionsByUser(AuthorizationProviderImpl.java:480) at org.jboss.portal.cms.security.AuthorizationProviderImpl.getSecurityBindings(AuthorizationProviderImpl.java:221) at org.jboss.portal.cms.impl.jcr.command.ACLEnforcer.getPermissions(ACLEnforcer.java:572) This is due to the fact that hibernate mappings instructs the DB to create the table jbp_cms_perm with column name 'ID', but AuthorizationProviderImpl.findPermissionsByUser has a hard coded SQL query with lower case. -- 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

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBREFLECT-74) Cleanup ClassPool tests

by Flavia Rainone (JIRA)

Cleanup ClassPool tests ----------------------- Key: JBREFLECT-74 URL: https://jira.jboss.org/jira/browse/JBREFLECT-74 Project: JBoss Reflection Issue Type: Task Components: Class Pool Affects Versions: JBossReflection.2.0.2.GA Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: JBossReflection.2.2.0-Alpha Currently the class pool tests contain duplicate code and big class files. This task includes: - moving CL and CP creation to other classes/ redesign this - replace cleanup code on finally blocks by automatic cleanup - remove duplicate test scenarios (follow example of ArchiveTest and subclasses) - remove file names that are currently lost in the middle of code (see ArchiveTest for example) - move archives to their own directory instead of target -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2370) Support <scoreDsl> besides <scoreDrl> for XmlSolverConfigurer in LocalSearchSolverConfig to allow to use DSL's instead of DRL's for score rules

by Geoffrey De Smet (JIRA)

Support <scoreDsl> besides <scoreDrl> for XmlSolverConfigurer in LocalSearchSolverConfig to allow to use DSL's instead of DRL's for score rules ----------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2370 URL: https://jira.jboss.org/jira/browse/JBRULES-2370 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-solver Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet It seems a bit wierd to me add both the drl and the dsl in the <scoreDsl>, so I think we need to do it like this: <scoreDsl> <dslr>/org/.../file1.dslr</dslr> <dsl>/org/.../file2.dsl</dsl> </scoreDsl> >From the manual: "Also, it is better to rename the extension of your rules file from ".drl" to ".dslr" when you start using DSLs, as that will allow the IDE to correctly recognize and work with your rules file." -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2367) Unexpected token - rules with similar names

by Andraz Skoric (JIRA)

Unexpected token - rules with similar names ------------------------------------------- Key: JBRULES-2367 URL: https://jira.jboss.org/jira/browse/JBRULES-2367 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Reporter: Andraz Skoric Assignee: Mark Proctor Priority: Minor Attachments: Drools407Issues.zip See attached file. Rules in Rules1.dsl/drl don't parse. Rules have same names, they just end with diff extension. -- 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

15 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREFLECT-83) UCLClassPoolTest is failing

by Flavia Rainone (JIRA)

UCLClassPoolTest is failing --------------------------- Key: JBREFLECT-83 URL: https://jira.jboss.org/jira/browse/JBREFLECT-83 Project: JBoss Reflection Issue Type: Bug Components: Class Pool Affects Versions: JBossReflection.2.0.2.GA Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: JBossReflection.2.2.0.GA Some of the SanityTestCases that have been ported to run against a ClassPool are failing: testUclWithParentClassLoaderAndSameClassInDomain testUclLoaderOrdering All tests failing are commented out and marked with a FIXME. -- 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

15 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMETA-230) Mandate JDK 6 in jboss-metadata-ejb project through Maven configuration

by jaikiran pai (JIRA)

Mandate JDK 6 in jboss-metadata-ejb project through Maven configuration ----------------------------------------------------------------------- Key: JBMETA-230 URL: https://jira.jboss.org/jira/browse/JBMETA-230 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Components: EJB Affects Versions: jboss-metadata-ejb-2.0.0-alpha-2 Reporter: jaikiran pai Assignee: jaikiran pai Configure the pom.xml appropriately to mandate JDK 1.6 -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7528) Setting HDScanner's scanEnabled Attribute to True via XML Results In NPE

by Jimmy Wilson (JIRA)

Setting HDScanner's scanEnabled Attribute to True via XML Results In NPE ------------------------------------------------------------------------ Key: JBAS-7528 URL: https://jira.jboss.org/jira/browse/JBAS-7528 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-6.0.0.M1, JBossAS-5.1.0.GA, JBossAS-5.0.1.GA, JBossAS-5.0.0.GA Reporter: Jimmy Wilson Assignee: Jimmy Wilson Fix For: JBossAS-6.0.0.M2 Setting HDScanner's scanEnabled attribute to true via XML caused an NPE because the setter logic relied on the fact that the class's create method had already been called. -- 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

15 years, 10 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2009