January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBXB-89) JBossXB automatically unzips gzipped content when decoding base64 data.

by Darran Lofthouse (JIRA)

JBossXB automatically unzips gzipped content when decoding base64 data. ----------------------------------------------------------------------- Key: JBXB-89 URL: http://jira.jboss.com/jira/browse/JBXB-89 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-1.0.0.CR7 Reporter: Darran Lofthouse Fix For: JBossXB-1.0 JBossXB automatically unzips gzipped content when decoding base64 data. The reason why it is automatically unzipped is becuase the method unmarshalBase64 in org.jboss.xb.binding.SimpleTypeBindings is calling the method decode in org.jboss.util.Base64, this decode method after converting from Base64 detects that it is gzipped so unzippes it. If we do not need to unzip the data we could call the decode method that takes the byte array instead of a String as this does not perform any unzipping. -- 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

19 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-383) XML Marshaling/Unmarshling code performs no normalisation on name values used to create XML/DOM element nodes.

by Tom Fennelly (JIRA)

XML Marshaling/Unmarshling code performs no normalisation on name values used to create XML/DOM element nodes. -------------------------------------------------------------------------------------------------------------- Key: JBESB-383 URL: http://jira.jboss.com/jira/browse/JBESB-383 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0 CR2 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.0 Maintenance Pack 1 An example of this can be seen in org.jboss.internal.soa.esb.message.format.xml.BodyImpl.toXML(Element) where the body attachment keys are used as the container element name. What if someone saves an attachment that contains special/unsupported chars?? This is very possible! -- 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

19 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-4030) make standard containers extend IPT

by Alexey Loubyansky (JIRA)

make standard containers extend IPT ----------------------------------- Key: JBAS-4030 URL: http://jira.jboss.com/jira/browse/JBAS-4030 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossAS-5.0.0.Beta2 This issue is related to CTS. Standard containers should be based on IPT to avoid self-deadlocking in some of the CTS tests. -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-382) XML Marshaling/Unmarshling code uses the namespace prefix for performing namespace checking.

by Tom Fennelly (JIRA)

XML Marshaling/Unmarshling code uses the namespace prefix for performing namespace checking. -------------------------------------------------------------------------------------------- Key: JBESB-382 URL: http://jira.jboss.com/jira/browse/JBESB-382 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0 CR2 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.0 Maintenance Pack 1 Parsers and serialisers need to be namespace aware and check against the full namespace URI. -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-946) How-To for installing/creating pojocacheable classes in JBoss 4.0.5/Cache 1.4.1/JDK5

by Jamie Reifsnyder (JIRA)

How-To for installing/creating pojocacheable classes in JBoss 4.0.5/Cache 1.4.1/JDK5 ------------------------------------------------------------------------------------ Key: JBCACHE-946 URL: http://jira.jboss.com/jira/browse/JBCACHE-946 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 1.4.1.GA Environment: JBoss 4.0.5.GA, JBoss AOP 1.5.2.GA, JBoss Cache 1.4.1GA, JDK5 Reporter: Jamie Reifsnyder Assigned To: Ben Wang Attachments: To set up the PojoCache in JBoss 4.doc I pulled together install and compile instructions to create precompiled POJOs and an installed version of PojoCache on JBoss. For Ben Wang (requested in http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004847#4004847 ) -- 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

19 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-946) Window changes in admin ui not immediate

by Roy Russo (JIRA)

Window changes in admin ui not immediate ---------------------------------------- Key: JBPORTAL-946 URL: http://jira.jboss.com/jira/browse/JBPORTAL-946 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4 Final Reporter: Roy Russo Assigned To: Julien Viet Moving windows via the ui do not register immediatley when the page refreshes. You must log in again to see the changes. -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3971) Add basic classloader leakage tests

by Brian Stansberry (JIRA)

Add basic classloader leakage tests ----------------------------------- Key: JBAS-3971 URL: http://jira.jboss.com/jira/browse/JBAS-3971 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: ClassLoading Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.CR1 Add basic tests for classloader leaks following deployment, use and undeployment of various packages (wars, ejb jars and ears with and without scoped classloaders). As part of deploy setup, test drivfer will deploy a sar with a service that deployments can use to register their classloader. Service will maintain a WeakReference to the classloader. Test will deploy various packages and invoke operations on them (web requests and remote ejb invocations). Deployments will register their classloader, and during invocations will log using commons-logging (thus testing for leaks via commons-logging). Test driver will then undeploy the package check with the service to see if the classloader was released. If JBoss Profiler is on the path and -agentlib:jbossAgent is passed to java, if the classloader is not released the service will generate and log a report tracing references to the classloader. This can be used to isolate the cause of the leak. -- 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

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-633) Package config editor

by Michael Neale (JIRA)

Package config editor --------------------- Key: JBRULES-633 URL: http://jira.jboss.com/jira/browse/JBRULES-633 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

19 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-3721) Clustered SSO entries not properly cleaned up if a server crashes

by Brian Stansberry (JIRA)

Clustered SSO entries not properly cleaned up if a server crashes ------------------------------------------------------------------ Key: JBAS-3721 URL: http://jira.jboss.com/jira/browse/JBAS-3721 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.5.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.0.6.CR1 If a server crashes, the entries for its sessions in the clustered sso cache will never be removed, and thus the sso may never be removed. TreeCacheSSOManager needs to listen for view changes and discard sessions associated with dead servers. -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-640) Implement an asynchronous method for handling callbacks.

by Ron Sigal (JIRA)

Implement an asynchronous method for handling callbacks. -------------------------------------------------------- Key: JBREM-640 URL: http://jira.jboss.com/jira/browse/JBREM-640 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) Tim Fox: Currently, it's my understanding that push callbacks (using socket transport anyway) are synchronous, i.e. the server side thread that executes the callback blocks until the callback has been delivered to the client side and returned. Is it currrently possible to execute asynch push callbacks? I.e. the thread that calls the callback returns immediately once it has registered the callback with remoting. And it is then delivered on a different thread? Ideally executing using some kind of executor (e.g. PooledExecutor) with a bounded queue size which blocks when it is full would be ideal. -- 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

19 years, 3 months

1
1
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 January 2007