managed-bean in richfaces-core-impl ----------------------------------- Key: RF-10755 URL: https://issues.jboss.org/browse/RF-10755 Project: RichFaces Issue Type: Enhancement Security Level: Public(Everyone can see) Components: compatibility Affects Versions: 4.0.0.CR1 Environment: Richfaces 4.0.0 branch Reporter: Martin Kočí Assignee: Nick Belaevski Fix For: 4.Future richfaces-core-impl contains three definitions of managed-beans: a4j a4jSkin richSkin By mistake one of our coders created CDI bean named "richSkin" and that caused malfunction of richfaces skinning. Suggestion: do not provide those beans but implement them as implicit object (similar like JSF implicit object "view" or "sessionScope") There is SkinPropertiesELResolver already, all what needs to be done is define new implicit object "richSkin" and handle it there in similar way how JSF impl handle implicit objects. a4jSkin managed-bean seems to be obsolete, about a4j(VerionBean) I'm not sure.

managed-bean in richfaces-core-impl ----------------------------------- Key: RF-10755 URL: https://issues.jboss.org/browse/RF-10755 Project: RichFaces Issue Type: Enhancement Security Level: Public(Everyone can see) Components: compatibility Affects Versions: 4.0.0.CR1 Environment: Richfaces 4.0.0 branch Reporter: Martin Kočí Assignee: Konstantin Mishin Labels: design, tran Fix For: 4.Future richfaces-core-impl contains three definitions of managed-beans: a4j a4jSkin richSkin By mistake one of our coders created CDI bean named "richSkin" and that caused malfunction of richfaces skinning. Suggestion: do not provide those beans but implement them as implicit object (similar like JSF implicit object "view" or "sessionScope") There is SkinPropertiesELResolver already, all what needs to be done is define new implicit object "richSkin" and handle it there in similar way how JSF impl handle implicit objects. a4jSkin managed-bean seems to be obsolete, about a4j(VerionBean) I'm not sure.

managed-bean in richfaces-core-impl ----------------------------------- Key: RF-10755 URL: https://issues.jboss.org/browse/RF-10755 Project: RichFaces Issue Type: Enhancement Security Level: Public(Everyone can see) Components: compatibility Affects Versions: 4.0.0.CR1 Environment: Richfaces 4.0.0 branch Reporter: Martin Kočí Assignee: Konstantin Mishin Fix For: 4.1.0.Milestone1 richfaces-core-impl contains three definitions of managed-beans: a4j a4jSkin richSkin By mistake one of our coders created CDI bean named "richSkin" and that caused malfunction of richfaces skinning. Suggestion: do not provide those beans but implement them as implicit object (similar like JSF implicit object "view" or "sessionScope") There is SkinPropertiesELResolver already, all what needs to be done is define new implicit object "richSkin" and handle it there in similar way how JSF impl handle implicit objects. a4jSkin managed-bean seems to be obsolete, about a4j(VerionBean) I'm not sure.

managed-bean in richfaces-core-impl ----------------------------------- Key: RF-10755 URL: https://issues.jboss.org/browse/RF-10755 Project: RichFaces Issue Type: Enhancement Security Level: Public(Everyone can see) Components: compatibility Affects Versions: 4.0.0.CR1 Environment: Richfaces 4.0.0 branch Reporter: Martin Kočí Fix For: 4.1.0.Final richfaces-core-impl contains three definitions of managed-beans: a4j a4jSkin richSkin By mistake one of our coders created CDI bean named "richSkin" and that caused malfunction of richfaces skinning. Suggestion: do not provide those beans but implement them as implicit object (similar like JSF implicit object "view" or "sessionScope") There is SkinPropertiesELResolver already, all what needs to be done is define new implicit object "richSkin" and handle it there in similar way how JSF impl handle implicit objects. a4jSkin managed-bean seems to be obsolete, about a4j(VerionBean) I'm not sure.