February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3834) i18n of jmx-console

by Ryusuke Kajiyama (JIRA)

i18n of jmx-console ------------------- Key: JBAS-3834 URL: http://jira.jboss.com/jira/browse/JBAS-3834 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.4.GA Environment: Any operating system with multiple language such as MS932 (Japanese) Reporter: Ryusuke Kajiyama We found that there are difference in screen-displayed multibyte characters on using Internet Explorer and Firefox. When using MS932, with IE, characters are returned same as posted, however with Firefox, characters are url-escaped like %xx. Our guess is that html of jmx-console does not have charset and there are no functions to handle encoding request parameter. It could be fixed if there were some filter action something like distinguish character set of posted data, and add <meta> tag into html or set Content-Type. -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4154) Get the server to run under a security manager

by Scott M Stark (JIRA)

Get the server to run under a security manager ---------------------------------------------- Key: JBAS-4154 URL: http://jira.jboss.com/jira/browse/JBAS-4154 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Scott M Stark Assigned To: Scott M Stark The testsuite tests-security-manager target was failing due to the aop layer not creating classes with correct ProtectionDomains. This is fixed in (JBAOP-368). The next problem is that the server.policy needs to use vfsfile urls for the permission assignments. However, because these are URLs and not URIs, there has to be a URL handler available when the policy is read at bootstrap. Currently a policy entry like: grant codeBase "vfsfile:${jboss.home.dir}/lib/-" { permission java.security.AllPermission; }; fails because the jboss vfsfile URL handler is unknown: policy: Adding policy entry: policy: signedBy null policy: codeBase vfsfile:/tmp/trunk/build/output/jboss-5.0.0.Beta2/lib/- java.security.policy: error adding Entry: java.net.MalformedURLException: unknown protocol: vfsfile policy: -- 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, 11 months

4
17
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-148) Implement ScopedKernel

by Ales Justin (JIRA)

Implement ScopedKernel ---------------------- Key: JBMICROCONT-148 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-148 Project: JBoss MicroContainer Issue Type: Feature Request Components: Kernel Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBossMC-2.0.0.GA Implement support for scoped deployments on top of scoped metadata. -- 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, 12 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3765) AOP-based version of RetryInterceptor

by Brian Stansberry (JIRA)

AOP-based version of RetryInterceptor ------------------------------------- Key: JBAS-3765 URL: http://jira.jboss.com/jira/browse/JBAS-3765 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB2, EJB3, Remoting Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta The (Single)RetryInterceptor only works for EJB 2. Need to: 1) Create a version that uses the AOP interceptor model rather than org.jboss.invocation. 2) Ensure all proxy factories bind an InvokerLocator in JNDI and include in the proxy metadata the location of the binding. 3) Add the interceptor to the various interceptor stack configs. -- 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, 12 months

8
13
0 / 0

[JBoss JIRA] Created: (EJBTHREE-757) getMessageContext Not Implemented

by ppc (JIRA)

getMessageContext Not Implemented --------------------------------- Key: EJBTHREE-757 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: ppc jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. Form this version with the new JbossWS stack as far i know i not anymore possible to retreive a SOAP attachement . With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :( -- 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

17 years

4
17
0 / 0

[JBoss JIRA] Created: (EJBTHREE-895) Allow clustered tests to run with -u set

by Brian Stansberry (JIRA)

Allow clustered tests to run with -u set ---------------------------------------- Key: EJBTHREE-895 URL: http://jira.jboss.com/jira/browse/EJBTHREE-895 Project: EJB 3.0 Issue Type: Task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Need to use the local.properties "udpGroup" stuff that the AS uses. Allows running with less concern for impactt from / impacting other running 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

17 years

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-857) Include and use buddy group topology information in clustered SFSB proxies

by Brian Stansberry (JIRA)

Include and use buddy group topology information in clustered SFSB proxies -------------------------------------------------------------------------- Key: EJBTHREE-857 URL: http://jira.jboss.com/jira/browse/EJBTHREE-857 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Look into including the replicated SFSB cache's buddy replication group topology in clustered SFSB proxies, and using that information in fail over decisions. This is basically an optimization such that when a failover occurs, data gravitation can occur in VM rather than over the network. -- 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

17 years

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-848) ClusteredStatefulCacheListener should be a singleton

by Brian Stansberry (JIRA)

ClusteredStatefulCacheListener should be a singleton ---------------------------------------------------- Key: EJBTHREE-848 URL: http://jira.jboss.com/jira/browse/EJBTHREE-848 Project: EJB 3.0 Issue Type: Task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: EJB 3.0 RC11 - FD Currently, each SFSB Container registers an instance of ClusteredStatefulCacheListener with the SFSB cache. This is inefficient if there are many containers, as each gets passivation/activation callbacks and has to filter for the ones it's interested in. The callbacks don't do anything container-specific, so it should be possible to use a quasi-singleton ClusteredStatefulCacheListener and eliminate the filtering. Quasi-singleton, because it's possible to have multiple SFSB caches; need one listener per cache. -- 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

17 years

3
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-845) Clarify transactional behavior of clustered SFSB cache

by Brian Stansberry (JIRA)

Clarify transactional behavior of clustered SFSB cache ------------------------------------------------------ Key: EJBTHREE-845 URL: http://jira.jboss.com/jira/browse/EJBTHREE-845 Project: EJB 3.0 Issue Type: Task Components: Clustering Affects Versions: EJB 3.0 RC9 - Patch 1, EJB 3.0 RC9 - FD Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: EJB 3.0 RC10 - FD The ejb3-clustered-sfsb-service.xml is not declaring a TransactionManagerLookupClass, so the cache is not transactional. Need to clarify why this is and correct if there is no good reason. If it is valid, work with JBC team to eliminate the WARN JBC logs when no lookup is specified. -- 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

17 years

3
4
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-146) Clustered EJB setting at the application level (EAR)

by Galder Zamarreno (JIRA)

Clustered EJB setting at the application level (EAR) ---------------------------------------------------- Key: JBCLUSTER-146 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-146 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assigned To: Brian Stansberry We are using clustering for tests. Our application is an ear-archive which has no information about clustering. If we will built up a cluster, we have to change the ejb-jar.xml to set the clustered-tag on True. This is very intricate. Out support team have to unpack the ear - set the clustered-tag for every bean and so on. Is it possible to set the clustered-tag all beans in a ear-Archive? -- 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

17 years

2
8
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 February 2007