August 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBVFS-52) Optimize FileHandler::getChildren calls during VirtualFile::getChild

by Marko Strukelj (JIRA)

[ https://jira.jboss.org/jira/browse/JBVFS-52?page=com.atlassian.jira.plugi... ] Marko Strukelj resolved JBVFS-52. --------------------------------- Resolution: Done This optimisation required slight modification of .vfslink linking support. LinkHandler name is no longer specified inside .vfslink.properties file, but is instead determined as the first component of .vfslink.properties file name (i.e. mylink.vfslink.properties). > Optimize FileHandler::getChildren calls during VirtualFile::getChild > -------------------------------------------------------------------- > > Key: JBVFS-52 > URL: https://jira.jboss.org/jira/browse/JBVFS-52 > Project: JBoss VFS > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.Beta20 > Reporter: Ales Justin > Assignee: Marko Strukelj > Fix For: 2.0.0.CR1 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBVFS-45) Create VirtualFile::delete method

by Ales Justin (JIRA)

Create VirtualFile::delete method --------------------------------- Key: JBVFS-45 URL: http://jira.jboss.com/jira/browse/JBVFS-45 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.Beta20 Reporter: Ales Justin Assigned To: Marko Strukelj Fix For: 2.0.0.CR1 Add delete method to VirtualFile API. -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Resolved: (JBVFS-51) Create lazy notion to VirtualFileHandler

by Marko Strukelj (JIRA)

[ https://jira.jboss.org/jira/browse/JBVFS-51?page=com.atlassian.jira.plugi... ] Marko Strukelj resolved JBVFS-51. --------------------------------- Resolution: Done Zip archives now get initialized lazily, meaning that archive content is not enumerated until absolutely necessary. VfsUrls also now get initialized lazily. > Create lazy notion to VirtualFileHandler > ---------------------------------------- > > Key: JBVFS-51 > URL: https://jira.jboss.org/jira/browse/JBVFS-51 > Project: JBoss VFS > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.Beta20 > Reporter: Ales Justin > Assignee: Marko Strukelj > Fix For: 2.0.0.CR1 > > > There should be a way to lazily construct VirtualFileHandler instances. > Initial instance should only keep minimal info required; e.g. name and parent reference. > This work should help resolve JBVFS-9 as well; e.g. lazy URL creation and creation optimization. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5692) org.jboss.test.naming

by Shelly McGowan (JIRA)

org.jboss.test.naming --------------------- Key: JBAS-5692 URL: http://jira.jboss.com/jira/browse/JBAS-5692 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assigned To: Shelly McGowan -- 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, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-5845) Upgrade jnpclient and jnpserver to 5.0.0.GA

by Brian Stansberry (JIRA)

Upgrade jnpclient and jnpserver to 5.0.0.GA ------------------------------------------- Key: JBAS-5845 URL: https://jira.jboss.org/jira/browse/JBAS-5845 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Fix For: JBossAS-5.0.0.CR2 Once jnpclient/jnpserver 5.0.0.GA releases are out, upgrade to pick up JBNAME-3 -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBNAME-6) Release jnp-client/jnpserver 5.0.0.CR2

by Dimitris Andreadis (JIRA)

Release jnp-client/jnpserver 5.0.0.CR2 -------------------------------------- Key: JBNAME-6 URL: https://jira.jboss.org/jira/browse/JBNAME-6 Project: JBoss Naming Issue Type: Release Components: build Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Fix For: 5.0.0.CR2 -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBNAME-5) Upgrade to latest jboss-common-core 2.2.7.GA

by Dimitris Andreadis (JIRA)

Upgrade to latest jboss-common-core 2.2.7.GA -------------------------------------------- Key: JBNAME-5 URL: https://jira.jboss.org/jira/browse/JBNAME-5 Project: JBoss Naming Issue Type: Thirdparty Change Components: build Affects Versions: 5.0.0.CR1 Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Fix For: 5.0.0.CR2 Upgrade from jboss-common-core 2.2.5.GA to 2.2.7.GA -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5522) Manage an ear/war app through ProfileService

by Mark Spritzler (JIRA)

Manage an ear/war app through ProfileService -------------------------------------------- Key: JBAS-5522 URL: http://jira.jboss.com/jira/browse/JBAS-5522 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Mark Spritzler -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMETA-92) Make replication-granularity optional in the jboss-web.xml DTD

by Brian Stansberry (JIRA)

Make replication-granularity optional in the jboss-web.xml DTD -------------------------------------------------------------- Key: JBMETA-92 URL: https://jira.jboss.org/jira/browse/JBMETA-92 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 1.0.0.Beta36 It doesn't need to be there, as we set a default in ClusteringDefaultsDeployer. And including a replication-config element in order to configure something else is a reasonable thing to do. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5851) incorrect tomcat behavior while header authorization

by Jacek Jackowski (JIRA)

incorrect tomcat behavior while header authorization ---------------------------------------------------- Key: JBAS-5851 URL: https://jira.jboss.org/jira/browse/JBAS-5851 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Installation Guide Affects Versions: JBossAS-5.0.0.CR1 Environment: Jboss 5.0.0.CR1 JDK , Java(TM) SE Runtime Environment (build 1.6.0_07-b06), kubuntu 8.04 Reporter: Jacek Jackowski Assignee: Samson Kittoli I've developed authorization on frontend apache, it works with AJP on Jboss 4.22 and even on Jboss 5 beta 4. I've upgraded server to 5.0.0.CR1 and I've found something wrong. I authoriza myself on apache then I'm forwarded by mod_proxy to jboss and I should access website without loggin but jboss shows me basic login window. User is authorized but the login window is shown, if You press cancell You'll see 403 but after page refresh You'll get the page You want to access. If I press OK without entering username and password jboss give me the page I want. User is authorized, Jboss know that but shows Basic login window. Previous versions of Jboss worked correctly. -- 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, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2008