[JBoss JIRA] Created: (RF-10958) Unnecessary attributes in message component
by Jan Jamrich (JIRA)
Unnecessary attributes in message component
-------------------------------------------
Key: RF-10958
URL: https://issues.jboss.org/browse/RF-10958
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: cdk, component
Affects Versions: 4.1.0.Milestone1
Environment: RichFaces 4.1.0-SNAPSHOT r.22442
Metamer 4.1.0-SNAPSHOT r.22441
Mojarra 2.0.4-b09
Apache Tomcat 6.0.29
Java(TM) SE Runtime Environment 1.6.0_19-b04 @ Linux
Chrome 12.0.718.0 @ Linux i686
Reporter: Jan Jamrich
There are some unnecessary attributes in faces-config.xml for rich:message component, such as: rendererType, rendersChildren. childCount, children, family, facets.
These attributes doesn't occurs in rich:messages component as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] Created: (RF-11252) Editor - submitting by a4j:commandButton (MyFaces)
by Jan Papousek (JIRA)
Editor - submitting by a4j:commandButton (MyFaces)
--------------------------------------------------
Key: RF-11252
URL: https://issues.jboss.org/browse/RF-11252
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.Milestone1
Environment: RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc
Metamer 4.1.0-SNAPSHOT r.22610
Apache MyFaces JSF-2.1 Core Impl 2.1.1
Apache Tomcat 6.0.32
OpenJDK Runtime Environment 1.6.0_22-b22 @Linux
Internet Explorer 8.0 @ Win32
RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc
Metamer 4.1.0-SNAPSHOT r.22610
Apache MyFaces JSF-2.1 Core Impl 2.1.1
Apache Tomcat 6.0.32
OpenJDK Runtime Environment 1.6.0_22-b22 @Linux
Firefox 5.0 @ Linux x86_64
Reporter: Jan Papousek
When the rich:editor is submitted by a4j:commandButton which renders an output area, the output area stays empty. This can be reproduced in Metamer - faces/components/richEditor/simple.xhtml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] (RF-12303) Customer topiclistener not working on richfaces push component of verion 4.2.2-Final and older
by Daniel Yang (JIRA)
Daniel Yang created RF-12303:
--------------------------------
Summary: Customer topiclistener not working on richfaces push component of verion 4.2.2-Final and older
Key: RF-12303
URL: https://issues.jboss.org/browse/RF-12303
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core, component-push/poll
Affects Versions: 4.2.2.Final
Environment: No deponds on what environment.
Reporter: Daniel Yang
See description here:
https://community.jboss.org/message/736651#736651
Copy it again:
I use it like following lines:
TopicsContext topicsContext = TopicsContext.lookup();
Topic topic = topicsContext.getOrCreateTopic(new TopicKey("test"));
topic.setMessageDataSerializer(DefaultMessageDataSerializer.instance());
topic.addTopicListener(new SessionTopicListener2() {
@Override
public void processPreSubscriptionEvent(SessionPreSubscriptionEvent event) throws SubscriptionFailureException {
//TODO
}
@Override
public void processSubscriptionEvent(SessionSubscriptionEvent event) {
//TODO
}
@Override
public void processUnsubscriptionEvent(SessionUnsubscriptionEvent event) {
//TODO
}
});
I noted that listeners in TopicImpl are all the SessionTopicListener2 type, because add method is:
public void addTopicListener(TopicListener topicListener) {
TopicListener listener = topicListener;
if (listener instanceof SessionTopicListener) {
listener = new SessionTopicListenerWrapper((SessionTopicListener) listener);
}
listeners.add(listener);
}
All SessionTopicListeners are wrapped to type SessionTopicListener2, and when event publish in TopicImpl, it check it if it is appropriate listener like this:
public void publishEvent(TopicEvent event) {
for (TopicListener listener : listeners) {
if (event.isAppropriateListener(listener)) {
try {
event.invokeListener(listener);
} catch (Exception e) {
logError(e);
}
}
}
}
But event type SessionPreSubscriptionEvent, SessionSubscriptionEvent or SessionUnsubscriptionEvent does not override the mothed isAppropriateListener, so when checking, it use the method of its parent SessionTopicEvent, its parent method is like this:
@Override
public boolean isAppropriateListener(EventListener listener) {
return (listener instanceof SessionTopicListener);
}
Then it always returns false for above three SessionTopicEvent , and the custom listeners will never be called. I think it may be changed from " return (listener instanceof SessionTopicListener);" to return (listener instanceof SessionTopicListener2); or override it in seperator implement of type SessionTopicEvent .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months