February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBBUILD-339) Enable viewing of long file names in directory lists on http://repository.jboss.com/maven2/

by Kevin Stoll (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-339?page=comments#action_12352948 ] Kevin Stoll commented on JBBUILD-339: ------------------------------------- added IndexOptions NameWidth=* this should fix your problem. > Enable viewing of long file names in directory lists on http://repository.jboss.com/maven2/ > ------------------------------------------------------------------------------------------- > > Key: JBBUILD-339 > URL: http://jira.jboss.com/jira/browse/JBBUILD-339 > Project: JBoss Build System > Issue Type: Task > Reporter: Charles Crouch > Assigned To: Paul Gier > > Looking at http://repository.jboss.com/maven2/jboss/jboss-logging-spi/2.0.3.GA/ its impossible to tell what files are actually there without mousing over them and seeing where the link goes, e.g. > [DIR] Parent Directory - > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 8.2K > [TXT] jboss-logging-spi-2...> 10-Feb-2007 14:59 115 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 40 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 7.5K > [TXT] jboss-logging-spi-2...> 10-Feb-2007 14:59 107 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 40 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 2.2K > [TXT] jboss-logging-spi-2...> 10-Feb-2007 14:59 107 > [ ] jboss-logging-spi-2...> 18-Dec-2006 20:40 40 > It should be possible to fix this following instructions similar to those discussed here: > http://www.networkworld.com/columnists/2006/051506internet.html -- 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 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2861) HttpSession sharing between WAR modules

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2861?page=all ] Brian Stansberry updated JBAS-2861: ----------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 JBossAS-4.2.1.CR1 (was: JBossAS-4.2.0.CR1) This will not be completed by Thursday, the cutoff date for 4.2.0. Therefore I have to reschedule it for 5.0.0/4.2.1. > HttpSession sharing between WAR modules > --------------------------------------- > > Key: JBAS-2861 > URL: http://jira.jboss.com/jira/browse/JBAS-2861 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Clustering > Affects Versions: JBossAS-3.2.7 Final, JBossAS-3.2.6 Final > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.1.CR1 > > > Creating a redacted version of JBAS-1909, which was opened as a non-public JIRA issue by a customer. > Our J2EE application is composed of several modules, each one addressing one facet of our business process, and currently this application has one web module (WAR) and several JAR modules (EJB). > We need to divide this web module into several smaller web modules. > In order to separate our unique WAR file into several WARs we must guarantee HttpSession sharing. This is due to the fact that we have a lot of session attributes that are used throughout the entire application and we cannot afford to refactor the application, in fact, that's impossible. > The security aspects for this requirement are completely addressed by the JBoss/Tomcat Single Sign-On mechanism but the session sharing requirements are not. > The ideal scenario is to keep the same HttpSession (same object in the heap, same session ID) when authenticating into one application (HttpSession created) and then forwarding to another application. > The current SSO mechanism allows the user to access the second application without reauthentication, as you know, but it creates a new HttpSession object. Also, if the two WARs have different session timeouts, if you access application A, migrates to application B, stays there until session in application A expires and then returns to application A from application B, a new HttpSession is also created in application A. > The ideal solution is to have one unique, monolithic session to all web applications configured to share a common session. IBM WebSphere and BEA WebLogic do have this configuration and feature. Please check the links below in case you want more information: > WebSphere Application Server V5: Sharing Session Context - http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/tips0215.ht... > BEA Weblogic - Enabling Web applications to share the same session - http://e-docs.bea.com/wls/docs90/webapp/sessions.html -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1235) unable to create a portal

by Anders Andersen (JIRA)

unable to create a portal ------------------------- Key: JBPORTAL-1235 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1235 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.6.Alpha2, 2.6.Alpha1 Environment: mac osx client running firefox 1.5.0.9, Safari and Mozilla shows same problem server: PowerBook G4 Reporter: Anders Andersen Assigned To: Julien Viet In the Management Portlet the root context contains no name "" So I am unable to add portal (to the root) In version 2.6 DR1 this was possible. I reported this under user "Announcement" for ALPHA1, but this announcement seems gone when ALPHA2 came. -- 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 months

3
2
0 / 0

(no subject)

by 90522jkl＠flashget.com

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1206) When looking for users in the user portlet, empty lines may be created

by Thomas Heute (JIRA)

When looking for users in the user portlet, empty lines may be created ---------------------------------------------------------------------- Key: JBPORTAL-1206 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1206 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.6.Alpha1 Reporter: Thomas Heute Assigned To: Julien Viet Fix For: 2.6.Beta1 When you search for a user in the user portlet, the result is displayed in a table. If the number of results is even, the table gets a new empty line. -- 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 months

2
1
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-558) Navigation with JSF/Facelets broken with multiple portlets in one page

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-558?page=all ] Julien Viet resolved JBPORTAL-558. ---------------------------------- Resolution: Cannot Reproduce Bug > Navigation with JSF/Facelets broken with multiple portlets in one page > ---------------------------------------------------------------------- > > Key: JBPORTAL-558 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-558 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.2 Final > Environment: Linux Red Hat Enterprise Server 4 64 Bit, JDK 1.5.0_06 > Reporter: gressho > Fix For: 2.6.Beta1 > > > Navigation results in JSF/Facelet appear allways in the first portlet of the page. The "result" is the same, but "from" and "to" aren't. > Everything works correct with JSF/JSP. -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1259) Minor task container

by Julien Viet (JIRA)

Minor task container -------------------- Key: JBPORTAL-1259 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1259 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.Beta1 Reporter: Julien Viet Fix For: 2.6.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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-659) Test web app instrumentation

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-659?page=all ] Julien Viet updated JBPORTAL-659: --------------------------------- Fix Version/s: (was: 2.6.Beta1) > Test web app instrumentation > ---------------------------- > > Key: JBPORTAL-659 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-659 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Server > Affects Versions: 2.4 Final > Reporter: Julien Viet > -- 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 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-455) Relax portlet security roles declaration

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-455?page=all ] Julien Viet updated JBPORTAL-455: --------------------------------- Fix Version/s: (was: 2.6.Beta1) > Relax portlet security roles declaration > ---------------------------------------- > > Key: JBPORTAL-455 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-455 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Portlet > Affects Versions: 2.0 Final > Reporter: Julien Viet > > Today when a portlet uses the req.isUserInRole(String roleName), this role must be declared in the portlet.xml otherwise the method returns false. > <portlet> > ... > <security-role-ref> > <role-name>Admin</role-name> > </security-role-ref> > ... > </portlet> > This is what the portlet spec tells to do. > But it could be possible to avoid this declaration and let all the role checks pass through and delegate the call to the servlet container when configuring jboss portal > in a certain mode (at server level or webapp level) -- 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 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-880) Move PortalDeployment classes to JBoss XB

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-880?page=all ] Julien Viet updated JBPORTAL-880: --------------------------------- Fix Version/s: (was: 2.6.Beta1) > Move PortalDeployment classes to JBoss XB > ----------------------------------------- > > Key: JBPORTAL-880 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-880 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.2.1 Final > Reporter: Chris Laprun > Assigned To: Chris Laprun > Priority: Minor > Original Estimate: 3 days > Time Spent: 5 hours > Remaining Estimate: 2 days, 3 hours > > Portal deployment files are currently "manually" parsed via the common.util.XML class. Leveraging JBoss XB should allow for easier maintenance and possibly speed. -- 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 months

1
0
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 February 2007