August 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4389) Decorator message is not being shown inside seam message.

by Roman Mandeleil (JIRA)

Decorator message is not being shown inside seam message. --------------------------------------------------------- Key: JBSEAM-4389 URL: https://jira.jboss.org/jira/browse/JBSEAM-4389 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA, 2.2.0.CR1, 2.1.2.GA Environment: Windows, JBoss 4.2.3 Reporter: Roman Mandeleil Priority: Critical I am strugling very strange problem with decorate tag for a simple input . It seams that decorate template been parsed right but I can't make the seam:message that decorates the input to be affected by the errors. The interesting part is that if I put rich:messages tag on the page I see the right messages for that input. Here is the sample I cooked to reveal the problem: http://rapidshare.com/files/270297734/sample-app.zip it is an imitation of a comments system there is a comment class that represents the model of comment to be validated and saved in the database, SubmitNewCommentAction should save the comment in the DB when submit button is hit. On the index.xhtml page there is a name input field that is decorated, it is there to reflect the problem. Thanks in advance. Roman -- 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

15 years, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4396) Dynamically disable/enable global transactions

by asookazian (JIRA)

Dynamically disable/enable global transactions ---------------------------------------------- Key: JBSEAM-4396 URL: https://jira.jboss.org/jira/browse/JBSEAM-4396 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.2.0.GA Environment: n/a Reporter: asookazian Need functionality to dynamically enable or disable global transactions. Currently, it's possible to enable or disable (globally, or once for the entire app) in components.xml like this: <core:init transaction-management-enabled="false"/> Would it be possible to enable/disable per JSF page or per Seam component in pages.xml, etc.? Please see this thread: http://seamframework.org/Community/UsageOfUTTransaction to find out what use case requires this functionality. As per SiA book, turning off global tx's is generally not a good idea due to the effects of lazy loading in auto-commit mode (multiple tx's, etc.) But for certain tx management requirements when not using EJB3 CMT (i.e. Seam @Transactional or BMT), I had to turn off global tx's so there was no active tx when the component's action method was executed. -- 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

15 years, 4 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4212) JMS feature does not work after cluster failover

by Scott McNab (JIRA)

JMS feature does not work after cluster failover ------------------------------------------------ Key: JBSEAM-4212 URL: https://jira.jboss.org/jira/browse/JBSEAM-4212 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.2.SP1 Environment: JBoss 4.2.3.GA (clustered) Reporter: Scott McNab Assignee: Shane Bryzak We have configured Seam to work in a clustered environment by using a custom JMSConnectionProvider that fetches the UIL2ConnectionFactory from HA-JNDI. This arrangements works perfectly fine while both servers are up - i.e. a web client connected to the slave server will correctly receive Asynchronous Seam notifications from a JMS topic hosted on the master server. However, when the master server fails over to the slave, the Seam JMS support on the slave stops working. We get the following exception: 06-02 12:52:45.405 ERROR [seam.remoting.messaging.SubscriptionRegistry] (http-192.168.100.140-80-2:) org.jboss.mq.SpyJMSException: Cannot get the Topic from the provider; - nested throwable: (java.io.IOE xception: Client is not connected) 06-02 12:52:45.406 ERROR [jboss.seam.remoting.Remoting] (http-192.168.100.140-80-2:) Error java.lang.NullPointerException at org.jboss.seam.remoting.messaging.SubscriptionRequest.marshal(SubscriptionRequest.java:31) at org.jboss.seam.remoting.SubscriptionHandler.marshalResponse(SubscriptionHandler.java:107) at org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:96) at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) at org.jboss.seam.servlet.SeamResourceServlet.doGet(SeamResourceServlet.java:75) at org.jboss.seam.servlet.SeamResourceServlet.doPost(SeamResourceServlet.java:92) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.service.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:97) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn.invoke(ClusteredSingleSignOn.java:677) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) We have diagnosed this issue and have developed a fix. The problem is as follows: - once failover occurs, the topicConnection field in the SubscriptionRegistry object becomes invalid, as the connection to the master server has died. - every subsequent call to SubscriptionRegistry.subscribe() will fail with SpyJMSException: Cannot get the Topic from the provider; Client is not connected. - even if the master server recovers, this connection is dead and all Seam JMS subscriptions will no longer work. The fix is to catch the Exception and retry with a new topicConnection if a subscribe request fails. The following patch on jboss-seam-2.0.2.SP1/src/remoting/org/jboss/seam/remoting/messaging/SubscriptionRegistry.java works for us: Index: SubscriptionRegistry.java =================================================================== --- SubscriptionRegistry.java (revision 5528) +++ SubscriptionRegistry.java (working copy) @@ -139,7 +139,21 @@ RemoteSubscriber sub = new RemoteSubscriber(UUID.randomUUID().toString(), topicName); try { - sub.subscribe(getTopicConnection()); + try { + sub.subscribe(getTopicConnection()); + } catch (Exception e) { + // If we failed during the first attempt, we might have a dead JMS connection. + // Clear the topic connection and try again. + if (topicConnection != null) { + try { + topicConnection.close(); + } catch (Exception e1) { + // Ignore any exception during the close, since this connection is probably dead anyway + } + } + topicConnection = null; + sub.subscribe(getTopicConnection()); + } subscriptions.put(sub.getToken(), sub); // Save the client's token in their session context -- 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

15 years, 4 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4394) HTML <button> for SEAM

by Christoph B (JIRA)

HTML <button> for SEAM ---------------------- Key: JBSEAM-4394 URL: https://jira.jboss.org/jira/browse/JBSEAM-4394 Project: Seam Issue Type: Feature Request Components: JSF Integration Affects Versions: 2.2.0.GA Environment: jboss 5.1.0.GA Reporter: Christoph B I need SEAM to generate a HTML <button> element for me. Right now there does not seem to be such a possibility. I Imagine the following syntax <s:button id="update" value="Update" action="#{somebean.update}"> <img src="update.png" /> <span> Update it!</span> </s:button> Right now SEAM does not support embedding HTML (or JSF) into the <s:button> as it gets rendered to '<input type="button">' and not '<button type="button">'. -- 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

15 years, 4 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4392) Introduce a tag e:columns

by Marcos Ribes (JIRA)

Introduce a tag e:columns ------------------------- Key: JBSEAM-4392 URL: https://jira.jboss.org/jira/browse/JBSEAM-4392 Project: Seam Issue Type: Feature Request Components: Excel Reporter: Marcos Ribes If you have a unknow number of columns, theres no way to create a excel using jboss-excel. A solution is create a tag e:columns like a existent rich:columns. Here's an example of what I'd like to do: <e:workbook> <e:worksheet name="cars"> <e:columns value="#{dataTableScrollerBean.columns}" var="columns" index="ind"> <f:facet name="header"> <e:cell value="#{columns.header}"/> </f:facet> <e:cell value="#{model[ind].model}"/> </e:columns> </e:worksheet> <e:workbook> -- 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

15 years, 4 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4390) Support for JDK 1.6 (JDK 1.5 EOL is Oct 2009)

by Eric Link (JIRA)

Support for JDK 1.6 (JDK 1.5 EOL is Oct 2009) --------------------------------------------- Key: JBSEAM-4390 URL: https://jira.jboss.org/jira/browse/JBSEAM-4390 Project: Seam Issue Type: Quality Risk Affects Versions: 2.2.0.GA Environment: jboss-5.1.0.GA-jdk6 jboss-seam-2.2.0.GA. Reporter: Eric Link I checked the Seam JDK 6.0 page but no status updates on JDK 6.0 since Pete commented in Jan 08: http://seamframework.org/Documentation/DoesSeamWorkWithJDK60 JDK 5 has EOL coming in october so we'd like some official jboss info on support for AS+SEAM using jdk 1.6. We want deploy our seam app w/ jdk1.6 if possible, and things appear to run ok w/ jboss-5.1.0.GA-jdk6 and jboss-seam-2.2.0.GA. From: http://java.sun.com/javase/downloads/index_jdk5.jsp J2SE 5.0 is in its Java Technology End of Life (EOL) transition period. The EOL transition period began April 8th, 2008 and will complete October 30th, 2009, when J2SE 5.0 will have reached its End of Service Life (EOSL). -- 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

15 years, 4 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2921) Wiki permission checking sometimes results in "no file extension in servlet path"

by Christian Bauer (JIRA)

Wiki permission checking sometimes results in "no file extension in servlet path" --------------------------------------------------------------------------------- Key: JBSEAM-2921 URL: http://jira.jboss.com/jira/browse/JBSEAM-2921 Project: Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer I've seen this in the live log sometimes, couldn't reproduce it until now: Trigger a @Factory method on a page, the component that has the @Factory method has @Create public void create() { if (!Identity.instance().hasPermission("User", "isAdmin", (User)Component.getInstance("currentUser") ) ) { throw new AuthorizationException("You don't have permission for this operation"); } } This is from AdminHome.java. So for example try to access 'systemPreferenceEntities' variable without being an admin. This will result in a permission exception which is hidden and obscured by another exception in the exception handling phase: >>> 12:45:02,053 DEBUG [org.jboss.seam.contexts.FacesLifecycle] >>> Begin exception recovery >>> 12:45:02,055 DEBUG [org.jboss.seam.core.Manager] No stored conversation, or concurrent call to the stored conversation >>> 12:45:02,059 DEBUG [org.jboss.seam.exception.Exceptions] reading exception mappings from /WEB-INF/pages.xml >>> 12:45:02,064 DEBUG [org.jboss.seam.faces.Navigator] redirecting to: /wiki.xhtml >>> 12:45:02,064 DEBUG [org.jboss.seam.contexts.FacesLifecycle] After render response, destroying contexts >>> 12:45:02,066 DEBUG [org.jboss.seam.contexts.FacesLifecycle] <<< End JSF request for /wiki/ >>> 12:45:02,066 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/wiki].[default]] Servlet.service() for servlet default threw exception java.lang.IllegalArgumentException: no file extension in servlet path: / at org.jboss.seam.mock.MockViewHandler.getActionURL(MockViewHandler.java:44) at org.jboss.seam.jsf.SeamViewHandler.getActionURL(SeamViewHandler.java:74) at org.jboss.seam.faces.FacesManager.redirect(FacesManager.java:162) at org.jboss.seam.faces.Navigator.redirect(Navigator.java:50) at org.jboss.seam.exception.RedirectHandler.handle(RedirectHandler.java:51) at org.jboss.seam.exception.Exceptions.handle(Exceptions.java:76) at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:613) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4360) Prefix bug in Seam integration of RESTEasy

by Stephane Epardaud (JIRA)

Prefix bug in Seam integration of RESTEasy ------------------------------------------ Key: JBSEAM-4360 URL: https://jira.jboss.org/jira/browse/JBSEAM-4360 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.GA Reporter: Stephane Epardaud The default way Seam integrates with RESTEasy is by mapping REST resources to the default path "/app/seam/resource/rest/..." but there is something fishy going on since calling uriInfo.getBaseUriBuilder().path(MyResourceClass.class, "getUser").build("2") on this resource: @Name("RESTUsers") @Path("/") public class MyResourceClass { @GET @Path("/user/{userId}") public Response getUser(@PathParam("userId") String identifier) {...} } Produces this URI: http://localhost/app/user/2 instead of http://localhost/app/seam/resource/rest/user/2 Funny thing is that the required path info is stripped from the URI in org.jboss.seam.resteasy.ResteasyResourceAdapter.extractUriInfo on purpose (there is a comment about it and a setting to disable this that breaks the application since it requires this path to be written in @Path annotations for some weird reason). I think the proper way to do it is to keep this path since it is required for generating inter-resource URIs and make sure RESTEasy uses it as a prefix when registering REST resource URIs. This should be done when registering resources by calling getDispatcher().getRegistry().setRootPath("/seam/resource/rest") so that @Path("/user/{userId}") will match the prefixed URIs without having to hard-code the prefix in there. At the moment it's quite hard to generate responses for HTTP CREATED. -- 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

15 years, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4387) Allow Pages Login Required to be set with an EL Expression

by John Gilbert (JIRA)

Allow Pages Login Required to be set with an EL Expression ---------------------------------------------------------- Key: JBSEAM-4387 URL: https://jira.jboss.org/jira/browse/JBSEAM-4387 Project: Seam Issue Type: Feature Request Components: Core Reporter: John Gilbert Currently in pages.xml, login-required must be either true or false. Using an expression like this would be more flexible. <page view-id="/MyPage.xhtml" login-required="#{myComponent.loginRequired}" /> -- 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

15 years, 4 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4351) Setting Conversation Timeout Gets Overwritten by FacesManager

by arin saghatelian (JIRA)

Setting Conversation Timeout Gets Overwritten by FacesManager ------------------------------------------------------------- Key: JBSEAM-4351 URL: https://jira.jboss.org/jira/browse/JBSEAM-4351 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.GA Environment: Mac OS X 10.5.7 Reporter: arin saghatelian When I try to extend the conversation timeout from the Conversation class, it is overwritten when the prepareBackswitch class is called in the FacesManager class. It sets the timeout to the page timeout value without checking to see if the timeout was already set. This seems to be a bug and so it prevents us from extending the conversation timeout. -- 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

15 years, 4 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2009