June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-457) User guide builds incorrectly using Java 6

by Darran Lofthouse (JIRA)

User guide builds incorrectly using Java 6 ------------------------------------------ Key: SECURITY-457 URL: https://jira.jboss.org/jira/browse/SECURITY-457 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.SP2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA The user guide builds incorrectly running Java 6, however Java 5 still works as expected. Suspect XML parsing differences, documentation should be updated to work with Java 6. -- 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

13 years, 6 months

1
4
0 / 0

[JBoss JIRA] (JBWEB-236) JSF Mojarra has serious performance issues, add MyFaces integration

by Adrian Everett (JIRA)

Adrian Everett created JBWEB-236: ------------------------------------ Summary: JSF Mojarra has serious performance issues, add MyFaces integration Key: JBWEB-236 URL: https://issues.jboss.org/browse/JBWEB-236 Project: JBoss Web Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Core Affects Versions: JBossWeb-7.0.13.GA Environment: JBoss 7.1.1 AS, Windows 7 64 bit Reporter: Adrian Everett Assignee: Remy Maucherat Please add MyFaces support to JBoss AS7 as an alternative to JSF Mojarra, because Mojarra has serious performance issues. For large data sets, a really bad JSF performance issue regarding AJAX requests has been identified. An issue ticket was created for this on the Mojarra issues tracker, but it might be quite a long time before they fix it, if it ever does get fixed. Here is the link: http://java.net/jira/browse/JAVASERVERFACES-2334 For every large data sets, the performance of a simple f:ajax calls slows down to the point it becomes as slow as a full page post. An f:ajax call passing 300 bytes of data could take 3+ seconds to perform a round trip, where the same exact f:ajax call might only take a 200ms if the page is smaller. The only difference between the big page and the small page might be several thousand h:outputText components that have no relation with the component associated with the f:ajax call. This is a serious problem for a site such as the one I'm working on, where we sometimes have to load large amounts of data in an un-paginated manner, and also perform AJAX requests on the same page. I took the example code attached to the Mojarra ticket and will be attaching it to this one. I have verified that it causes the problem by running the code on JBoss AS, the latest Glassfish server and even Tomcat. The problem isn't with JBoss, it's with the Mojarra implementation of JSF, so support for MyFaces would greatly benefit projects with large data sets. Finally, as seen in the Mojarra ticket, the author of the PrimeFaces component library has also performed some tests with the attached code and found that the MyFaces JSF stack doesn't have the problem. His comments can be seen in the reference ticket. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
5
0 / 0

[JBoss JIRA] (AS7-4154) TS: API changes report - Animal sniffer maven plugin

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-4154: --------------------------------- Summary: TS: API changes report - Animal sniffer maven plugin Key: AS7-4154 URL: https://issues.jboss.org/browse/AS7-4154 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka Fix For: 7.1.2.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
13
0 / 0

[JBoss JIRA] (AS7-4568) JSF component libraries does not work in AS7 modules

by Gernot P (JIRA)

Gernot P created AS7-4568: ----------------------------- Summary: JSF component libraries does not work in AS7 modules Key: AS7-4568 URL: https://issues.jboss.org/browse/AS7-4568 Project: Application Server 7 Issue Type: Bug Components: Class Loading Affects Versions: 7.1.1.Final, 7.1.0.Final Reporter: Gernot P Assignee: David Lloyd Deploying JSF component libraries (like primefaces and other) as AS/ module does not work. The JSF runtime does not find the compontent library. That's rather bad, because modules are the only way to share jar's across the whole server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
13
0 / 0

[JBoss JIRA] (AS7-4642) mechanism to load tag libraries from module

by Ivica Loncar (JIRA)

Ivica Loncar created AS7-4642: --------------------------------- Summary: mechanism to load tag libraries from module Key: AS7-4642 URL: https://issues.jboss.org/browse/AS7-4642 Project: Application Server 7 Issue Type: Feature Request Components: Class Loading, Web Affects Versions: 7.1.1.Final Reporter: Ivica Loncar Assignee: David Lloyd Priority: Critical tag libraries are scanned only if they appear in jar inside WEB-INF/lib or are defined in tld under WEB-INF. The simplest scenario to explain why this is a problem: portlet 2 defines standard portlet taglib, but the classes in this file come from concrete implementations. Currently I see no way to use 2 different portals in a portable way. Please provide a way to notify a web application that module contains .tld. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
3
0 / 0

[JBoss JIRA] (AS7-3377) TS: Check how JDBC drivers are copied

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3377: --------------------------------- Summary: TS: Check how JDBC drivers are copied Key: AS7-3377 URL: https://issues.jboss.org/browse/AS7-3377 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
13
0 / 0

[JBoss JIRA] (AS7-2105) TS: Put all management tests into one dir (org.jboss.as.test.integration.mgmt)

by Ondrej Zizka (Created) (JIRA)

TS: Put all management tests into one dir (org.jboss.as.test.integration.mgmt) ------------------------------------------------------------------------------ Key: AS7-2105 URL: https://issues.jboss.org/browse/AS7-2105 Project: Application Server 7 Issue Type: Sub-task Reporter: Ondrej Zizka integration/org.jboss.as.test.integration.management and further separated by subsystems/interfaces: org.jboss.as.test.integration.management.cli org.jboss.as.test.integration.management.http org.jboss.as.test.integration.management.api org.jboss.as.test.integration.management.api.messaging Thanks Dominik for pointing out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] (AS7-2176) TS: Check tests workdirs

by Ondrej Zizka (Created) (JIRA)

TS: Check tests workdirs ------------------------ Key: AS7-2176 URL: https://issues.jboss.org/browse/AS7-2176 Project: Application Server 7 Issue Type: Sub-task Reporter: Ondrej Zizka Some tests (also unit tests) have work dirs in ${basedir}, which leaves garbage after running. That should change either to target/work or /tmp/... (consider what's better). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
4
0 / 0

[JBoss JIRA] (AS7-2007) Testsuite tasks (tracking)

by Ondrej Zizka (Created) (JIRA)

Testsuite tasks (tracking) -------------------------- Key: AS7-2007 URL: https://issues.jboss.org/browse/AS7-2007 Project: Application Server 7 Issue Type: Task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

10
28
0 / 0

[JBoss JIRA] (AS7-4090) Opimize organization and management of the Infinispan subsystem

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created AS7-4090: ---------------------------------------- Summary: Opimize organization and management of the Infinispan subsystem Key: AS7-4090 URL: https://issues.jboss.org/browse/AS7-4090 Project: Application Server 7 Issue Type: Task Components: Clustering Affects Versions: 7.1.0.Final Reporter: Richard Achmatowicz Assignee: Paul Ferraro Fix For: 7.1.2.Final There are a number of areas where the Infinispan subsystem is organizationally deficient: - does not make use of ResourceDefinitions to (i) simplify the generation of DescriptionProviders and (ii) localize the definition of AttributeDefinitions - handlers are in some cases written from scratch rather than subclassing helper handlers such as AbstractWriteAttributeHandler, AbstractAddStepHandler, AbstractRemoveStepHandler, etc. - collections of services are defined monolithically, rather than in distinct units which makes stopping/restarting them error prone (c.f. CacheContainerAdd, CacheAdd install three or four services each with complex processing - stopping and restarting this in another handler is next to impossible) - ServiceNames are not always easy to reconstruct These issues make maintenance of the subsystem hard. These matters can be helped by: - making use of ResourceDefinitions - defining for each service X a static method installX(context, operation, model) and removeX(context, operation, model) which can be made use of in installServices(context, operation, model) and removeServices(operation, context, model) - define the static method populate(), used to populate a model from an operation, which can be reused in populateModel(), creating describe operations, as well as other contexts - define a static method installServices(context, operation, model) which can be used in performRuntime(), and in contexts where all services for a resource need to be stopped and restarted; similarly define removeServices(context, operation, model) - make sure each ServiceName can be regenerated easily (c.f. regenerating JNDI names can involve model processing) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
10
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 2012