April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4371) Upgrade to jbossxb 1.0.0.GA

by Dimitris Andreadis (JIRA)

Upgrade to jbossxb 1.0.0.GA --------------------------- Key: JBAS-4371 URL: http://jira.jboss.com/jira/browse/JBAS-4371 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: XML services Affects Versions: JBossAS-4.2.0.CR2 Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.GA jbossxb 1.0.0.CR10 has been promoted to GA status. -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-40) EJBPolicyModuleDelegate warning should be a debug msg

by Scott M Stark (JIRA)

EJBPolicyModuleDelegate warning should be a debug msg ----------------------------------------------------- Key: SECURITY-40 URL: http://jira.jboss.com/jira/browse/SECURITY-40 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Reporter: Scott M Stark Assigned To: Anil Saldhana Running the WebIntegrationUnitTestCase.testUnsecureRunAsServletWithPrincipalNameAndRoles case produces spurious warning msgs for the roles added at the deployment level: 17:12:20,947 WARN [EJBPolicyModuleDelegate] no match found for security role InternalUser in the deployment descriptor for ejb UnsecureRunAsServletWithPrincipalNameAndRolesTarget 17:12:20,947 WARN [EJBPolicyModuleDelegate] no match found for security role ExtraRole1 in the deployment descriptor for ejb UnsecureRunAsServletWithPrincipalNameAndRolesTarget 17:12:20,947 WARN [EJBPolicyModuleDelegate] no match found for security role ExtraRole2 in the deployment descriptor for ejb UnsecureRunAsServletWithPrincipalNameAndRolesTarget 17:12:20,978 WARN [EJBPolicyModuleDelegate] no match found for security role InternalUser in the deployment descriptor for ejb UnsecureRunAsServletWithPrincipalNameAndRolesTarget 17:12:20,979 WARN [EJBPolicyModuleDelegate] no match found for security role ExtraRole1 in the deployment descriptor for ejb UnsecureRunAsServletWithPrincipalNameAndRolesTarget 17:12:20,979 WARN [EJBPolicyModuleDelegate] no match found for security role ExtraRole2 in the deployment descriptor for ejb UnsecureRunAsServletWithPrincipalNameAndRolesTarget This should be no more than debug level msgs. -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-926) Negative message count

by Kurt Stam (JIRA)

Negative message count ---------------------- Key: JBMESSAGING-926 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-926 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.GA Environment: any Reporter: Kurt Stam Assigned To: Ovidiu Feodorov Fix For: 1.2.0.SP1 When I removeAllMessages from the Queue while the thing is working on the queue, I can get a negative message count (see screenshot) I thought this was a funny bug :). -- 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

19 years, 3 months

4
13
0 / 0

[JBoss JIRA] Created: (JBAS-4367) Extend the ActiveAlarmTable with a a plugin mechanism for persisting the Alarms.

by Dimitris Andreadis (JIRA)

Extend the ActiveAlarmTable with a a plugin mechanism for persisting the Alarms. -------------------------------------------------------------------------------- Key: JBAS-4367 URL: http://jira.jboss.com/jira/browse/JBAS-4367 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management services Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis We need a plugin mechanism and a hibernate plugin for that. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4368) Create a simple xml driven mbean for mapping custom notifications to alarms for the ActiveAlarmTable

by Dimitris Andreadis (JIRA)

Create a simple xml driven mbean for mapping custom notifications to alarms for the ActiveAlarmTable ---------------------------------------------------------------------------------------------------- Key: JBAS-4368 URL: http://jira.jboss.com/jira/browse/JBAS-4368 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management services Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis We need to think about what would be the available mappings. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-410) java:/JmsXA in no-tx context does not work the same way as JBossMQ

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-410?page=comments#action_12... ] Clebert Suconic commented on JBMESSAGING-410: --------------------------------------------- I'm adding this comment just to send a notification, that this is being reopened as http://jira.jboss.com/jira/browse/JBMESSAGING-946. > java:/JmsXA in no-tx context does not work the same way as JBossMQ > ------------------------------------------------------------------ > > Key: JBMESSAGING-410 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-410 > Project: JBoss Messaging > Issue Type: Bug > Components: Configuration and Management > Affects Versions: 1.0.1.CR2, 1.2.0.Beta2, 1.0.1.SP4 > Reporter: Elias Ross > Assigned To: Tim Fox > Priority: Critical > Fix For: Unscheduled > > > The same code I wrote that uses java:/JmsXA in a non-transacted environment with JBossMQ does not work with JBoss Messaging. And actually the same code does work correctly with SonicMQ as well, using the JCA adaptor with the Sonic XA connection factory. > Why allow the use java:/JmsXA without transactions? It makes sense to use a cached connection manager anyway, like you would with a database. And anyway, should be addressed for compatibility. > The following code *should* successfully send a message to a queue running without a transaction. Currently, it doesn't seem to do anything and no usage warnings are produced. > QueueConnectionFactory queueCF = (QueueConnectionFactory)new InitialContext.lookup("java:/JmsXA"); > ... > QueueConnection queueConnection = queueCF.createQueueConnection(); > QueueSession queueSession = > queueConnection.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE); > QueueSender queueSender = queueSession.createSender(queue); > ObjectMessage om = queueSession.createObjectMessage(); > queueSender.send(om); > queueSender.close(); > queueSession.close(); > queueConnection.close(); -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-671) Rule modeller costmetic improments

by Michael Neale (JIRA)

Rule modeller costmetic improments ---------------------------------- Key: JBRULES-671 URL: http://jira.jboss.com/jira/browse/JBRULES-671 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

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAOP-393) Tutorial Examples need changing to use JDK 5 only or JBoss Retro when using JDK 1.4

by Kabir Khan (JIRA)

Tutorial Examples need changing to use JDK 5 only or JBoss Retro when using JDK 1.4 ----------------------------------------------------------------------------------- Key: JBAOP-393 URL: http://jira.jboss.com/jira/browse/JBAOP-393 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha5 This especially refers to the examples requiring annotations, and really boils down to whether we want to support JDK 1.4 or not -- 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

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAOP-313) Better error messages in AspectXmlLoader

by Kabir Khan (JIRA)

Better error messages in AspectXmlLoader ---------------------------------------- Key: JBAOP-313 URL: http://jira.jboss.com/jira/browse/JBAOP-313 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha2 Reporter: Kabir Khan Fix For: 2.0.0.alpha3 -- 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

19 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4366) javax.enterprise.deploy.spi.TargetModuleID.getChildTargetModuleID() should return null when there are no children

by Dimitris Andreadis (JIRA)

javax.enterprise.deploy.spi.TargetModuleID.getChildTargetModuleID() should return null when there are no children ----------------------------------------------------------------------------------------------------------------- Key: JBAS-4366 URL: http://jira.jboss.com/jira/browse/JBAS-4366 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.2.0.CR2 Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.GA In our jsr88 implementation of javax.enterprise.deploy.spi.TargetModuleID, (i.e. org.jboss.deployment.spi.TargetModuleIDImpl.) the getChildTargetModuleID() method currently returns an empty array when there are no children, instead of null as the specification requires. -- 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

19 years, 3 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 April 2007