August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3576) Unified Security Context

by Anil Saldhana (JIRA)

Unified Security Context ------------------------ Key: JBAS-3576 URL: http://jira.jboss.com/jira/browse/JBAS-3576 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta Currently the roles are an aspect of the Subject that is populated as part of the Jaas Authentication process (in the derivatives of the AbstractServerLoginModule). There is a need for the establishment of a security context to hold the roles, authoriation info etc. -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-399) add support for authentication / permissions / ownership

by Michael Neale (JIRA)

add support for authentication / permissions / ownership --------------------------------------------------------- Key: JBRULES-399 URL: http://jira.jboss.com/jira/browse/JBRULES-399 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale For ben. This authentication/permissions should be tied to the user context that JAAS established. The only things that need to be programmatic are ideally ACLs on a resource. We may need however to show/hide functionality based on the users roles. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-955) Use globally unique (i.e. prefixed by org.jboss.portal for ex.) session/invocation attribute names to avoid collisions.

by Chris Laprun (JIRA)

Use globally unique (i.e. prefixed by org.jboss.portal for ex.) session/invocation attribute names to avoid collisions. ----------------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-955 URL: http://jira.jboss.com/jira/browse/JBPORTAL-955 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.6 Final -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-471) Add support for "from" keyword

by Kris Verlaenen (JIRA)

Add support for "from" keyword ------------------------------ Key: JBRULES-471 URL: http://jira.jboss.com/jira/browse/JBRULES-471 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Kris Verlaenen Assigned To: Kris Verlaenen Content completion should be able to handle the from keyword. -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-435) Large integer values in decision tables are converted to scientific notation in DRL which cannot be parsed

by Volker Augustin (JIRA)

Large integer values in decision tables are converted to scientific notation in DRL which cannot be parsed ---------------------------------------------------------------------------------------------------------- Key: JBRULES-435 URL: http://jira.jboss.com/jira/browse/JBRULES-435 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Decision tables, Drl Parser/Builder Reporter: Volker Augustin Assigned To: Mark Proctor When a condition column in a decision table contains values like 25000000, this is compiled using the SpreadsheetCompiler into 2.5E7 in the DRL. However, the DRL parser/compiler cannot cope with this notation and exists with a unexpected token "E7" error message. -- 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, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-434) Cannot enter more than one parameter in one column on German computers

by Volker Augustin (JIRA)

Cannot enter more than one parameter in one column on German computers ---------------------------------------------------------------------- Key: JBRULES-434 URL: http://jira.jboss.com/jira/browse/JBRULES-434 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Decision tables Environment: Windows XP, standard GERMAN settings Reporter: Volker Augustin Assigned To: Mark Proctor Section 4.1.4.1 of the JBoss Rules documentation states: The "$para" place holder is used in templates to indicate where data form the cell will be interpolated. You can also use "$1" to the same effect. If the cell contains a comma seperated list of values, $1 and $2 etc. may be used to indicate which positional parameter from the list of values in the cell will be used. As the German decimal separator is ',' and not '.' as in the English locale, no list of this form can be entered on a German computer system if there are e.g. only two values and they happen to be integers. E.g. if you try to create the list containing the two values 10 and 20, according to the documentation you must enter '10,20'. This will be interpreted as 10.20 by a German computer and result in a single decimal value instead of a list of two integers. The separator ',' is hardcoded somewhere (in SnippedBuilder (?) I think). Maybe this can be made configurable. E.g. a "Configuration" section in the Excel spreadsheet would do. -- 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, 2 months

5
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-520) Messages received from Receiver.receive() using an XA are never deleted from the database if not withing a transactional boundary.

by Joel Lindheimer (JIRA)

Messages received from Receiver.receive() using an XA are never deleted from the database if not withing a transactional boundary. ---------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-520 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-520 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.0.1.CR4 Environment: Windows XP, JBossServer4.0.4GA, Oracle10G Reporter: Joel Lindheimer Assigned To: Ovidiu Feodorov Create a simple receiver, but do not place it within a Transaction boundary; shut down the server; look up the tables and you will see all the messages are still in the Messages and MessageRef tables. ========================================= Observations using a debbuger reveal the following: ========================================= Looking over the org.jboss.resource.adapter.jms.JmsManagedConnection the setup method will always call createXAQueueSession() and create an XAQueconnection as transacted and Session.SESSION_TRANSACTED. That being the case, non-XA Queues have no message-deletion problems with the current version (RC4) because the API removes all messages that are "not transacted and (!ack==1). I am guessing that using XA is problematic because the persistence layer is expecting manipulation of the transacted XASession--which for some reason is not working in this version of Messaging. More specifically, I suspect that when MDBs are tested you are not seeing this problem because the container is doing needed magic to manage the XASession transacted state, and therefore everything works fine therein. And consequently, when operating as a non-MDB client, AKA a simple Receiver, there is something missing in the equation ergo the problems that I have been reporting regarding the ClickCommerce applications which use Receivers and not MDBs. Work-around: None; the strategy for my team is to NOT use an XAQueueConnection while waiting for a fix. -- 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, 2 months

5
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-438) Allow ports used by JBossMessaging to be mapped using ServiceBindingManager

by Tim Fox (JIRA)

Allow ports used by JBossMessaging to be mapped using ServiceBindingManager --------------------------------------------------------------------------- Key: JBMESSAGING-438 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-438 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.0.1.GA -- 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, 2 months

4
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-446) Start the QA process in concert with QA team

by Ovidiu Feodorov (JIRA)

Start the QA process in concert with QA team -------------------------------------------- Key: JBMESSAGING-446 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-446 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 -- 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, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-454) InVM callbackserver

by Tim Fox (JIRA)

InVM callbackserver ------------------- Key: JBMESSAGING-454 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-454 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.0.1.CR3 Reporter: Tim Fox Fix For: 1.0.2 When running with both client and server invm and using the socket transport, a callbackserver is opened on the client and creates several sockets to listen for incoming requests. This uses up system resources (threads and sockets) which are never used for the invm case. -- 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, 2 months

4
3
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 August 2006