September 2010 - embjopr-issues - Jboss List Archives

[JBoss JIRA] Created: (EMBJOPR-101) Nav tree JS object (Tree.Item) is not ready after page refresh, causing ScriptException: TypeError: Cannot call method "fireExpansionEvent"

by Ondrej Žižka (JIRA)

Nav tree JS object (Tree.Item) is not ready after page refresh, causing ScriptException: TypeError: Cannot call method "fireExpansionEvent" ------------------------------------------------------------------------------------------------------------------------------------------- Key: EMBJOPR-101 URL: https://jira.jboss.org/jira/browse/EMBJOPR-101 Project: Embedded Jopr Issue Type: Task Reporter: Ondrej Žižka Right after page is loaded and test thread is running, JavaScript function object `Tree.Item` is not initialized yet. This function is created in an externally loaded file, admin-console/a4j/g/3_3_0.GAorg/richfaces/renderkit/html/scripts/tree-item.js . This problem appears when we click() in tests on some tree node after page load. It is unlikely that user will be clicking fast enough to trigger this error, moreover IMHO Firefox blocks JS execution until external JS files are all loaded (but not sure), so this is only problem for QA. Currently we solve this by calling NavTree#waitUntilReady( int intervalMs, int retries ) - e.g. in getNavTreeArrow(): ejtt.navTree.waitUntilReady(100, 15); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (EMBJOPR-321) withdrawing EMBJOPR-182

by y y (JIRA)

withdrawing EMBJOPR-182 ----------------------- Key: EMBJOPR-321 URL: https://jira.jboss.org/browse/EMBJOPR-321 Project: Embedded Jopr Issue Type: Task Components: Look 'n' Feel (html/css) Reporter: y y For several reasons, I need to withdraw the following patch: https://jira.jboss.org/browse/EMBJOPR-182 Please remove the change from the upstream code and further releases. Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
8
0 / 0

[JBoss JIRA] Resolved: (EMBJOPR-302) EWP AS console: Hide JMS and EJB 2.0 nodes

by Ondrej Zizka (JIRA)

[ https://jira.jboss.org/browse/EMBJOPR-302?page=com.atlassian.jira.plugin.... ] Ondrej Zizka resolved EMBJOPR-302. ---------------------------------- Assignee: Ondrej Zizka Resolution: Partially Completed JMS node hidden. EJB 2.0 still shown. Not sure if EJB 2.0 should be supported; I've checked PRD and this is not stated. > EWP AS console: Hide JMS and EJB 2.0 nodes > ------------------------------------------ > > Key: EMBJOPR-302 > URL: https://jira.jboss.org/browse/EMBJOPR-302 > Project: Embedded Jopr > Issue Type: Bug > Affects Versions: 1.3.2 > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Priority: Critical > Fix For: 1.3.3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (EMBJOPR-338) Datasources: metrics do not reflect changes in max/min pool size params

by Ivo Studensky (JIRA)

Datasources: metrics do not reflect changes in max/min pool size params ----------------------------------------------------------------------- Key: EMBJOPR-338 URL: https://jira.jboss.org/browse/EMBJOPR-338 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.3.4 Environment: EAP 5.1.0 CR-3.5 + CXF Reporter: Ivo Studensky -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (EMBJOPR-329) Reliance on Hardcoded Library Paths

by Thomas Hauser (JIRA)

Reliance on Hardcoded Library Paths ----------------------------------- Key: EMBJOPR-329 URL: https://jira.jboss.org/browse/EMBJOPR-329 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.3.3 Reporter: Thomas Hauser This is related to https://jira.jboss.org/browse/JBPAPP-4886 >From JBPAPP-4886: If the JBoss library locations are altered and the JBoss variables for the libraries (jboss.lib.url,jboss.common.lib.url and jboss.server.lib.url) are made consistent with the library locations the JBoss Admin Console cannot be opened. Investigations shows This is because the ApplicationServerDiscoveryComponent class don't use JBoss variables and instead hard coded the path to jar files: See at the end of ApplicationServerDiscoveryComponent: CLIENT_JARS = Arrays.asList(new String[] { "client/jbossall-client.jar", "client/trove.jar", "client/javassist.jar", "common/lib/jboss-security-aspects.jar", "lib/jboss-managed.jar", "lib/jboss-metatype.jar", "lib/jboss-dependency.jar" }); AS6_CLIENT_JARS = new ArrayList(CLIENT_JARS); AS6_CLIENT_JARS.add("lib/jboss-classpool.jar"); AS6_CLIENT_JARS.add("lib/jboss-classpool-scoped.jar"); And it seems still the case in the trunk: http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=blob;f=modules/plugins/j... Customers timescale is that they need a patch in October as their first production of a JBoss application is expected in November. Please not that this is a time sensitive issue! Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (EMBJOPR-331) EMBJOPR-330 EJB3 Restart operation -> org.jboss.seam.ConcurrentRequestTimeoutException: Concurrent call to conversation

by Ondrej Zizka (JIRA)

EMBJOPR-330 EJB3 Restart operation -> org.jboss.seam.ConcurrentRequestTimeoutException: Concurrent call to conversation ------------------------------------------------------------------------------------------------------------------------ Key: EMBJOPR-331 URL: https://jira.jboss.org/browse/EMBJOPR-331 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.3.4 Reporter: Ondrej Zizka Attachments: BasicEJB3-good.jar, EMBJOPR-concbug.txt STR (or, better said, happened after this was done): 1) Install and run EAP 5.1.0.CR3.5 -c default 2) Deploy some EJB3 (attached) 3) Run it's Stop operation 4) Run it's Restart operation 5) That caused the attached exception to be thrown. From the nature of the bug, it's not easily reproducible. Similar to EMBJOPR-236, if not the same. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues September 2010