July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3133) Declarative types: Extending requires explicit import statement

by Michael Anstis (JIRA)

Declarative types: Extending requires explicit import statement --------------------------------------------------------------- Key: JBRULES-3133 URL: https://issues.jboss.org/browse/JBRULES-3133 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.Final Reporter: Michael Anstis Assignee: Mark Proctor Given Person class:- {code} package com.guvnor.domain; import java.math.BigDecimal; public class Person { private BigDecimal salary; public BigDecimal getSalary() { return salary; } public void setSalary(BigDecimal salary) { this.salary = salary; } } {code} The following compiles OK:- {code} package com.sample import com.guvnor.domain.Person declare Person end {code} However the following does not (without explicitly importing java.math.BigDecimal - which is a field type in Person):- {code} package com.sample import com.guvnor.domain.Person import com.guvnor.domain.Address declare Person end declare Person2 extends Person flange : String end {code} Error being "Unknown DroolsError class org.drools.compiler.TypeDeclarationError: Unable to find class 'BigDecimal' ". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1026) Refactor extended persistence context

by Carlo de Wolf (JIRA)

Refactor extended persistence context ------------------------------------- Key: EJBTHREE-1026 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1026 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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

14 years, 9 months

3
19
0 / 0

[JBoss JIRA] Created: (AS7-1234) Hibernate does not read/use metadata for orm.xml defined entites

by Tomaz Cerar (JIRA)

Hibernate does not read/use metadata for orm.xml defined entites ---------------------------------------------------------------- Key: AS7-1234 URL: https://issues.jboss.org/browse/AS7-1234 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.0.0.CR1, 7.0.0.Beta3, 7.0.0.Final, 7.0.1.Final, 7.1.0.Alpha1 Environment: windows 7, sql server 2008 r2 Reporter: Tomaz Cerar Assignee: Scott Marlow I have setup where we have "common" entities defined in global lib/module that application(war/ear) in then dependent on. Then I declare this entities in orm.xml of my application just by class name. for instance: {code:xml} <entity class="com.company.module.Article"/> <entity class="com.company.module.Binary"/> <entity class="com.company.module.Category"/> {code} Up until as7/hibernate 4 this worked with no problems, but now it dies with exception "no id defined on entity Article". If I defined id in orm.xml it then finds id field but fails to find anything that is annotated on classes. It looks like metadata is not read for this classes and hibernate sees them as just plain pojo with no annotations. I am guessing that problem has to do something with integration with AS7 that now has jandex index for all annotations... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
18
0 / 0

[JBoss JIRA] Created: (JBBOOT-136) Set up URL Stream HandlerFactory in MC Server initialization

by Andrew Rubinger (JIRA)

Set up URL Stream HandlerFactory in MC Server initialization ------------------------------------------------------------ Key: JBBOOT-136 URL: https://issues.jboss.org/browse/JBBOOT-136 Project: JBoss Bootstrap Issue Type: Task Components: impl-mc Reporter: Andrew Rubinger Assignee: Andrew Rubinger Fix For: 2.1.0-alpha-6 Attachments: URL__setURLStreamHandlerFactory_patch__.patch Setup the URL Stream Handler Factory as part of doInitialization. Patch provided by Ales. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1257) Command given in CLI help text is wrong

by Misty Stanley-Jones (JIRA)

Command given in CLI help text is wrong --------------------------------------- Key: AS7-1257 URL: https://issues.jboss.org/browse/AS7-1257 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.0.0.CR1 Reporter: Misty Stanley-Jones Assignee: Jason Greene When you are logged into the Management CLI and you type "help", one of the example commands it gives is: e.g. /subsystem=web/connector=http:read-resource(recursive=1) The syntax of the command is really this: /subsystem=web/connector=http:read-resource(recursive=true) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1885) Duplicated message delivery in closing a connection while a transaction is committing

by Yong Hao Gao (JIRA)

Duplicated message delivery in closing a connection while a transaction is committing ------------------------------------------------------------------------------------- Key: JBMESSAGING-1885 URL: https://issues.jboss.org/browse/JBMESSAGING-1885 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.8.SP1, 1.4.0.SP3.CP13 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP14, 1.4.8.SP2 A message may be delivered twice when the following events happens in order: 1. A client receives a message in a transaction and is committing it. In the meantime the connection is closed (by, for example, user shut down the client application) in another thread. 2. At the server side, the connection closing will cause the message (not prepared) to be cancelled back to queue. In the meantime the committing will remove the message. Both actions are performed concurrently. 3. If the committing happens before the connection closing, transaction commit successfully and message won't get cancelled. But if the committing happens after connection closing, there is a chance the message is cancelled back to queue and yet the transaction is committed successfully. So the message will be delivered twice. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (AS7-1236) copied lib directory in the deployments directory results in deployment

by Jim Tyrrell (JIRA)

copied lib directory in the deployments directory results in deployment ------------------------------------------------------------------------ Key: AS7-1236 URL: https://issues.jboss.org/browse/AS7-1236 Project: Application Server 7 Issue Type: Feature Request Environment: JBoss AS 7 CR 1 Reporter: Jim Tyrrell Having an existing zipped up war file, and then unzipping it in the deployment directory, creates a lib directory that has a bunch of jar files in it. It appears that these jar files in this lib directory are marked as .failed as they are tried to be deployed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
17
0 / 0

[JBoss JIRA] Created: (JBAS-7944) Move GlobalDiscoveryDisableTestCase to defaultcfg package

by Brian Stansberry (JIRA)

Move GlobalDiscoveryDisableTestCase to defaultcfg package --------------------------------------------------------- Key: JBAS-7944 URL: https://jira.jboss.org/jira/browse/JBAS-7944 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-6.0.0.M4 AFAICT this test doesn't need to be run with different JGroups stacks. -- 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

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-229) Comparison of String objects using == in FamilyClusterInfoImpl.equals(Object)

by Brian Stansberry (JIRA)

Comparison of String objects using == in FamilyClusterInfoImpl.equals(Object) ------------------------------------------------------------------------------ Key: JBCLUSTER-229 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-229 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: HA-Client 2.0.0.BETA1 return fr.familyName == this.familyName; Minor issue as this is semi-valid since the familyName field comes via ClusteringTargetsRepository, which ensures only a single String gets passed. -- 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

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-231) ClusteringTargetsRepository.families isn't final but should be

by Brian Stansberry (JIRA)

ClusteringTargetsRepository.families isn't final but should be -------------------------------------------------------------- Key: JBCLUSTER-231 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-231 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: HA-Client 2.0.0.BETA1 -- 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

14 years, 9 months

1
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 July 2011