March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7855) parameter element missing value in profile.xml

by thamizhelango natarajan (JIRA)

parameter element missing value in profile.xml ----------------------------------------------- Key: JBAS-7855 URL: https://jira.jboss.org/jira/browse/JBAS-7855 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: thamizhelango natarajan -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7835) "ignore-dependency" injection from jboss.xml not work in bean with superclass'es

by Krashan Brahmanjara (JIRA)

"ignore-dependency" injection from jboss.xml not work in bean with superclass'es -------------------------------------------------------------------------------- Key: JBAS-7835 URL: https://jira.jboss.org/jira/browse/JBAS-7835 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.1.0.GA Environment: jboss-5.1.0.GA with jdk1.6.0_17 Reporter: Krashan Brahmanjara Priority: Minor I got bean based on superclass with shared logic and some circular dependencies Unfortunately "ignore-dependency" injection from jboss.xml seems to work only if attributes are declared in current class not in superclass'es - I can't use annotations because ear is praparet for weblogic too. Error example : org.jboss.deployers.spi.DeploymentException: Error deploying test.jar: Unable to create annotation for method/field defBean for EJB AlgBean Deployment "vfszip:test.ear/" is in error due to the following reason(s): java.lang.NoSuchFieldException: defBean for case : <?xml version="1.0" encoding="UTF-8" ?> <jboss xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" version="3.0"> <enterprise-beans> <session> <ejb-name>AlgBean</ejb-name> <ignore-dependency> <injection-target> <injection-target-class>test.DefLocal</injection-target-class> <injection-target-name>defBean</injection-target-name> </injection-target> </ignore-dependency> </session> </enterprise-beans> </jboss> @Stateless(name = "AlgBean", mappedName = "ejb.DefAlg") public class AlgBean extends AlgBeanImpl implements DefAlgLocal,DefAlgRemote { } public class AlgBeanImpl implements DefAlg { @EJB protected DefLocal defBean; } There are no problems is DefLocal defBean is moved from superclass to AlgBean. -- 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

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2456) Field completion in guided rule editor doesn't show camel-case 'multi-words' java beans properties

by Guillaume HOLLER (JIRA)

Field completion in guided rule editor doesn't show camel-case 'multi-words' java beans properties -------------------------------------------------------------------------------------------------- Key: JBRULES-2456 URL: https://jira.jboss.org/jira/browse/JBRULES-2456 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: FUTURE Environment: windows Reporter: Guillaume HOLLER Assignee: Mark Proctor I have attached an example model class and the modified BRMSSuggestionCompletionLoaderTest class (with the new testLoaderWithComplexFields method) to demonstrate the issue. The test shows that the SuggestionCompletionLoader exposes all javabean properties as ModelFields but then fails to expose them in specific categories according to accessor/mutator classification. In the test, only the fields for which the assertion: assert fieldName.equals(fieldName.toLowerCase()) is verified are exposed by methods engine.getModelFields(FieldAccessorsAndMutators.[ACCESSOR|MUTATOR], "Agent"): nom, prenom and sexe (and the keyword 'this' of course). Consequence is for example that in guided editor, only this fields are proposed as restriction fields in the WHEN side of the RULE . I have found tha the problem lies in method loadClassFields of SuggestionCompletionLoader and propose a patch (attached). -- 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

16 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAOP-779) FieldTestCase fails

by Flavia Rainone (JIRA)

FieldTestCase fails ------------------- Key: JBAOP-779 URL: https://jira.jboss.org/jira/browse/JBAOP-779 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.2.0.GA FieldTestCase is failing on compatibility tests -- 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

16 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-1213) If the server fails to create a SaslServer, it never sends an error back to the client

by David Lloyd (JIRA)

If the server fails to create a SaslServer, it never sends an error back to the client -------------------------------------------------------------------------------------- Key: JBREM-1213 URL: https://jira.jboss.org/jira/browse/JBREM-1213 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: r3 core: remote Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta3 -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7734) Upgrade jboss naming

by Brian Stansberry (JIRA)

Upgrade jboss naming -------------------- Key: JBAS-7734 URL: https://jira.jboss.org/jira/browse/JBAS-7734 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Naming Reporter: Brian Stansberry Assignee: Scott M Stark Fix For: JBossAS-6.0.0.M3 Upgrade either to a 5.0.5.GA or a 5.1.0 release; which depends on whether trunk is ready for 5.1.x -- 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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7582) Add dependecies on HttpRMIClassLoading

by Brian Stansberry (JIRA)

Add dependecies on HttpRMIClassLoading -------------------------------------- Key: JBAS-7582 URL: https://jira.jboss.org/jira/browse/JBAS-7582 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M2 The tests-jbossmessaging-cluster testsuite target doesn't stop one of the two AS instances it starts. One of the tests stops the server and the ant target assumes that will happen so it doesn't do it. This is fragile since problems with the test can prevent the server being stopped. That server remaining alive then screws up the rest of the testsuite run. This is a frequent cause of hudson testsuite failures. Adding a call to the server:stop task doesn't seem to cause a problem even if the server isn't running, so I'm adding one. -- 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

16 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBMETA-274) Remove FIELD replication-granularity configuration

by Brian Stansberry (JIRA)

Remove FIELD replication-granularity configuration -------------------------------------------------- Key: JBMETA-274 URL: https://jira.jboss.org/jira/browse/JBMETA-274 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Components: web Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: jboss-metadata-common-2.0.0-alpha-15 AS 6 will not support FIELD as PojoCache does not work with Infinispan and no Infiinspan based equivalent exists yet. So: Add comments to the 4.0, 4.2 and 5.0 jboss-web dtds and to the 5.0 schema noting that it's removed in AS 6. Remove it altogether as a replication-granularity option in the 6.0 schema, plus remove the replication-field-batch-mode element. -- 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

16 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7811) Multithreaded access to remote JDBC datasource is broken

by Justin Bertram (JIRA)

Multithreaded access to remote JDBC datasource is broken -------------------------------------------------------- Key: JBAS-7811 URL: https://jira.jboss.org/jira/browse/JBAS-7811 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-6.0.0.M2 Reporter: Justin Bertram Assignee: Justin Bertram Fix For: JBossAS-6.0.0.M3 Heavy access to a remote JDBC datasource (i.e. one configured with <use-java-context>false</use-java-context>) with multiple threads sometimes results in errors. The root of this problem is how the proxied datasource objects (e.g. ResultSet, Connection, Statement, etc.) are stored in the server-side HashMap for re-use by the remote client. These objects are, not surprisingly, keyed by their respective hash code (i.e. object.hashCode()). There are cases where different objects return the same hashCode which means a remote client can close someone else's ResultSets, etc. One can easily see this by turning on DEBUG logging and executing your test. For example: DEBUG [org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService] Created ResultSet proxy for invoker=jboss:service=invoker,type=jrmp, targetName=jboss.jca:service=DataSourceBinding,name=PostgresDS, cacheID=12215563 DEBUG [org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService] Created ResultSet proxy for invoker=jboss:service=invoker,type=jrmp, targetName=jboss.jca:service=DataSourceBinding,name=PostgresDS, cacheID=12215563 ... DEBUG [org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService] Closed ResultSet=12215563 Of course, the *other* client using the ResultSet whose cacheID is "12215563" will break when it tries to access it later. To solve this problem, something other than hashCode should be used to key the HashMap entries. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBLOGGING-41) LogManager is missing a privileged block

by Anil Saldhana (JIRA)

LogManager is missing a privileged block ---------------------------------------- Key: JBLOGGING-41 URL: https://jira.jboss.org/jira/browse/JBLOGGING-41 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-logging-logmanager Reporter: Anil Saldhana Assignee: David Lloyd Forum thread. -- 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

16 years, 4 months

2
1
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 March 2010