December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6186) Mojarra 2.1.16 upgrade breaks Seam2.3.0 conversations

by Marek Schmidt (JIRA)

[ https://issues.jboss.org/browse/AS7-6186?page=com.atlassian.jira.plugin.s... ] Marek Schmidt commented on AS7-6186: ------------------------------------ At least one of the problems with the Mojarra 2.1.16 upgrade seems to be the change of behaviour in the case FacesContext.getCurrentInstance().getViewRoot().getViewMap() is called before the view map is created by JSF. While an empty map is returned in such case in both the current version and the previous version, it seems that in 2.1.16 the map will not be updated with the actual view map data... so the view map data from the previous request is lost if one calls getViewMap() too soon. This is a problem for Seam, as it calls getViewMap the first time a page-scoped component is accessed, which may be, e.g. the Seam EntityIdentifierStore, which is a page-scoped component used by the EntityConverter seam component, which is a faces converter. The following example shows where the behaviour differs, with no Seam in it: To reproduce the problem, click "set foo" button, and then click the "Click" button. Notice that with Mojarra 2.1.16 the "bar" from "ViewMap value: bar" disappears after clicking "click", which means it is lost from the viewmap. (the converter doesn't do anything, it is just so we can call getViewMap() in the converter constructor, which happens before the view map gets filled with the actual view map to demonstrate the problem, which seems to also happen in Seam 2.3.0) {code} @FacesConverter("org.jboss.seam.test.MyConverter") public class MyConverter implements Converter { public MyConverter() { // This is the problematic line: FacesContext.getCurrentInstance().getViewRoot().getViewMap(); } @Override public Object getAsObject(FacesContext context, UIComponent component, String value) { return null; } @Override public String getAsString(FacesContext context, UIComponent component, Object value) { return (String)value; } } {code} {code} @Model public class Action { public String getFoo() { return (String)FacesContext.getCurrentInstance().getViewRoot().getViewMap().get("foo"); } public void setFoo() { UIViewRoot root = FacesContext.getCurrentInstance().getViewRoot(); Map<String, Object> viewMap = root.getViewMap(); viewMap.put("foo", "bar"); } } {code} {code} <h:form> <div> ViewMap value: <h:outputText value="#{action.getFoo()}" /> </div> <div> Converter: <h:outputText value="#{'converter'}"> <f:converter converterId="org.jboss.seam.test.MyConverter"/> </h:outputText> </div> <div> <h:commandButton value="set foo" action="#{action.setFoo()}" /> <h:commandButton value="Click"/> </div> </h:form> {code} > Mojarra 2.1.16 upgrade breaks Seam2.3.0 conversations > ----------------------------------------------------- > > Key: AS7-6186 > URL: https://issues.jboss.org/browse/AS7-6186 > Project: Application Server 7 > Issue Type: Bug > Components: JSF > Affects Versions: 7.1.4.Final (EAP) > Environment: Current 7.1.4.Final-SNAPSHOT (2012-12-15), Mojarra 2.1.16, Seam2.3.0.Final > Reporter: Marek Schmidt > Assignee: Stan Silvert > Priority: Critical > Attachments: seam-booking.ear > > > Recent Mojarra upgrade seems to break Seam 2.3.0 conversations. > Not exactly sure yet what has changed and whether it is a Mojarra bug or Seam depending on something it shouldn't. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-187) Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux

by Alexander Zinin (JIRA)

[ https://issues.jboss.org/browse/JASSIST-187?page=com.atlassian.jira.plugi... ] Alexander Zinin updated JASSIST-187: ------------------------------------ Attachment: javassist-test.rar > Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux > --------------------------------------------------------------------------------------- > > Key: JASSIST-187 > URL: https://issues.jboss.org/browse/JASSIST-187 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.16.0-GA, 3.16.1-GA, 3.17.0-GA > Environment: Windows 7 x64 Oracle JVM x86/x64 1.6.37 - no error > Linux Ubuntu x64 Oracle JVM x64 1.6.37 - error > Reporter: Alexander Zinin > Assignee: Shigeru Chiba > Attachments: javassist-test.rar > > > It will be difficult to describe what the error. > I will attach source code that reproduce error. > If you have hibernate entity with overrided getId() method, in hibernate session this method returns null instead of correct value. > Running on Windows: > 2012-12-16 17:33:19,332 INFO ru.zinin.service.SomeServiceImpl :44 - ID = 1 > Running on Linux: > 2012-12-16 17:41:47,772 INFO ru.zinin.service.SomeServiceImpl :44 - ID = null > 2012-12-16 17:41:47,772 ERROR ru.zinin.service.SomeServiceImpl :46 - ID IS NULL!!! > Bug appeared in version 3.16.0. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-187) Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux

by Alexander Zinin (JIRA)

Alexander Zinin created JASSIST-187: --------------------------------------- Summary: Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux Key: JASSIST-187 URL: https://issues.jboss.org/browse/JASSIST-187 Project: Javassist Issue Type: Bug Affects Versions: 3.17.0-GA, 3.16.1-GA, 3.16.0-GA Environment: Windows 7 x64 Oracle JVM x86/x64 1.6.37 - no error Linux Ubuntu x64 Oracle JVM x64 1.6.37 - error Reporter: Alexander Zinin Assignee: Shigeru Chiba It will be difficult to describe what the error. I will attach source code that reproduce error. If you have hibernate entity with overrided getId() method, in hibernate session this method returns null instead of correct value. Running on Windows: 2012-12-16 17:33:19,332 INFO ru.zinin.service.SomeServiceImpl :44 - ID = 1 Running on Linux: 2012-12-16 17:41:47,772 INFO ru.zinin.service.SomeServiceImpl :44 - ID = null 2012-12-16 17:41:47,772 ERROR ru.zinin.service.SomeServiceImpl :46 - ID IS NULL!!! Bug appeared in version 3.16.0. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3) Migrate from Hibernate 3 to Hibernate 4

by Marco Rietveld (JIRA)

Marco Rietveld created DROOLS-3: ----------------------------------- Summary: Migrate from Hibernate 3 to Hibernate 4 Key: DROOLS-3 URL: https://issues.jboss.org/browse/DROOLS-3 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Marco Rietveld Assignee: Marco Rietveld -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6191) SimpleAttributeDefinition spams the logs with deprecation messages

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6191: ------------------------------------- Summary: SimpleAttributeDefinition spams the logs with deprecation messages Key: AS7-6191 URL: https://issues.jboss.org/browse/AS7-6191 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 If an attribute is deprecated, SAD writes INFO messages in the log in both parse and the marshallAs methods. The superclass does it in validateAndSet. The superclass is sufficient. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6190) ExtensionAdd won't initialize parsers for more than one Extension per module

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6190: ------------------------------------- Summary: ExtensionAdd won't initialize parsers for more than one Extension per module Key: AS7-6190 URL: https://issues.jboss.org/browse/AS7-6190 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.3.Final (EAP) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 ExtensionAdd loops through the extensions the ServiceLoader loads from the modules, but will only call initializeParsers on the first because thereafter it assumes the parser is already registered since the ExtensionRegistry knows about the module. The effect of this is the xml-namespace information for the extension won't show up in the management API. It doesn't affect parsing. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6189) Incorrect use of equals in SubDeploymentDependencyProcessor.deploy(DeploymentPhaseContext)

by Stephen Coy (JIRA)

[ https://issues.jboss.org/browse/AS7-6189?page=com.atlassian.jira.plugin.s... ] Stephen Coy updated AS7-6189: ----------------------------- Description: This loop appears to confuse ModuleDependency and ModuleIdentifier: {code:java} for (ModuleDependency identifier : accessibleModules) { if (!identifier.equals(moduleIdentifier)) { moduleSpec.addLocalDependency(identifier); } } {code} > Incorrect use of equals in SubDeploymentDependencyProcessor.deploy(DeploymentPhaseContext) > ------------------------------------------------------------------------------------------ > > Key: AS7-6189 > URL: https://issues.jboss.org/browse/AS7-6189 > Project: Application Server 7 > Issue Type: Bug > Reporter: Stephen Coy > > This loop appears to confuse ModuleDependency and ModuleIdentifier: > {code:java} > for (ModuleDependency identifier : accessibleModules) { > if (!identifier.equals(moduleIdentifier)) { > moduleSpec.addLocalDependency(identifier); > } > } > {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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6189) Incorrect use of equals in SubDeploymentDependencyProcessor.deploy(DeploymentPhaseContext)

by Stephen Coy (JIRA)

Stephen Coy created AS7-6189: -------------------------------- Summary: Incorrect use of equals in SubDeploymentDependencyProcessor.deploy(DeploymentPhaseContext) Key: AS7-6189 URL: https://issues.jboss.org/browse/AS7-6189 Project: Application Server 7 Issue Type: Bug Reporter: Stephen Coy -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6150) Upgrade JSF based on Mojarra 2.1.16

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/AS7-6150?page=com.atlassian.jira.plugin.s... ] Stan Silvert resolved AS7-6150. ------------------------------- Resolution: Done > Upgrade JSF based on Mojarra 2.1.16 > ----------------------------------- > > Key: AS7-6150 > URL: https://issues.jboss.org/browse/AS7-6150 > Project: Application Server 7 > Issue Type: Feature Request > Components: JSF > Affects Versions: 7.1.1.Final, 7.1.3.Final (EAP) > Reporter: Stan Silvert > Assignee: Stan Silvert > Labels: jsf, jsf2, jsf21 > Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) > > > Upgrade JSF API and JSF IMPL based on Mojarra 2.1.16 -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6188) Incorrect use of equals in JMSBridgeHandler.executeRuntimeStep(OperationContext, ModelNode)

by Stephen Coy (JIRA)

Stephen Coy created AS7-6188: -------------------------------- Summary: Incorrect use of equals in JMSBridgeHandler.executeRuntimeStep(OperationContext, ModelNode) Key: AS7-6188 URL: https://issues.jboss.org/browse/AS7-6188 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.2.0.Alpha1 Environment: n/a Reporter: Stephen Coy Assignee: Jeff Mesnil A org.jboss.as.controller.AttributeDefinition is being compared with a String: {code:java} } else if (PAUSED.equals(name)) { context.getResult().set(bridge.isPaused()); } else { {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

13 years, 7 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 December 2012