October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-803) PojoCache to map internal workspace under region fqn if present

by Ben Wang (JIRA)

PojoCache to map internal workspace under region fqn if present --------------------------------------------------------------- Key: JBCACHE-803 URL: http://jira.jboss.com/jira/browse/JBCACHE-803 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0 In 2.0 release, we use the "flat-space" POJO mapping that stores the real POJO under the __JBossInternal__ workspace. This will create a problem for 1) partial state transfer and 2) marshalling where both requires some notion of "region". To resolve this, we propose if region is present, we store the internal workspace under the specific region fqn. That is, say, a user specifies a region as "/person". Then: cache.attach("/person/joe", joe) will result in the internal workspace for joe is stored under "/pseron/__JBossInternal__". With this scheme, there will be no special handling of partial state transfer and marshalling from PojoCache point of view since all the data will fall under the region. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-385) javax.ejb.EJBContext.lookup() should look relative to the bean's ENC. Currently it is a global JNDI lookup

by Haohua xie (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-385?page=comments#action_12344949 ] Haohua xie commented on EJBTHREE-385: ------------------------------------- it make the model hard to be reused. > javax.ejb.EJBContext.lookup() should look relative to the bean's ENC. Currently it is a global JNDI lookup > ----------------------------------------------------------------------------------------------------------- > > Key: EJBTHREE-385 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-385 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC3 > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: EJB 3.0 RC4 - PFD > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-385) javax.ejb.EJBContext.lookup() should look relative to the bean's ENC. Currently it is a global JNDI lookup

by Haohua xie (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-385?page=comments#action_12344948 ] Haohua xie commented on EJBTHREE-385: ------------------------------------- i think the problem is still open, does'nt it? here is my my code: i have a session bean ManagerSessionBean with remote interface i want to use a factorybean to create this ManagerSessionBean ; so i can't use @EJB to inject the ManagerSessionBean . the factorybean and the ManagerSessionBean are in the same package. in factorybean, i inject SessionContext and define the jndiname of the bean @Resource protected SessionContext sessionContext; protected String sessionUrl = "ManagerSessionBean/remote"; to create the ManagerSessionBean in factory method : ManagerSessionSPI sessionSPI = (ManagerSessionSPI) ctx.lookup(sessionUrl); the sessionSPI can't be created if the ejb-jar is deployed in am ear. and i find that if the global jndi name of ManagerSessionBean is used in EJBContext.lookup(), the codes run well. > javax.ejb.EJBContext.lookup() should look relative to the bean's ENC. Currently it is a global JNDI lookup > ----------------------------------------------------------------------------------------------------------- > > Key: EJBTHREE-385 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-385 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC3 > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: EJB 3.0 RC4 - PFD > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBMESSAGING-443) Release 1.0.2 GA after waiting for a week for feedback on the latest CR

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-443?page=all ] Ovidiu Feodorov deleted JBMESSAGING-443: ---------------------------------------- > Release 1.0.2 GA after waiting for a week for feedback on the latest CR > ----------------------------------------------------------------------- > > Key: JBMESSAGING-443 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-443 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-251) Cached map uses toString() of key to create FQN

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-251?page=all ] Ben Wang resolved JBCACHE-251. ------------------------------ Resolution: Done Assignee: Ben Wang (was: Manik Surtani) In 1.4 we have construct the new Fqn directly, so this should be a non-issue anymore. > Cached map uses toString() of key to create FQN > ----------------------------------------------- > > Key: JBCACHE-251 > URL: http://jira.jboss.com/jira/browse/JBCACHE-251 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.2.3 > Reporter: twundke > Assigned To: Ben Wang > Fix For: 2.0.0 > > Time Spent: 15 minutes > Remaining Estimate: 0 minutes > > The cached map adds values to the cache by creating a child FQN as follows: > new Fqn(getFqn(), key); > or, more recently, AopUtil.constructFqn(getFqn(), key); > This ultimately calls toString() on the key object when the FQN is converted to a string representation. However, toString() should not have to be written to give a meaningful value to the cache in this instance. A well-written toString() will most likely produce very cache-unfriendly FQNs. > A better option is to convert the key object into an internal representation using hashcode(), similar to the default Object.toString() implementation. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-398) @Redirect, @HttpError, etc, break when the occur inside EL evaluation

by Gavin King (JIRA)

@Redirect, @HttpError, etc, break when the occur inside EL evaluation --------------------------------------------------------------------- Key: JBSEAM-398 URL: http://jira.jboss.com/jira/browse/JBSEAM-398 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1 Reporter: Gavin King Assigned To: Gavin King Not sure if this can be fixed, but when a component calls another component via EL, and an exception occurs that Seam is supposed to handle, it instead gets wrapped in one of those awful ELExceptions. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-397) page parameters for wildcarded view-ids

by Gavin King (JIRA)

page parameters for wildcarded view-ids --------------------------------------- Key: JBSEAM-397 URL: http://jira.jboss.com/jira/browse/JBSEAM-397 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Priority: Minor Currently it is not possible to specify a page parameter for a wilcard view-id in pages.xml. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-396) @RequestParameter(converterId="...")

by Gavin King (JIRA)

@RequestParameter(converterId="...") ------------------------------------ Key: JBSEAM-396 URL: http://jira.jboss.com/jira/browse/JBSEAM-396 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Priority: Minor Automatic conversion works, but no way to specify a JSF converter. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-305) More sophisticated handling of request parameters

by Gavin King (JIRA)

More sophisticated handling of request parameters ------------------------------------------------- Key: JBSEAM-305 URL: http://jira.jboss.com/jira/browse/JBSEAM-305 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1 Currently @RequestParameter does basic type conversion, but it would also be nice to support (1) custom converters (2) validation via Hibernate Validator (3) validation via custom validators eg. @RequestParameter(required=true, converter="myConverterId", validator="myValidatorId") @RequestParameter(converter="#{myComponent.myConverter}", validator="#{myComponent.myValidator}") @RequestParameter @NotNull <page view-id="/item.xhtml"> <parameter name="id" required="true"> <converter converterId="myConverterId"/> <validator binding="#{myComponent.myValidator}"/> </parameter> </page> -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-730) Security Domain value in AuthenticationInterceptorFactory and RoleBasedAuthorizationInterceptorFactory

by Anil Saldhana (JIRA)

Security Domain value in AuthenticationInterceptorFactory and RoleBasedAuthorizationInterceptorFactory ------------------------------------------------------------------------------------------------------ Key: EJBTHREE-730 URL: http://jira.jboss.com/jira/browse/EJBTHREE-730 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: EJB 3.0 RC10 - FD Both the AuthenticationInterceptorFactory and RoleBasedAuthorizationInterceptorFactory are not dealing with the value of security domain properly. The final security domain value that is derived is "java:/jaas/java:/jaas/something -- 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, 3 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006