February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1791) Integrate the ProducerPortletInvoker in the portlet container stack in order to be able to have one persistence manager per war file

by Julien Viet (JIRA)

Integrate the ProducerPortletInvoker in the portlet container stack in order to be able to have one persistence manager per war file ------------------------------------------------------------------------------------------------------------------------------------ Key: JBPORTAL-1791 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1791 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Portlet Reporter: Julien Viet Assigned To: 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

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1537) Migrate and refactor instance container to the portlet module

by Julien Viet (JIRA)

Migrate and refactor instance container to the portlet module ------------------------------------------------------------- Key: JBPORTAL-1537 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1537 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Portlet Reporter: Julien Viet Assigned To: Julien Viet 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

18 years, 5 months

1
1
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] Deleted: (HIBERNATE-76) Edit Launch Configuration Dialog: Browse button for project doesn't work when properties file specified

by Dima Geraskov (JIRA)

[ http://jira.jboss.com/jira/browse/HIBERNATE-76?page=all ] Dima Geraskov deleted HIBERNATE-76: ----------------------------------- > Edit Launch Configuration Dialog: Browse button for project doesn't work when properties file specified > ------------------------------------------------------------------------------------------------------- > > Key: HIBERNATE-76 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-76 > Project: Hibernate > Issue Type: Bug > Reporter: Dima Geraskov > Assigned To: Dima Geraskov > -- 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

1
0
0 / 0

[JBoss JIRA] Created: (HIBERNATE-76) Edit Launch Configuration Dialog: Browse button for project doesn't work when properties file specified

by Dima Geraskov (JIRA)

Edit Launch Configuration Dialog: Browse button for project doesn't work when properties file specified ------------------------------------------------------------------------------------------------------- Key: HIBERNATE-76 URL: http://jira.jboss.com/jira/browse/HIBERNATE-76 Project: Hibernate Issue Type: Bug Reporter: Dima Geraskov Assigned To: Dima Geraskov -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1525) RichFaces : finish integration : features, examples...

by Antoine Herzog (JIRA)

RichFaces : finish integration : features, examples... ------------------------------------------------------ Key: JBPORTAL-1525 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1525 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.6 CR3 Environment: JBoss Portal 2.6CR3 (on a JBoss AS 4.0.5) Rich Faces 3.0.0 and 3.0.2 (fixed version) Reporter: Antoine Herzog Assigned To: Julien Viet RichFaces has provided a sample application to work in a JBoss Portal Portlet. There was quiet a lot of tuning and adaptation (RichFaces side only ?). It seems that it work with the JBoss Portal 2.6.0 as released. But they may be some things to do in JBoss Portal side. - Use of RichFaces for admin portlets etc... (as it is now inside JBoss products) - At least, integrate a sample RichFaces Portlet, to show how nice it is, and how it works etc... -- 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

5
14
0 / 0

[JBoss JIRA] Created: (JGRP-654) Scheduler thread goes in infinite loop after getting interrupted by the priority task

by vivek v (JIRA)

Scheduler thread goes in infinite loop after getting interrupted by the priority task ------------------------------------------------------------------------------------- Key: JGRP-654 URL: http://jira.jboss.com/jira/browse/JGRP-654 Project: JGroups Issue Type: Bug Affects Versions: 2.6.1 Environment: Linux, JGroups v. 2.6.1 Reporter: vivek v Assigned To: Bela Ban This seems like a bug in Scheduler class. The scheduler thread goes into infinite loop and never recovers after being interrupted by the priority task (upon deadlock detection). Here is what I think happens (with both deadlock_detection and concurrent_processing enabled for RpcDispatcher), 1) The tasks are added to the Scheduler Queue 2) If the deadlock_detection is turned on and there is a kind of deadlock (2-way method calls) the RequestCorrelator.receiveMessage() calls scheduler.addPrio(req) method 3) The addPrio(Runnable task) method adds the priority task to the head of the queue and calls the interrupt method on the Scheduler thread. 4) In the run() method of Scheduler we peek the queue, take the task from head and run it 5) "sched_thread.isInterrupted()" in the run method returns true and throws InterruptedException 6) Since, interrupted exception is thrown we bypass the "queue.removeElement(current_task)" - and the task is not removed from the queue. 7) The catch block of InterruptedException sets the current_task.suspended=true, but never resets the interrupt flag 8) Now we keep going through the same loop for the same task in the queue in the run() method as we never resets the interrupt flag. I hope this is a correct diagnosis of this "TimeoutException" problem we have been seeing for last 2-3 months. I'm not sure if there are some nested Rpc calls in our system, but with deadlock-detection turned on they should be resolved. As tasks are never moved out of the queue, all the tasks just keep adding up (I see my queue over 2300 elements) and thus, we get TimeoutException for all the incoming calls. I think we need to call "sched_thread.interrupted()" in the InterruptedException catch block so we can remove items from the queue as we process them. I've tried with this change (added Thread.interrupted at the end of InterruptedException catch block) in my local jgroups-all.jar and it seems to work fine for a long time now (3-4 hours, earlier it used to fail within 2 hours). I haven't found any workaround for this problem if the deadlock detection logic is exercised. -- 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
5
0 / 0

[JBoss JIRA] Closed: (JBSER-81) Enable Ghost Constructors for NonSerializableClasses

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBSER-81?page=all ] Clebert Suconic closed JBSER-81. -------------------------------- Resolution: Rejected It would be possible to build new Objects that don't have a constructor, but that is way too dangerous... so I'm not doing it. Suppose you have an Object, using some JNI code, with long pointers or File resources. If you instantiate that Object, some of the properties required by the JNI layer will cause a core dumped, or GPF on the JVM. I have seen this on my tests while instantiating Sockets... So, this is just too dangerous to be used. If you don't have a default Constructor, and if the class it's not serializable, that just mens you can't instantiate it without a known constructor. > Enable Ghost Constructors for NonSerializableClasses > ---------------------------------------------------- > > Key: JBSER-81 > URL: http://jira.jboss.com/jira/browse/JBSER-81 > Project: JBoss Serialization > Issue Type: Feature Request > Reporter: Clebert Suconic > Assigned To: Clebert Suconic > Fix For: 1.1.0 Beta > > > We need a way to create NonSerializableClasses without a default constructor, by using the GhostCosntructor Feature. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-240) Handle Spring specific interfaces

by Ales Justin (JIRA)

Handle Spring specific interfaces --------------------------------- Key: JBMICROCONT-240 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-240 Project: JBoss MicroContainer Issue Type: Sub-task Components: Kernel Affects Versions: JBossMC-2.0.0.Beta10 Reporter: Ales Justin Assigned To: Ales Justin Priority: Minor Fix For: JBossMC-2.0.0.CR1 Make MC to be Spring BeanNameAware. Doing this in a generic way, being able to handle all different specific interfaces or special bean treatment (e.g. method override). The code should still be Spring library unaware. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2008