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