February 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1714) Give each EJB3 project its own package namespace

by Andrew Lee Rubinger (JIRA)

Give each EJB3 project its own package namespace ------------------------------------------------ Key: EJBTHREE-1714 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1714 Project: EJB 3.0 Issue Type: Task Components: cache, common, core, deployers, embedded, ext-api, ext-api-impl, injection, installer, interceptors, locator, mc-int, metadata, plugin, pool, proxy, proxy-clustered, socket-inflow, test, testsuite, transactions Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger For unified assemblies to be possible (and as a matter of good practice), each EJB3 component must have its own package namespace. For instance, ejb3-core should be restricted to "org.jboss.ejb3.core". -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1713) @NoPassivation annotation

by Galder Zamarreno (JIRA)

@NoPassivation annotation ------------------------- Key: EJBTHREE-1713 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1713 Project: EJB 3.0 Issue Type: Feature Request Reporter: Galder Zamarreno Assignee: Galder Zamarreno Priority: Minor >From a customer perpesctive, we could do with having an easier to solution to what is suggested in http://wiki.jboss.org/wiki/Ejb3DisableSfsbPassivation EB: "If Seam knows you don't do passivation, we could optimize some things. AFAI understand option 1 does not remove passivation, it just changes it to a no-op IO wise. So all the work done in the interceptor is lost. option 2 is better in that regard but not very user friendly. @NoPassivation is much clearer :) " -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1214) Discard consumer messages

by Tim Fox (JIRA)

Discard consumer messages ------------------------- Key: JBMESSAGING-1214 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1214 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta Some message data e.g. stock prices is transitory, if the consumer is slow, we don't want many messages for the consumer to build up in its subscription. We should allow for the max number of messages to keep over and above the prefetch buffer to be specified. Older messages are removed. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1296) Client connect port should be configurable

by Tim Fox (JIRA)

Client connect port should be configurable ------------------------------------------ Key: JBMESSAGING-1296 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1296 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta The client TCP connect port should be configurable in the JBM config, so it can work behind firewalls where the port needs to be specified -- 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, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMETA-177) track JCA spec metadata svn:keywords prop modify

by Jeff Zhang (JIRA)

track JCA spec metadata svn:keywords prop modify ------------------------------------------------ Key: JBMETA-177 URL: https://jira.jboss.org/jira/browse/JBMETA-177 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR16 Reporter: Jeff Zhang Assignee: Jeff Zhang Priority: Minor Fix For: 1.0.0.GA svn:keywords prop modify and package.html for API and test package -- 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

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Updated: (JGRP-134) Emission of JMX notifications on membership changes

by Bela Ban (JIRA)

[ https://jira.jboss.org/jira/browse/JGRP-134?page=com.atlassian.jira.plugi... ] Bela Ban updated JGRP-134: -------------------------- Fix Version/s: 2.x (was: 2.8) Description: Moved to 2.x > Emission of JMX notifications on membership changes > --------------------------------------------------- > > Key: JGRP-134 > URL: https://jira.jboss.org/jira/browse/JGRP-134 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.9 > Reporter: Bela Ban > Assignee: Vladimir Blagojevic > Fix For: 2.x > > > Moved to 2.x -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2296) Misnamed Identity Property

by Fernando Ribeiro (JIRA)

Misnamed Identity Property -------------------------- Key: JBPORTAL-2296 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2296 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.7.1 Final Reporter: Fernando Ribeiro Attachments: identity-ui-configuration.xml, profile-config.xml The "nickName" property is the only one that doesn't follow the convention according to which it would be named "nick-name". -- 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

17 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMETA-176) update JCA 1.6 offical xsd file and metadata

by Jeff Zhang (JIRA)

update JCA 1.6 offical xsd file and metadata -------------------------------------------- Key: JBMETA-176 URL: https://jira.jboss.org/jira/browse/JBMETA-176 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR16 Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.GA JCA 1.6 xsd/dtd out, we should update the schema file and metadata -- 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

17 years, 3 months

1
2
0 / 0

[JBoss JIRA] Commented: (JGRP-134) Emission of JMX notifications on membership changes

by Vladimir Blagojevic (JIRA)

[ https://jira.jboss.org/jira/browse/JGRP-134?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic commented on JGRP-134: ------------------------------------------ Yeah, I agree, we can scrap it until 3.0 when we might have another model for view notifications similar to ChannelListener. The only other option I can see is having a thread poll a view every second or so and if the view changes emit a notification. > Emission of JMX notifications on membership changes > --------------------------------------------------- > > Key: JGRP-134 > URL: https://jira.jboss.org/jira/browse/JGRP-134 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.9 > Reporter: Bela Ban > Assignee: Vladimir Blagojevic > Fix For: 2.8 > > -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-889) Up-port SimpleMultiplexer from Branch_4_2

by Carlo de Wolf (JIRA)

Up-port SimpleMultiplexer from Branch_4_2 ----------------------------------------- Key: EJBTHREE-889 URL: http://jira.jboss.com/jira/browse/EJBTHREE-889 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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, 3 months

1
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 February 2009