February 2009 - jboss-jira - Jboss List Archives

[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

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

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

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

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

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

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

15 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1697) Move the current ejb3 timer service to a separate optional component

by Carlo de Wolf (JIRA)

Move the current ejb3 timer service to a separate optional component -------------------------------------------------------------------- Key: EJBTHREE-1697 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1697 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: 1.1.0-Beta1 Currently EJB3 doesn't use the EJB3 TimerService. It should be moved out of the default setup and made optional. -- 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, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1401) Create Tests for @Remote pass-by-value within local JVM

by Andrew Lee Rubinger (JIRA)

Create Tests for @Remote pass-by-value within local JVM ------------------------------------------------------- Key: EJBTHREE-1401 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1401 Project: EJB 3.0 Issue Type: Task Components: proxy Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.CR2 Ensure EJB3 Core Specification 3.2.1 is intact: "The arguments and results of the methods of the remote business interface are passed by value." -- 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, 3 months

3
12
0 / 0

[JBoss JIRA] Created: (JBRULES-1811) syntax errors caused by use of special characters in decision table cells

by Frank Langelage (JIRA)

syntax errors caused by use of special characters in decision table cells ------------------------------------------------------------------------- Key: JBRULES-1811 URL: https://jira.jboss.org/jira/browse/JBRULES-1811 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 4.0.7 Environment: JBoss-4.24GA with Drools 4.0.7 on Solaris Sparc 10, Sun JDK 1.6.0_07 Reporter: Frank Langelage Assignee: Mark Proctor A customer entered item codes with special characters into an decision table. This caused syntax errors on the generated code. The item codes contained dimension in inches and they used a double quote for the unit (e.g. '... 24"....'). As this double quotes terminate a string, the generated code out of the decision table is invalid. If a double quote sign is in the cell content this double quote must be masked by inserting a backslash character automatically. So we would get "....24\"...." as the string literal in generated code. >From our opinion it's not acceptable to force the user who fills in the data cells into the spreadsheet to learn java and masquerade problematic characters by inserting the backslash in front of them. -- 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, 3 months

3
3
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