October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-145) Missing validationFailed and isValidationFailed Methods in FacesContext

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-145?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on JBEE-145: ------------------------------------- What version of the org.jboss.spec.javax.faces version are you using? The methods are in the 2.0.9.Final version: https://github.com/jboss/jboss-jsf-api_spec/blob/jboss-jsf-api_2.1_spec-2... and 2.1.26.Final https://github.com/jboss/jboss-jsf-api_spec/blob/jboss-jsf-api_2.1_spec-2... > Missing validationFailed and isValidationFailed Methods in FacesContext > ----------------------------------------------------------------------- > > Key: JBEE-145 > URL: https://issues.jboss.org/browse/JBEE-145 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jsf-api > Environment: Debian GNU Linux 7 64-Bit > Java: 1.7.0_25; OpenJDK 64-Bit Server VM 23.7-b01 > Runtime: OpenJDK Runtime Environment 1.7.0_25-b30 > System: Linux version 3.2.0-4-amd64 running on amd64; UTF-8; en_US (nb) > JBoss 7.1.1 Final > Reporter: Kay Wrobel > Assignee: Shelly McGowan > Labels: FacesContext, JSF2 > > I have a NetBeans module called PrimeFaces CRUD Generator. One thing I do when an error was detected on a page is add a FacesMessage to the current FacesContext and the invalidate the page with validationFailed() method. My IDE (NetBeans 7.4) cannot compile this code because of missing symbols for validationFailed and isValidationFailed for javax.faces.context.FacesContext. These are supposed to be there according to Oracle Java EE 6 Spec. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-145) Missing validationFailed and isValidationFailed Methods in FacesContext

by Kay Wrobel (JIRA)

[ https://issues.jboss.org/browse/JBEE-145?page=com.atlassian.jira.plugin.s... ] Kay Wrobel commented on JBEE-145: --------------------------------- Just noticed that I am looking at the wrong jar file. JBoss has another jar also containing FacesContext inside jboss-jsf-api_2.1_spec-2.0.1.Final.jar, which DOES contain those two methods. Seems as if the IDE is at fault here. > Missing validationFailed and isValidationFailed Methods in FacesContext > ----------------------------------------------------------------------- > > Key: JBEE-145 > URL: https://issues.jboss.org/browse/JBEE-145 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jsf-api > Environment: Debian GNU Linux 7 64-Bit > Java: 1.7.0_25; OpenJDK 64-Bit Server VM 23.7-b01 > Runtime: OpenJDK Runtime Environment 1.7.0_25-b30 > System: Linux version 3.2.0-4-amd64 running on amd64; UTF-8; en_US (nb) > JBoss 7.1.1 Final > Reporter: Kay Wrobel > Assignee: Shelly McGowan > Labels: FacesContext, JSF2 > > I have a NetBeans module called PrimeFaces CRUD Generator. One thing I do when an error was detected on a page is add a FacesMessage to the current FacesContext and the invalidate the page with validationFailed() method. My IDE (NetBeans 7.4) cannot compile this code because of missing symbols for validationFailed and isValidationFailed for javax.faces.context.FacesContext. These are supposed to be there according to Oracle Java EE 6 Spec. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-145) Missing validationFailed and isValidationFailed Methods in FacesContext

by Kay Wrobel (JIRA)

[ https://issues.jboss.org/browse/JBEE-145?page=com.atlassian.jira.plugin.s... ] Kay Wrobel commented on JBEE-145: --------------------------------- Please see http://docs.oracle.com/javaee/6/api/javax/faces/context/FacesContext.html of the Java EE 6 API Documentation. > Missing validationFailed and isValidationFailed Methods in FacesContext > ----------------------------------------------------------------------- > > Key: JBEE-145 > URL: https://issues.jboss.org/browse/JBEE-145 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jsf-api > Environment: Debian GNU Linux 7 64-Bit > Java: 1.7.0_25; OpenJDK 64-Bit Server VM 23.7-b01 > Runtime: OpenJDK Runtime Environment 1.7.0_25-b30 > System: Linux version 3.2.0-4-amd64 running on amd64; UTF-8; en_US (nb) > JBoss 7.1.1 Final > Reporter: Kay Wrobel > Assignee: Shelly McGowan > Labels: FacesContext, JSF2 > > I have a NetBeans module called PrimeFaces CRUD Generator. One thing I do when an error was detected on a page is add a FacesMessage to the current FacesContext and the invalidate the page with validationFailed() method. My IDE (NetBeans 7.4) cannot compile this code because of missing symbols for validationFailed and isValidationFailed for javax.faces.context.FacesContext. These are supposed to be there according to Oracle Java EE 6 Spec. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1712) Erroneous name attribute on root-logger after add-handler operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1712?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1712: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1017881 > Erroneous name attribute on root-logger after add-handler operation > -------------------------------------------------------------------- > > Key: WFLY-1712 > URL: https://issues.jboss.org/browse/WFLY-1712 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Execution of the {{add-handler}} operation adds a name attribute with the handlers name to the root-logger model. > {code} > "root-logger" => {"ROOT" => { > "filter" => undefined, > "filter-spec" => undefined, > "handlers" => [ > "FILE", > "CONSOLE" > ], > "level" => "INFO", > "name" => "CONSOLE" > }} > {code} -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1712) Erroneous name attribute on root-logger after add-handler operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1712?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1712: ----------------------------------------------- James Perkins <jperkins(a)redhat.com> made a comment on [bug 1017881|https://bugzilla.redhat.com/show_bug.cgi?id=1017881] I forgot to add. I think we should delay from EAP 6.2 because the workaround is easy enough. The error is only going to occur in composite operations when using multiple add-handler operations to the same logger. If we need to get this into 6.2 it is possible, but at this stage I'm not sure it's worth the change for the simple workaround. Also I doubt this use-case, adding handlers to the same logger in a composite operation, is used all that often. This same issue is present in EAP 6.1.x and it's the first time I've seen it. > Erroneous name attribute on root-logger after add-handler operation > -------------------------------------------------------------------- > > Key: WFLY-1712 > URL: https://issues.jboss.org/browse/WFLY-1712 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Execution of the {{add-handler}} operation adds a name attribute with the handlers name to the root-logger model. > {code} > "root-logger" => {"ROOT" => { > "filter" => undefined, > "filter-spec" => undefined, > "handlers" => [ > "FILE", > "CONSOLE" > ], > "level" => "INFO", > "name" => "CONSOLE" > }} > {code} -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-145) Missing validationFailed and isValidationFailed Methods in FacesContext

by Kay Wrobel (JIRA)

[ https://issues.jboss.org/browse/JBEE-145?page=com.atlassian.jira.plugin.s... ] Kay Wrobel updated JBEE-145: ---------------------------- Steps to Reproduce: Download and install NetBeans 7.4 Add JBoss AS 7.1.1 as a server Download PrimeFaces CRUD Generator from SourceForge. Make sure it's for implementation 7.4. Install the plugin. Now, add some entities from a database using the Entity Classes From Database wizard. Run the PrimeFaces Pages from Entity Classes wizard Once finished, look at JsfUtil.java. NetBeans highlights lines 29 and 51 with invalid symbol errors. > Missing validationFailed and isValidationFailed Methods in FacesContext > ----------------------------------------------------------------------- > > Key: JBEE-145 > URL: https://issues.jboss.org/browse/JBEE-145 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jsf-api > Environment: Debian GNU Linux 7 64-Bit > Java: 1.7.0_25; OpenJDK 64-Bit Server VM 23.7-b01 > Runtime: OpenJDK Runtime Environment 1.7.0_25-b30 > System: Linux version 3.2.0-4-amd64 running on amd64; UTF-8; en_US (nb) > JBoss 7.1.1 Final > Reporter: Kay Wrobel > Assignee: Shelly McGowan > Labels: FacesContext, JSF2 > > I have a NetBeans module called PrimeFaces CRUD Generator. One thing I do when an error was detected on a page is add a FacesMessage to the current FacesContext and the invalidate the page with validationFailed() method. My IDE (NetBeans 7.4) cannot compile this code because of missing symbols for validationFailed and isValidationFailed for javax.faces.context.FacesContext. These are supposed to be there according to Oracle Java EE 6 Spec. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-145) Missing validationFailed and isValidationFailed Methods in FacesContext

by Kay Wrobel (JIRA)

[ https://issues.jboss.org/browse/JBEE-145?page=com.atlassian.jira.plugin.s... ] Kay Wrobel updated JBEE-145: ---------------------------- Labels: FacesContext JSF2 (was: ) Description: I have a NetBeans module called PrimeFaces CRUD Generator. One thing I do when an error was detected on a page is add a FacesMessage to the current FacesContext and the invalidate the page with validationFailed() method. My IDE (NetBeans 7.4) cannot compile this code because of missing symbols for validationFailed and isValidationFailed for javax.faces.context.FacesContext. These are supposed to be there according to Oracle Java EE 6 Spec. > Missing validationFailed and isValidationFailed Methods in FacesContext > ----------------------------------------------------------------------- > > Key: JBEE-145 > URL: https://issues.jboss.org/browse/JBEE-145 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jsf-api > Environment: Debian GNU Linux 7 64-Bit > Java: 1.7.0_25; OpenJDK 64-Bit Server VM 23.7-b01 > Runtime: OpenJDK Runtime Environment 1.7.0_25-b30 > System: Linux version 3.2.0-4-amd64 running on amd64; UTF-8; en_US (nb) > JBoss 7.1.1 Final > Reporter: Kay Wrobel > Assignee: Shelly McGowan > Labels: FacesContext, JSF2 > > I have a NetBeans module called PrimeFaces CRUD Generator. One thing I do when an error was detected on a page is add a FacesMessage to the current FacesContext and the invalidate the page with validationFailed() method. My IDE (NetBeans 7.4) cannot compile this code because of missing symbols for validationFailed and isValidationFailed for javax.faces.context.FacesContext. These are supposed to be there according to Oracle Java EE 6 Spec. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1712) Erroneous name attribute on root-logger after add-handler operation

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1712?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-1712: ------------------------------------- The name is added in the {{validateAndSet}} which should be assigning to the model. This should likely happen on a new model and the runtime needs a way to get the correct handler name to set or just use the {{setHandlers()}}, but needs to also include any previous handlers. {code:java} static final OperationStepHandler ADD_HANDLER = new LoggerUpdateOperationStepHandler() { @Override public void updateModel(final ModelNode operation, final ModelNode model) throws OperationFailedException { HANDLER_NAME.validateAndSet(operation, model); model.get(HANDLERS.getName()).add(operation.get(HANDLER_NAME.getName())); } @Override public void performRuntime(final OperationContext context, final ModelNode operation, final LoggerConfiguration configuration, final String name, final ModelNode model) throws OperationFailedException { // Get the handler name final String handlerName = HANDLER_NAME.resolveModelAttribute(context, model).asString(); final String loggerName = getLogManagerLoggerName(name); if (configuration.getHandlerNames().contains(handlerName)) { throw createOperationFailure(LoggingMessages.MESSAGES.handlerAlreadyDefined(handlerName)); } LoggingLogger.ROOT_LOGGER.tracef("Adding handler '%s' to logger '%s' at '%s'", handlerName, getLogManagerLoggerName(loggerName), LoggingOperations.getAddress(operation)); configuration.addHandlerName(handlerName); } }; {code} > Erroneous name attribute on root-logger after add-handler operation > -------------------------------------------------------------------- > > Key: WFLY-1712 > URL: https://issues.jboss.org/browse/WFLY-1712 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Execution of the {{add-handler}} operation adds a name attribute with the handlers name to the root-logger model. > {code} > "root-logger" => {"ROOT" => { > "filter" => undefined, > "filter-spec" => undefined, > "handlers" => [ > "FILE", > "CONSOLE" > ], > "level" => "INFO", > "name" => "CONSOLE" > }} > {code} -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-145) Missing validationFailed and isValidationFailed Methods in FacesContext

by Kay Wrobel (JIRA)

[ https://issues.jboss.org/browse/JBEE-145?page=com.atlassian.jira.plugin.s... ] Kay Wrobel updated JBEE-145: ---------------------------- Environment: Debian GNU Linux 7 64-Bit Java: 1.7.0_25; OpenJDK 64-Bit Server VM 23.7-b01 Runtime: OpenJDK Runtime Environment 1.7.0_25-b30 System: Linux version 3.2.0-4-amd64 running on amd64; UTF-8; en_US (nb) JBoss 7.1.1 Final Component/s: jboss-jsf-api > Missing validationFailed and isValidationFailed Methods in FacesContext > ----------------------------------------------------------------------- > > Key: JBEE-145 > URL: https://issues.jboss.org/browse/JBEE-145 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jsf-api > Environment: Debian GNU Linux 7 64-Bit > Java: 1.7.0_25; OpenJDK 64-Bit Server VM 23.7-b01 > Runtime: OpenJDK Runtime Environment 1.7.0_25-b30 > System: Linux version 3.2.0-4-amd64 running on amd64; UTF-8; en_US (nb) > JBoss 7.1.1 Final > Reporter: Kay Wrobel > Assignee: Shelly McGowan > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-145) Missing validationFailed and isValidationFailed Methods in FacesContext

by Kay Wrobel (JIRA)

Kay Wrobel created JBEE-145: ------------------------------- Summary: Missing validationFailed and isValidationFailed Methods in FacesContext Key: JBEE-145 URL: https://issues.jboss.org/browse/JBEE-145 Project: JBoss JavaEE Spec APIs Issue Type: Bug Reporter: Kay Wrobel Assignee: Shelly McGowan -- 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

12 years, 8 months

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 October 2013