December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBFORUMS-259) Actions in admin panel no longer work

by Ryszard Kozmik (JIRA)

Actions in admin panel no longer work ------------------------------------- Key: JBFORUMS-259 URL: http://jira.jboss.com/jira/browse/JBFORUMS-259 Project: JBoss Forums Issue Type: Bug Components: Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC, 1.1.0 Alpha Something caused that all actions in admin panel don't work. Additionally, some of jsf actions should be moved to jsf events to make the code look and work better. -- 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, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4148) Replace Gjt code used in the ejb 2.x validation phase

by Fernando Nasser (JIRA)

Replace Gjt code used in the ejb 2.x validation phase ----------------------------------------------------- Key: JBAS-4148 URL: http://jira.jboss.com/jira/browse/JBAS-4148 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Fernando Nasser Fix For: JBossAS-4.2.1.CR1 The JBossAS thirdpart-build.xml grabs a <componentref name="gjt-jpl-util" version="1.0"/> from repository.jboss.com However, the Gjt project has never released a 1.0 version, only a 0.6 version for the Linffors utils and the jpl_util_0_6 is the only tag in their CVS. So, what is the meaning for version 1.0? The CVS tip? Also, what is marked as gjt-jpl-util also contains gjt-jpl-pattern, and the latest CVS tag for that is: jpl-pattern_0_3_b (0.3 beta perhaps) Besides, there is a warning in the pattern source directory: "Untagged files may be (and probably are) in an unstable state and might not compile. If you want something that works, checkout with tags. You have been warned. :) -- Juha" Here, for the record, is Scott's opinion: Scott M Stark wrote: > This is some ancient code used only in the ejb 2.x validation phase. It > has not been touched in something like 5 years. Either we need to > replace it or pull together some code that makes up a usable release. -- 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, 12 months

4
20
0 / 0

[JBoss JIRA] Created: (JBRULES-1375) remove backdated concurrency classes, now that we are jdk1.5+

by Mark Proctor (JIRA)

remove backdated concurrency classes, now that we are jdk1.5+ ------------------------------------------------------------- Key: JBRULES-1375 URL: http://jira.jboss.com/jira/browse/JBRULES-1375 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 4.0.4 -- 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, 12 months

1
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1688) Maven module template

by Julien Viet (JIRA)

Maven module template --------------------- Key: JBPORTAL-1688 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1688 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Julien Viet Assigned To: Wesley Hales Fix For: 2.8 Final -- 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, 12 months

3
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-177) Merge the unified metadata work

by Scott M Stark (JIRA)

Merge the unified metadata work ------------------------------- Key: JBMICROCONT-177 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-177 Project: JBoss MicroContainer Issue Type: Task Components: MetaData Reporter: Scott M Stark Need to merge the unified metadata work so we can start integrate it into the deployers. -- 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, 12 months

5
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1745) DTD documentation is out of date

by Chris Laprun (JIRA)

DTD documentation is out of date -------------------------------- Key: JBPORTAL-1745 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1745 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun This applies to the actual documentation in the DTD but also to the DTD documentation in the reference guide. -- 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, 12 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1462) Documentation should include a section on how to remove/destroy created objects via the Admin GUI

by Chris Laprun (JIRA)

Documentation should include a section on how to remove/destroy created objects via the Admin GUI ------------------------------------------------------------------------------------------------- Key: JBPORTAL-1462 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1462 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6.CR2 Reporter: Chris Laprun Assigned To: Julien Viet Fix For: 2.6 Final -- 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, 12 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1841) URL hacking allows edit mode in weather portlet

by Prabhat Jha (JIRA)

URL hacking allows edit mode in weather portlet ----------------------------------------------- Key: JBPORTAL-1841 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1841 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.3 Final Reporter: Prabhat Jha Assigned To: Thomas Heute Priority: Critical If you are not logged in then weather portlet does not show edit icon which is good. But if I hack the URL to http://localhost:8080/portal/auth/portal/default/Weather/WeatherPortletWi..., I am able to get into edit mode and change the zip code. Is this how it supposed to be? Sohil suggests: "no it shouldn't do that. Either the Edit Mode logic of the Portlet should protect against this (a bit painful design), or Portal's security layer should have the granularity to provide role-based protection of the "Edit Mode" of Portlets as a cross cutting aspect. I like the second option better personally" -- 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, 12 months

2
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1521) Missing documentation on properties?

by Chris Laprun (JIRA)

Missing documentation on properties? ------------------------------------ Key: JBPORTAL-1521 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1521 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6 Final Reporter: Chris Laprun Assigned To: Julien Viet Fix For: 2.6.1 Final -- 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, 12 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-4725) Upgrade Hibernate to 3.3.x (from 3.2.4.SP1_CP01)

by Dimitris Andreadis (JIRA)

Upgrade Hibernate to 3.3.x (from 3.2.4.SP1_CP01) ------------------------------------------------ Key: JBAS-4725 URL: http://jira.jboss.com/jira/browse/JBAS-4725 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Hibernate service Reporter: Dimitris Andreadis Assigned To: Steve Ebersole Fix For: JBossAS-5.0.0.CR1 An issue to track the hibernate upgrade needed by JBoss Cache. Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0 (JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and include it in the hibernate-int module. I'm currently working with Steve on a *much* improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have AS 5 use that." -- 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

17 years

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 December 2007