January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8704) Upgrade to JBoss Modules 1.0.0.Beta12

by David Lloyd (JIRA)

Upgrade to JBoss Modules 1.0.0.Beta12 ------------------------------------- Key: JBAS-8704 URL: https://jira.jboss.org/browse/JBAS-8704 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Modules Reporter: David Lloyd Assignee: David Lloyd Priority: Minor Fix For: 7.0.0.Beta1 Update to latest modules version for bug fixes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8838) Provide initial WS subsystem functionalities

by Alessio Soldano (JIRA)

Provide initial WS subsystem functionalities -------------------------------------------- Key: JBAS-8838 URL: https://issues.jboss.org/browse/JBAS-8838 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 7.0.0.Alpha2 Provide initial WS subsystem for basic jaxws / pojo endpoint functionalities. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-480) Add jmx monitoring to jvm.

by Jeremy Whiting (JIRA)

Add jmx monitoring to jvm. -------------------------- Key: JBJCA-480 URL: https://jira.jboss.org/browse/JBJCA-480 Project: IronJacamar Issue Type: Task Components: Performance Environment: All environments. Reporter: Jeremy Whiting Assignee: Jesper Pedersen Priority: Minor This contribution changes the jmeter benchmarking to provide JMX monitoring. Also the in memory database used is changed to HSQLDB due to it's ability to shutdown a standalone database. The performance guide documentation has also been updated with instructions to control jvm processes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBCL-94) Spaces in URLs returned by getResource() should in vfszip: handler

by Ondrej Medek (JIRA)

Spaces in URLs returned by getResource() should in vfszip: handler ------------------------------------------------------------------ Key: JBCL-94 URL: https://jira.jboss.org/jira/browse/JBCL-94 Project: JBoss ClassLoader Issue Type: Bug Components: ClassLoader Environment: JBoss AS 5.0.1, WinXP, JDK 1.6.0u12 Reporter: Ondrej Medek Priority: Minor Hi, I have an EAR deployed as directory (not as JAR). Inside I have one service bean and a config directory. I have tried to deploy config directory as a plain directory and packed in the JAR. I have spotted different behaviour of handling spaces in the resource URLS returned by org.jboss.classloader.spi.base.BaseClassLoader when accessing the config directory. My service bean reads config direcory by: this.getClass().getClassLoader().getResource("conf/") I get the URL: vfsfile:/C:/Program%20Files/JBoss/jboss-5.0.1.GA/server/default/deploy/prinsee-ear.ear/conf/ (Space is '%20') however, when I put the resource in the JAR and access it by: this.getClass().getClassLoader().getResource("prinsee-client.jar/conf") I get the URL: vfszip:/C:/Program Files/JBoss/jboss-5.0.1.GA/server/default/deploy/prinsee-ear.ear/prinsee-client.jar/conf/ (Space is ' '). I think, the behaviour of vfszip: handler is wrong. The space should be always '%20'. Cheers andy -- 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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBVFS-60) Need better hasBeenModified implementation

by Scott M Stark (JIRA)

Need better hasBeenModified implementation ------------------------------------------ Key: JBVFS-60 URL: https://jira.jboss.org/jira/browse/JBVFS-60 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR1 Reporter: Scott M Stark Fix For: 2.0.0.GA The current hasBeenModified implementation relies on the URLConnection.getLastModified() value. This has relatively low resolution (~1ms) on some systems and rapid changes to the underlying files is not be reflected. One example of this was the JBVFS-59 repeated updates to a link file not been seen. -- 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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBVFS-50) Don't use host names in custom vfs urls

by Adrian Brock (JIRA)

Don't use host names in custom vfs urls --------------------------------------- Key: JBVFS-50 URL: https://jira.jboss.org/jira/browse/JBVFS-50 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Adrian Brock The InMemory vfs and AssembledDirectory vfs are using host names as part of their urls/uris. This is causing the JDK to do some kind of security check which involves going to the dns to try to determine the ip address of the host. This is obviously inefficent. The URL schemes should be changed not to use host names. -- 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

13 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (JBBUILD-633) Nexus Audit plugin doesn't save user name for files uploaded through the Nexus GUI

by Paul Gier (JIRA)

Nexus Audit plugin doesn't save user name for files uploaded through the Nexus GUI ---------------------------------------------------------------------------------- Key: JBBUILD-633 URL: https://jira.jboss.org/browse/JBBUILD-633 Project: JBoss Build System Issue Type: Feature Request Components: Artifact Repositories Reporter: Paul Gier Assignee: John Casey Fix For: Repository Support 2010 The audit plugin doesn't appear to be saving the user for files that were uploaded directly through the Nexus GUI. This can be seen by browsing artifacts in the "thirdparty uploads" directory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-94) Reauthentication support

by Jesper Pedersen (JIRA)

Reauthentication support ------------------------ Key: JBJCA-94 URL: https://jira.jboss.org/jira/browse/JBJCA-94 Project: JBoss JCA Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Implement reauthentication support. See chapter 8 and related security discussions for details. -- 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

13 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (SECURITY-545) Code Cleanup Tasks

by Darran Lofthouse (JIRA)

Code Cleanup Tasks ------------------ Key: SECURITY-545 URL: https://jira.jboss.org/browse/SECURITY-545 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Minor Fix For: Negotiation_2.0.4 Tracking of minor code updates related to clean up rather than features / bugs. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1231) create a Discovery protocol using a javax.sql.DataSource

by Sanne Grinovero (JIRA)

create a Discovery protocol using a javax.sql.DataSource -------------------------------------------------------- Key: JGRP-1231 URL: https://jira.jboss.org/browse/JGRP-1231 Project: JGroups Issue Type: Feature Request Reporter: Sanne Grinovero Assignee: Bela Ban Fix For: 2.11, 3.0 It would be useful to have a JDBC/Datasource protocol do perform the autodiscovery of other nodes. For example when used together to Infinispan which might use a database as cache store it would be practical to be able to reuse the same datasource for this purpose, so that setting up a service requires a single set of credentials. In case of deployments on EC2 so it could be possible to use S3 for both discovery and cache store, or RDS for both discovery and cache store (or mixed in any form). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2011