[JBoss JIRA] Created: (RF-10883) PUSH doesn't work properly on Glassfish 3.1 (JMS issue I think)
by Pablo Martinez (JIRA)
PUSH doesn't work properly on Glassfish 3.1 (JMS issue I think)
---------------------------------------------------------------
Key: RF-10883
URL: https://issues.jboss.org/browse/RF-10883
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Final
Environment: Glassfish 3.1
Reporter: Pablo Martinez
When trying to make this PUSH example to work (http://in.relation.to/Bloggers/GettingStartedWithRichFaces40Push) on glassfish 3.1, I'm getting this error:
javax.jms.JMSException: MQJMSRA_DC2001: Unsupported:setClientID():inACC=false:connectionId=6046697373872048384
I think the problem comes from this line of code
{code:title=org.richfaces.application.push.impl.jms.MessagingContext.java|borderStyle=solid}
//TODO - review
try {
//durable subscription requires ClientID to be set
connection.setClientID(UUID.randomUUID().toString());
} catch (IllegalStateException e) {
//ignore - clientId has already been set
}
{code}
I builded richfaces 4 from scratch (only the richfaces-core-api and richfaces-core-impl), and the error disapeared. I setted the ClientId using the create-jms-resource on glassfish admin console.
Now, after that, the app "works" BUT, I don't get the notificaciones on the client side (web), I can only send messages to the irc and stuf, but don't see any change on the web app (I confirm this because I use another IRC client to see what happens).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (RF-11298) For attribute of messages does not work inside iteration components
by Pavol Pitonak (JIRA)
For attribute of messages does not work inside iteration components
-------------------------------------------------------------------
Key: RF-11298
URL: https://issues.jboss.org/browse/RF-11298
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-validators
Affects Versions: 4.1.0.Milestone1
Environment: RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc
Metamer 4.1.0-SNAPSHOT r.22616
Mojarra 2.1.2-FCS, Mojarra 2.0.4-b09
Apache Tomcat 6.0.32
OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
Chrome 13.0.782.112 @ Linux i686
Reporter: Pavol Pitonak
# deploy Metamer and open http://localhost:8080/metamer/faces/components/richMessages/csv.xhtml
# click button "Generate Msgs"
# verify that "Messages1 - with 'for' attribute" group contains two messages
# select iteration template, e.g. richList or a4jRepeat
# click button "Generate Msgs"
# verify that "Messages1 - with 'for' attribute" group contains two messages
result:
messages are not displayed inside rich:list
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (RF-11323) Autocomplete - selecting item from popup list
by Jan Papousek (JIRA)
Autocomplete - selecting item from popup list
---------------------------------------------
Key: RF-11323
URL: https://issues.jboss.org/browse/RF-11323
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-selects
Affects Versions: 4.1.0.Milestone1
Environment: RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc
Metamer 4.1.0-SNAPSHOT r.22637
Mojarra 2.1.2-FCS
Apache Tomcat 6.0.32
OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
Firefox 5.0 @ Linux x86_64
Reporter: Jan Papousek
# type something into the input
# popup list appears
# select an item from the list and confirm (with enter or mouse clicking)
# input stays empty
expected: input contains selected item
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (RF-11445) Client side validation should search for inputs inside a component
by José Freitas (JIRA)
Client side validation should search for inputs inside a component
------------------------------------------------------------------
Key: RF-11445
URL: https://issues.jboss.org/browse/RF-11445
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.Milestone2
Reporter: José Freitas
Client side validation should search for inputs inside a component to look for its value instead of collecting the value directly from the component, based on its id.
That would basically help csv system to work with composite components like seamfaces:inputcontainer and some primefaces components.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (RF-11409) showcase - aj4:push - all samples - when push is done then NullPointerException is thrown but the expected result of push is there
by Juraj Huska (JIRA)
showcase - aj4:push - all samples - when push is done then NullPointerException is thrown but the expected result of push is there
----------------------------------------------------------------------------------------------------------------------------------
Key: RF-11409
URL: https://issues.jboss.org/browse/RF-11409
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: showcase
Affects Versions: 4.1.0.Milestone2
Environment: richfaces-showcase-4.1.0.20110805-M1-jee6.war
container - Tomcat 7.0.20
browser - Chrome 13, IE 9, FF 3.6
Reporter: Juraj Huska
When push is done on all samples for aj4:push in showcase, then NullPointerException is thrown but the expected result of push is there. So the functionality is correct, only on the server console exception is thrown, with this stacktrace:
{code}
SEVERE: Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.environment.servlet.Listener
java.lang.NullPointerException
at org.jboss.weld.context.AbstractBoundContext.deactivate(AbstractBoundContext.java:81)
at org.jboss.weld.servlet.WeldListener.requestDestroyed(WeldListener.java:115)
at org.jboss.weld.servlet.api.helpers.ForwardingServletListener.requestDestroyed(ForwardingServletListener.java:42)
at org.apache.catalina.core.StandardContext.fireRequestDestroyEvent(StandardContext.java:6008)
at org.apache.catalina.connector.CoyoteAdapter.asyncDispatch(CoyoteAdapter.java:281)
at org.apache.coyote.http11.AbstractHttp11Processor.asyncDispatch(AbstractHttp11Processor.java:1220)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:511)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:302)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
This exception is thrown after each push execution, and it is not broken after first trowing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months