February 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2470) user name containing underscore breaks the UsersActivityStatsService

by Gary Hu (JIRA)

user name containing underscore breaks the UsersActivityStatsService -------------------------------------------------------------------- Key: JBPORTAL-2470 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2470 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Hu If a user name contains underscore, for example "john_dow", it breaks the UsersActivityStatsService MBean sevice. This is the code from UsersActivityStatsServiceImpl: public void registerActivity(final UserActivity userActivity) { try { Notification notification = new Notification(Integer.toString(userActivity.getType()), this.getServiceName(), userActivity.getTimestamp(), userActivity.getTimestamp(), userActivity.getId() + "_" + userActivity.getSessionId()); .... And here is the code from UserActivity: public UserActivity(Notification notification) { if (notification.getMessage() == null) { throw new IllegalArgumentException("Id (notification message) cannot be null"); } this.id = notification.getMessage().substring(0, notification.getMessage().indexOf("_")); this.sessionId = notification.getMessage().substring(notification.getMessage().indexOf("_")); this.timestamp = notification.getTimeStamp(); this.type = Integer.parseInt(notification.getType()); } -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7691) Reduce the jbm-data JGroups MPING.timeout config

by Brian Stansberry (JIRA)

Reduce the jbm-data JGroups MPING.timeout config ------------------------------------------------ Key: JBAS-7691 URL: https://jira.jboss.org/jira/browse/JBAS-7691 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-6.0.0.M2 It's 5000 instead of the 2000 used for discovery timeouts everywhere else. This will cut 'all' config startup time by 3 seconds. -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1989) Create nointerface "component"

by jaikiran pai (JIRA)

Create nointerface "component" ------------------------------ Key: EJBTHREE-1989 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1989 Project: EJB 3.0 Issue Type: Task Components: nointerface Reporter: jaikiran pai Assignee: jaikiran pai As discussed, maintain nointerface as a component along these lines http://community.jboss.org/message/520306 -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1972) Move Ejb3MetadataProcessingDeployer and related MC configs from core/ejb3-deployers-jboss-beans.xml to appropriate component

by jaikiran pai (JIRA)

Move Ejb3MetadataProcessingDeployer and related MC configs from core/ejb3-deployers-jboss-beans.xml to appropriate component ---------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-1972 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1972 Project: EJB 3.0 Issue Type: Task Components: core, deployers Affects Versions: 1.1.22 Reporter: jaikiran pai Assignee: jaikiran pai As discussed in the referenced forum thread, the Ejb3MetadataProcessingDeployer and the EjbMetadataJndiPolicyDecoratorDeployer don't really belong in the core/ejb3-deployers-jboss-beans.xml. They should instead be maintained in their own *-jboss-beans.xml in the deployers component. -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1971) Create a jboss-ejb3_1 component

by jaikiran pai (JIRA)

Create a jboss-ejb3_1 component ------------------------------- Key: EJBTHREE-1971 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1971 Project: EJB 3.0 Issue Type: Task Reporter: jaikiran pai Assignee: jaikiran pai Create a jboss-ejb3_1 component (similar to the jboss-ejb3 component) -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1965) Track release of plugin 1.0.19

by jaikiran pai (JIRA)

Track release of plugin 1.0.19 ------------------------------ Key: EJBTHREE-1965 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1965 Project: EJB 3.0 Issue Type: Task Reporter: jaikiran pai Assignee: jaikiran pai JIRA to track the release of plugin 1.0.19 -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1953) Create a "package" for the jboss-ejb3-nointerface component

by jaikiran pai (JIRA)

Create a "package" for the jboss-ejb3-nointerface component ----------------------------------------------------------- Key: EJBTHREE-1953 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1953 Project: EJB 3.0 Issue Type: Task Affects Versions: EJB 3.1 Reporter: jaikiran pai Assignee: jaikiran pai Now that the package manager is usable to install/remove/upgrade* packages, create a package for the jboss-ejb3-nointerface component to allow it to be installed using the package manager. Although, this is being currently done only for ejb3-nointerface component, it should (and will) be made common for other components too so that packages can be created for those components too. * Upgrade feature works although at this point it is in a very basic state - needs some logic around the version(s) being upgraded. -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1787) Refactor the source of jndi-name(s) for no-interface view bindings

by jaikiran pai (JIRA)

Refactor the source of jndi-name(s) for no-interface view bindings ------------------------------------------------------------------ Key: EJBTHREE-1787 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1787 Project: EJB 3.0 Issue Type: Task Affects Versions: 1.1.2 Reporter: jaikiran pai Assignee: jaikiran pai Right now, the no-interface view component hardcodes the jndi-names for various binding: 1) The no-interface view jndi name is hardcoded to SBMD.getEjbName() + "/no-interface"; 2) The jndi name for the no-interface stateful view factory is hardcoded to SBMD.getEjbName() + "no-interface-stateful-proxyfactory"; These names should ideally come from the metadata or some other common component which is available across components so that the jndi-names remain accessible and common to every component. -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2002) Nointerface view binding to a jndi name with non-existent subcontext can lead to NameNotFoundException

by jaikiran pai (JIRA)

Nointerface view binding to a jndi name with non-existent subcontext can lead to NameNotFoundException ------------------------------------------------------------------------------------------------------ Key: EJBTHREE-2002 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2002 Project: EJB 3.0 Issue Type: Bug Components: nointerface Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.3 A stateful bean with a no-interface view deployed through an .ear runs into a NameNotFoundException while trying to bind to something like the following: A/b/no-interface The reason is the StatefulNoInterfaceViewJNDIBinder while binding, does not create any relevant sub-contexts. The fix is to use org.jboss.naming.Util.bind() API to bind to JNDI. This API internally creates any relevant sub-contexts. -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1168) jsr94, create stateful rule session, allow to set keepReference

by Juergen none (JIRA)

jsr94, create stateful rule session, allow to set keepReference --------------------------------------------------------------- Key: JBRULES-1168 URL: http://jira.jboss.com/jira/browse/JBRULES-1168 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JSR94 Affects Versions: 4.0.1 Reporter: Juergen none Assigned To: Mark Proctor Priority: Minor org.drools.jsr94.rules.StatefulRuleSessionImpl currently calls initSession() with constant value true for keepReference. Would be nice if this could be configurable via properties map. -- 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

16 years, 5 months

3
5
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 February 2010