February 2009 - jboss-jira - Jboss List Archives

[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: ------------------------------------------ Is acceptable solution inserting a custom protocol on top of the stack programatically that would catch view change events, send JMX notification and pass the view event up the stack. I do not see another way to do this, do you? > 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JASSIST-73) getAvailableAnnotations() sometimes returns null for the same method in unittesting

by Christian ÃkerstrÃ¶m (JIRA)

getAvailableAnnotations() sometimes returns null for the same method in unittesting ----------------------------------------------------------------------------------- Key: JASSIST-73 URL: https://jira.jboss.org/jira/browse/JASSIST-73 Project: Javassist Issue Type: Bug Environment: Eclipse Ganymede, Windows Vista, jUnit 3.4... Reporter: Christian ÃkerstrÃ¶m Assignee: Shigeru Chiba We have developed a jUnit testcase that test the annotation for an existing method. Our own classloader first loads the class that contains the method and then tries to get any available annotations. Our annotated method looks like this, using our own NotificationEmitter.class. @NotificationEmitter(description = "Notifies xxx", type = xxx.class) public void method() { ... } Sometimes when we call method.getAvailableAnnotations(); it returns When it fails seems to be very nondeterministic. Any help would be appreciated. -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2197) convert portal reference guide to product format

by Prabhat Jha (JIRA)

convert portal reference guide to product format ------------------------------------------------ Key: JBPORTAL-2197 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2197 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Reference Guide Reporter: Prabhat Jha Assignee: Samson Kittoli current contents are at: http://anonsvn.jboss.org/repos/portal/docs/branches/JBoss_Portal_Branch_2.... Please put the converted contents at http://anonsvn.jboss.org/repos/portal/docs/enterprise/trunk/ -- 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, 5 months

4
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1494) UUIDGenerator does not use a different network address

by Jeff Mesnil (JIRA)

UUIDGenerator does not use a different network address ------------------------------------------------------ Key: JBMESSAGING-1494 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1494 Project: JBoss Messaging Issue Type: Feature Request Reporter: Jeff Mesnil Assignee: Tim Fox Fix For: 2.0.0 Beta UUIDGenerator always use InetAddress.getLocalHost() for its address which is likely to return the same result on different machines thus compromising the uniqueness of the UUID generated by different machines at the same time. Instead, we should use an address returned by NetworkInterface to retrieve an address different from the local address. In the case the UUIDGenerator is called from restricted clients (e.g. applets, no network permissions), we'd fall back on using the InetAddress.getLocalHost() but the uniqueness would not be guaranteed -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Commented: (GPD-297) org.jbpm.gd.jpdl has wrong provider, and wrong version?

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-297?page=com.atlassian.jira.plugin... ] Koen Aers commented on GPD-297: ------------------------------- I still have to verify, but if that is a possibility than that could be very much the case. > org.jbpm.gd.jpdl has wrong provider, and wrong version? > ------------------------------------------------------- > > Key: GPD-297 > URL: https://jira.jboss.org/jira/browse/GPD-297 > Project: JBoss jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.6 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.1.7 > > > See screenshot. This is taken from JBT 3.0.0.CR2-R200901280154. > Despite fetching from fetchTag=jbpm_jpdl_gpd_3_1_6, this shows the plugin is at 3.1.5, not 3.1.6. Is that correct? If so, then fixing the provider should increment it to 3.1.6, I suppose. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (GPD-297) org.jbpm.gd.jpdl has wrong provider, and wrong version?

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-297?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on GPD-297: ----------------------------------------- I assumed the number issue was because of a glitch in the build not in the plugin it self ? > org.jbpm.gd.jpdl has wrong provider, and wrong version? > ------------------------------------------------------- > > Key: GPD-297 > URL: https://jira.jboss.org/jira/browse/GPD-297 > Project: JBoss jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.6 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.1.7 > > > See screenshot. This is taken from JBT 3.0.0.CR2-R200901280154. > Despite fetching from fetchTag=jbpm_jpdl_gpd_3_1_6, this shows the plugin is at 3.1.5, not 3.1.6. Is that correct? If so, then fixing the provider should increment it to 3.1.6, I suppose. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (GPD-297) org.jbpm.gd.jpdl has wrong provider, and wrong version?

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-297?page=com.atlassian.jira.plugin... ] Koen Aers updated GPD-297: -------------------------- Summary: org.jbpm.gd.jpdl has wrong provider, and wrong version? (was: CLONE -org.jbpm.gd.jpdl has wrong provider, and wrong version?) Affects Version/s: jBPM jPDL Designer 3.1.6 > org.jbpm.gd.jpdl has wrong provider, and wrong version? > ------------------------------------------------------- > > Key: GPD-297 > URL: https://jira.jboss.org/jira/browse/GPD-297 > Project: JBoss jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.6 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.1.7 > > > See screenshot. This is taken from JBT 3.0.0.CR2-R200901280154. > Despite fetching from fetchTag=jbpm_jpdl_gpd_3_1_6, this shows the plugin is at 3.1.5, not 3.1.6. Is that correct? If so, then fixing the provider should increment it to 3.1.6, I suppose. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Moved: (GPD-297) CLONE -org.jbpm.gd.jpdl has wrong provider, and wrong version?

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-297?page=com.atlassian.jira.plugin... ] Koen Aers moved JBIDE-3716 to GPD-297: -------------------------------------- Project: JBoss jBPM GPD (was: Tools (JBoss Tools)) Key: GPD-297 (was: JBIDE-3716) Component/s: jpdl (was: jbpm) Fix Version/s: jBPM jPDL Designer 3.1.7 (was: 3.0.0.GA) Affects Version/s: (was: 3.0.0.CR2) > CLONE -org.jbpm.gd.jpdl has wrong provider, and wrong version? > -------------------------------------------------------------- > > Key: GPD-297 > URL: https://jira.jboss.org/jira/browse/GPD-297 > Project: JBoss jBPM GPD > Issue Type: Bug > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.1.7 > > > See screenshot. This is taken from JBT 3.0.0.CR2-R200901280154. > Despite fetching from fetchTag=jbpm_jpdl_gpd_3_1_6, this shows the plugin is at 3.1.5, not 3.1.6. Is that correct? If so, then fixing the provider should increment it to 3.1.6, I suppose. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1710) Create a new tutorial to demonstrate the usage of partial deployment descriptors for EJB3 in JBoss

by jaikiran pai (JIRA)

Create a new tutorial to demonstrate the usage of partial deployment descriptors for EJB3 in JBoss -------------------------------------------------------------------------------------------------- Key: EJBTHREE-1710 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1710 Project: EJB 3.0 Issue Type: Task Components: Documentation Environment: JBossAS-5.0 GA Reporter: jaikiran pai Assignee: jaikiran pai Add a new tutorial to show the usage of "partial_deployment_descriptor" for EJB3 in JBoss -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6114) http://www.jboss.org/j2ee/dtd/jboss-ds_5_0.dtd is missing

by Juergen Zimmermann (JIRA)

http://www.jboss.org/j2ee/dtd/jboss-ds_5_0.dtd is missing --------------------------------------------------------- Key: JBAS-6114 URL: https://jira.jboss.org/jira/browse/JBAS-6114 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR2 Reporter: Juergen Zimmermann %JBOSS_HOME%\docs\schema\jboss-ds_5_0.dtd refers to http://www.jboss.org/j2ee/dtd/jboss-ds_5_0.dtd. But this url doesn't exist -- 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, 5 months

2
6
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