[JBoss JIRA] (RF-11695) showcase - deploying on JBoss AS 7.1.0-SNAPSHOT trows error: JMSInitializer was not correctly initialized
by Juraj Huska (Created) (JIRA)
showcase - deploying on JBoss AS 7.1.0-SNAPSHOT trows error: JMSInitializer was not correctly initialized
---------------------------------------------------------------------------------------------------------
Key: RF-11695
URL: https://issues.jboss.org/browse/RF-11695
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: build/distribution, showcase
Affects Versions: 4.1.0.CR1
Environment: richfaces-showcase-4.1.0-CR1
container: JBoss AS 7.1.0.Alpha2-SNAPSHOT
Reporter: Juraj Huska
Deploying on latest *JBoss AS 7.1.0-SNAPSHOT*
(last successful artifact from Nov 15, 2011 12:41:27 PM )
causes *critical error during deployment* with this stacktrace:
{code}
18:58:34,893 ERROR [org.jboss.remoting.remote] (Remoting "management-client" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: No more authentication mechanisms to try
18:58:34,905 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-3) Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:376) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:225) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
Caused by: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized
at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:66) [classes:]
at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2129) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2105) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:300) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) [jboss-as-weld-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:601) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:370) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
... 9 more
Caused by: java.net.ConnectException: Could not connect to remote://127.0.0.1:9999. Make sure the server is running.
at org.jboss.as.protocol.ProtocolChannelClient.connect(ProtocolChannelClient.java:113) [jboss-as-protocol-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:123) [jboss-as-protocol-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.protocol.mgmt.ManagementRequest$1.run(ManagementRequest.java:101) [jboss-as-protocol-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
... 3 more
Caused by: javax.security.sasl.SaslException: No more authentication mechanisms to try
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:300) [jboss-remoting-3.2.0.CR2.jar:3.2.0.CR2]
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:199) [jboss-remoting-3.2.0.CR2.jar:3.2.0.CR2]
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.0.CR3.jar:3.0.0.CR3]
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:179) [xnio-api-3.0.0.CR3.jar:3.0.0.CR3]
at org.xnio.channels.TranslatingSuspendableChannel$2.handleEvent(TranslatingSuspendableChannel.java:100) [xnio-api-3.0.0.CR3.jar:3.0.0.CR3]
at org.xnio.channels.TranslatingSuspendableChannel$2.handleEvent(TranslatingSuspendableChannel.java:98) [xnio-api-3.0.0.CR3.jar:3.0.0.CR3]
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.0.CR3.jar:3.0.0.CR3]
at org.xnio.nio.NioHandle.run(NioHandle.java:90)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:184)
at ...asynchronous invocation...(Unknown Source)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:273) [jboss-remoting-3.2.0.CR2.jar:3.2.0.CR2]
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:336) [jboss-remoting-3.2.0.CR2.jar:3.2.0.CR2]
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:324) [jboss-remoting-3.2.0.CR2.jar:3.2.0.CR2]
at org.jboss.as.protocol.ProtocolChannelClient.connect(ProtocolChannelClient.java:107) [jboss-as-protocol-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
... 5 more
{code}
--
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
12 years, 10 months
[JBoss JIRA] (RF-11720) rich:tab double click to change tab (inside h:panelGroup with initally render property set to false)
by Nicola Nick (Created) (JIRA)
rich:tab double click to change tab (inside h:panelGroup with initally render property set to false)
----------------------------------------------------------------------------------------------------
Key: RF-11720
URL: https://issues.jboss.org/browse/RF-11720
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.Milestone4
Environment: Tomcat 6.0.16
Reporter: Nicola Nick
Hi, I have the following rich:tabPanel that is rendered when the customerShow variable is true.
The issue appear when the the variable is initally to False and then is set to True.
The strange behavior is that at the first change of tab i have to click two times to do it.
This behavior doesn't appear if the customerShow variable is initally true.
THIS IS THE CODE:
<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html" xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich" xmlns:sf="http://www.springframework.org/tags/faces">
<div class="container">
<h:panelGroup rendered="#{customerShow}" layout="block">
<h:form>
<rich:tabPanel id="customerTabPanel" switchType="ajax" headerPosition="top"
headerLocation="center">
<rich:tab id="customerList" header="› Search">
</rich:tab>
<rich:tab id="customerDetail" header="› Customer">
</rich:tab>
<rich:tab id="vehicleDetail" header="› Vehicle">
</rich:tab>
<rich:tab id="subscriptionDetail" header="› Subscription">
</rich:tab>
<rich:tab id="history" header="› History">
</rich:tab>
</rich:tabPanel>
</h:form>
</h:panelGroup>
</div>
</ui:composition>
LAYOUT:
<h:body id="top">
<div id="body" class="wrapper">
<h:panelGroup id="content-area" layout="block">
<ui:insert name="content">
<ui:include src="/WEB-INF/sections/contentEmpty.xhtml" />
</ui:insert>
</h:panelGroup>
</div>
</h:body>
And finally those are the two POST responses:
FIRST CLICK:
<?xml version='1.0' encoding='UTF-8'?>
<partial-response><changes><update id="javax.faces.ViewState"><![CDATA[e10s1]]></update></changes></partial-response>
SECOND CLICK:
<?xml version='1.0' encoding='UTF-8'?>
<partial-response><changes><update id="j_idt246:customerDetail"><![CDATA[<div id="j_idt246:customerDetail" class="rf-tab"><div class="rf-tab-cnt" id="j_idt246:customerDetail:content"></div><script type="text/javascript">new RichFaces.ui.Tab("j_idt246:customerDetail",{"index":1,"leave":null,"togglePanelId":"j_idt246:customerTabPanel","switchMode":"ajax","name":"customerDetail","enter":null,"disabled":false} )</script></div>]]></update><update id="javax.faces.ViewState"><![CDATA[e10s1]]></update></changes><extension id="org.richfaces.extension"><complete>RichFaces.$('j_idt246:customerTabPanel').onCompleteHandler('customerDetail');;</complete></extension></partial-response>
--
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
12 years, 10 months