May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1420) Portal region table should be extended

by Thomas Heute (JIRA)

Portal region table should be extended -------------------------------------- Key: JBPORTAL-1420 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1420 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 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. -- 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-1421) The "Sub-Pages" function should be left aligned in the cell.

by Thomas Heute (JIRA)

The "Sub-Pages" function should be left aligned in the cell. ------------------------------------------------------------- Key: JBPORTAL-1421 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1421 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
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1423) In Step 1 "Select Portlet" of the wizard, the "Next" button should be disabled until a portlet has been selected.

by Thomas Heute (JIRA)

In Step 1 "Select Portlet" of the wizard, the "Next" button should be disabled until a portlet has been selected. ------------------------------------------------------------------------------------------------------------------ Key: JBPORTAL-1423 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1423 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 In Step 1 "Select Portlet" of the wizard, the "Next" button should be disabled until a portlet has been selected. -- 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-1417) Wizard confirmation screen

by Thomas Heute (JIRA)

Wizard confirmation screen -------------------------- Key: JBPORTAL-1417 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1417 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 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) -- 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-1406) Management page should not contain the navigation portlet

by Thomas Heute (JIRA)

Management page should not contain the navigation portlet --------------------------------------------------------- Key: JBPORTAL-1406 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1406 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 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. -- 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-1409) The "Create a nested page:" label should be changed to "Create a Page:"

by Thomas Heute (JIRA)

The "Create a nested page:" label should be changed to "Create a Page:" ------------------------------------------------------------------------ Key: JBPORTAL-1409 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1409 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 I guess it should be "Create a page" on a portal node and "Create a nested page" or "Create a child page" on a page node -- 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-1408) Label "Creating a portal" is above the field it is associated with. This label should be to the left of the field.

by Thomas Heute (JIRA)

Label "Creating a portal" is above the field it is associated with. This label should be to the left of the field. ------------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1408 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1408 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
1
0 / 0

[JBoss JIRA] Created: (JBAS-4430) Default JNDI name for EJB2 beans no longer ejb-name

by Shelly McGowan (JIRA)

Default JNDI name for EJB2 beans no longer ejb-name --------------------------------------------------- Key: JBAS-4430 URL: http://jira.jboss.com/jira/browse/JBAS-4430 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Shelly McGowan There is a problem identified with the default JNDI names for EJB2 beans -- it breaks compatibility with older JBoss AS versions (say 4.0.x). I Basically, in the past, if you deploy an EJB2 without jboss.xml, the default JNDI name would be the value of <ejb-name>. But this is no longer the case in AS 4.2.0. The new default JNDI name for EJB2 beans is now something like: local/ chap2.EchoBean@32512809, where the number looks like a hashcode. This problem can be fixed by adding a jboss.xml file to the EJB2 application and explicitly specify the JNDI binding. The sample app is one documented in the Server Configuration Guide - Chapter 4.4 http://docs.jboss.com/jbossas/guides/j2eeguide/r2/jboss4-j2ee- examples.zip "Basically the problem is due to the EJB in question being bound into the Global JNDI tree using the name local/chap2.EchoBean@32512809, where the number looks like a hashcode. This results in the objectName for the EJB container being jboss.j2ee:jndiName=local/chap2.EchoBean@32512809,service=EJB. As the EjbMBeanAdaptor service explicitly depends on an EJB Container with objectName jboss.j2ee:service=EJB,jndiName=local/chap2.EchoBean (without the @32512809) it never starts as the dependency is not resolved so the EJB home is never cached. This explains why a NullPointerException is thrown when the echo() method is called." To reproduce, once the above is unzipped. cd examples ant -Dchap=jmx -Dex=3 run-example This deploys the archive. To run the test: go to the jmx-console http://localhost:8080/jmx-console find the service=EjbMBeanAdaptor in the jboss.book domain click on the link and scroll down to the echo operation section enter the ParamValue -echo-arg and hit invoke NPE thrown: 2007-05-18 17:56:20,204 INFO [org.jboss.book.jmx.ex3.EjbMBeanAdaptor] Begin invoke, actionName=echo 2007-05-18 17:56:20,204 INFO [org.jboss.book.jmx.ex3.EjbMBeanAdaptor] Lookup EchoLocalHome(a)local/chap2.EchoBean 2007-05-18 17:56:20,205 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console].[HtmlAdaptor]] Servlet.service() for servlet HtmlAdaptor threw exception java.lang.NullPointerException at org.jboss.book.jmx.ex3.EjbMBeanAdaptor.echo(EjbMBeanAdaptor.java:131) at org.jboss.book.jmx.ex3.EjbMBeanAdaptor.invoke(EjbMBeanAdaptor.java:284) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:258) at org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:223) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:262) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) A requiremenht of the JBEAP PRD: Customers who have deployed JBoss AS 4.0.x should be able to migrate their applications to the application platform. This means they should be able to deploy existing WARs and EARs that worked on JBoss 4.0.x to the application platform. -- 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: (JBRULES-858) legacy DRL import

by Michael Neale (JIRA)

legacy DRL import ----------------- Key: JBRULES-858 URL: http://jira.jboss.com/jira/browse/JBRULES-858 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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: (JBRULES-690) improve fron-end Standards and templates

by Fernando Meyer (JIRA)

improve fron-end Standards and templates ---------------------------------------- Key: JBRULES-690 URL: http://jira.jboss.com/jira/browse/JBRULES-690 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Fernando Meyer Assigned To: Fernando Meyer -- 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

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