[JBoss JIRA] Created: (EJBTHREE-807) Bean meta data does not include security role references
by Anil Saldhana (JIRA)
Bean meta data does not include security role references
--------------------------------------------------------
Key: EJBTHREE-807
URL: http://jira.jboss.com/jira/browse/EJBTHREE-807
Project: EJB 3.0
Issue Type: Task
Components: Security
Affects Versions: EJB 3.0 RC9 - Patch 1
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: EJB 3.0 RC10 - FD
====================================
<session>
<ejb-name>SecTestEJB</ejb-name>
<business-local>xxx</business-local>
<ejb-class>xxx</ejb-cla
ss>
<security-role-ref>
<role-name>ADMIN</role-name>
<role-link>Administrator</role-link>
</security-role-ref>
<security-role-ref>
<role-name>MGR</role-name>
<role-link>Manager</role-link>
</security-role-ref>
</session>
==================================================
There can be security role references configured at the bean level in ejb-jar.xml
The metadata that is parsed by the ejb3 metamodel does not recognize the security role references.
The isCallerInRole checks on the EnterpriseContext needs to be aware of these security role references.
--
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
17 years, 9 months
[JBoss JIRA] Commented: (JBTM-18) Use inhouse DTF for QA
by Richard Achmatowicz (JIRA)
[ http://jira.jboss.com/jira/browse/JBTM-18?page=comments#action_12348832 ]
Richard Achmatowicz commented on JBTM-18:
-----------------------------------------
I have movd the DTF to the QA Labs machines.
A database called dtf has been set up on a MySQL server on dev02.qa.atl.jboss.com.
I have installed a copy of Tomcat in my home directory on the labs machines, with the following node pool:
dev04: runs the DTF executive (NameServer, Coordinator, ServiceManager, ProductRepository, ResultsCollator) and one TestNode
dev02: runs one TestNode
The DTFweb user interface starts up correctly using the URL http://dev04:8080/dtf.
Initiation of test nodes, product deployment, work fine under the control of the DTFweb user interface.
However test cases which work on my local machine fail to work correctly when run on the QA Labs machines. There seems to be
a problem with (i) receiving output from tasks and (ii) the results of the tests.
I am investigating these problems.
> Use inhouse DTF for QA
> ----------------------
>
> Key: JBTM-18
> URL: http://jira.jboss.com/jira/browse/JBTM-18
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JTA Implementation, JTS Implementation, WS-T Implementation
> Reporter: Mark Little
> Assigned To: Richard Achmatowicz
>
> Get the QA up and running for refactored ATS. Require refactoring DTF too.
--
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
17 years, 9 months
[JBoss JIRA] Created: (JGRP-374) Flow control should send new credits only *after* processing a message
by Bela Ban (JIRA)
Flow control should send new credits only *after* processing a message
----------------------------------------------------------------------
Key: JGRP-374
URL: http://jira.jboss.com/jira/browse/JGRP-374
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.5
Currently, FC sends new credits (when the sender's credits drop below a threshold) *before* passing the message up. However, if the receiver takes a long time to process the message, we might queue up messages, possibly leading to OOMs.
SOLUTION: in FC.up(), decrement the sender's credits by number of bytes received, but only send replenishment (if needed) *after* the message was passed up. This requires that passUp() includes delivery of the message to the receiver and we can be sure that, once passUp() returns, the message has been delivered. If we use a queue in Channel (e.g. using the pull model, Channel.receive()), this won't work.
--
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
17 years, 9 months
[JBoss JIRA] Updated: (JBFORUMS-83) Write User and Administration Guide
by Ryszard Kozmik (JIRA)
[ http://jira.jboss.com/jira/browse/JBFORUMS-83?page=all ]
Ryszard Kozmik updated JBFORUMS-83:
-----------------------------------
Fix Version/s: 1.0.0 RC
(was: 1.0.0 Beta)
I'll work more on guides just after beta release as there will be no more coding tasks, only eventual bug fixes if users or I will find something wrong in Forums.
> Write User and Administration Guide
> -----------------------------------
>
> Key: JBFORUMS-83
> URL: http://jira.jboss.com/jira/browse/JBFORUMS-83
> Project: JBoss Forums
> Issue Type: Task
> Components: Documentation, Portlet Productization
> Affects Versions: 1.0.0 Alpha
> Reporter: Damon Sicore
> Assigned To: Ryszard Kozmik
> Fix For: 1.0.0 RC
>
> Time Spent: 2 hours
>
> Create and write a JBoss Forums User and Admin Guide.
> I suspect we only need to combine the Admin and User guide into one due to the size of this project (i.e., it's small).
> Specifically:
> * JBoss Forums Deployment Packaging.
> * Deployment Steps
> * User Administration
> * Forum and Topic Administration
> * Security and Spam
> * Forum and Topic User Instructions
--
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
17 years, 9 months