October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3527) Tomcat 6 fixes needed for JSF

by Stan Silvert (JIRA)

Tomcat 6 fixes needed for JSF ----------------------------- Key: JBAS-3527 URL: http://jira.jboss.com/jira/browse/JBAS-3527 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta Reporter: Stan Silvert Assigned To: Remy Maucherat Fix For: JBossAS-5.0.0.GA This JIRA task is for tracking the Tomcat 6 bugs that need to be fixed for JSF in JBoss AS 5.0.0 http://issues.apache.org/bugzilla/show_bug.cgi?id=39803 http://issues.apache.org/bugzilla/show_bug.cgi?id=39805 http://issues.apache.org/bugzilla/show_bug.cgi?id=40279 We have a workaround for this one, but it would be nice if it were fixed: http://issues.apache.org/bugzilla/show_bug.cgi?id=39804 -- 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

16 years, 7 months

3
8
0 / 0

[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

16 years, 7 months

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

16 years, 7 months

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

16 years, 7 months

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

16 years, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1039) Optimized replication of entities and extended persistence context in SFSBs

by Brian Stansberry (JIRA)

Optimized replication of entities and extended persistence context in SFSBs --------------------------------------------------------------------------- Key: EJBTHREE-1039 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1039 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Optimize replication of clustered SFSBs that hold refs to managed entities and extended persistence contexts, while still ensuring that object identity is maintained between refs to an entity held by the SFSB and those held by the replicated EntityManager. Currently object identity is maintained by serializing the SFSB and the related EntityManager in one operation. The entire EM is serialized, including entities that have been flushed to the db. This is inefficient, since the replication is only done to support failover and in the case of node failover, the flushed entities can be restored from the db or the EM's 2nd level cache. Intent is to: 1) Use JBoss serialization in order to have the ability to alter the serialized form of entities and XPCs. 1) Have Hibernate's EM impl expose getUnflushedChanges()/setUnflushedChanges() methods to support replication of only the unflushed changes held in the XPC, rather than all data. 2) When writing the fields in an SFSB, check if the object is a managed entity; if so write it's id to the stream rather than the whole object. 3) Deserialization process needs to ensure that any EntityManager is deserialized before the managed entities. 4) Deserialization of a managed entity would involve reading the id from the stream, identifying the EntityManager and doing a find(). 5) SFSBs should be lazy-deserialized (i.e. only deserialize if needed to handle failover). This is the way SFSBs clustering already works. This is critical, otherwise the cost of the find() operations would likely outweigh the benefits of reducing the amount of replicated data. Additionally, intent is to allow registration with the container of an impl, say, "ManagedPersistenceContextSerializer". If registered, implementation of many of the steps above would be delegated. JBoss Seam would intend to register an implementation. -- 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

16 years, 7 months

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

16 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1097) InitialContextFactory doesn't always create a new InitialContext

by Carlo de Wolf (JIRA)

InitialContextFactory doesn't always create a new InitialContext ---------------------------------------------------------------- Key: EJBTHREE-1097 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1097 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.2.GA Reporter: Carlo de Wolf InitialContextFactory is not really a factory, it doesn't always create a new InitialContext. This can lead to interesting situations if someone closes an InitialContext which doesn't have any properties and then tries to reuse it. -- 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

16 years, 7 months

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

16 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAOP-461) Resolve outstanding issues on Linux

by Kabir Khan (JIRA)

Resolve outstanding issues on Linux ----------------------------------- Key: JBAOP-461 URL: http://jira.jboss.com/jira/browse/JBAOP-461 Project: JBoss AOP Issue Type: Sub-task Reporter: Kabir Khan -- 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

16 years, 7 months

2
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007