June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1192) Hiding old versions of documents

by Nils Kassube (JIRA)

Hiding old versions of documents --------------------------------- Key: JBPORTAL-1192 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1192 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4.1 Final Reporter: Nils Kassube Assigned To: Roy Russo To improve usability it's a good idea to hide old versions of a document, e.g. using paging or a "More versions..." link. Currently you have to export and import stuff to get rid of the distracting display of dozens of old versions. -- 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, 5 months

6
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1283) "Powered by JBoss" overlayed on lower column headers in CMS Admin portlet

by oberiko (JIRA)

"Powered by JBoss" overlayed on lower column headers in CMS Admin portlet ------------------------------------------------------------------------- Key: JBPORTAL-1283 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1283 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.4.1 SP1 Environment: Windows XP SP2, JBoss Portal 2.4.1-GA (default bundled installation w/ JBoss AS), Firefox 2.0.0.1, screen resolution 1280 x 1024 Reporter: oberiko Assigned To: Julien Viet The CMS Admin portlet has the "Powered by JBoss Portal" text in the same location (overlayed) with the lower column headers (action, name, type, created, etc.). This is on starting JBoss Portal for the first time, so the CMS Admin portlet is empty. -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1176) Error Displaying Flash in JBoss Portal 2.4.1.CR2

by Mitch De Felice (JIRA)

Error Displaying Flash in JBoss Portal 2.4.1.CR2 ------------------------------------------------ Key: JBPORTAL-1176 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1176 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.4.1 SP1 Environment: Release ID: JBoss [Zion] 4.0.5.GA Home Dir: E:\Apache Group\jboss-portal-2.4.1-CR2 Java version: 1.4.2_09,Sun Microsystems Inc. Java VM: Java HotSpot(TM) Server VM 1.4.2_09-b05,Sun Microsystems Inc. OS-System: Windows 2000 5.0,x86 Database: Oracle 9i Reporter: Mitch De Felice Assigned To: Julien Viet I'm having two problems with running the flash plugin in Jboss Portel window. 1. When I try to set the height and width on the object tag to a 100%, the window goes totally blank, like I didn't have any statements in the jsp. However, if I set the width="100%" and set a specific height="450" the flash plugin will be displayed. <center> <object width="100%" height="100%"> <param name="movie" value="<%= request.getAttribute("flashurl") %>"/> <embed src="<%= request.getAttribute("flashurl") %>" width="100%" height="100%"/> </object> </center> 2. The second problem that I'm seeing when trying to view a flash plungin in a Portlet Window is when I specify the classid on the object tag, the footer of the Portlet Window gets clipped off. <center> <object width="100%" height="455" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" > <param name="movie" value="<%= request.getAttribute("flashurl") %>"/> <embed src="<%= request.getAttribute("flashurl") %>" width="100%" height="455"/> </object> </center> I need to specify the classid so as the flash plugin can make an Ajax call back into the server. -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-661) Security: Deploying a bean without mandatory org.jboss.ejb3.security.SecurityDomain results in a NullPointerException

by Galder Zamarreno (JIRA)

Security: Deploying a bean without mandatory org.jboss.ejb3.security.SecurityDomain results in a NullPointerException --------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-661 URL: http://jira.jboss.com/jira/browse/EJBTHREE-661 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: EJB 3.0 RC7 - FD Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Fix For: EJB 3.0 RC9 - FD When setting up security in a EJB3 bean, it is mandatory adding the org.jboss.ejb3.security.SecurityDomain tag. Failure to do so results on a NullPointerException. AS should log a more meaningful message rather than a NullPointerException. -- 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, 5 months

6
11
0 / 0

[JBoss JIRA] Created: (JBAS-3540) Streamable based serialization for HAPartitionImpl

by Brian Stansberry (JIRA)

Streamable based serialization for HAPartitionImpl -------------------------------------------------- Key: JBAS-3540 URL: http://jira.jboss.com/jira/browse/JBAS-3540 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 JGroups has some utility functions that optimize serialization of its classes that implement its Streamable interface. But, HAPartitionImpl has to bypass those opimizations due to the need to use MarshalledValueInputStream. We should look into adding similar optimizations into a Marshaller for HAPartitionImpl. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (HIBERNATE-52) HibernateMBean.SecondLevelCacheEnabled attribute ignored

by Steve Ebersole (JIRA)

HibernateMBean.SecondLevelCacheEnabled attribute ignored -------------------------------------------------------- Key: HIBERNATE-52 URL: http://jira.jboss.com/jira/browse/HIBERNATE-52 Project: Hibernate Issue Type: Bug Reporter: Steve Ebersole Assigned To: Steve Ebersole Thats because transferSettings() ignores it when transferring the properties to the Configuration. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4215) Need to externalize the web container class loader to use outside of the web container

by Scott M Stark (JIRA)

Need to externalize the web container class loader to use outside of the web container -------------------------------------------------------------------------------------- Key: JBAS-4215 URL: http://jira.jboss.com/jira/browse/JBAS-4215 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services, Web (Tomcat) service Reporter: Scott M Stark Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta3 We need a WarClassLoadingDeployer that allows for the creation of the web container class loader during the DeploymentUnit processing based on the class loading metadata. In the absence of jboss UCL or osgi bundle metadata, this should create the standard tomcat war first class loader. Not having this at the DeploymentUnit level does not allow other deployers to interact with war deployments properly. -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3883) JBoss ignores "Class-Path" attribute in WAR's MANIFEST.MF

by Amit Kasher (JIRA)

JBoss ignores "Class-Path" attribute in WAR's MANIFEST.MF --------------------------------------------------------- Key: JBAS-3883 URL: http://jira.jboss.com/jira/browse/JBAS-3883 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading, Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Amit Kasher Assigned To: Scott M Stark An EAR file that deploys well in JBoss4.0.5 fails to deploy in JBoss5.0Beta1 when initializing the web application (NoClassDefFound). However, this ear does deploy well when taking the required jar files (the WAR dependencies) out of the EAR and placing them inside the .war/WEB-INF/lib folder, as well as removing the "Class-Path" entry in the WAR's MANIFEST.MF. Documents stating, as far as I understand, the existence of the requirement that this should work are here: http://java.sun.com/j2ee/verified/packaging.html ... as well as in the spec ... (http://jcp.org/en/jsr/detail?id=244) in section EE.8.2.1 (Bundled Libraries) starting in page 155. It's related to Tomcat's classpath (or to the classpath augmentation JBoss performs, where there were probably recent changes to support resource injection into web clients, like servlets). This is why I indicated Tomcat as an additional affected component. -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4333) JBoss DD shemas should use a jboss specific namespace

by Thomas Diesler (JIRA)

JBoss DD shemas should use a jboss specific namespace ----------------------------------------------------- Key: JBAS-4333 URL: http://jira.jboss.com/jira/browse/JBAS-4333 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossAS-5.0.0.CR1 Curently the documentation for jboss_5_0.xsd reads This is the XML Schema for the JBoss 5.0 deployment descriptor. The deployment descriptor must be named "META-INF/jboss.xml" in the EJB's jar file. All EJB deployment descriptors must indicate the JBoss schema by using the Java EE namespace: http://www.jboss.org/j2ee/schema and by indicating the version of the schema by using the version element as shown below: <jboss xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.org/j2ee/schema http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" version="5.0"> ... </jboss> The instance documents may indicate the published version of the schema using the xsi:schemaLocation attribute for the Java EE namespace with the following location: http://www.jboss.org/j2ee/schema/jboss_5_0.xsd Note, that the default namespace for element is http://java.sun.com/xml/ns/javaee, which is IMHO incorrect. This is the namespace reserved for standard JavaEE5 elements -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4306) Invalid invoker mbean names in standardjboss.xml

by Scott M Stark (JIRA)

Invalid invoker mbean names in standardjboss.xml ------------------------------------------------ Key: JBAS-4306 URL: http://jira.jboss.com/jira/browse/JBAS-4306 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 The following invoker-proxy-binding is useless in terms of defining the invoker-mbean such that it can be used as a ejb container dependency: <invoker-proxy-binding> <name>message-driven-bean</name> <invoker-mbean>default</invoker-mbean> <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory> <proxy-factory-config> <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI> <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI> <CreateJBossMQDestination>false</CreateJBossMQDestination>  <MinimumSize>1</MinimumSize> <MaximumSize>15</MaximumSize> <KeepAliveMillis>30000</KeepAliveMillis> <MaxMessages>1</MaxMessages> <MDBConfig> <ReconnectIntervalSec>10</ReconnectIntervalSec> <DLQConfig> <DestinationQueue>queue/DLQ</DestinationQueue> <MaxTimesRedelivered>10</MaxTimesRedelivered> <TimeToLive>0</TimeToLive> </DLQConfig> </MDBConfig> </proxy-factory-config> </invoker-proxy-binding> Either there should be an mbean representing the state of the default invoker, or the mdb invoker config specified in another way such that dependencies can be configured. -- 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, 5 months

2
2
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 June 2007