jboss-jira July 2008

jboss-jira@lists.jboss.org

1 participants
2084 discussions

[JBoss JIRA] Created: (JBPORTAL-2016) CMS content object should have a method to return the size of the latest version of the file

by Martin Putz (JIRA)

CMS content object should have a method to return the size of the latest version of the file -------------------------------------------------------------------------------------------- Key: JBPORTAL-2016 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2016 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.5 Final Reporter: Martin Putz Assigned To: Sohil Shah I'd like to suggest that the File object (org.jboss.portal.cms.model.Content) should also have a method to return the size of the latest version of the file. It seems to have methods to return other information about the latest version (last update time), so I'm a little unclear as to why I'd need to retrieve the content in order to determine the file size. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-169) Add support for setting the SchemaValidation usage to ObjectModelFactoryDeployer

by Scott M Stark (JIRA)

Add support for setting the SchemaValidation usage to ObjectModelFactoryDeployer -------------------------------------------------------------------------------- Key: JBMICROCONT-169 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-169 Project: JBoss MicroContainer Issue Type: Feature Request Components: Deployment Reporter: Scott M Stark Assigned To: Scott M Stark To address JBAS-4193, the ObjectModelFactoryDeployer needs a flag controlling the Unmarshaller.SchemaValidation behavior. -- 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, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1946) Fix Localized displayName

by Thomas Heute (JIRA)

Fix Localized displayName ------------------------- Key: JBPORTAL-1946 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1946 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Reporter: Thomas Heute Assigned To: Julien Viet Fix For: 2.7 Final org.jboss.portal.core.model.instance.metadata.InstanceMetaData Parts related to localized display names have been broken during the migration -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-857) Deal with non standard Locales better

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-857?page=all ] Chris Laprun resolved JBPORTAL-857. ----------------------------------- Resolution: Done > Deal with non standard Locales better > ------------------------------------- > > Key: JBPORTAL-857 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-857 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final > Reporter: Chris Laprun > Assigned To: Chris Laprun > Priority: Minor > Fix For: 2.6.6 Final, 2.7 Final > > Original Estimate: 3 hours > Time Spent: 1 hour > Remaining Estimate: 2 hours > > Per the WSRP Spec regarding UnsupportedLocale fault: > The Portlet does not support generating markup for the requested locale. Since the Portlet is not required to generate markup in the requested locale, a Portlet returning this fault message is indicating that it processes locales in a stricter manner and has no markup for the requested locales. The Consumer can treat this as a specialization of the OperationFailed fault message and does not have to retry getting the markup in other locales. > Currently, LocaleInfo throws an IllegalArgumentException if the locale is not standard which gets wrapped into an OperationFailedFault at the handler level. We should deal with locale errors better and maybe be more lenient as to what we accept. -- 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, 6 months

1
0
0 / 0

← Newer
1
...
206
207
208
209
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008