October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-473) Add 1.5.6 artifacts to the JBoss Maven respository

by Anders Hammar (JIRA)

Add 1.5.6 artifacts to the JBoss Maven respository -------------------------------------------------- Key: JBAOP-473 URL: http://jira.jboss.com/jira/browse/JBAOP-473 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.5.6.GA Environment: n/a Reporter: Anders Hammar Attachments: jboss-aop-1.5.6.GA.pom, jboss-aop-jdk50-1.5.6.GA.pom Please add the jdk1.4 and jdk5.0 artifacts of jboss-aop 1.5.6.GA to the maven repository. I've attached the pom files for both artifacts. To be consistent with the deployed 1.5.0.GA artifact, I've keept the "jboss.jboss-aop" groupId and I also kept the "jboss-aop" artifactId for the jdk1.4 artifact. The jdk5.0 artifact uses the "jboss-aop-jdk50" artifactId to be consistent with the jar file in the distribution zip. (While this is not artifact naming standard used in 2.0.0.beta1.) -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4802) FirstAvailable target should not be transient

by Brian Stansberry (JIRA)

FirstAvailable target should not be transient --------------------------------------------- Key: JBAS-4802 URL: http://jira.jboss.com/jira/browse/JBAS-4802 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor If a bean proxy that already has a target established gets serialized (e.g. passed through a remote call), the sticky target is lost on the other end. This can lead to invocations against the same target bean on multiple servers. I don't see any reason for FirstAvailable.electedTarget to be transient. Problem here is changing this changes the serialized form of the class, breaking interoperability. Class also does not implement Externalizable. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4925) Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5)

by Dimitris Andreadis (JIRA)

Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5) ------------------------------------------------- Key: JBAS-4925 URL: http://jira.jboss.com/jira/browse/JBAS-4925 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JBoss Cache Affects Versions: JBossAS-4.2.2.GA Reporter: Dimitris Andreadis Assigned To: Brian Stansberry Fix For: JBossAS-4.2.3.GA Upgrade JBossCache to the latest SP6. -- 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, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-4934) JBossCacheWrapper should not re-use data gravitation option

by Brian Stansberry (JIRA)

JBossCacheWrapper should not re-use data gravitation option ----------------------------------------------------------- Key: JBAS-4934 URL: http://jira.jboss.com/jira/browse/JBAS-4934 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.2.0.GA, JBossAS-4.0.5.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.3.GA JBossCacheWrapper has a minor optimization where it creates an instance of Option, sets it to forceDataGravitation=true and then tries to re-use it across all invocations where we need to gravitate. This is invalid usage; JBC does not promise an Option will be in its original state when an invocation returns. Just need to create an Option for each call; no big deal. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1751) portlet-instances.xml security-constraints are not verified using request.isUserInRole()

by Johannes Fiala (JIRA)

portlet-instances.xml security-constraints are not verified using request.isUserInRole() ---------------------------------------------------------------------------------------- Key: JBPORTAL-1751 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1751 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Security Affects Versions: 2.6.2 Final, 2.6.1 Final Environment: Java JDK 1.4.2 Reporter: Johannes Fiala Assigned To: Julien Viet The implementation which verifies the security of portlet-instances.xml against the user roles currently doesn't seem to use request.isUserInRole(). Fact 1: If you use a role-link in the portlet.xml (to have a role which is not originally created by the Jboss Portal Loginmodule (IdentityLoginModule)) <portlet> ... <security-role-ref> <role-name>PortletUser</role-name> <role-link>User</role-link> </security-role-ref> </portlet> and then use it in the portlet-instances.xml: <instance> ... <security-constraint> <policy-permission> <role-name>PortletUser</role-name> <action-name>view</action-name> </policy-permission> </security-constraint> </instance> </deployment> the portlet instance will not show up. If you use the User-role instead, it works correctly. However, if I do a request.isUserInRole("PortletUser") in the portlet itself, it will always show up as expected. Fact 2: Additionally, it seems the portlet-instances.xml- security check also makes use of the org.jboss.portal.identity.auth.UserPrincipal. I wrote a custom loginmodule and added the "User"-role using my own Principal-class. Again, the portlet instance doesn't show up with my custom loginmodule. If I check it using request.isUserInRole("User"), it shows up correctly. -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1721) Improve error handling when the CMS content cannot be found by the content selector

by Thomas Heute (JIRA)

Improve error handling when the CMS content cannot be found by the content selector ----------------------------------------------------------------------------------- Key: JBPORTAL-1721 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1721 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Reporter: Thomas Heute Assigned To: Sohil Shah Fix For: 2.6.3 Final If the content of a file doesn't exist neither in the user preferred locale and the default locale set up at the service level, the CMS content selector will fail with a NPE in: /WEB-INF/jsp/cms/editor/main.jsp at line 128 125: <p class="portlet-font"> 126: Selected file: <%= uri %><br /> 127: <% 128: if (content.getTitle() != null) 129: { 130: out.println("File title: " + content.getTitle() + "<br />"); 131: } -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4568) AOP 2.0.0.beta

by Kabir Khan (JIRA)

AOP 2.0.0.beta -------------- Key: JBAS-4568 URL: http://jira.jboss.com/jira/browse/JBAS-4568 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: AOP Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: JBossAS-5.0.0.Beta3 -- 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, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1742) ACLEnforcer - folder.getFolders() give results for Anonymus user only if child folders have write or manage permssion for anonymous (read is not enough)

by Mariusz Smykula (JIRA)

ACLEnforcer - folder.getFolders() give results for Anonymus user only if child folders have write or manage permssion for anonymous (read is not enough) -------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1742 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1742 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.2 Final Environment: JBoss 4.2.1 Reporter: Mariusz Smykula Assigned To: Sohil Shah I want to execute simple code from my portlet: Command listCMD = cmsService.getCommandFactory().createFolderGetListCommand("/"); mainFolder = (Folder) cmsService.execute(listCMD); LOG.info(mainFolder .getFolders().size()); This is ALWAYS empty folders list, if executed as Anonymous user. For real result I need to set role write or manage for Anonymus user to all subfolders. This is correct? This happens because in ACLEnforce there is checked for write or mange permssion, but read is enough! for(Iterator itr=specificPermissions.iterator();itr.hasNext();) { Permission specificPermission = (Permission)itr.next(); if( (specificPermission.getService().equals("cms")) && (specificPermission.getAction().equals("write") || specificPermission.getAction().equals("manage")) ) { for(Iterator itr2=userPermissions.iterator();itr2.hasNext();) { Permission userPermission = (Permission)itr2.next(); if( (userPermission.getService().equals("cms")) && (userPermission.getAction().equals("write") || userPermission.getAction().equals("manage")) ) { String pathCriteria = userPermission.findCriteriaValue("path"); if(pathCriteria.equals(path)) { //this means this user has read access to this path toolAccess = true; } } } } } This is correct? -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1727) CLONE -CMS saves pages in native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then national leters are damaged

by Mariusz Smykula (JIRA)

CLONE -CMS saves pages in native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then national leters are damaged --------------------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1727 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1727 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Environment: jboss4.0.3sp1 Reporter: Mariusz Smykula Assigned To: Sohil Shah Fix For: 2.6 CR3 When I input ru-characters in the text area it has been puted into table in native encoding (cp1251) - !!! not UTF-8. But pages are sends in UTF-8, and it damaged. I think that I have to encode the request in UTF-8 ??? --------------------------------------------- create file.html in Ru (in cms admin) with this text abc??? then look at the last record of JBP_CMS_VERSION_BINVAL (six bytes in BINVAL_DATA field): 61 62 63 e0 e1 e2 it is cp1251 encoding !!!! why this text non unicoded ??? then when i retrive it i have - 'abc???' I think that problem isn't in ContentTypeInterceptor because it succefully sets UTF8, because localized resources seems right (in russian). may be it is need to store text in CLobs insdead blobs ??? (a use Derby) or customize Jackrabbit ??? ----------------------------------------------------------- but when I upload file on UTF-8 with russian characters - all correct. I think that cms saves the content in one byte encoding (cp1250 or same). -- 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, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-4766) HTTP session replication failover failures with async buddy replication

by Dominik Pospisil (JIRA)

HTTP session replication failover failures with async buddy replication ----------------------------------------------------------------------- Key: JBAS-4766 URL: http://jira.jboss.com/jira/browse/JBAS-4766 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-4.2.0.GA Environment: 4 nodes, buddy async replication, 100 clients Reporter: Dominik Pospisil Assigned To: Brian Stansberry Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files. -- 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, 8 months

2
11
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 October 2007