April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5970) RichFaces Showcase portlet is unable to switch skins

by Ken Finnigan (JIRA)

[ https://issues.jboss.org/browse/AS7-5970?page=com.atlassian.jira.plugin.s... ] Ken Finnigan commented on AS7-5970: ----------------------------------- I don't see a problem with that. Safe to close from my perspective > RichFaces Showcase portlet is unable to switch skins > ---------------------------------------------------- > > Key: AS7-5970 > URL: https://issues.jboss.org/browse/AS7-5970 > Project: Application Server 7 > Issue Type: Bug > Components: JSF > Affects Versions: 7.1.3.Final (EAP) > Reporter: Ken Finnigan > Assignee: Stan Silvert > > The following exception is thrown when the user changes skins for the second time immediately after changing the skin for the first time: > {noformat} > Caused by: javax.faces.FacesException: Cannot remove the same component twice: pbG9dea276d_2dee9e_2d4150_2dad91_2d22255b5a57d2_j_id1:j_idt444 > at com.sun.faces.context.StateContext$AddRemoveListener.handleAddRemoveWithAutoPrune(StateContext.java:489) [jsf-impl-2.1.13-redhat-1.jar:2.1.13-redhat-1] > at com.sun.faces.context.StateContext$AddRemoveListener.handleRemove(StateContext.java:371) [jsf-impl-2.1.13-redhat-1.jar:2.1.13-redhat-1] > at com.sun.faces.context.StateContext$AddRemoveListener.processEvent(StateContext.java:334) [jsf-impl-2.1.13-redhat-1.jar:2.1.13-redhat-1] > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) [jboss-jsf-api_2.1_spec-2.0.7.Final-redhat-1.jar:2.0.7.Final-redhat-1] > {noformat} > This error manifests due to the Portlet Bridge needing to retain the UIViewRoot from JSF between Portlet Requests, which causes the list of component tree actions, ie. adding and removing, to be retained making JSF think that it's trying to remove a component that was actually removed in a previous request. > This has been raised as http://java.net/jira/browse/JAVASERVERFACES-2609, but wanted to raise this as a tracker so that when that fix is available it can be incorporated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBAS-7210) JBossContextConfig needs to be isolated from the war class loader

by John Chan (JIRA)

[ https://issues.jboss.org/browse/JBAS-7210?page=com.atlassian.jira.plugin.... ] John Chan commented on JBAS-7210: --------------------------------- Dear Bruno HALEBLIAN, can you just send me the source files "JBossContextConfig.java" and "SecurityActions.java" that works with JB 5.1.0_GA ? I have got stuck in this problem for many weeks and the fix is my last resort. I cannot upgrade to JBOSS 7 as my project is so old that it is written in EJB2.1 codes. JBOSS 7 will not work with EJB2.1 codes, am I right? So please help me by sending the 2 source files to this email: shuhang2(a)netvigator.com. Millions of thanks if you can help! > JBossContextConfig needs to be isolated from the war class loader > ----------------------------------------------------------------- > > Key: JBAS-7210 > URL: https://issues.jboss.org/browse/JBAS-7210 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ClassLoading, Web (Tomcat) service > Affects Versions: JBossAS-5.1.0.GA > Reporter: Scott Stark > Assignee: Scott Stark > Fix For: 6.0.0.M2 > > Attachments: jbas-7210.war.zip > > > The parsing of the context.xml by the JBossContextConfig class is using the tccl which causes problems when the war app has tried to load its own xml parser. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6590) JSR-349 Bean Validation 1.1 API support and integration

by Gunnar Morling (JIRA)

[ https://issues.jboss.org/browse/AS7-6590?page=com.atlassian.jira.plugin.s... ] Gunnar Morling commented on AS7-6590: ------------------------------------- Stefano, I'm preparing a pull request for the update to the latest version of Hibernate Validator (5.0.0.CR5) at the moment (see AS7-6665). > JSR-349 Bean Validation 1.1 API support and integration > ------------------------------------------------------- > > Key: AS7-6590 > URL: https://issues.jboss.org/browse/AS7-6590 > Project: Application Server 7 > Issue Type: Sub-task > Components: EE > Reporter: David Lloyd > Assignee: Emmanuel Bernard > Fix For: 8.0.0.Alpha1 > > > Integrate Bean Validation 1.1 and Hibernate Validator 5 to support the BV 1.1 requirement of Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5768) Support resource adapter deployments via modules

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/AS7-5768?page=com.atlassian.jira.plugin.s... ] Stefano Maestri commented on AS7-5768: -------------------------------------- compressed rar are not supported deployed via module. It was in a first step, but after a long discussion we have removed support for them. We are supporting only flat rar deplyed in module as original issue description requires "where the latter contains the resource adapter in its unpacked form." > Support resource adapter deployments via modules > ------------------------------------------------ > > Key: AS7-5768 > URL: https://issues.jboss.org/browse/AS7-5768 > Project: Application Server 7 > Issue Type: Task > Components: JCA > Reporter: Jesper Pedersen > Assignee: Stefano Maestri > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > Attachments: AS7-5768-example.tgz > > > Add a new minor revision of the :resource-adapters: subsystem where the user has a choice of using > {code} > <archive>foo.rar</archive> > {code} > or > {code} > <module id="com.eis" slot="main"/> > {code} > where the latter contains the resource adapter in its unpacked form. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBAS-7210) JBossContextConfig needs to be isolated from the war class loader

by Bruno HALEBLIAN (JIRA)

[ https://issues.jboss.org/browse/JBAS-7210?page=com.atlassian.jira.plugin.... ] Bruno HALEBLIAN commented on JBAS-7210: --------------------------------------- These 2 referenced patches failed to apply "as is" on JB 5.1.0_GA sources. Line numbers and former $Id tags didn't match because the diffs comply with JB 6.X code source. So I had to adapt the diffs (change line numbers and former $Id tag comment) to have the patch successfully apply on JB 5.1.0_GA sources. That's what I call backport. I just posted this comment as a HowTo for those who, like me, wanted to hotfix the issue on old running JB5.1 systems with no time for a full JB7 migration. I fully agree with Brad Maxwell : Upgrading to JB7 is the recommended option, although driving the change from JB5 to JB7 on production systems varies from simple to head-aching (depending on what's deployed)... > JBossContextConfig needs to be isolated from the war class loader > ----------------------------------------------------------------- > > Key: JBAS-7210 > URL: https://issues.jboss.org/browse/JBAS-7210 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ClassLoading, Web (Tomcat) service > Affects Versions: JBossAS-5.1.0.GA > Reporter: Scott Stark > Assignee: Scott Stark > Fix For: 6.0.0.M2 > > Attachments: jbas-7210.war.zip > > > The parsing of the context.xml by the JBossContextConfig class is using the tccl which causes problems when the war app has tried to load its own xml parser. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6819) MBD @ResourceAdapter deployment issue with JCA inbound listener

by Sudip Bhowmik (JIRA)

[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ] Sudip Bhowmik commented on AS7-6819: ------------------------------------ Got same kind of error in jboss-eap-6.1: [jboss-eap-6.1] 15:01:07,911 ERROR [org.jboss.as.server] (HttpManagementService-threads - 7) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with the following failure message: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"jboss-as-helloworld-mdb.war\".component.MessageDrivenBean.CREATE is missing [jboss.ra.\"DiameterRAInDeploy-1.0\"]"]} May be I am missing something very basic. Please help. Thank you. > MBD @ResourceAdapter deployment issue with JCA inbound listener > --------------------------------------------------------------- > > Key: AS7-6819 > URL: https://issues.jboss.org/browse/AS7-6819 > Project: Application Server 7 > Issue Type: Release > Components: EJB, JCA > Affects Versions: 7.1.3.Final (EAP) > Environment: Windows with Jboss 7.1.3 EAP version. > Reporter: Sudip Bhowmik > Labels: jboss > Attachments: SourceCode_MDB_JCA.rar, standalone-full.xml > > > The source set is attached here with. > ================================================= > 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t > ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame > terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6819) MBD @ResourceAdapter deployment issue with JCA inbound listener

by Sudip Bhowmik (JIRA)

[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ] Sudip Bhowmik updated AS7-6819: ------------------------------- Issue Type: Release (was: Clarification) > MBD @ResourceAdapter deployment issue with JCA inbound listener > --------------------------------------------------------------- > > Key: AS7-6819 > URL: https://issues.jboss.org/browse/AS7-6819 > Project: Application Server 7 > Issue Type: Release > Components: EJB, JCA > Affects Versions: 7.1.3.Final (EAP) > Environment: Windows with Jboss 7.1.3 EAP version. > Reporter: Sudip Bhowmik > Labels: jboss > Attachments: SourceCode_MDB_JCA.rar, standalone-full.xml > > > The source set is attached here with. > ================================================= > 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t > ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame > terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6590) JSR-349 Bean Validation 1.1 API support and integration

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/AS7-6590?page=com.atlassian.jira.plugin.s... ] Stefano Maestri commented on AS7-6590: -------------------------------------- Any update on the plan for this issue? Thanks in advance. > JSR-349 Bean Validation 1.1 API support and integration > ------------------------------------------------------- > > Key: AS7-6590 > URL: https://issues.jboss.org/browse/AS7-6590 > Project: Application Server 7 > Issue Type: Sub-task > Components: EE > Reporter: David Lloyd > Assignee: Emmanuel Bernard > Fix For: 8.0.0.Alpha1 > > > Integrate Bean Validation 1.1 and Hibernate Validator 5 to support the BV 1.1 requirement of Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6823) Warning if no JDBC drivers can be found in domain mode

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6823?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6823: ----------------------------- Labels: Console_1.5.3 (was: ) > Warning if no JDBC drivers can be found in domain mode > ------------------------------------------------------ > > Key: AS7-6823 > URL: https://issues.jboss.org/browse/AS7-6823 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: Console_1.5.3 > Fix For: 8.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6823) Warning if no JDBC drivers can be found in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6823?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-6823: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=901322 > Warning if no JDBC drivers can be found in domain mode > ------------------------------------------------------ > > Key: AS7-6823 > URL: https://issues.jboss.org/browse/AS7-6823 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 8.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013