January 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4648) s:defaultAction blocks new lines in <textArea>

by Adrian Mitev (JIRA)

s:defaultAction blocks new lines in <textArea> ---------------------------------------------- Key: JBSEAM-4648 URL: https://jira.jboss.org/jira/browse/JBSEAM-4648 Project: Seam Issue Type: Bug Components: JSF Controls Reporter: Adrian Mitev s:defaultAction shouldn't work if the enter button is presses inside textarea element. To fix the issue wrap the javascript that s:convertEntity generates inside this code: var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() != 'textarea') { <original javascript here> } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
9
0 / 0

[JBoss JIRA] Created: (JBSEAM-4830) Seam version is not displayed on JBoss AS 7

by Marek Novotny (JIRA)

Seam version is not displayed on JBoss AS 7 ------------------------------------------- Key: JBSEAM-4830 URL: https://issues.jboss.org/browse/JBSEAM-4830 Project: Seam 2 Issue Type: Bug Components: Core Affects Versions: 2.2.2.Final Reporter: Marek Novotny Assignee: Marek Novotny Fix For: 2.3.0.BETA1 While testing seam examples on JBoss AS 7, i noticed that Seam version is displayed as: INFO [javax.servlet.ServletContextListener] (MSC service thread 1-1) Welcome to Seam null This should give a version from jboss-seam.jar META-INF/Manifest.MF file like: INFO [javax.servlet.ServletContextListener] (MSC service thread 1-1) Welcome to Seam 2.3.0-SNAPSHOT -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
4
0 / 0

[JBoss JIRA] (SEAMJMS-65) Ingress JMS bridging results in endless invocations of observer method

by Thorsten Kunz (Created) (JIRA)

Ingress JMS bridging results in endless invocations of observer method ---------------------------------------------------------------------- Key: SEAMJMS-65 URL: https://issues.jboss.org/browse/SEAMJMS-65 Project: Seam JMS Issue Type: Bug Components: Event Bridging Affects Versions: 3.1.0.CR1 Environment: JBAS 7.1.0.Beta1b Reporter: Thorsten Kunz I have defined this interface method: @Outbound public void routeStringToQueue(@Observes String string, @JmsDestination(jndiName = "queue/pegasusMessage") Queue queue); @Inbound public void routeStringsFromQueue(@Observes String string, @JmsDestination(jndiName = "queue/pegasusMessage") Queue queue); Then create this observer method: public void inboundMessageTest(@Observes @Inbound String message) { ... } Once a String type event is fired this is being logged: 13:59:26,095 INFO [org.jboss.seam.jms.MessageManagerImpl] (http-localhost-127.0.0.1-8080-1) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT 13:59:26,108 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message 13:59:26,110 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT 13:59:26,337 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message 13:59:26,339 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT 13:59:26,386 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message 13:59:26,387 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT 13:59:26,403 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message 13:59:26,404 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT 13:59:26,403 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message 13:59:26,404 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT [ ... and so on ... ] It works just fine if I replace the observer method with a regular MDB for this destination. -- 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

13 years, 11 months

7
10
0 / 0

[JBoss JIRA] Created: (SEAMSOCIAL-19) WebClient example NPE in MultiServicesManagerImpl.connectCurrentService on facebook callback

by Marek Schmidt (JIRA)

WebClient example NPE in MultiServicesManagerImpl.connectCurrentService on facebook callback -------------------------------------------------------------------------------------------- Key: SEAMSOCIAL-19 URL: https://issues.jboss.org/browse/SEAMSOCIAL-19 Project: Seam Social Issue Type: Bug Components: Facebook Environment: jboss-as-7.1.0.Alpha1-SNAPSHOT, 3.0.0-SNAPSHOT revision 54570b8e1267b00b76c60b0345fe79d5d2b175ef Reporter: Marek Schmidt Assignee: Antoine Sabot-Durand Sometimes (but not always, but happened more than once... ) after a redirect from Facebook login, I see the following exception instead of the webclient callback page: I could not reproduce it by aggresive clicking after it happened, so I suspect it may occur after some session times out somewhere... also, I am not sure it is facebook-specific or not. {noformat} 15:52:38,299 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/social-web-client].[Faces Servlet]] (http--127.0.0.1-8080-5) Servlet.service() for servlet Faces Servlet threw exception: java.lang.NullPointerException at org.jboss.seam.social.core.MultiServicesManagerImpl.connectCurrentService(MultiServicesManagerImpl.java:118) [seam-social-3.0.0-SNAPSHOT.jar:] at org.jboss.seam.social.examples.webclient.SocialClient.connectCurrentService(SocialClient.java:103) [classes:] at org.jboss.seam.social.examples.webclient.SocialClient$Proxy$_$$_WeldClientProxy.connectCurrentService(SocialClient$Proxy$_$$_WeldClientProxy.java) [classes:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24] at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4] at com.sun.faces.facelets.tag.jsf.core.DeclarativeSystemEventListener.processEvent(EventHandler.java:128) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4] at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2477) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final] at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final] at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2102) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4] at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2050) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:287) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:245) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4] at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:293) [jboss-as-weld-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:108) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4] at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:313) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

6
6
0 / 0

[JBoss JIRA] (JBSEAM-4891) JSF2 Booking example validation doesn't work

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-4891: ------------------------------------- Summary: JSF2 Booking example validation doesn't work Key: JBSEAM-4891 URL: https://issues.jboss.org/browse/JBSEAM-4891 Project: Seam 2 Issue Type: Bug Components: Examples Environment: Seam 2.3.0-SNAPSHOT r14271, JBoss AS 7.1.0.CR1b Reporter: Marek Schmidt Assignee: Marek Novotny Priority: Critical Fix For: 2.3.0.BETA1 Validation doesn't work in the examples-ee6/booking example. -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] (SEAMINTL-72) Seam 3.1.0.Beta3 Bug - Messages NOT displayed

by Luca Cavagnoli (Created) (JIRA)

Seam 3.1.0.Beta3 Bug - Messages NOT displayed --------------------------------------------- Key: SEAMINTL-72 URL: https://issues.jboss.org/browse/SEAMINTL-72 Project: Seam International Issue Type: Bug Components: Messages Affects Versions: 3.1.0.Beta3 Environment: JBoss AS 7.0.1.Final Seam 3.1.0.Beta3 Reporter: Luca Cavagnoli Assignee: Ken Finnigan I opened the security-idmconsole example included in 3.1.0.Beta3 I created a controller that has the following: @Inject org.jboss.seam.international.status.Messages messages; public void save() { messages.info("Here is an info message!"); messages.warn("Here is a warning message!"); messages.error("Here is an error message!"); } I deployed the project in JBoss AS 7.0.1.Final The messages are NOT being displayed in the page. If I remove the <h:messages> component from the page, I do NOT even get the "WARNING: FacesMessage(s) have been enqueued, but may not have been displayed." warning. -- 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

13 years, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4637) Seam does not work with JSF 2.0 faces-config.xml

by Ryan Nideffer (JIRA)

Seam does not work with JSF 2.0 faces-config.xml ------------------------------------------------ Key: JBSEAM-4637 URL: https://jira.jboss.org/jira/browse/JBSEAM-4637 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.2.1.CR1 Reporter: Ryan Nideffer I am attempting to use JSF 2.0 in my Seam application for, among other benefits, composite components. I am able to upgrade the jsf-api.jar and jsf-impl.jar, remove jsf-facelets.jar and my application functions fine, however I am still running in JSF 1.2 mode due to this faces-config.xml: <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"> <view-handler>com.sun.facelets.FaceletViewHandler</view-handler> According to thread comments from a Mojarra developer and the Release Notes for Mojarra 2, all thats needed is to remove the view-handler and reference v2.0 in faces-config. http://forums.java.net/jive/message.jspa?messageID=373539 https://javaserverfaces.dev.java.net/nonav/rlnotes/2.0.1/releasenotes.html As soon as I do this though, I get the following exception when my application is deployed: 2010-04-16 11:24:18,249 INFO [javax.enterprise.resource.webcontainer.jsf.config] (Thread-2) Unsanitized stacktrace from failed start... javax.faces.view.facelets.FaceletException: Must have a Constructor that takes in a ComponentConfig at com.sun.faces.facelets.tag.AbstractTagLibrary$UserComponentHandlerFactory.<init>(AbstractTagLibrary.java:289) ... Caused by: java.lang.NoSuchMethodException: org.jboss.seam.ui.handler.CommandButtonParameterComponentHandler.<init>(javax.faces.view.facelets.ComponentConfig) at java.lang.Class.getConstructor0(Class.java:2706) According to Dan Allen, Seam 2 and JSF 2 work together beautifully: http://seamframework.org/Documentation/DoesSeamWorkWithJSF2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
17
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-59) Implement EntityHome from Seam 2

by Sheng Gu (JIRA)

Implement EntityHome from Seam 2 -------------------------------- Key: SEAMPERSIST-59 URL: https://issues.jboss.org/browse/SEAMPERSIST-59 Project: Seam Persistence Issue Type: Feature Request Affects Versions: 3.0.0.Final Environment: Upgrading to Seam 3 Reporter: Sheng Gu Fix For: 3.0.1.CR1 Migrating Seam 2 to Seam 3 is very hard to find a replacement for Seam 2's EntityHome. Also it looks that EntityHome is very important for Seam persist. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
8
0 / 0

[JBoss JIRA] (JBSEAM-4895) Add Seam-Version into <jar>/META-INF/Manifest.mf as JBoss Tools requires it

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-4895: ------------------------------------- Summary: Add Seam-Version into <jar>/META-INF/Manifest.mf as JBoss Tools requires it Key: JBSEAM-4895 URL: https://issues.jboss.org/browse/JBSEAM-4895 Project: Seam 2 Issue Type: Bug Components: Build Affects Versions: 2.3.0.ALPHA Reporter: Marek Novotny Assignee: Marek Novotny Fix For: 2.3.0.BETA1 JBoss Tools Seam2 relies on Manifest entry Seam-Version: to recognize Seam Runtime properly. Without it can't recognize Seam 2.3 - JBIDE-10749 -- 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

13 years, 11 months

1
3
0 / 0

[JBoss JIRA] (JBSEAM-4887) Create thread safe org.jboss.el.util.ReferenceCache in jbos-el.jar

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-4887: ------------------------------------- Summary: Create thread safe org.jboss.el.util.ReferenceCache in jbos-el.jar Key: JBSEAM-4887 URL: https://issues.jboss.org/browse/JBSEAM-4887 Project: Seam 2 Issue Type: Sub-task Components: EL Affects Versions: 2.3.0.ALPHA Reporter: Marek Novotny Assignee: Marek Novotny Fix For: 2.3.0.BETA1 org.jboss.el.util.ReferenceCache.startMonitor is not thread safe. Fix it! -- 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

13 years, 11 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2012