Bug 957838
| Summary: | An exception "java.io.NotActiveException: Fields were never written" occurs when FacesMessage object is serialized in JBoss EAP 6. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | ivassile | ||||
| Component: | JSF | Assignee: | ivassile | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Marek Schmidt <maschmid> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1.0 | CC: | myarboro, smumford, ssilvert, tremes | ||||
| Target Milestone: | ER7 | ||||||
| Target Release: | EAP 6.1.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
The deserialization of `FacesMessage` objects would throw an exception (`java.io.NotActiveException`) in some circumstances. This occurred because the `ObjectOutputStream`'s `defaultWriteObject()` or `writeFields()` methods were not invoked during serialization as required by the JSF specification. These methods are now correctly called during serialization and the deserialization of `FacesMessage` objects now works as expected.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 960073 (view as bug list) | Environment: | |||||
| Last Closed: | 2013-07-18 13:52:06 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 960073 | ||||||
| Attachments: |
|
||||||
|
Description
ivassile
2013-04-29 16:46:21 UTC
Email from Stan: This only requires a change to the jar in javax.faces.api. Here is the released artifact for the new version, 2.1.19.1. https://repository.jboss.org/nexus/index.html#nexus-search;gav~~~2.1.19.1.Final~~ The code is here: https://github.com/jboss/jboss-jsf-api_spec/tree/2.1.19.1 This should be used in conjunction with the previously-released version of the impl jar which is here: https://repository.jboss.org/nexus/index.html#nexus-search;gav~~~2.1.19-jbossorg-1~~ Brew build of jsf-api 2.1.19.1 with jars: https://brewweb.devel.redhat.com/buildinfo?buildID=269945 Adding acks to check if this update is ok to include in 6.1. Created attachment 742929 [details]
one-off patch
To QA: Please verify the patch PR for jboss-eap repo: https://github.com/jbossas/jboss-eap/pull/128 Draft Release Note content added. Setting NEEDINFO to get a technical review of the draft content. Comment to approve or correct it. I am confused, I believe this issue has been created as a one-off release for EAP 6.0.1, but now it looks like a EAP 6.1.0 issue. It can't be both, but we need both. @Ilia, will you please clone the issue and make one of them a one-off issue, with the proper ON_QA state, so I can proceed with the QA-ACKing the one-off? The EAP 6.0.1 one-off itself passes the tests. 9cc100b0bb11e0c85ad39fdc2be72734 README.txt aba3644142be3bdd78d9bee7b3c27ed3 jboss-jsf-api/jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar f4f04455b984371c134c4c004985a599 jboss-jsf-api/module.xml 1bfea67291907b7c0cc57244a775147e jsf-impl/jsf-impl-2.1.19-redhat-1.jar 6bce03a05537840ee6aab7d9c53e8ad2 jsf-impl/module.xml I originaly created this issue as one-off. @Marek: Created new one-off BZ: https://bugzilla.redhat.com/show_bug.cgi?id=960073 Marek, sorry for the confusion, next time I'll create a separate bz right away when we decide to include a one off in the next eap release. Updated Release Notes draft. Verified at EAP 6.1.0.ER8 release. Adding NEEDINFO to request verification of Release Note in Doc Text field above. The object name is FacesMessage (not FacesMessages). It looks OK after this minor correction. |