July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-794) NotSerializableException from LdapLoginModule/AD

by Darren Hartford (JIRA)

NotSerializableException from LdapLoginModule/AD ------------------------------------------------ Key: EJBTHREE-794 URL: http://jira.jboss.com/jira/browse/EJBTHREE-794 Project: EJB 3.0 Issue Type: Bug Environment: jboss 4.0.5.GA/JEMS install, Win2000, ActiveDirectory Reporter: Darren Hartford "java.io.NotSerializableException: com.sun.jndi.ldap.LdapCtx" When incorrect credentials are passed from the client, the server swallows with NotSerializableException and the client does not get correct feedback. Test environment was login-config.xml with org.jboss.security.auth.spi.LdapLoginModule talking to an ActiveDirectory server. Note that when correct credentials are passed, everything works fine. -- 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, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (JBFORUMS-164) lastPostDate must be persisted in database

by Ryszard Kozmik (JIRA)

lastPostDate must be persisted in database ------------------------------------------ Key: JBFORUMS-164 URL: http://jira.jboss.com/jira/browse/JBFORUMS-164 Project: JBoss Forums Issue Type: Task Components: Forum Model Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Blocker Fix For: 1.1.0 Alpha Forums are not efficient mainly because of this very big problem of their module and database schema. There is no place to keep lastPostDates so they have to be generated each time what takes big amounts of time as those are very timetaking sql queries. This is main performance killer at this point. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBFORUMS-249) Make Forums compatible with Portal URLMapper

by Ryszard Kozmik (JIRA)

Make Forums compatible with Portal URLMapper -------------------------------------------- Key: JBFORUMS-249 URL: http://jira.jboss.com/jira/browse/JBFORUMS-249 Project: JBoss Forums Issue Type: Task Components: Forum Enhancements, Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC It is now impossible to overwrite url parameter names of Forums by Portal URLMapper and it should be. -- 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, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBFORUMS-140) Caching

by Ryszard Kozmik (JIRA)

Caching ------- Key: JBFORUMS-140 URL: http://jira.jboss.com/jira/browse/JBFORUMS-140 Project: JBoss Forums Issue Type: Task Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.0 Beta JBoss Forums model have to have caching enabled and configured. Secondary level cache and sql statements caching for Hibernate must be configured and properly used by queries. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1023) Typing the parameter to be replace by DSL/DRL replacement

by christian bastin (JIRA)

Typing the parameter to be replace by DSL/DRL replacement --------------------------------------------------------- Key: JBRULES-1023 URL: http://jira.jboss.com/jira/browse/JBRULES-1023 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: christian bastin Assigned To: Mark Proctor We have a very long DSL including more 150 différent lines (wich could be very similar). We have no posibility to be sure of the replacement operarted by the parsing. We often dicover problem that force us to move the order of the lines in the DSL. This is an simple example of what I think could be improved. If you have a DSL test {code} is {value} this could replace this 2 rules in the DRL rule "Rule-1" when test 10 is 10 then > System.out.println("test 1 OK"); end rule "Rule-1" when test 10 + 10 is 10 then > System.out.println("test 1 OK"); end I would like the ability to type the parameter of my DSL, for example with regular expression. test {code|[0-9]+} is {value|[0-9]+} so the only rule available for replacement should be the first rule ("Rule-1"). The other rule would not find a replacement and should be implemented in the DSL. -- 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, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-380) Create some decision table examples

by william hayhurst (JIRA)

Create some decision table examples ----------------------------------- Key: JBRULES-380 URL: http://jira.jboss.com/jira/browse/JBRULES-380 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Decision tables, Documentation Affects Versions: 3.0 Reporter: william hayhurst Assigned To: Mark Proctor Attachments: barbarian.xls As per IRC, some more fleshed out examples of decision tables in action. -- 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, 8 months

5
14
0 / 0

[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

15 years, 8 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

15 years, 8 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

15 years, 8 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

15 years, 8 months

8
13
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007