May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4198) Align EJB3 Security with JEE 1.4 Behavior

by Anil Saldhana (JIRA)

Align EJB3 Security with JEE 1.4 Behavior ----------------------------------------- Key: JBAS-4198 URL: http://jira.jboss.com/jira/browse/JBAS-4198 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3, Security Affects Versions: JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA Reporter: Anil Saldhana Assigned To: Bill Burke Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.1.CR1 EJB3 security layer needs to be aligned with the ejb2 security layer. There is a need to sync up metadata and maybe pull a common abstract layer out such that there is alignment. -- 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

18 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-896) Specifying an interceptor-order in ejb-jar.xml also creates a new instance of the interceptor

by Carlo de Wolf (JIRA)

Specifying an interceptor-order in ejb-jar.xml also creates a new instance of the interceptor --------------------------------------------------------------------------------------------- Key: EJBTHREE-896 URL: http://jira.jboss.com/jira/browse/EJBTHREE-896 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: interceptor2 Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Critical -- 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

18 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-1082) Optimise nodes for single elements

by Manik Surtani (JIRA)

Optimise nodes for single elements ---------------------------------- Key: JBCACHE-1082 URL: http://jira.jboss.com/jira/browse/JBCACHE-1082 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR1 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.CR3, 2.0.0.GA Many use cases just place a single object in a Node. Rather than going through the memory and performance penalties of using Maps for a single entry, we should: 1) Create a reference to 2 Objects for key and value, as well as a Map. 2) Only initialise/construct the Map if Node.putAll() is called, or when Node.put() is called with a second key/value pair 3) Otherwise just hold the key/value pair as direct object refs. Would affect UnversionedNode and WorkspaceNodeImpl. -- 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

18 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-1009) Support preload functionality as part of region activation

by Brian Stansberry (JIRA)

Support preload functionality as part of region activation ---------------------------------------------------------- Key: JBCACHE-1009 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Reporter: Brian Stansberry Assigned To: Manik Surtani Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region. If one of the defined preload regions names a subregion of the region being activated, preload the subregion. -- 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

18 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-4220) Hot deployment of jars does not always work

by Scott M Stark (JIRA)

Hot deployment of jars does not always work ------------------------------------------- Key: JBAS-4220 URL: http://jira.jboss.com/jira/browse/JBAS-4220 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Scott M Stark Due to JBMICROCONT-160, redeployment of an existing jar may not work. -- 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

18 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3775) org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly

by David Kilzer (JIRA)

org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly -------------------------------------------------------------------------------------------------------- Key: JBAS-3775 URL: http://jira.jboss.com/jira/browse/JBAS-3775 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.2 Final Environment: Microsoft Windows XP [Version 5.1.2600] java version "1.5.0_07" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03) Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode) Xerces-J 2.6.2 Reporter: David Kilzer Attempting to parse a document using Xerces-J 2.6.2 by passing in a java.io.File object containing a UNC path fails when run under JBossAS 4.0.2 Final, but works fine when run outside of JBoss. The particular code run under JBoss was started through a Spring-1.2.8-controlled Quartz-1.4.5 job (all deployed within a WAR within an EAR), but the stack trace clearly shows that org.jboss.net.protocol.file.FileURLConnection is the culprit (file path changed to protect the innocent): java.io.FileNotFoundException: \c$\path\to\file.xml at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80) at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89) at java.net.URL.openStream(URL.java:1007) at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172) [...] Here is some sample code that should reproduce the issue. Note the path used to create the java.io.File object. File xmlFile = new File("\\\\127.0.0.1\\c$\\path\\to\\file.xml"): DocumentBuilderFactory factory = new org.apache.xerces.jaxp.DocumentBuilderFactoryImpl(); factory.setNamespaceAware(false); factory.setValidating(false); DocumentBuilder builder = factory.newDocumentBuilder(); Document document = builder.parse(xmlFile); // exception thrown under JBossAS The FileURLConnection class is loaded from jboss-4.0.2/client/jboss-common-client.jar. -- 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

18 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-4246) JBoss logo not displayed for web status when accessed from web console

by Stephen Burdeau (JIRA)

JBoss logo not displayed for web status when accessed from web console ---------------------------------------------------------------------- Key: JBAS-4246 URL: http://jira.jboss.com/jira/browse/JBAS-4246 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-4.0.5.GA Environment: Found on Windows XP; should exist everywhere. Reporter: Stephen Burdeau Assigned To: Darran Lofthouse This is a minor issue to be sure. Run web console and navigate to Monitoring - Web Status - Connector scoreboard in the left frame. The right frame displays the Tomcat status, but it does not include the JBoss logo on the top and it does not use the JBoss style sheet. Navigating to Monitoring - Web Status - Full status also shows the same problem. When accessing the same Tomcat status pages from the main page (e.g., http://localhost:8080), this problem does not occur. It appears that logo.gif and jboss.css are located in the "root" directory for Tomcat. However, for the web console, logo.gif is located in the "images" subdirectory and jboss.css is located in the "css" subdirectory, so they are not found when using the web console. An easy workaround is to copy the files logo.gif and jboss.css into the directory deploy/management/console-mgr.sar/web-console.war. -- 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

18 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-983) Upload of large files fails.

by Peter Johnson (JIRA)

Upload of large files fails. ---------------------------- Key: JBPORTAL-983 URL: http://jira.jboss.com/jira/browse/JBPORTAL-983 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Environment: Windows XP, JDK 1.5, JBoss AS 4.0.4GA Reporter: Peter Johnson Fix For: 2.4 Final Using the CMS Admin portlet, I attempted to upload a zip file into a directory, as per section 3.2.9 of the User Guide. Initially I tried a zip ofabout 6MB containing many files, and eventually got down to a a zip file of about 500M with only a single Word document inside. The upload failed and an "SQLException: could not reset reader" error appeared (see forum post for stack trace). I am, however, able to upload very small zip files. -- 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

18 years, 2 months

8
23
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-179) VFS caches old jar files

by Carlo de Wolf (JIRA)

VFS caches old jar files ------------------------ Key: JBMICROCONT-179 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-179 Project: JBoss MicroContainer Issue Type: Bug Components: VFS Reporter: Carlo de Wolf Priority: Critical New jar files are not being picked up by VFS. Somehow the cached ones -- 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

18 years, 2 months

6
15
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-164) JarEntry as VFS root does not return empty vfspath

by Bill Burke (JIRA)

JarEntry as VFS root does not return empty vfspath -------------------------------------------------- Key: JBMICROCONT-164 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-164 Project: JBoss MicroContainer Issue Type: Bug Components: VFS Affects Versions: JBossMC_2_0_0 Beta3 Reporter: Bill Burke Fix For: JBossMC_2_0_0_CR1 There's a test already in SVN. Just don't know how to fix cleanly at the moment: JARVFSContextUnitTestCase.testPathIsEmptryForJarEntryAsRoot -- 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

18 years, 2 months

4
11
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 May 2007