July 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1790) Provide support for resolving @EJB/ejb-local-ref references to no-interface view

by jaikiran pai (JIRA)

Provide support for resolving @EJB/ejb-local-ref references to no-interface view -------------------------------------------------------------------------------- Key: EJBTHREE-1790 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1790 Project: EJB 3.0 Issue Type: Task Affects Versions: EJB 3.1 Reporter: jaikiran pai Assignee: jaikiran pai The EJB3.1 spec allows no-interface view reference, using a @EJB and through ejb-local-ref. We need to have a resolver (similar to FirstMatchEjbReferenceResolver) which does this. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-859) Message: add LOOPBACK flag

by Bela Ban (JIRA)

Message: add LOOPBACK flag -------------------------- Key: JGRP-859 URL: https://jira.jboss.org/jira/browse/JGRP-859 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 When LOOPBACK is set in a message, the UNICAST.loopback and TP.loopback flags are overridden and a message is looped back up the stack, regardless of the value of the property. This is useful for example for VIEW and SUSPECT messages, where a socket could be disconnected (e.g. cable plugged) and we still need to be able to receive our own messages. -- 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, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JGRP-996) AUTH: handle multiple physical addresses in FixedMembershipToken

by Bela Ban (JIRA)

AUTH: handle multiple physical addresses in FixedMembershipToken ---------------------------------------------------------------- Key: JGRP-996 URL: https://jira.jboss.org/jira/browse/JGRP-996 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 -- 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, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-5599) Eliminate build time configuration directories and replace with tool for generating configuration through the profile service API

by Andrig Miller (JIRA)

Eliminate build time configuration directories and replace with tool for generating configuration through the profile service API --------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-5599 URL: http://jira.jboss.com/jira/browse/JBAS-5599 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System, Getting Started Guide, Installation Guide, Installer, Management services, ProfileService, Server Configuration Guide, Test Suite Reporter: Andrig Miller Assigned To: Paul Gier Fix For: No Release With the addition of the profile service, it seems silly to generate various configurations, like "all", "default" and "minimal" through the build. Instead we should have a tool that generates the configuration through the profile service, with the understanding of the dependencies of the various features. The tool could still have the concepts of "all", "default" and "minimal" embedded in it to make the transition easier, but most times to do the testing that we need to do we customize the configuration. We also add an additional configuration in productizing the EAP, and this would simplify that process as well. This tool would have to be usable at the command-line, in JBoss Tools, and from the installer. -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-897) Anycasting: better use of logical addresses

by Bela Ban (JIRA)

Anycasting: better use of logical addresses ------------------------------------------- Key: JGRP-897 URL: https://jira.jboss.org/jira/browse/JGRP-897 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 See whether logical addresses allow us to handle anycasting more efficiently, ie. handle them at the transport level, and not by sending multiple unicasts -- 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, 11 months

1
9
0 / 0

[JBoss JIRA] Created: (JBAS-6987) Disable registering of MC bean components as MBeans by default

by jaikiran pai (JIRA)

Disable registering of MC bean components as MBeans by default -------------------------------------------------------------- Key: JBAS-6987 URL: https://jira.jboss.org/jira/browse/JBAS-6987 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-5.1.0.GA Reporter: jaikiran pai Assignee: jaikiran pai Fix For: JBossAS-6.0.0.Alpha1 Every MC bean that gets deployed, also gets registered as a MBean. These MBeans are optional and only provide debug information. These can by default be disabled. Refer to the referenced forum thread for details. -- 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, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JASSIST-48) Create a common interface to MethodCall & NewExpr

by Guy Korland (JIRA)

Create a common interface to MethodCall & NewExpr ------------------------------------------------- Key: JASSIST-48 URL: http://jira.jboss.com/jira/browse/JASSIST-48 Project: Javassist Issue Type: Feature Request Reporter: Guy Korland Assigned To: Shigeru Chiba MethodCall & NewExpr both have common methods that are not part of the javassist.expr.Expr interface. public String getClassName() public String getSignature() suggested API: abstract public class Invoke extends Expr{ abstract public String getClassName(); abstract public String getSignature(); } public class MethodCall extends Invoke public class NewExpr extends Invoke -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1861) Ruleflow diagram not proprly displayed

by Jaroslaw Kijanowski (JIRA)

Ruleflow diagram not proprly displayed -------------------------------------- Key: JBRULES-1861 URL: https://jira.jboss.org/jira/browse/JBRULES-1861 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.0.0.M3 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Attachments: expected.png, rf.png -- 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, 11 months

3
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-913) java.lang.IllegalStateException in SessionContext::getCallerPrincipal()

by Mihail Druzinin (JIRA)

java.lang.IllegalStateException in SessionContext::getCallerPrincipal() ----------------------------------------------------------------------- Key: EJBTHREE-913 URL: http://jira.jboss.com/jira/browse/EJBTHREE-913 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: EJB 3.0 RC9 - FD Environment: AS: jboss-4.0.5 (ejb3 Version EJB 3.0 RC7 - FD and EJB3 RC9 Patch 1) OS: Windows, GentooLinux Reporter: Mihail Druzinin >From HttpServlet I execute methods from stateless been. All methods executed correctly with authorization. When in method I try sessionContext.getCallerPrincipal(), then throws java.lang.IllegalStateException: No valid security context for the caller identity After see in jboss security module I find that in org.jboss.security.SecurityAssociation getCallerPrincipal() when used RunAsIdentity, it getted not from top of RunAsIdentity stack, but "for the active run-as the previous caller has assumed": Principal thePrincipal = peekRunAsIdentity(1); (SecurityAssociation.java:216). After fixed that string to: Principal thePrincipal = peekRunAsIdentity(0), all start 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

15 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1518) implement Singleton Session Beans

by Alexey Loubyansky (JIRA)

implement Singleton Session Beans --------------------------------- Key: EJBTHREE-1518 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1518 Project: EJB 3.0 Issue Type: Task Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Section 4.8 "Singleton Session Beans" of the EJB3.1 spec draft. -- 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, 11 months

3
2
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 July 2009