January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5182) Retire EJB3 JaccHelper

by Anil Saldhana (JIRA)

Retire EJB3 JaccHelper ---------------------- Key: JBAS-5182 URL: http://jira.jboss.com/jira/browse/JBAS-5182 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3, Security Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Anil Saldhana Assigned To: Anil Saldhana Priority: Critical Fix For: JBossAS-5.0.0.CR1 The entire EJB3 Jacc Layer needs to go. The Permissions creation will be done via a separate deployer working on the Metadata. The Policy enforcement will be done by the security layer. We have already consolidated the enforcement for web and ejb2 layers. -- 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

15 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-3828) spelling mistake in xml tag

by Goran Oberg (JIRA)

spelling mistake in xml tag --------------------------- Key: JBAS-3828 URL: http://jira.jboss.com/jira/browse/JBAS-3828 Project: JBoss Application Server Issue Type: Bug Affects Versions: JBossAS-4.0.4.GA Environment: All Reporter: Goran Oberg Priority: Trivial Just a spelling mistake... Should be <url-delimiter> instead of <url-delimeter> in <ha-local-tx-datasource> -- 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

15 years, 10 months

5
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-953) wiki not visible

by Sacha Labourey (JIRA)

wiki not visible ---------------- Key: JBPORTAL-953 URL: http://jira.jboss.com/jira/browse/JBPORTAL-953 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Reporter: Sacha Labourey deploying wiki.war from portletswap in JBP deploy's folder doesn't make it visible in the list of creatable portlet (admin interface) -- 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

15 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JGRP-640) Shared protocols

by Bela Ban (JIRA)

Shared protocols ---------------- Key: JGRP-640 URL: http://jira.jboss.com/jira/browse/JGRP-640 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.x Like the shared transport, investigate whether we can share other protocols. E.g. FD, FD_SOCK (preventing duplicate server sockets and sockets), Discovery and so on. -- 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

15 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-983) Messages can be delivered after connection is stopped

by Tim Fox (JIRA)

Messages can be delivered after connection is stopped ----------------------------------------------------- Key: JBMESSAGING-983 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-983 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR1 Stopping a connection does not currently block until all current onMessage invocations are complete, as per JMS spec. We need to make sure it does. -- 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

15 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-806) JBM is assuming it can look up system properties on the client side

by Tim Fox (JIRA)

JBM is assuming it can look up system properties on the client side ------------------------------------------------------------------- Key: JBMESSAGING-806 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-806 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.SP3, 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta2, 1.0.1.SP4 JBM (JMSRemotingConnection) does several System.getProperties() to get the override bind address and port. However in a security restricted environment e.g. jnlp or applet this may not work. This causes an exception to be thrown and the connection is not created. Need to catch the exception and set to null. -- 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

15 years, 10 months

5
15
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1197) support HTTP transport

by Jeff Mesnil (JIRA)

support HTTP transport ---------------------- Key: JBMESSAGING-1197 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1197 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Remoting Reporter: Jeff Mesnil Assigned To: Jeff Mesnil Fix For: 2.0.0 Alpha the new remoting code based on MINA currently supports only TCP transport. It must also support HTTP transport. MINA provides an HTTP package we can use for both the JMS clients (send requests/receive responses) and the JMS servers (receive request/send response). Message delivery must also be taken into account. The client can use polling (and remains a simple HTTP client). However since MINA code is used on both the client and ther server, we need to check if we can send HTTP requests to the client on the same TCP connection (the ideabeing that we MUST NOT open a server connection on the client in any way) -- 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

15 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1846) Create Style Guide for renaissance theme and for global styles

by Wesley Hales (JIRA)

Create Style Guide for renaissance theme and for global styles -------------------------------------------------------------- Key: JBPORTAL-1846 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1846 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Wesley Hales Fix For: 2.6.4 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4722) Injection of ISecurityManagement via Annotation

by Anil Saldhana (JIRA)

Injection of ISecurityManagement via Annotation ----------------------------------------------- Key: JBAS-4722 URL: http://jira.jboss.com/jira/browse/JBAS-4722 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Anil Saldhana Assigned To: William DeCoste Fix For: JBossAS-5.0.0.Beta3 Currently an instance of JNDIBasedSecurityManagement (interface is ISecurityManagement) is being used in the EJB3AuthenticationInterceptorv2. We need to get this injected (rather than hard coded) via an annotation. -- 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

15 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-4904) Improve error message when binding fails

by Andrew Rubinger (JIRA)

Improve error message when binding fails ---------------------------------------- Key: JBAS-4904 URL: http://jira.jboss.com/jira/browse/JBAS-4904 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-4.2.2.GA Reporter: Andrew Rubinger Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA Upon attempt to bind an a subcontext to an address already bound by an object, the following exception occurs: java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context at org.jboss.util.naming.Util.createSubcontext(Util.java:69) at org.jboss.util.naming.Util.rebind(Util.java:125) at org.jboss.util.naming.Util.rebind(Util.java:113) Error message should be in form "Can't bind subContext/obj, because subContext is already bound" -- 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

15 years, 10 months

3
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008