April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login

by Antoine Herzog (JIRA)

ConsumerCacheInterceptor : should not use the cache just after login -------------------------------------------------------------------- Key: JBPORTAL-1325 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Environment: jbp 2.4.0 Reporter: Antoine Herzog Assigned To: Julien Viet Use case : - user come to the site. - Portlet show views for unchecked user. These views are put in the cache. - user log in, let's say as admin - the cached views still show the previous things, not taking into account the change of authorizations - the user can't see the proper things usual needs : - for I18n portals : change of locale when user log in. all the portlets must do the change, not depending on cache - for admin or special roles features in the portlet views - for modes depending on roles (see forum post) In the default portal, there are no use of cache. so all these use cases are fullfiled. to reproduce the problem : - put some cache on the user portlet (great feature for prod), the user portlet window may not update after logging. resolution : in the ConsumerCacheInterceptor the CacheKey do not take into account the login state. see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode) so store the user name (or "unchecked") in the CacheEntry. put the parameter "userOfFragment" in the CacheKey. when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and don't use the cache if different. just to see : can we have access to the logued user in this interceptor ? (that, i don't know) -- 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

18 years, 11 months

3
10
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1231) Management beans initialized too many times

by Ryszard Kozmik (JIRA)

Management beans initialized too many times ------------------------------------------- Key: JBPORTAL-1231 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1231 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1, 2.6.Alpha2 Environment: AS 4.0.5 Portal 2.6Alpha1 or Alpha2 from svn tag Reporter: Ryszard Kozmik Assigned To: Julien Viet Priority: Minor Fix For: 2.6.Beta1 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'portalobjectmgr' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'portalAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'addPageAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'addWindowAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'themePropertyAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'instancemgr' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'preferenceAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'portletmgr' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'createInstanceAction' - only keeping the Those warnings are harmless and are caused by newer myfaces libraries in AS 4.0.5. Please look at forum link included in this task for sollution. However, this sollution might not fully work as Portal has quite old Facelets libraries. -- 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

18 years, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1146) java.lang.NegativeArraySizeException in uploading zip archive

by Antoine Herzog (JIRA)

java.lang.NegativeArraySizeException in uploading zip archive ------------------------------------------------------------- Key: JBPORTAL-1146 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1146 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Environment: Windows XP / JBP 2.4 Reporter: Antoine Herzog Assigned To: Roy Russo when uploading an archive file, there is an exception : java.lang.NegativeArraySizeException at org.jboss.portal.cms.impl.jcr.command.StoreArchiveCommand.execute(StoreArchiveCommand.java:72) at org.jboss.portal.cms.impl.jcr.JCRCommand.dispatch(JCRCommand.java:61) It is because of the zipEntry.getSize() that return -1 (unknown size). this is because of the use of ZipInputStream class. there is a turnaround with using the ZipFile class instead. see : http://forum.java.sun.com/thread.jspa?threadID=492219&messageID=2316626 -- 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

18 years, 11 months

5
9
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-123) Better mechanism to determine Array class

by Adrian Brock (JIRA)

Better mechanism to determine Array class ----------------------------------------- Key: JBMICROCONT-123 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-123 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock Priority: Minor The current implementation of getArrayClass uses the horrible public static Class getArrayClass(Class clazz, int depth) { return Array.newInstance(clazz, depth).getClass(); } there must be a better way to do this? -- 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

18 years, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-868) java.lang.IllegalArgumentException: Unable to find operation XYZ for dependent beans in seperate jars

by William DeCoste (JIRA)

java.lang.IllegalArgumentException: Unable to find operation XYZ for dependent beans in seperate jars ----------------------------------------------------------------------------------------------------- Key: EJBTHREE-868 URL: http://jira.jboss.com/jira/browse/EJBTHREE-868 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: William DeCoste Assigned To: William DeCoste java.lang.IllegalArgumentException: Unable to find operation sayHello() javax.ejb.EJBException: java.lang.IllegalArgumentException: Unable to find operation sayHello() at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:999) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:848) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:454) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:527) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261) Caused by: java.lang.IllegalArgumentException: Unable to find operation sayHello() at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:231) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy89.sayHello(Unknown Source) at org.jboss.ejb3.test.dependency.ABean.getHelloB(ABean.java:18) -- 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

18 years, 12 months

3
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-360) Retrotranslated project dependencies

by Paul Gier (JIRA)

Retrotranslated project dependencies ------------------------------------ Key: JBBUILD-360 URL: http://jira.jboss.com/jira/browse/JBBUILD-360 Project: JBoss Build System Issue Type: Feature Request Reporter: Paul Gier Assigned To: Paul Gier The jboss-retro plugin should be able to translated a project's dependency jars along with the main project artifact. -- 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

18 years, 12 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-878) correct ejb3 testsuite so that all "expected" failures do not ... well ... fail

by William DeCoste (JIRA)

correct ejb3 testsuite so that all "expected" failures do not ... well ... fail ------------------------------------------------------------------------------- Key: EJBTHREE-878 URL: http://jira.jboss.com/jira/browse/EJBTHREE-878 Project: EJB 3.0 Issue Type: Task Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: William DeCoste Assigned To: William DeCoste Fix For: EJB 3.0 RC10 - FD -- 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
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-942) support RemoteBindings annotations from ejb3-interceptors-aop.xml

by William DeCoste (JIRA)

support RemoteBindings annotations from ejb3-interceptors-aop.xml ----------------------------------------------------------------- Key: EJBTHREE-942 URL: http://jira.jboss.com/jira/browse/EJBTHREE-942 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: AS 4.2.0 CR1, EJB 3.0 RC9 - Patch 1, EJB 3.0 RC9 - FD Reporter: William DeCoste Assigned To: William DeCoste The proxy is being created and deployed before the EJBContainer is being started, so the annotations are not populated early enough. See EJBContainer.start() { initializeClassContainer(); } -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-846) PojoCache 2.0 key features

by Ben Wang (JIRA)

PojoCache 2.0 key features -------------------------- Key: JBCACHE-846 URL: http://jira.jboss.com/jira/browse/JBCACHE-846 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Manik Surtani Priority: Minor Fix For: 2.0.0.GA Manik, FYI, followings are the key features for PojoCache 2.0. When do the announcement later, please include them in. Thanks! -Ben Key PojoCache 2.0 features: 1. Supports replicated POJO field as Enum class (JBCACHE-619) 2. Option to replicate POJO final field (JBCACHE-839) 3. Support JDK5.0 only 4. PojoCache provides MBean interface (JBCACHE-783) 5. Uses a pojocache-aop.xml for configuration (JBCACHE-780) 6. Handle complete rollback of POJO field operation under transaction if needed (JBCACHE-723) 7. PojoCache to throw PojoCacheException only runtime exception (JBCACHE-700) 8. Interceptor based architecture to allow easy customization (JBCACHE-588) 9. PojoCache now uses Cache as a delegate (JBCACHE-673) 10. PojoCache event listener (JBCACHE-85) 11. During passivation, PojoCache now lazily loads the individual POJO. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1035) StateTransfer200AopTest fails

by Jason T. Greene (JIRA)

StateTransfer200AopTest fails ----------------------------- Key: JBCACHE-1035 URL: http://jira.jboss.com/jira/browse/JBCACHE-1035 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Reporter: Jason T. Greene Assigned To: Jason T. Greene Fix For: 2.0.0.CR2 -- 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

2
4
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 April 2007