March 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1303) Invalidation is not transactional

by Brian Stansberry (JIRA)

Invalidation is not transactional --------------------------------- Key: JBCACHE-1303 URL: http://jira.jboss.com/jira/browse/JBCACHE-1303 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.0.CR4 Reporter: Brian Stansberry Assigned To: Manik Surtani Invalidation is not transactional, particularly with optimistic locking. 1) With OL, the invalidation messages are sent in the afterCompletion() phase. So, if there is a problem with the invalidation it is too late to roll back the tx. 2) With PL, there is no handling of tx rollback (i.e. undo the invalidation). This is less of an issue, as it can be argued that not rolling back an invalidation doesn't leave a PL cache in an inconsistent state. Will discuss in more detail on forum thread. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1490) org.drools.util.AbstractHashTable$SingleIndex is not serializable

by Pedro Costa (JIRA)

org.drools.util.AbstractHashTable$SingleIndex is not serializable ----------------------------------------------------------------- Key: JBRULES-1490 URL: http://jira.jboss.com/jira/browse/JBRULES-1490 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.4 Environment: windows xp, jdk 1.5.0.7 Reporter: Pedro Costa Assigned To: Mark Proctor Priority: Blocker When serializing a working memory I get the following error: Caused by: java.io.NotSerializableException: org.drools.util.AbstractHashTable$SingleIndex at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1251) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) ............ I checked the docs and org.drools.util.AbstractHashTable$SingleIndex is not serializable ... -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1196) EJB3 role mapping could lead to wrong role

by Roland Räz (JIRA)

EJB3 role mapping could lead to wrong role ------------------------------------------ Key: EJBTHREE-1196 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1196 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.2.GA Reporter: Roland Räz In the class org.jboss.ejb3.BaseSessionContext in the method isCallerInRole(String roleName) the security role references are resolved repeated but the mapping should be terminated after the first match. Consider the following mappings that would be handled in the given order. The current implementation would resolve the mapping for role A to C but it should be B. A -> B B -> C -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1940) Investigate NPE when accessing the profile

by Julien Viet (JIRA)

Investigate NPE when accessing the profile ------------------------------------------ Key: JBPORTAL-1940 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1940 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Reporter: Julien Viet Assigned To: Julien Viet Fix For: Portlet-2.0 -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-5269) securityDomain property not being picked up / initiated in JRMPInvoker's RMIServerSocketFactoryBean attribute

by Yukai Wang (JIRA)

securityDomain property not being picked up / initiated in JRMPInvoker's RMIServerSocketFactoryBean attribute ------------------------------------------------------------------------------------------------------------- Key: JBAS-5269 URL: http://jira.jboss.com/jira/browse/JBAS-5269 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Remoting, Security Affects Versions: JBossAS-4.0.5.GA Environment: Redhat Linux, JBoss 4.0.5GA Reporter: Yukai Wang Assigned To: Ron Sigal securityDomain property has not been picked up / initiated in JRMPInvoker's RMIServerSocketFactoryBean attribute so that when this property is set, JBoss can not start the related MBean service and gives out NullPointerException. Reference from http://lists.jboss.org/pipermail/jbossws-users/2007-March/001817.html I did already check out: http://jira.jboss.com/jira/browse/JBAS-1983 but was not able to configure the ciphersuites accordingly (this included JBAS-2785). I wasn't unable to check out, if these settings would change anything on WebServices, since JBoss doesn't start due to a null pointer exception (see attachment). As some debugging reveals, this is because the member "securityDomain" within: org.jboss.security.ssl.ServerSocketFactory seems to not get initialized.

16 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1939) JSF Validator cannot be cast to javax.faces.validator.Validator

by Alex Kachanov (JIRA)

JSF Validator cannot be cast to javax.faces.validator.Validator ---------------------------------------------------------------- Key: JBPORTAL-1939 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1939 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: Identity-1.0 Environment: JBoss Portal - Identity portlet Reporter: Alex Kachanov JBoss portal is using idenityt portlet to regster new users and edit profiles for existing users I added new my own JSF validator to the identty portlet which when opened throws the following exception: java.lang.ClassCastException: com.kachanov.test004.validators.MyValidator cannot be cast to javax.faces.validator.Validator at org.apache.myfaces.application.ApplicationImpl.createValidator(ApplicationImpl.java:613) The code of my validator is: ========================================================== package com.kachanov.test004.validators; import javax.faces.application.FacesMessage; import javax.faces.component.UIComponent; import javax.faces.context.FacesContext; import javax.faces.validator.Validator; import javax.faces.validator.ValidatorException; public class MyValidator implements Validator { public void validate(FacesContext arg0, UIComponent arg1, Object arg2) throws ValidatorException { System.out.println("testing this validator"); } } ========================================================== So please thell me how can it bee that a class that implements Validator cannot be cast to javax.faces.validator.Validator?????? Is in't it against basic design of Java languages? -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBREM-753) Assure version compatibility with earlier versions of Remoting

by Ron Sigal (JIRA)

Assure version compatibility with earlier versions of Remoting -------------------------------------------------------------- Key: JBREM-753 URL: http://jira.jboss.com/jira/browse/JBREM-753 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.CR1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Critical Fix For: 2.4.0.CR1 (Pinto) Each version of Remoting must be API and wire compatible with earlier versions, at least as far back as 1.4.3.GA, which is used in JBossAS 4.0.4.GA and 4.0.5.GA. -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-703) allow for total configuration of socket via socket invoker

by Tom Elrod (JIRA)

allow for total configuration of socket via socket invoker ---------------------------------------------------------- Key: JBREM-703 URL: http://jira.jboss.com/jira/browse/JBREM-703 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.Alpha7 Reporter: Tom Elrod Assigned To: Tom Elrod Priority: Minor Fix For: 2.2.0.Beta2 (Bluto) Currently remoting does not expose all the configuration properties for a socket for the socket invokers. Should just allow configuration of everything allowed by the jdk api for a socket to be allowed via remtoing (i.e. sendBufferSize and receiveBufferSize) -- 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, 2 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2008