June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-908) Clean up DRL.g accoding to ANTLR consultancy recommendations

by Edson Tirelli (JIRA)

Clean up DRL.g accoding to ANTLR consultancy recommendations ------------------------------------------------------------ Key: JBRULES-908 URL: http://jira.jboss.com/jira/browse/JBRULES-908 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.MR2 Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 4.0.0.MR3 Fix DRL.g grammar as per ANTLR consultancy recommendations. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1474) Portal Page "view" and "viewrecursive" are equivilent.

by Andrew Oliver (JIRA)

Portal Page "view" and "viewrecursive" are equivilent. -------------------------------------------------------- Key: JBPORTAL-1474 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1474 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Security Affects Versions: 2.4.1 SP1 Reporter: Andrew Oliver Assigned To: Julien Viet Create a Page, set that page to no unchecked actions and user "view". Add a CMSPortlet instance called whatever you like. Set that instance on the page to no permissions or only admin view. Log in as a plain user. The user can see the portlet if he can see the page even though the page is view and he has no permission to view that particular portlet. Thus it is not clear how you'd secure an individual portlet independent of page security. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1471) portlets overlap in dashboard

by Prabhat Jha (JIRA)

portlets overlap in dashboard ----------------------------- Key: JBPORTAL-1471 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1471 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6 Final Reporter: Prabhat Jha Assigned To: Julien Viet Fix For: 2.6 Final Codebase: Portal trunk as of June 1, 2007 1. Login as admin 2. Go to dashboard 3. Swap Greetings place and CMS portlet ( I think that's what it is, if not then it's guy with binocular portlet :-)) 4. These portlets overlap. I verified both in IE6 and the latest Firefox 1.5 Attached is the screen shot. -- 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, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1371) issue with creating consumer from WSDL

by Prabhat Jha (JIRA)

issue with creating consumer from WSDL -------------------------------------- Key: JBPORTAL-1371 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1371 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.CR2 Reporter: Prabhat Jha Assigned To: Chris Laprun Two issues: 1. I was not able to create consumer using http://wsrp.bea.com:7001/producer/producer?WSDL. Validate throws error. ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/portal-wsrp]] Root cause java.lang.NullPointerException at org.jboss.portal.wsrp.admin.ui.ConsumerBean.getProducerInfo(ConsumerBean.java:174) at org.jboss.portal.wsrp.admin.ui.ConsumerBean.isUseWSDL(ConsumerBean.java:65) at sun.reflect.GeneratedMethodAccessor517.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) 2. If for some reason creating a consumer fails (mine failed when I tried to create using bea's WSDL http://wsrp.bea.com:7001/producer/producer?WSDL), I can not see WSRP page correctly. Meaning when I click on WSRP, i see this message: /WEB-INF/jsf/consumers/editConsumer.xhtml @55,45 test="#{consumer.useWSDL}" /WEB-INF/jsf/consumers/editConsumer.xhtml @55,45 test="#{consumer.useWSDL}": Exception getting value of property useWSDL of base of type : org.jboss.portal.wsrp.admin.ui.ConsumerBean I was still hoping to see original GUI. -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Updated: (JBAS-4465) Rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4465?page=all ] Adrian Brock updated JBAS-4465: ------------------------------- Fix Version/s: JBossAS-5.0.0.Beta3 JBossAS-4.0.5.SP1 I've updated the comment to read as follows:            > Rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml > -------------------------------------------------------------- > > Key: JBAS-4465 > URL: http://jira.jboss.com/jira/browse/JBAS-4465 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.2.0.GA > Reporter: Rajesh Rajasekaran > Assigned To: Adrian Brock > Fix For: JBossAS-4.0.5.SP1 , JBossAS-4.2.1.CR1, JBossAS-5.0.0.Beta3 > > > We should rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml as this is not specific to HSQLDB and works with all the other 8 DB's certified with the platform release. > Also the comment is misleading, as we dont have JBossMQ State Management configurations for other db's under docs/examples/jms >  >  >  >  > The docs team also wanted this change to avoid any confusion. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-4465) Rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4465?page=all ] Adrian Brock updated JBAS-4465: ------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=110226 As described on the attached forums post, my vote is against it. The issue is more subtle than described. The comment at the top of the file does not changing to indicate that the file is generic and that there are no alternate configs in docs/examples/jca > Rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml > -------------------------------------------------------------- > > Key: JBAS-4465 > URL: http://jira.jboss.com/jira/browse/JBAS-4465 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.2.0.GA > Reporter: Rajesh Rajasekaran > Assigned To: Adrian Brock > Fix For: JBossAS-4.2.1.CR1 > > > We should rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml as this is not specific to HSQLDB and works with all the other 8 DB's certified with the platform release. > Also the comment is misleading, as we dont have JBossMQ State Management configurations for other db's under docs/examples/jms >  >  >  >  > The docs team also wanted this change to avoid any confusion. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-4465) Rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4465?page=all ] Adrian Brock moved JBPAPP-209 to JBAS-4465: ------------------------------------------- Project: JBoss Application Server (was: Jboss Enterprise Platform App Edition) Key: JBAS-4465 (was: JBPAPP-209) Fix Version/s: JBossAS-4.2.1.CR1 (was: 4.2.RC6) Affects Version/s: JBossAS-4.2.0.GA (was: 4.2.RC5) > Rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml > -------------------------------------------------------------- > > Key: JBAS-4465 > URL: http://jira.jboss.com/jira/browse/JBAS-4465 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.2.0.GA > Reporter: Rajesh Rajasekaran > Assigned To: Adrian Brock > Fix For: JBossAS-4.2.1.CR1 > > > We should rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml as this is not specific to HSQLDB and works with all the other 8 DB's certified with the platform release. > Also the comment is misleading, as we dont have JBossMQ State Management configurations for other db's under docs/examples/jms >  >  >  >  > The docs team also wanted this change to avoid any confusion. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-4465) Rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4465?page=all ] Adrian Brock updated JBAS-4465: ------------------------------- Issue Type: Feature Request (was: Task) Component/s: JMS service > Rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml > -------------------------------------------------------------- > > Key: JBAS-4465 > URL: http://jira.jboss.com/jira/browse/JBAS-4465 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.2.0.GA > Reporter: Rajesh Rajasekaran > Assigned To: Adrian Brock > Fix For: JBossAS-4.2.1.CR1 > > > We should rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml as this is not specific to HSQLDB and works with all the other 8 DB's certified with the platform release. > Also the comment is misleading, as we dont have JBossMQ State Management configurations for other db's under docs/examples/jms >  >  >  >  > The docs team also wanted this change to avoid any confusion. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-107) The different types of classloader integration for AOP belong in the related release not jboss-head

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-107?page=all ] Kabir Khan updated JBAOP-107: ----------------------------- Fix Version/s: 2.0.0.alpha5 > The different types of classloader integration for AOP belong in the related release not jboss-head > --------------------------------------------------------------------------------------------------- > > Key: JBAOP-107 > URL: http://jira.jboss.com/jira/browse/JBAOP-107 > Project: JBoss AOP > Issue Type: Task > Affects Versions: 2.0.0.alpha4 > Reporter: Adrian Brock > Assigned To: Kabir Khan > Priority: Minor > Fix For: 2.0.0.alpha5 > > > The JBoss classloading integration with JBossAOP should be managed by JBoss release, > not by the aop/aspects modules in jboss-head. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JBAOP-107) The different types of classloader integration for AOP belong in the related release not jboss-head

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-107?page=comments#action_12364240 ] Kabir Khan commented on JBAOP-107: ---------------------------------- Too late (probably) to be done for AS 4.0.x, but should certainly be done for 4.2.x and 5 > The different types of classloader integration for AOP belong in the related release not jboss-head > --------------------------------------------------------------------------------------------------- > > Key: JBAOP-107 > URL: http://jira.jboss.com/jira/browse/JBAOP-107 > Project: JBoss AOP > Issue Type: Task > Affects Versions: 2.0.0.alpha4 > Reporter: Adrian Brock > Assigned To: Kabir Khan > Priority: Minor > > The JBoss classloading integration with JBossAOP should be managed by JBoss release, > not by the aop/aspects modules in jboss-head. -- 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, 1 month

1
0
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