November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2035) Partial Refresh Failure - Deprecated Functions in dyna.js

by Dan Krieger (JIRA)

Partial Refresh Failure - Deprecated Functions in dyna.js --------------------------------------------------------- Key: JBPORTAL-2035 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2035 Project: JBoss Portal Issue Type: Patch Security Level: Public (Everyone can see) Components: Portal CMS, Portal Theme Affects Versions: 2.6.5 SP1 Environment: N/A Reporter: Dan Krieger Assigned To: Sohil Shah Priority: Optional I originally had a problem getting partial refresh to operate correctly in Firefox 3 CR1 (although I was not able to test other platforms due to limited computer access). With Prototype having been updated to the most recent version, dyna.js had several deprecated functions that seemed to be the source of the problems in Firefox 3. Changes worth mentioning: Element.getElementsByClassName is deprecated now - $(element).select('.'+classname); is the preferred (and functional) solution document.getElementsByClassName("class-name") is best performed now by $$(".class-name") - notice the inclusion of a . in the classname string (css-style selector) -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6170) Update package names moved from "main" to "bootstrap"

by Andrew Lee Rubinger (JIRA)

Update package names moved from "main" to "bootstrap" ----------------------------------------------------- Key: JBAS-6170 URL: https://jira.jboss.org/jira/browse/JBAS-6170 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: JBossAS-5.0.0.GA Refactoring in JBAS-6169 moved sources from "main" to "bootstrap" modules. Rename the packages to be consistent with their new home, and update the run.jar assembly in main/build.xml to reflect this as well. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBVFS-69) Add VFSCache initalization/construction with Map parameter

by Ales Justin (JIRA)

Add VFSCache initalization/construction with Map parameter ---------------------------------------------------------- Key: JBVFS-69 URL: https://jira.jboss.org/jira/browse/JBVFS-69 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR4 Reporter: Ales Justin Assignee: Ales Justin Fix For: 2.0.0.GA As some VFSCache impls have some parameters that you need to set, - e.g. LRUVFSCache needs to take min and max - we should enable its construction with Map parameter, allowing the impl to get values out of that map, instead of just System properties. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBVFS-68) PathTokenizer can't handle hidden unix directories

by Carlo de Wolf (JIRA)

PathTokenizer can't handle hidden unix directories -------------------------------------------------- Key: JBVFS-68 URL: https://jira.jboss.org/jira/browse/JBVFS-68 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR4 Reporter: Carlo de Wolf Priority: Critical Fix For: 2.0.0.GA java.lang.IllegalArgumentException: Illegal token in path: /home/hudson/.hudson/jobs/JBoss_VFS/workspace/trunk/target/test-classes/vfs/test/nested/nested.jar/META-INF/empty.txt/ at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:133) at org.jboss.virtual.plugins.cache.PathMatchingVFSCache.findContext(PathMatchingVFSCache.java:46) at org.jboss.virtual.plugins.cache.AbstractVFSCache.getFile(AbstractVFSCache.java:66) at org.jboss.virtual.plugins.cache.AbstractVFSCache.getFile(AbstractVFSCache.java:97) at org.jboss.test.virtual.test.VFSCacheTest.testCache(VFSCacheTest.java:68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:163) at org.apache.maven.surefire.Surefire.run(Surefire.java:84) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:261) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:875) -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6169) Make "bootstrap" module reusable

by Andrew Lee Rubinger (JIRA)

Make "bootstrap" module reusable -------------------------------- Key: JBAS-6169 URL: https://jira.jboss.org/jira/browse/JBAS-6169 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: JBossAS-5.0.0.GA The current "bootstrap" module currently has a dependency on "main". This is backwards, "main" pertains to a mechanism of launching AS as a standalone process, and requires a bootstrap to do so. Likewise, other launchers of AS should be able to reuse a generic "bootstrap" component. Resolve the dependency issues, refactoring (moving) sources as appropriate. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-383) Provide access to the BasicXMLDeployer.deploymentsByName values

by Scott M Stark (JIRA)

Provide access to the BasicXMLDeployer.deploymentsByName values --------------------------------------------------------------- Key: JBMICROCONT-383 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-383 Project: JBoss Microcontainer Issue Type: Feature Request Components: Deployment Affects Versions: JBossMC.2.0.0.CR5 Reporter: Scott M Stark There is a need to access the KernelDeployments loaded by a BasicXMLDeployer -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6167) Restore the ServerInfo bean/mbean

by Scott M Stark (JIRA)

Restore the ServerInfo bean/mbean --------------------------------- Key: JBAS-6167 URL: https://jira.jboss.org/jira/browse/JBAS-6167 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: System service Affects Versions: JBossAS-5.0.0.CR2 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.0.0.GA The org.jboss.system.server.ServerInfo bean, formerly registered under the jmx name jboss.system:type=ServerInfo is not being deployed. We need a server-info-jboss-beans.xml deployment for informational beans. <?xml version="1.0" encoding="UTF-8"?>  <deployment xmlns="urn:jboss:bean-deployer:2.0"> <bean name="ServerInfo" class="org.jboss.system.server.ServerInfo"> <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.system:type=ServerInfo", exposedInterface=org.jboss.system.server.ServerInfoMBean.class, registerDirectly=true)</annotation> </bean> </deployment> -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-308) Findbugs analysis

by Anil Saldhana (JIRA)

Findbugs analysis ----------------- Key: SECURITY-308 URL: https://jira.jboss.org/jira/browse/SECURITY-308 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: ACL, Identity, JBossSX, Security SPI Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 2.0.2.GA Simplest way to analyse is to use webstart: http://findbugs.cs.umd.edu/demo/jnlp/findbugs.jnlp -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-118) ACL framework integration with AuthorizationManager implementation

by Anil Saldhana (JIRA)

ACL framework integration with AuthorizationManager implementation ------------------------------------------------------------------ Key: SECURITY-118 URL: http://jira.jboss.com/jira/browse/SECURITY-118 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: ACL, JBossSX, Security SPI Affects Versions: 2.0.2-BETA4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA5 Implement the JBossAuthorizationManager ->getEntitlements method. Additionally, there is a need for ACLContext. -- 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, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1282) Test XA recovery of temporary topic subscriptions

by Michael Musgrove (JIRA)

Test XA recovery of temporary topic subscriptions ------------------------------------------------- Key: JBMESSAGING-1282 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1282 Project: JBoss Messaging Issue Type: Task Components: AS Integration Affects Versions: AS 5.0 Integration Reporter: Michael Musgrove Assigned To: Tim Fox Priority: Optional After integrating JBossMQ recovery code into build 4.2.3.GA of the app server (see JIRA JBTM-279) XA recovery fails if any of the resources used in a transaction corresponds to a JMS topic that only has temporary subscriptions. What happens is that the TM records the transaction branch and when it replays the branch the JMS server does not have any record of the transaction so the TM can never complete the transaction. It works with durable subscriptions since JMS remembers the transaction id. I've raised this task in order to test the behavior of non-durable subscriptions with JBoss Messaging. The files used to test the feature on MQs are attached to JIRA JBTM-279. -- 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, 7 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008