September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-2101) Remove reference to jboss-ejb3-metadata-deployers from bom-eap5.

by Carlo de Wolf (JIRA)

Remove reference to jboss-ejb3-metadata-deployers from bom-eap5. ---------------------------------------------------------------- Key: EJBTHREE-2101 URL: https://jira.jboss.org/browse/EJBTHREE-2101 Project: EJB 3.0 Issue Type: Task Components: bom Affects Versions: bom-eap5-0.1.2 Reporter: Carlo de Wolf Fix For: bom-eap5-0.1.3 jboss-ejb3-metadata-deployers is an AS 6 artifact and not used in EAP 5. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2052) Use an L1 Cache for SFSB context stored in a DIST mode Infinispan

by Brian Stansberry (JIRA)

Use an L1 Cache for SFSB context stored in a DIST mode Infinispan ----------------------------------------------------------------- Key: EJBTHREE-2052 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2052 Project: EJB 3.0 Issue Type: Sub-task Components: cache, Clustering Reporter: Brian Stansberry With Infinispan DIST, an SFSB context may not be stored in Infinispan on the local node. (Even if it's originally stored locally, it may move due to a rehash following a topology change). Keep an L1 cache on the node that's servicing the session to improve read performance. The session ownership system discussed in EJBTHREE-2051 can be used to detect failover and the need to invalidate the session out of L1. The locking system should return whether the call required obtaining the lock from a remote node; if yes that implies failover and an invalid L1. -- 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

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2049) Create an Infinispan-backed SFSB cache

by Brian Stansberry (JIRA)

Create an Infinispan-backed SFSB cache -------------------------------------- Key: EJBTHREE-2049 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2049 Project: EJB 3.0 Issue Type: Task Components: cache, Clustering Reporter: Brian Stansberry Assignee: Paul Ferraro Infinispan is replacing JBC in the AS; need a Cache impl that integrates with Infinispan. -- 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

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2050) Ensure ids for newly created SFSB contexts will hash locally in Infinispan

by Brian Stansberry (JIRA)

Ensure ids for newly created SFSB contexts will hash locally in Infinispan -------------------------------------------------------------------------- Key: EJBTHREE-2050 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2050 Project: EJB 3.0 Issue Type: Sub-task Components: cache, Clustering Reporter: Brian Stansberry Assignee: Paul Ferraro If Infinispan DIST is used, at least one of the cache locations for an SFSB should be the node that created it. This way in the normal case where there are 2 copies, a single unicast to the backup node is sufficient to replicate. If the cache key (the SFSBContext id) hashes to 2 remote nodes, then every cache write will require 2 unicasts. The problem here is unlike web sessions, the id for an SFSB context is not generated by the caching layer; it's generated by StatefulBeanContext itself. So the web session strategy of having a background thread occasionally populate a pool of ids that are known to map locally (using the consistent hash algorithm Mircea Marcus is going to expose for ISPN-232) won't work. -- 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

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-6338) Review webservices chapters

by Scott M Stark (JIRA)

Review webservices chapters --------------------------- Key: JBAS-6338 URL: https://jira.jboss.org/jira/browse/JBAS-6338 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: JBossAS-5.0.0.GA Reporter: Scott M Stark Assignee: Alessio Soldano We need to review the admin guide web services chapters: https://svn.jboss.org/repos/jbossas/projects/docs/community/5/Administrat... -- 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

15 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (SECURITY-355) JBoss Negotiation - User Guide Enhancements

by Darran Lofthouse (JIRA)

JBoss Negotiation - User Guide Enhancements ------------------------------------------- Key: SECURITY-355 URL: https://jira.jboss.org/jira/browse/SECURITY-355 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.GA Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA Add additional clarification to the critical points within the user guide. -- 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

15 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (SECURITY-433) Calls to getCallerPrincipal() return session ID

by Darran Lofthouse (JIRA)

Calls to getCallerPrincipal() return session ID ----------------------------------------------- Key: SECURITY-433 URL: https://jira.jboss.org/jira/browse/SECURITY-433 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.SP1 Reporter: Darran Lofthouse Assignee: Anil Saldhana Fix For: Negotiation_2.0.3.SP2 After SPNEGO based authentication the caller principal is the session ID - it should be possible to switch this to the name of the authenticated user. Also add an option to either return the full principal name or remove the realm. -- 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

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-8031) Update JBossTS to 4.11

by Jonathan Halliday (JIRA)

Update JBossTS to 4.11 ---------------------- Key: JBAS-8031 URL: https://jira.jboss.org/browse/JBAS-8031 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Manager (Arjuna) Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 6.0.0.M4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2697) Description not in documentation

by Tomáš Schlosser (JIRA)

Description not in documentation -------------------------------- Key: JBRULES-2697 URL: https://jira.jboss.org/browse/JBRULES-2697 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.1.1.FINAL Environment: jboss-eap-5.1 brms-guvnor 5.1.0 35066 Reporter: Tomáš Schlosser Assignee: Mark Proctor Although description is set in rules it doesn't appear in documentation generated by Guvnor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBJCA-426) Track component updates

by Jesper Pedersen (JIRA)

Track component updates ----------------------- Key: JBJCA-426 URL: https://jira.jboss.org/browse/JBJCA-426 Project: IronJacamar Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 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 September 2010