May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-609) Decide the way to go forward (with or without Remoting)

by Ovidiu Feodorov (JIRA)

Decide the way to go forward (with or without Remoting) ------------------------------------------------------- Key: JBMESSAGING-609 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-609 Project: JBoss Messaging Issue Type: Task Components: JMS Remoting Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.Alpha2 Conclude the http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971228 discussion thread and make a decision on how to go further: 1. Modify Remoting to include Messaging-specific requirements (asynchronicity, AMQP, etc) 2. Implement our own remoting solution. -- 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
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-848) Shutting down messaging with JBoss 4.0.3SP1 standalone fails

by Ovidiu Feodorov (JIRA)

Shutting down messaging with JBoss 4.0.3SP1 standalone fails ------------------------------------------------------------ Key: JBMESSAGING-848 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-848 Project: JBoss Messaging Issue Type: Bug Components: AS Integration Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical -- 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
6
0 / 0

[JBoss JIRA] Created: (JBFORUMS-213) Change UserProfileView

by Ryszard Kozmik (JIRA)

Change UserProfileView ---------------------- Key: JBFORUMS-213 URL: http://jira.jboss.com/jira/browse/JBFORUMS-213 Project: JBoss Forums Issue Type: Sub-task Components: Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC UserProfileView has to be rewritten to new design. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBAS-4442) Need to update exception handling code in HypersonicDatabase.java

by Deepak Bhole (JIRA)

Need to update exception handling code in HypersonicDatabase.java ----------------------------------------------------------------- Key: JBAS-4442 URL: http://jira.jboss.com/jira/browse/JBAS-4442 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.2.0.GA Reporter: Deepak Bhole Assigned To: Deepak Bhole HypersonicDatabase.java has code to handle a headless exception, but it cannot detect it when the headless exception is wrapped inside an invocation target exception. The reason this needs to be remedied is because the manager is launched via reflection, and any headless exception from therein will always be wrapped inside an invocation target exception. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1402) First Pass Management Portlet Improvements

by Julien Viet (JIRA)

First Pass Management Portlet Improvements ------------------------------------------ Key: JBPORTAL-1402 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1402 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.CR2 Reporter: Julien Viet Fix For: 2.6 Final Management Portlet The page that houses the management portlet called "Home" has the Pages portlet on it as well. This portlet is redundant since it just repeats what is in the navigation tabs. It should be removed. Consider using icon images (with alt attributes set to the name of the function) for actions in the lists in this portlet. Portal Objects Portal List Screen Label "Creating a portal" is above the field it is associated with. This label should be to the left of the field. Page List Screen The "Create a nested page:" label should be changed to "Create a Page:" The text box to create a page, and the drop-down list below it should be left aligned in the same column. Portlet Window List Screen The text box for creating a nested page, and the drop-down list for the default page should be left aligned in the same column. Portlet Window Details Screen When clicking on the Window Name of a portlet window, the user is taken to a screen showing a list of portlet Instances, but the current portlet instance is not shown. The current portlet instance should be the default selected item in the list. The Portlet Instance list should have a field label describing what it is. Perhaps "Portlet Instance used by this window:". Clicking the "Select" button shows the same result as clicking the "Info" button, but no feed back is given to the user that they have updated the portlet instance that the portlet window is using. Clicking the "Select" button should change the screen back to the Portlet Window List screen. Wizard Mode On the final screen of the wizard, the "confirm" and "cancel" buttons should be on the same horizontal line as the "previous" button, but separated by more space than between the "previous" and "next" buttons on the previous pages. The buttons should have as much spacing between them as all the other steps int the wizard. The "Step" panels at the top of each of the wizard pages should be clickable so that the user can get back to any point in the wizard. In Step 5 "Confirm", the field labels should be bolded, there should be a colon after each field label, and the field data should be left aligned in a single column (this alignment may already be there, but I couldn't be sure) In Step 3 "Select Page" of the wizard, the table that contains the portal regions should be extended to fill the width of the portlet, as with all the other tables in the portlet. The "Sub-Pages" function should be left aligned in the cell. In Step 1 "Select Portlet" of the wizard, the "Next" button should be disabled until a portlet has been selected. In Step 2 "Select Portal", the "Previous" button should have the same padding as the "Next" button. Security * The security screen on any portal object should have the table of permissions replaced with a table of checkboxes, but the permission label at the top of each column, and the roles at the leftmost column should have the word "Role" removed and placed at the top of the column. The table should be styled similarly to the other tables in the management portlet. The "Update" and "Cancel" buttons should be moved to the left side of the portlet, sized, padded, and spaced similar to the rest of the buttons in the portlet. After applying security settings, there is a message displayed at the top of the resulting view in the portlet. This message should be bolded, and it's size increased. When clicking on the security action for an item not in the current context, subsequently clicking cancel should return the user to the parent context. For example, if a user selects the default portal, then clicks the security link from the default page from within the default portal details page, they are presented with a security screen for the default page. But when the user clicks cancel, they are sent to the default page detailed view, instead of being sent back to the page they came from, as would be expected. Properties In the "Properties" screen for a portal instance, the style on the predefined property drop-down list doesn't match the style of any of the other drop-down lists in the portlet. The "Properties" screen for portal objects should have a "Cancel" button. The "Properties" screen should align the "Add Property" button to the left side of the portlet. If there are no remaining predefined properties to add to a portal object in the "Properties" screen, the predefined property field and its label should be hidden. The label for the custom property field should be changed to read "Custom Property Name:" The border around the predefined and custom property fields should be removed. Theme In the "Theme" screen for a portal object, the border and "Theme Properties" label should be removed. The "Update" and "Cancel" buttons in the "Theme" screen should be left aligned. The "Please set the display options for the portal: " label at the top of the screen should be replaced with the title "Theme Properties". Destroy The "Destroy" screen should show the tabs similar to the other screens in the management portlet. The "Breadcrumbs" under the WARNING message should be placed at the top of the screen, similar to other screens in the portlet. The WARNING message should be increased in size, and bolded to show its importance. The "Yes" and "No" links should be made into buttons to be consistent with the rest of the screens in the portlet. Portlet Instances In the Portlet Instance Details that show up at the bottom of the portlet when a portlet instance ID is clicked, the field data should be left aligned in a column next to the labels. The "Show the associated portlet" link should be removed, and the name in the "Portlet Name" should be a link to the associated portlet definition instead. If the portlet instance has no Preferences, do not show the Preferences link for it. The "Security" and "Preferences" actions show their screens below the portlet instance list, which is inconsistent with the action screens in the Portlet Objects section. The action screens should be shown and the list hidden, or the action screens in the Portlet Objects portion of the portlet should operate like these screens. The destroy action has no confirmation screen for it. It should have a similar confirmation screen to the destroy function in the "Portal Objects" section of the portlet, with the aforementioned changes applied. Security The Security action screen should move the name of the permission up as a column header over the check boxes, and the word "Role" should be removed from each line, and moved to the top of the list as a header. This table should be made to look similar to other tables in the portlet. The "Update" and "Cancel" buttons should be left aligned in the portlet to be consistent with the rest of the buttons in the portlet. The "Update" and "Cancel" buttons should have the same padding, size, and spacing as the other buttons in the portal. Portlet Definitions Clicking the Portlet Definition ID has the same function as clicking the "Info" action link. Remove the "Info" action link. If there are no preferences defined in the portlet definition, do not display the "Preferences" action link. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1411) The text box for creating a nested page, and the drop-down list for the default page should be left aligned in the same column.

by Thomas Heute (JIRA)

The text box for creating a nested page, and the drop-down list for the default page should be left aligned in the same column. -------------------------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1411 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1411 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.CR2 Reporter: Thomas Heute 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

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1410) The text box to create a page, and the drop-down list below it should be left aligned in the same column.

by Thomas Heute (JIRA)

The text box to create a page, and the drop-down list below it should be left aligned in the same column. ---------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1410 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1410 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.CR2 Reporter: Thomas Heute Assigned To: Thomas Heute 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

19 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-913) ProcessBean.startInstance does not set ProcessInstance.key, causing second process start for any user to fail

by Kevin Klinemeier (JIRA)

ProcessBean.startInstance does not set ProcessInstance.key, causing second process start for any user to fail ------------------------------------------------------------------------------------------------------------- Key: JBPM-913 URL: http://jira.jboss.com/jira/browse/JBPM-913 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM jPDL 3.2 Reporter: Kevin Klinemeier Assigned To: Tom Baeyens The web console isn't setting the ProcessInstance.key value. This value has a unique constraint across key_ and processdefinition_ To reproduce, either: run against a non-hypersonic database and attempt to create two process instances for any one process definition. or run against hypersonic, writing data to a file. Inspect Process_Instances to see constraint violated by null, which apparently isn't caught by hypersonic. It's not clear to me how to correctly populate this field. -- 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

5
10
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1433) Clicking cancel should return the user to the parent context

by Thomas Heute (JIRA)

Clicking cancel should return the user to the parent context ------------------------------------------------------------ Key: JBPORTAL-1433 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1433 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.CR2 Reporter: Thomas Heute Assigned To: Thomas Heute Fix For: 2.6 Final When clicking on the security action for an item not in the current context, subsequently clicking cancel should return the user to the parent context. For example, if a user selects the default portal, then clicks the security link from the default page from within the default portal details page, they are presented with a security screen for the default page. But when the user clicks cancel, they are sent to the default page detailed view, instead of being sent back to the page they came from, as would be expected. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1445) The "Destroy" screen should show the tabs similar to the other screens in the management portlet.

by Thomas Heute (JIRA)

The "Destroy" screen should show the tabs similar to the other screens in the management portlet. -------------------------------------------------------------------------------------------------- Key: JBPORTAL-1445 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1445 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.CR2 Reporter: Thomas Heute Assigned To: Thomas Heute 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

19 years, 2 months

1
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 May 2007