February 2009 - jboss-jira - Jboss List Archives

[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

15 years, 4 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

15 years, 4 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

15 years, 4 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

15 years, 4 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

15 years, 4 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

15 years, 4 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

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5424) Resolve EJB 3 issues

by Carlo de Wolf (JIRA)

Resolve EJB 3 issues -------------------- Key: JBAS-5424 URL: http://jira.jboss.com/jira/browse/JBAS-5424 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Critical Fix For: JBossAS-4.2.3.GA http://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&&fixfor=... -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Commented: (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 commented on JGRP-134: ------------------------------- Thinking about this, I'm not sure we want an additional protocol just to emit notifications. Maybe we should scrap this JIRA issue ? > 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

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6436) Fix in memory webapp deployment

by Thomas Diesler (JIRA)

Fix in memory webapp deployment ------------------------------- Key: JBAS-6436 URL: https://jira.jboss.org/jira/browse/JBAS-6436 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-5.0.0.GA Reporter: Thomas Diesler Assignee: Ales Justin Fix For: JBossAS-5.0.1.GA The WS Endpoint API depends on in-memory webapp deployment. This required piece of JavaEE5 functionality is however not properly tested by the TCK. The Endpoint API works in AS42. -- 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, 4 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2009